Troubleshooting guide

6-28
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 2 Verify that the data for the provisioned route lists is correct by logging in to the active
Cisco PGW 2200 Softswitch, starting an MML session, and entering the prov-rtrv:rtlist:“all”
command:
Step 3 If the data for the route lists is incorrect, correct it by using the prov-ed MML command. Otherwise,
proceed to Step 4. See the Cisco PGW 2200 Softswitch Release 9.8 Provisioning Guide for more
information on provisioning route lists.
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.
ANAL: Rte_TableHopCtrExceeded
This alarm occurs when generic analysis fails because of an excessive number of routing table changes.
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 Test for a loop in the routing configuration by completing the following steps:
a. Export the routing configuration to a file, as described in the “Exporting Provisioning Data” section
on page 3-76.
b. Import the routing configuration file that is created in Step 2a, as described in the “Importing
Provisioning Data” section on page 3-75.
If the import fails, proceed to Step 3. Otherwise, proceed to Step 4.
Step 3 Perform a call trace, as described in the “Performing a Call Trace” section on page 6-156.
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.
ANAL: RteTableFail_GetRteList
This alarm occurs when access to the route list failed. The problem occurs if the index to the route list
is not valid or if the route list is not loaded.
Corrective Action
To correct the problem, verify that the dial plan file was loaded correctly, using the procedure that is
described in the “Verifying Proper Loading of a Dial Plan” section on page 6-121.