Troubleshooting guide

6-22
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
Corrective Action
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 parameter, engine.SysConnectDataAccess, is set to true in the XECfgParm.dat file on the
active Cisco PGW 2200 Softswitch. If the setting is correct, proceed to Step 4. Otherwise, update the
value of the parameter for each host, using the procedure in the “Rebooting Software to Modify
Configuration Parameters” section on page 6-183.
If correcting the setting does not clear the alarm, 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: Data Failure Rcvd
This alarm occurs during analysis when the Cisco PGW 2200 Softswitch detects a data failure in the
external routing engine.
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.
ANAL:dpselection_table_fail
This alarm occurs when the Cisco PGW 2200 Softswitch cannot find the correct dial plan selection.
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.
ANAL:getDialplanBase_fail
This alarm occurs when the Cisco PGW 2200 Softswitch could not load or generate the dial plan.
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.
ANAL: InvalidtrkGrpType
This alarm occurs when the analysis module has not provided a valid trunk group type. The problem
occurs if the route analysis table specifies an invalid trunk group type.