Troubleshooting guide

6-78
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
Note If you modify an ss7path that is configured for M3UAKEY, the system generates the “All M3UAKEY
Ack Pending“ alarm for all the other ss7paths that are configured with the same M3UAKEY, although
they are not being modified.
Coincidentally, when you modify an ss7path, the system generates the M3UAKEY Ack Pending alarms
when the prov-cpy and prov-dply commands are being processed. However, these alarms are cleared
after the commands have been completed.
When the prov-cpy and prov-dply commands are being processed, no new calls can be placed on any
of the ss7paths for which alarms were generated. However, the calls that already exist on the ss7paths
are not affected.
SSN FAIL
This alarm occurs when the SCP located by the subsystem number (SSN) is not available.
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 Ensure that the provisioning settings for the SSN and the associated routes match the settings that are
used on the far-end, as described in the “Retrieving Provisioning Data” section on page 3-69.
If the configuration data associated with the SSN is incorrect, begin a dynamic reconfiguration session,
as described in the “Invoking Dynamic Reconfiguration” section on page 3-66.
If the configuration data associated with the SSN is correct, proceed to Step 3.
Step 3 Verify the network configuration to confirm that the SCP identified with the SSN is reachable.
If the SCP is not reachable, begin a dynamic reconfiguration session, as described in the “Invoking
Dynamic Reconfiguration” section on page 3-66. Reprovision your data for an SCP that is reachable or
remove the SSN and its associated data.
If the SCP is reachable, 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.
SUAKEY Ack Pending
This alarm occurs when the Cisco PGW 2200 Softswitch cannot send or receive traffic for the identified
SS7 subsystem via the Cisco ITP that has not acknowledged the SUAKEY.
Corrective Action
To correct the problem, perform the following steps: