![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 142](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550142.webp)
3-36
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 3 Billing Troubleshooting
Troubleshooting Billing Alarms
Billing Partition Disk Usage Critical Threshold Exceeded—Billing (4)
The Billing Partition Disk Usage Critical Threshold Exceeded alarm (critical) indicates that a billing
partition disk usage critical threshold crossing has occurred. The primary cause of the alarm is that 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. Some fluctuation in disk usage is to be expected as
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 call volume, and then step downward
(CRITICAL to MAJOR to MINOR) when call volume slows. To correct the primary cause of the alarm,
Monitor this alarm. The read should catch up to write within a few minutes, and the alarm should not
remain active. 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. 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
.
File Transfer Protocol/Secure File Transfer Protocol Transfer Failed—Billing
(6)
The File Transfer Protocol/Secure File Transfer Protocol Transfer Failed alarm (major) indicates that
the billing information FTP/SFTP transfer has failed. The primary cause of the alarm is that the BTS
10200 is unable to connect to remote host. To correct the primary cause of the alarm, 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, by using the
change billing-acct-addr
command.
The secondary cause of the alarm is that the BTS 10200 is unable to login to remote host. To correct the
secondary cause of the alarm, use the
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 FTP, re-enter the password by using the
change billing-acct-addr
command. If
user-name is correct and the TransferType dataword shows SFTP, verify that SSH keys have been
pre-configured for user-name on both the BTS 10200 and the remote host. The ternary cause of the alarm
is that a file transfer error occurred. To correct the ternary cause of the alarm, 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. The subsequent
cause of the alarm is that the CDB_BILLING_SUPP flag is not set to Y in the call-agent-profile table.
To correct the subsequent cause of the alarm, check and verify that the CDB_BILLING_SUPP flag is
set to Y in the call-agent-profile table.
Note
OpenSSH version 3.9p1 contains a bug that may cause billing file transfers over SFTP to fail.