Table Of Contents
Billing Troubleshooting
Introduction
Billing Events and Alarms
BILLING (1)
BILLING (2)
BILLING (3)
BILLING (4)
BILLING (5)
BILLING (6)
BILLING (7)
BILLING (8)
BILLING (9)
BILLING (10)
BILLING (11)
BILLING (12)
BILLING (13)
BILLING (14)
BILLING (15)
BILLING (16)
BILLING (17)
BILLING (18)
BILLING (19)
BILLING (20)
BILLING (21)
BILLING (22)
BILLING (23)
BILLING (24)
BILLING (25)
BILLING (26)
BILLING (27)
BILLING (28)
BILLING (29)
BILLING (30)
BILLING (31)
BILLING (32)
BILLING (33)
BILLING (34)
BILLING (35)
BILLING (36)
BILLING (37)
BILLING (38)
BILLING (39)
BILLING (40)
BILLING (41)
BILLING (42)
BILLING (43)
BILLING (44)
BILLING (45)
BILLING (46)
BILLING (47)
BILLING (48)
BILLING (49)
BILLING (50)
BILLING (51)
BILLING (52)
BILLING (53)
BILLING (54)
BILLING (55)
BILLING (56)
BILLING (57)
BILLING (58)
BILLING (59)
Monitoring Billing Events
Test Report—Billing (1)
Billing Partition Disk Usage Minor Threshold Exceeded—Billing (2)
Billing Partition Disk Usage Major Threshold Exceeded—Billing (3)
Billing Partition Disk Usage Critical Threshold Exceeded—Billing (4)
Billing Partition Disk Usage Within Normal Range—Billing (5)
File Transfer Protocol/Secure File Transfer Protocol Transfer Failed—Billing (6)
Transmission Control Protocol Connection Error—Billing (7)
Transmission Control Protocol Packet Receive Failure—Billing (8)
Database Connection Error—Billing (13)
File Open Error—Billing (14)
File Write Error—Billing (15)
Call Data Block Send Failed—Billing (29)
Domain Name Mapping Failed—Billing (30)
Port not Specified—Billing (31)
Element Management System Address not Specified—Billing (32)
File Transfer Protocol/Secure File Transfer Protocol Parameters Invalid—Billing (33)
All Billing Links at Billing Server Down—Billing (35)
Billing Link Restored—Billing (36)
Billing Link Failure—Billing (37)
Event Message Log File Access Error—Billing (38)
Event Message Encode Failure—Billing (40)
Message Content Error—Billing (41)
Error Reading Provisioned Data-Using Default—Billing (42)
Record Keeping System Switch Occurred—Billing (44)
Event Message Log File Opened—Billing (45)
Event Message Log File Closed—Billing (46)
Record Keeping System Unreachable for One Hour—Billing (47)
Record Keeping System Unreachable for Three Hours—Billing (48)
Record Keeping System Unreachable for Five Hours—Billing (49)
Bulk Data Management System Stopped Generating New Billing File—Billing (52)
Event Message Disk Space 50 Percent Full—Billing (53)
Event Message Disk Space 70 Percent Full—Billing (54)
Event Message Disk Space 100 Percent Full—Billing (55)
Billing Data Corruption Detected—Billing (56)
Prepaid Subscriber Call Attempt Failed Because of Balance—Billing (57)
Signaling Prepaid Server Inaccessible—Billing (58)
Billing File Name Type Change in Command Line Interface is Inconsistent—Billing (59)
Troubleshooting Billing Alarms
Billing Partition Disk Usage Minor Threshold Exceeded—Billing (2)
Billing Partition Disk Usage Major Threshold Exceeded—Billing (3)
Billing Partition Disk Usage Critical Threshold Exceeded—Billing (4)
File Transfer Protocol/Secure File Transfer Protocol Transfer Failed—Billing (6)
Transmission Control Protocol Connection Error—Billing (7)
Transmission Control Protocol Packet Receive Failure—Billing (8)
Database Connection Error—Billing (13)
File Write Error—Billing (15)
Call Data Block Send Failed—Billing (29)
Domain Name Mapping Failed—Billing (30)
Port not Specified—Billing (31)
Element Management System Address not Specified—Billing (32)
File Transfer Protocol/Secure File Transfer Protocol Parameters Invalid—Billing (33)
All Billing Links at Billing Server Down—Billing (35)
Billing Link Failure—Billing (37)
Event Message Log File Access Error—Billing (38)
Event Message Encode Failure—Billing (40)
Message Content Error—Billing (41)
Record Keeping System Switch Occurred—Billing (44)
Event Message Log File Opened—Billing (45)
Event Message Log File Closed—Billing (46)
Record Keeping System Unreachable for One Hour—Billing (47)
Record Keeping System Unreachable for Three Hours—Billing (48)
Record Keeping System Unreachable for 5 Hours—Billing (49)
Bulk Data Management System Stopped Generating New Billing File—Billing (52)
Event Message Disk Space 50 Percent Full—Billing (53)
Event Message Disk Space 70 Percent Full—Billing (54)
Event Message Disk Space 100 Percent Full—Billing (55)
Billing Data Corruption Detected—Billing (56)
Signaling Prepaid Server Inaccessible—Billing (58)
Billing Troubleshooting
Revised: December 11, 2008, OL-8723-17
Introduction
This chapter provides the information needed to monitor and troubleshoot billing events and alarms. This chapter is divided into the following sections:
•
Billing Events and Alarms—Provides a brief overview of each billing event and alarm.
•Monitoring Billing Events—Provides the information needed to monitor and correct the billing events.
•Troubleshooting Billing Alarms—Provides the information needed to troubleshoot and correct the billing alarms.
Note The following billing records are created when a call is rejected due to overload conditions:
· SS7 termination cause code 42
· Cable signaling stop event cause code "resource unavailable"
Calls rejected by the signaling adapter will not generate a billing record.
Billing Events and Alarms
This section provides a brief overview of the billing events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 3-1 lists all of the billing events and alarms by severity.
Note Click the Billing message number in Table 3-1 to display information about the event or alarm.
BILLING (1)
For additional information, refer to the "Test Report—Billing (1)" section.
DESCRIPTION
|
Test Report
|
SEVERITY
|
Information (INFO)
|
THRESHOLD
|
10000
|
THROTTLE
|
0
|
BILLING (2)
To troubleshoot and correct the cause of the alarm, refer to the "Billing Partition Disk Usage Minor Threshold Exceeded—Billing (2)" section.
DESCRIPTION
|
Billing Partition Disk Usage Minor Threshold Exceeded
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Disk Usage Percentage-TWO_BYTES
|
PRIMARY
CAUSE
|
Call detail records are accumulating on the disk associated with the billing database in the Element Management System (EMS). This is because data is being written into the database faster than it is being read out of the database. The minor threshold (default value = 70%) has been exceeded.
|
PRIMARY
ACTION
|
Monitor this alarm. The read process should catch up to write process within a few minutes, and the alarm should not remain active.
|
SECONDARY
CAUSE
|
Some fluctuation in disk usage is to be expected as the call volume rises and falls during the day. Threshold crossings might step upward (from MINOR to MAJOR to CRITICAL) when there is a rapid increase in the call volume, and then step downward (CRITICAL to MAJOR to MINOR) when the call volume slows.
|
SECONDARY
ACTION
|
To monitor the alarm, use the subscribe alarm-report command. To obtain a summary, use the report alarm-summary command. Verify that type = billing is entered in the commands.
|
BILLING (3)
To troubleshoot and correct the cause of the alarm, refer to the "Billing Partition Disk Usage Major Threshold Exceeded—Billing (3)" section.
DESCRIPTION
|
Billing Partition Disk Usage Major Threshold Exceeded
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Disk Usage Percentage-TWO_BYTES
|
PRIMARY
CAUSE
|
Call detail records are accumulating on the disk associated with the billing database in the EMS. This is because data is being written into the database faster than it is being read out of the database. The major threshold (default value = 80%) has been exceeded.
|
PRIMARY
ACTION
|
Monitor this alarm. The read process should catch up to write process within a few minutes, and the alarm should not remain active.
|
SECONDARY
CAUSE
|
Some fluctuation in disk usage is to be expected as the call volume rises and falls during the day. Threshold crossings might step upward (from MINOR to MAJOR to CRITICAL) when there is a rapid increase in the call volume, and then step downward (CRITICAL to MAJOR to MINOR) when the call volume slows.
|
SECONDARY
ACTION
|
To monitor the alarm, use the subscribe alarm-report command. To obtain a summary, use the report alarm-summary command. Verify that type = billing is entered in the commands.
|
TERNARY
ACTION
|
If the alarm does not clear (or step down to a reduced level) in a few minutes, contact Cisco Technical Assistance Center (TAC) for assistance.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
Prior to contacting Cisco TAC, from the UNIX prompt collect df -k.
BILLING (4)
To troubleshoot and correct the cause of the alarm, refer to the "Billing Partition Disk Usage Critical Threshold Exceeded—Billing (4)" section.
DESCRIPTION
|
Billing Partition Disk Usage Critical Threshold Exceeded
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Disk Usage Percentage-TWO_BYTES
|
PRIMARY
CAUSE
|
Call detail records are accumulating on the disk associated with the billing database in the EMS. This is because data is being written into the database faster than it is being read out of the database. The major threshold (default value = 90%) has been exceeded.
|
PRIMARY
ACTION
|
Monitor this alarm. The read process should catch up to write process within a few minutes, and the alarm should not remain active.
|
SECONDARY
CAUSE
|
Some fluctuation in disk usage is to be expected as the call volume rises and falls during the day. Threshold crossings might step upward (from MINOR to MAJOR to CRITICAL) when there is a rapid increase in the call volume, and then step downward (CRITICAL to MAJOR to MINOR) when the call volume slows.
|
SECONDARY
ACTION
|
To monitor the alarm, use the subscribe alarm-report command. To obtain a summary, use the report alarm-summary command. Verify that type = billing is entered in these commands.
|
TERNARY
ACTION
|
If the alarm does not clear (or step down to a reduced level) in a few minutes, contact Cisco TAC for assistance.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
Prior to contacting Cisco TAC, from the UNIX prompt collect df -k.
BILLING (5)
For additional information, refer to the "Billing Partition Disk Usage Within Normal Range—Billing (5)" section.
DESCRIPTION
|
Billing Partition Disk Usage Within Normal Range
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Disk Usage Percentage-TWO_BYTES
|
BILLING (6)
To troubleshoot and correct the cause of the alarm, refer to the "File Transfer Protocol/Secure File Transfer Protocol Transfer Failed—Billing (6)" section.
Note OpenSSH version 3.9p1 contains a bug that may cause billing file transfers over SFTP to fail.
DESCRIPTION
|
File Transfer Protocol/Secure File Transfer Protocol Transfer Failed (FTP/SFTP Transfer Failed)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
TransferType-STRING [5]
FileName-STRING [40]
RemoteAddress-STRING [40]
Error-STRING [50]
|
PRIMARY
CAUSE
|
Unable to connect to the remote host.
|
PRIMARY
ACTION
|
Verify the remote host is reachable. Run the show billing-acct-addr command and verify that the billing-server-addr is correct. Change the billing-server-addr, if necessary, using the change billing-acct-addr command.
|
SECONDARY
CAUSE
|
Unable to login to the remote host.
|
SECONDARY
ACTION
|
Use show billing-acct-addr command to verify that the user-name is a valid user for the host specified in the billing-server-addr. If user-name is correct and the TransferType dataword shows File Transfer Protocol (FTP), re-enter the password via the change billing-acct-addr command. If user-name is correct and the TransferType dataword shows Secure File Transfer Protocol (SFTP), verify that secure shell (SSH) keys have been pre-configured for the user-name on both the BTS 10200 and the remote host.
|
TERNARY
CAUSE
|
An file transfer error has occurred.
|
TERNARY
ACTION
|
Check the Error dataword to see if it gives an indication of the kind of error that occurred. It could be a file-system error on the remote host, or a communication failure between the BTS 10200 and the remote host.
|
SUBSEQUENT
CAUSE
|
The CDB_BILLING_SUPP flag is not set to Y in the call-agent-profile table.
|
SUBSEQUENT
ACTION
|
Check and verify that the CDB_BILLING_SUPP flag is set to Y in the call-agent-profile table.
|
BILLING (7)
To troubleshoot and correct the cause of the alarm, refer to the "Transmission Control Protocol Connection Error—Billing (7)" section.
DESCRIPTION
|
Transmission Control Protocol Connection Error (TCP Connection Error)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Hostname-STRING [100]
|
PRIMARY
CAUSE
|
A system call error has occurred.
|
PRIMARY
ACTION
|
Check the address in platform configuration.
|
SECONDARY
CAUSE
|
The BTS 10200 is not connected to the right address.
|
SECONDARY
ACTION
|
Call Cisco TAC technical support. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
If the alarm is repeating, collect a packet capture between the BTS 10200 and the billing server prior to contacting Cisco TAC.
BILLING (8)
To troubleshoot and correct the cause of the alarm, refer to the "Transmission Control Protocol Packet Receive Failure—Billing (8)" section.
DESCRIPTION
|
Transmission Control Protocol Packet Receive Failure (TCP Packet Receive Failure)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Host Name-STRING [25]
|
PRIMARY
CAUSE
|
Peer went down; socket closed.
|
PRIMARY
ACTION
|
Check the peer status and bring it up.
|
BILLING (9)
BILLING (9) is not used.
BILLING (10)
BILLING (10) is not used.
BILLING (11)
BILLING (11) is not used.
BILLING (12)
BILLING (12) is not used.
BILLING (13)
To troubleshoot and correct the cause of the alarm, refer to the "Database Connection Error—Billing (13)" section.
DESCRIPTION
|
Database Connection Error
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
Structured Query Language (SQL) server is down.
|
PRIMARY
ACTION
|
Restart server; if this does not correct the problem, call Cisco TAC technical support. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for 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:
From the CLI prompt:
BILLING (14)
To monitor and correct the cause of the event, refer to the "File Open Error—Billing (14)" section.
DESCRIPTION
|
File Open Error
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Path Name-STRING [100]
|
PRIMARY
CAUSE
|
System error, may be out of file descriptors.
|
PRIMARY
ACTION
|
Call Cisco TAC technical support. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
Prior to contacting Cisco TAC, collect the following information:
From the UNIX prompt:
BILLING (15)
To troubleshoot and correct the cause of the alarm, refer to the "File Write Error—Billing (15)" section.
DESCRIPTION
|
File Write Error
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Path Name-STRING [100]
|
PRIMARY
CAUSE
|
System error, may be out of file descriptors.
|
PRIMARY
ACTION
|
Call Cisco TAC technical support. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
Prior to contacting Cisco TAC, collect the following information:
From the UNIX prompt:
BILLING (16)
BILLING (16) is not used.
BILLING (17)
BILLING (17) is not used.
BILLING (18)
BILLING (18) is not used.
BILLING (19)
BILLING (19) is not used.
BILLING (20)
BILLING (20) is not used.
BILLING (21)
BILLING (21) is not used.
BILLING (22)
BILLING (22) is not used.
BILLING (23)
BILLING (23) is not used.
BILLING (24)
BILLING (24) is not used.
BILLING (25)
BILLING (25) is not used.
BILLING (26)
BILLING (26) is not used.
BILLING (27)
BILLING (27) is not used.
BILLING (28)
BILLING (28) is not used.
BILLING (29)
To troubleshoot and correct the cause of the alarm, refer to the "Call Data Block Send Failed—Billing (29)" section.
DESCRIPTION
|
Call Data Block Send Failed (CDB Send Failed)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
Transmission Control Protocol (TCP) send call failure.
|
PRIMARY
ACTION
|
Check the port number and address of the blg and bmg processes in the platform.cfg file.
|
SECONDARY
CAUSE
|
Both the EMS servers are down.
|
SECONDARY
ACTION
|
Check if both EMS servers are down. If so, bring at least one up.
|
BILLING (30)
To troubleshoot and correct the cause of the alarm, refer to the "Domain Name Mapping Failed—Billing (30)" section.
DESCRIPTION
|
Domain Name Mapping Failed
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Address-STRING [50]
|
PRIMARY
CAUSE
|
Wrong domain name system (DNS) name mapping specified in the configuration files.
|
PRIMARY
ACTION
|
Check the opticall.cfg and platform.cfg for the right mapping.
|
BILLING (31)
To troubleshoot and correct the cause of the alarm, refer to the "Port not Specified—Billing (31)" section.
DESCRIPTION
|
Port not Specified
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
Port not specified in the platform.cfg file.
|
PRIMARY
ACTION
|
Check platform.cfg file and add the argument to blg -port 15260.
|
BILLING (32)
To troubleshoot and correct the cause of the alarm, refer to the "Element Management System Address not Specified—Billing (32)" section.
DESCRIPTION
|
Element Management System Address not Specified (EMS Address not Specified)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
Either the primary or secondary EMS address has not been specified in the platform.cfg file.
|
PRIMARY
ACTION
|
Check the platform.cfg for the process billing (BLG) and add the missing addresses to the file.
|
BILLING (33)
To troubleshoot and correct the cause of the alarm, refer to the "File Transfer Protocol/Secure File Transfer Protocol Parameters Invalid—Billing (33)" section.
DESCRIPTION
|
File Transfer Protocol/Secure File Transfer Protocol Parameters Invalid (FTP/SFTP Parameters Invalid)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
TransferType-STRING [5]
BillingServerDir-STRING [100]
BillingServerAddr-STRING [100]
User Name-STRING [100]
|
PRIMARY
CAUSE
|
The billing-acct-addr table is not fully provisioned with the information needed to perform file transfers.
|
PRIMARY
ACTION
|
Check billing-acct-addr fields using the show billing-acct-addr command. For FTP file transfer, ensure that the billing-server-addr, billing-server-directory, user-name, and password (not displayed) are provisioned. Also ensure that sftp-supp is set to N. For SFTP file transfer, ensure that the billing-server-addr, billing-server-directory, and user-name are provisioned. Also ensure that sftp-supp is set to Y.
|
BILLING (34)
BILLING (34) is not used.
BILLING (35)
To troubleshoot and correct the cause of the alarm, refer to the "All Billing Links at Billing Server Down—Billing (35)" section.
DESCRIPTION
|
All Billing Links at Billing Server Down
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
The cable connection might have been pulled out.
|
PRIMARY
ACTION
|
Restore the cable connection.
|
SECONDARY
CAUSE
|
An ifconfig down command might have been executed on the interfaces.
|
SECONDARY
ACTION
|
Execute an ifconfig up command on the interfaces.
|
BILLING (36)
For additional information, refer to the "Billing Link Restored—Billing (36)" section.
DESCRIPTION
|
Billing Link Restored
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Interface Name-STRING [50]
|
PRIMARY
CAUSE
|
The cable connection has been restored.
|
PRIMARY
ACTION
|
None
|
BILLING (37)
To troubleshoot and correct the cause of the alarm, refer to the "Billing Link Failure—Billing (37)" section.
DESCRIPTION
|
Billing Link Failure
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Interface Name-STRING [5]
|
PRIMARY
CAUSE
|
The cable connection may have been pulled.
|
PRIMARY
ACTION
|
Restore the cable connection.
|
SECONDARY
CAUSE
|
An ifconfig down command may have been performed on the interface.
|
SECONDARY
ACTION
|
Perform an ifconfig up command on the interface.
|
BILLING (38)
To troubleshoot and correct the cause of the alarm, refer to the "Event Message Log File Access Error—Billing (38)" section.
DESCRIPTION
|
Event Message Log File Access Error (EM Log File Access Error)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
50
|
THROTTLE
|
0
|
DATAWORDS
|
Type of Access Error-STRING [25]
Reason for Error-STRING [40]
Sequence Number OFF-FOUR_BYTES
Index of Event Messa-FOUR_BYTES
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
System error, may be out of file descriptors.
|
PRIMARY
ACTION
|
Call Cisco TAC. (Contact Cisco TAC.)
|
SECONDARY
CAUSE
|
The disk may be faulty.
|
SECONDARY
ACTION
|
Make the Bulk Data Management System (BDMS) switch over to its mate node.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
BILLING (39)
BILLING (39) is not used.
BILLING (40)
To troubleshoot and correct the cause of the alarm, refer to the "Event Message Encode Failure—Billing (40)" section.
DESCRIPTION
|
Event Message Encode Failure (EM Encode Failure)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
There is a problem with the format of the data to be sent to the record keeping system (RKS).
|
PRIMARY
ACTION
|
If problem persists, call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
BILLING (41)
To troubleshoot and correct the cause of the alarm, refer to the "Message Content Error—Billing (41)" section.
DESCRIPTION
|
Message Content Error
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Message Type-FOUR_BYTES
Field Name-STRING [20]
Field Value (Text)-STRING [20]
Field Value (Numeric)-FOUR_BYTES
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
There is a mismatch between what the sender populated in the message and what the receiver expects.
|
PRIMARY
ACTION
|
Call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
BILLING (42)
To monitor and correct the cause of the event, refer to the "Error Reading Provisioned Data-Using Default—Billing (42)" section.
DESCRIPTION
|
Error Reading Provisioned Data-Using Default
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Error Code-FOUR_BYTES
Table Name-STRING [20]
Field Name-STRING [20]
Default Value (Decim-FOUR_BYTES
Default Value (Text)-STRING [20]
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
An application was unable to read the provisioned data, and had to resort to using default values.
|
PRIMARY
ACTION
|
Check to ensure that a complete load has been installed on the system. If the load is complete and problem persists, call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
BILLING (43)
BILLING (43) is not used.
BILLING (44)
To troubleshoot and correct the cause of the alarm, refer to the "Record Keeping System Switch Occurred—Billing (44)" section.
DESCRIPTION
|
Record Keeping System Switch Occurred (RKS Switch Occurred)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Type of RKS Switch-STRING [20]
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
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.
|
PRIMARY
ACTION
|
No action is necessary.
|
BILLING (45)
To troubleshoot and correct the cause of the alarm, refer to the "Event Message Log File Opened—Billing (45)" section.
DESCRIPTION
|
Event Message Log File Opened
|
SEVERITY
|
MINOR
|
THRESHOLD
|
50
|
THROTTLE
|
0
|
DATAWORDS
|
Element Type-STRING [5]
File Name-STRING [60]
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
A log file has been created for the storage of event messages that cannot be transmitted to an RKS.
|
PRIMARY
ACTION
|
No action is necessary.
|
BILLING (46)
To troubleshoot and correct the cause of the alarm, refer to the "Event Message Log File Closed—Billing (46)" section.
DESCRIPTION
|
Event Message Log File Closed
|
SEVERITY
|
MINOR
|
THRESHOLD
|
50
|
THROTTLE
|
0
|
DATAWORDS
|
Element Type-STRING [5]
File Name-STRING [60]
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
An open event message log file has been closed.
|
PRIMARY
ACTION
|
No action is necessary.
|
BILLING (47)
To troubleshoot and correct the cause of the alarm, refer to the "Record Keeping System Unreachable for One Hour—Billing (47)" section.
DESCRIPTION
|
Record Keeping System Unreachable for One Hour (RKSs Unreachable for 1 Hour)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
25
|
THROTTLE
|
0
|
DATAWORDS
|
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
Billing has not been able to communicate with any RKS for the past one hour.
|
PRIMARY
ACTION
|
Check status of the primary and secondary RKS servers; attempt to bring them into service. Verify that the radius-profile table and call-agent-profile table are provisioned such that communication with the RKS servers is possible.
|
BILLING (48)
To troubleshoot and correct the cause of the alarm, refer to the "Record Keeping System Unreachable for Three Hours—Billing (48)" section.
DESCRIPTION
|
Record Keeping System Unreachable for Three Hours (RKSs Unreachable for 3 Hours)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
25
|
THROTTLE
|
0
|
DATAWORDS
|
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
Billing has not been able to communicate with any RKS for the past three hours.
|
PRIMARY
ACTION
|
Check status of the primary and secondary RKS servers: attempt to bring them into service. Verify that the radius-profile table and call-agent-profile table are provisioned such that communication with the RKS servers is possible.
|
BILLING (49)
To troubleshoot and correct the cause of the alarm, refer to the "Record Keeping System Unreachable for 5 Hours—Billing (49)" section.
DESCRIPTION
|
Record Keeping System Unreachable for 5 Hours (RKSs Unreachable for 5 Hours)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
25
|
THROTTLE
|
0
|
DATAWORDS
|
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
Billing has not been able to communicate with any RKS for the past five hours.
|
PRIMARY
ACTION
|
Check status of the primary and secondary RKS servers; attempt to bring them into service. Verify that the radius-profile table and call-agent-profile table are provisioned such that communication with the RKS servers is possible.
|
BILLING (50)
BILLING (50) is not used.
BILLING (51)
BILLING (51) is not used.
BILLING (52)
To troubleshoot and correct the cause of the alarm, refer to the "Bulk Data Management System Stopped Generating New Billing File—Billing (52)" section.
DESCRIPTION
|
Bulk Data Management System Stopped Generating New Billing File (BDMS Stopped Generating New Billing File)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
Call detail records are accumulating on the disk associated with the billing files in the EMS. This is because data is being written into the billing files faster than it is being forwarded to the Billing Mediation Server. The FTP to the Billing Mediation Server may not be working. The maximum disk partition for billing records has been exceeded or the maximum number of files has been exceeded.
|
PRIMARY
ACTION
|
Check Billing Mediation Server node name, user name and password specified in BILLING_ACCT_ADDR table and log files. Correct any error to let FTP start again. If billing_server_directory = "/dev/null" as in the lab, primary files under billing_directory will not be forwarded or deleted automatically. In this case, files have to be manually deleted or moved, and BDMS needs to be restarted before it will start generating new billing files.
|
BILLING (53)
To troubleshoot and correct the cause of the alarm, refer to the "Event Message Disk Space 50 Percent Full—Billing (53)" section.
DESCRIPTION
|
Event Message Disk Space 50 Percent Full
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Number of Megabytes Used for Eve-FOUR_BYTES
Directory Containing Event Messa-STRING [30]
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
The event message storage has reached 50% of the maximum storage allowed.
|
PRIMARY
ACTION
|
Move the event message files out of the specified directory. Store them in another location, or discard them.
|
BILLING (54)
To troubleshoot and correct the cause of the alarm, refer to the "Event Message Disk Space 70 Percent Full—Billing (54)" section.
DESCRIPTION
|
Event Message Disk Space 70 Percent Full
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Number of Megabytes Used for Eve-FOUR_BYTES
Directory Containing Event Messa-STRING [30]
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
The event message storage has reached 70% of the maximum storage allowed.
|
PRIMARY
ACTION
|
Move the event message files out of the specified directory. Store them in another location, or discard them.
|
BILLING (55)
To troubleshoot and correct the cause of the alarm, refer to the "Event Message Disk Space 100 Percent Full—Billing (55)" section.
DESCRIPTION
|
Event Message Disk Space 100 Percent Full
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Number of Megabytes Used for Eve-FOUR_BYTES
Directory Containing Event Messa-STRING [30]
Location Tag-STRING [30]
|
PRIMARY
CAUSE
|
The event message storage has been completely filled. No additional event messages will be written to disk until more space is made available.
|
PRIMARY
ACTION
|
Move the event message files out of the specified directory. Store them in another location, or discard them.
|
BILLING (56)
To troubleshoot and correct the cause of the alarm, refer to the "Billing Data Corruption Detected—Billing (56)" section.
DESCRIPTION
|
Billing Data Corruption Detected
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
File/Table That May be Corrupt-STRING [32]
Low End of the Range of Records-FOUR_BYTES
High En |
