Transmission Control Protocol Packet Receive Failure—Billing (8) - Cisco BTS 10200 Troubleshooting Manual

Troubleshooting Billing Alarms
Transmission Control Protocol Packet Receive Failure—Billing (8)
The Transmission Control Protocol Packet Receive Failure alarm (major) indicates that a TCP packet
receive failure has occurred. The primary cause of the alarm is that the peer went down and the socket
closed. To correct the primary cause of the alarm, check the status of the peer and bring it up if it is down.
Database Connection Error—Billing (13)
The Database Connection Error alarm (critical) indicates that a database connection error has occurred.
The primary cause of the alarm is that the SQL server is down. To correct the primary cause of the alarm,
restart SQL server. If restarting SQL server does not correct the problem and clear the alarm, contact
Cisco TAC for technical support.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Prior to contacting Cisco TAC, collect the following additional information:
From the EMS UNIX prompt:
ps -ef
nodestat
From the CLI prompt:
status system
File Write Error—Billing (15)
The File Write Error alarm (major) indicates that a file write error has occurred. The primary cause of
the alarm is that a system error has occurred. The BTS 10200 system may be out of file descriptors. To
correct the primary cause of the alarm, contact Cisco TAC for technical support.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Prior to contacting Cisco TAC, collect the following information:
From the UNIX prompt:
sysdef -i
df -k
Call Data Block Send Failed—Billing (29)
The Call Data Block Send Failed alarm (major) indicates that a CDB send has failed. The primary cause
of the alarm is that a TCP send call has failed. To correct the primary cause of the alarm, check the port
number and address of blg and bmg processes in he platform.cfg file. The secondary cause of the alarm
is that both the EMS servers are down. To correct the secondary cause of the alarm, check if both EMS
servers are down. If both EMS servers are down, bring at least one EMS server up.
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
3-38
"Obtaining Documentation and Submitting a Service Request" section on page lvi
"Obtaining Documentation and Submitting a Service Request" section on page lvi
Chapter 3 Billing Troubleshooting
for
for
OL-8723-19