Troubleshooting guide

6-71
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
SC CONFIG FAIL
This alarm occurs when the provisioning parameters for the data link layer of a signaling channel are
inconsistent or invalid. The signaling channel might already be provisioned. The configuration file might
be corrupted so that the Cisco PGW 2200 Softswitch cannot read it.
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 Place the affected signaling channel in the out-of-service state.
Step 3 Start a provisioning session, as described in the “Starting a Provisioning Session” section on page 3-64.
Step 4 Remove the affected signaling channel from your configuration using the prov-dlt MML command. See
Cisco PGW 2200 Softswitch Release 9 MML Command Reference for more information.
Step 5 While referring to your local provisioning parameters, reprovision the signaling channel using the
prov-add MML command. See Cisco PGW 2200 Softswitch Release 9 MML Command Reference for
more information.
Step 6 Save and activate the provisioning session, as described in the “Saving and Activating your Provisioning
Changes” section on page 3-65.
Step 7 Place the signaling channel in the in-service state.
If placing the signaling channel in-service does not resolve the problem, proceed to Step 8.
Step 8 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.
SC FAIL
This alarm occurs when the signaling channel is down and unable to process traffic. As a result, the
signaling channel fails to negotiate a D-channel session, automatic restarts cannot recover the session,
and the data link-layer fails. This problem can occur when SS7 SLTM/SLTA fails or when a PRI
D-channel fails.