Billing Link Failure—Billing (37) - Cisco BTS 10200 Troubleshooting Manual

Troubleshooting Billing Alarms
Billing Link Failure—Billing (37)
The Billing Link Failure alarm (major) indicates that a link to the billing server has failed. The primary
cause of the alarm is that an interface cable may have been pulled. To correct the primary cause of the
alarm, restore cable connection. The secondary cause of the alarm is that an ifconfig down command
may have been executed on the interface. To correct the secondary cause of the alarm, execute an ifconfig
up command on the interface.
Event Message Log File Access Error—Billing (38)
The Event Message Log File Access Error alarm (major) indicates that an EM log file access 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 primary cause of the alarm, contact Cisco TAC. The secondary
cause of the alarm is that a system hard drive may be faulty. To verify the secondary cause of the alarm,
cause the BDMS to switch over to its mate node.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Event Message Encode Failure—Billing (40)
The Event Message Encode Failure alarm (minor) indicates that an EM encode failure has occurred. The
primary cause of the alarm is that there is a problem with the format of the data being sent to the RKS.
To correct the primary cause of the alarm, contact Cisco TAC.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Message Content Error—Billing (41)
The Message Content Error alarm (minor) indicates that a message content error has occurred. The
primary cause of the alarm is that there is a mismatch between what the sender populated in the message
and what the receiver expects. To correct the primary cause of the alarm, contact Cisco TAC.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Record Keeping System Switch Occurred—Billing (44)
The Record Keeping System Switch Occurred alarm (major) indicates that a RKS switch has occurred.
The primary cause of the alarm is that billing changed the destination RKS to which event messages are
transmitted. The change could have been triggered by a communication problem with an RKS, or by an
attempt to reestablish RKS communication. No further action is required to correct the primary cause of
the alarm.
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
3-40
"Obtaining Documentation and Submitting a Service Request" section on page lvi
"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
for
OL-8723-19