Troubleshooting guide

6-30
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
ANAL: TableFail_CondRouteDescTable
This alarm occurs when the conditional route description table could not be read during generic analysis.
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 Perform a call trace, as described in the “Performing a Call Trace” section on page 6-156.
Step 3 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: TableFail_CondRouteTable
This alarm occurs when the system could not read the conditional routing table during generic analysis.
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 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.
If that procedure resolves the problem, the procedure is finished. Otherwise, proceed to Step 3.
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: TableFail_CPCTable
This alarm occurs when the calling party category (CPC) table could not be read during generic analysis.
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 Perform a call trace, as described in the “Performing a Call Trace” section on page 6-156.