3-22
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 3 Billing Troubleshooting
Billing Events and Alarms
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 on page 3-42
.
BILLING (53)
To troubleshoot and correct the cause of the alarm, refer to the
“Event Message Disk Space 50 Percent
Full—Billing (53)” section on page 3-42
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.
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.
