7-76
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 7 Maintenance Troubleshooting
Monitoring Maintenance Events
Administrative State Change Successful with Warning—Maintenance (41)
The Administrative State Change Successful with Warning event functions as a warning that the system
was in a flux when a successful administrative state change occurred. The primary cause of the event is
that the system was in flux state when an administrative change state command was issued. To correct
the primary cause of the event, retry the command.
Number of Heartbeat Messages Received is Less Than 50% of
Expected—Maintenance (42)
The Number of Heartbeat messages Received is Less Than 50% of Expected alarm (major) indicates that
number of heartbeat (HB) messages being received is less than 50% of expected number. To
troubleshoot and correct the cause of the Number of Heartbeat messages Received is Less Than 50% of
Expected alarm, refer to the
“Number of Heartbeat Messages Received is Less Than 50% of
Expected—Maintenance (42)” section on page 7-99
.
Process Manager: Process Failed to Come Up in Active Mode—Maintenance
(43)
The Process Manager: Process Failed to Come Up in Active Mode alarm (critical) indicates that the
process has failed to come up in active mode. To troubleshoot and correct the cause of the Process
Manager: Process Failed to Come Up in Active Mode alarm, refer to the
Failed to Come Up in Active Mode—Maintenance (43)” section on page 7-99
.
Process Manager: Process Failed to Come Up in Standby Mode—Maintenance
(44)
The Process Manager: Process Failed to Come Up in Standby Mode alarm (critical) indicates that the
process has failed to come up in standby mode. To troubleshoot and correct the cause of the Process
Manager: Process Failed to Come Up in Standby Mode alarm, refer to the
Failed to Come Up in Standby Mode—Maintenance (44)” section on page 7-100
Application Instance State Change Failure—Maintenance (45)
The Application Instance State Change Failure alarm (major) indicates that an application instance state
change failed. To troubleshoot and correct the cause of the Application Instance State Change Failure
alarm, refer to the
“Application Instance State Change Failure—Maintenance (45)” section on
.
Network Interface Restored—Maintenance (46)
The Network Interface Restored event functions as an informational alert that the network interface was
restored. The primary cause of the event is that the interface cable is reconnected and the interface is put
‘up’ using
ifconfig
command. The event is informational and no further action is required.