![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 788](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550788.webp)
16-40
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 16 Disaster Recovery Procedures
Automatic Restart
The following processes are completed during the automatic restart processing:
•
Check if Restart is Possible (
)—An intelligent processing to check if a restart should be
attempted is completed. The default behavior is to attempt an Automatic Restart the maximum
number of configured tries.
•
platform start/platform stop—The
platform start
and
platform stop
commands will not work when
an Automatic Restart is scheduled. However, the user can use the
-noautorestar
t command option
on either command to bypass the Automatic Restart and force the platform start or stop to occur
immediately.
Switchover to standby, but failure.
SDAAR
Switchover to standby, but timeout failure.
SDAAR
Switchover to standby, but DB copy failure.
SDAAR
All States
KAM received a signal.
SDAAR
Application-initiated Shutdowns
Active
BMG2 (Billing Manager). Problems parsing command line options.
See Note 2
H3A. When there are no good H3A signaling links.
See Note 2
MGA. When all the needed interfaces are either faulty or not stabilized.
See Note 2
SGA. When both signaling gateways are down.
See Note 2
EPA. When the EMS is not reachable.
See Note 2
NIM. When all of the HUB interfaces are faulty.
See Note 2
Standby
BMG2 (Billing Manager). Problems parsing command line options.
See Note 2
H3A. When there are no good H3A signaling links.
See Note 2
MGA. When all the needed interfaces are either faulty or not stabilized.
See Note 2
SGA. When both signaling gateways are down.
See Note 2
EPA. When the EMS is not reachable.
See Note 2
NIM. When all of the HUB interfaces are faulty.
See Note 2
1.
Most references to process state in this table refer to a platform-internal state assigned to each process. The Process Manager
methodically brings up the platform by starting processes in a given sequence. When a process does not reach the proper state
at a given point during startup, it is declared to be in a bad/or incorrect state.
2.
The shutdown action is specified by the process’ platform.cfg parameters: ProcessCriticalFailureActionWhenMateStandby,
ProcessCriticalFailureActionWhenMateActive, or ProcessCriticalFailureActionWhenMateFaulty.
Table 16-2
OOS-FAULTY Behavior (continued)
Description
Result