Troubleshooting guide

6-79
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 6 Troubleshooting the Cisco PGW 2200 Softswitch Platform
Troubleshooting Using Cisco PGW 2200 Softswitch Alarms
Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC”
section on page 6-93.
Step 2 Determine the AS definitions on the associated Cisco ITP. See the documentation for your Cisco ITP for
more information.
Step 3 Retrieve the settings for the affected SUA routing keys using the prov-rtrv MML command, as
described in the “Retrieving Provisioning Data” section on page 3-69.
Step 4 The AS definitions should match the routing contexts of the SUA routing keys. If they match, proceed
to Step 6. Otherwise, proceed to Step 5.
Step 5 Open a dynamic reconfiguration session to modify the routing contexts of the M3UA routing keys, as
described in the “Invoking Dynamic Reconfiguration” section on page 3-66.
If modifying the routing contexts of the M3UA routing keys corrects the problem, the procedure is
complete. Otherwise, proceed to Step 6.
Step 6 Verify that the AS is not shut down on the Cisco ITP. See the documentation for your Cisco ITP for more
information. If the AS is shut down, restart it. Otherwise, proceed to Step 7.
If restarting the AS corrects the problem, the procedure is complete. Otherwise, proceed to Step 7.
Step 7 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information
about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request”
section on page xviii.
SUPPORT FAILED
This alarm occurs when the identified entity cannot provide service because a supporting entity is not
providing service. The supporting entity might be hardware or software.
Corrective Action
To correct the problem, perform the following steps:
Step 1 To collect system data, see the method that is described in the “Collecting System Data for Cisco TAC”
section on page 6-93.
Step 2 Check for other alarms, as described in the “Retrieving All Active Alarms” section on page 6-3, which
further identify the failed entity.
Step 3 After you have identified the failed entity, replace it and restore it to service. If the entity is hardware,
see the appropriate documentation for replacement. If it is software, attempt to reboot the software.
If the alarms clear, the procedure is complete. Otherwise, proceed to Step 4.
Step 4 Contact the Cisco TAC to analyze the problem further and to determine a solution. For more information
about contacting the Cisco TAC, see the “Obtaining Documentation and Submitting a Service Request”
section on page xviii.