Troubleshooting guide

6-170
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Platform Troubleshooting
Step 2 Delete the identified call trace files using the rm -i filename UNIX command.
Where:
filename—Name of the call trace file (either *.btr or *.trc) that you identified for deletion.
Step 3 Repeat Step 2 for each additional call trace file that is identified for deletion.
Step 4 Enter the cd /opt/CiscoMGC/var/spool and ls UNIX commands to view the archived logs in the
/opt/CiscoMGC/var/spool directory on the affected disk drive:
The system responds with a list of files in the directory. Review the listed files. If archived log files are
listed, which are no longer required, proceed to Step 5. Otherwise, proceed to Step 7.
Note If you back up the system software regularly, you can retrieve files that to delete from your
backup files. For more information on backing up your system software, see the “Backing Up
System Software” section on page 3-29.
Step 5 Delete the identified archived log files using the rm -i filename UNIX command.
Where:
filename—Name of the archived log file you want to delete.
Step 6 Repeat Step 5 for each additional identified archived log file.
Step 7 Use the config-lib viewer to view the contents of the configuration library, according to instructions the
“Using the Config-Lib Viewer” section on page 3-127. Determine whether any of the configurations that
are listed are no longer necessary for the operation of the system. If you can delete any of the
configurations, delete them by using the procedure in the “Using the Config-Lib Viewer” section on
page 3-127.
Recovering from a Switchover Failure
Use the procedure in this section to recover from a failed switchover operation. Typically, you would use
this procedure when the standby Cisco PGW 2200 Softswitch is unavailable to process calls and a critical
alarm occurs on the active Cisco PGW 2200 Softswitch.
To recover from a switchover failure, complete the following steps:
Step 1 If you have not already collected system data, refer to the method that is described in the “Collecting
System Data for Cisco TAC” section on page 6-93.
Step 2 Log in to the active Cisco PGW 2200 Softswitch, start an MML session, and view the current alarms, as
described in the “Retrieving All Active Alarms” section on page 6-3.
Step 3 To identify the critical alarm that caused the switchover attempt, review the alarms that are listed in the
response. There should be at least one critical alarm and an alarm indicating that a switchover began and
another alarm indicating that the switchover failed.
If only one critical alarm is listed, that alarm caused the switchover attempt.
If more than one critical alarm is listed, compare the timestamp of the critical alarms with the timestamp
of the alarm indicating that a switchover began. The critical alarm that occurred before the switchover
was begun is the alarm that caused the switchover attempt.