11-14
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 11 Statistics Troubleshooting
Monitoring Statistics Events
Message Send Failure—Statistics (8)
The Message Send Failure event serves as a warning that a message send has failed. The primary cause
of the event is that the originating process (for CA, FS or EMS) is not in active state, or is shut down.
To correct the primary cause of the event, check for other alarms and events generated from this
component (CA, FS or EMS). The secondary cause of the event is that the hub is down. To correct the
secondary cause of the event, is if the hub process is down, try to bring it into a normal state. The ternary
cause of the event is that the platform is currently shutting down a process. To correct the ternary cause
of the event, is if the originating process is down, try to bring the process back into the normal state. If
this event report is being issued on every collection interval and there are no other event reports being
issued, contact the Cisco TAC to resolve the communication issue.
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.
Issued when the traffic measurement subsystem in the CA fails to send messages to the EMS due to:
•
Originating process (for CA, FS or EMS) is not in active state, or is shut down.
•
Hub is down.
•
Platform is currently shutting down a process.
If this event is being issued frequently (every collection interval), then there are communication
difficulties between the Call Agent and the EMS, and there will be additional events being issued. These
other events will indicate the nature of the communication difficulties. The repair procedures for the
other event reports should be followed to correct the Call Agent/EMS communication issue:
•
Check for other alarms and events generated from this component (CA, FS or EMS).
•
If the originating process is down, try to bring the process back into the normal state.
•
If the hub process is down, try to bring it into a normal state.
If this event report is being issued on every collection interval and there are no other event reports being
issued, contact the Cisco TAC to resolve the communication issue.
Measurement Table Structured Query Language Read Error—Statistics (9)
The Measurement Table Structured Query Language Read Error event serves as a warning that the
measurement table had a Structured Query Language (SQL) read error. The primary cause of the event
is that there is no database connection, or the connection is faulty. To correct the primary cause of the
event, check to see if there are any other events generated that indicate there is a database problem. The
secondary cause of the event is that the traffic measurement tables are corrupted. To correct the
secondary cause of the event, correct any database-related problems. The ternary cause of the event is
that two processors or more are attempting to access the table at the same time. To correct the ternary
cause of the event, check to see if all of the database-related problems are cleared, and this warning event
report still occurs, contact Cisco TAC for technical support.
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.
