Troubleshooting guide

6-33
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
To correct the problem, perform the procedure in the “Resolving an Association Alarm” section on
page 6-122.
Association Fail
This alarm occurs when an SCTP association fails because of an IP connectivity failure or an
out-of-service (OOS) destination.
Corrective Action
To correct the problem, perform the procedure in the “Resolving an Association Alarm” section on
page 6-122.
C7LNK ALGNMT LOST
This alarm occurs when the MTP2 for the C7 link between a Cisco ITP-L and an associated APC loses
alignment.
Corrective Action
To correct the problem, use the diagnostics on the affected Cisco ITP-L to determine why the link lost
alignment. See the “Verifying the Link Alignment Status” section on page B-6.
C7DPC CONGESTION
This alarm occurs when a link in a signaling route towards a given DPC becomes congested or when a
DPC is congested and has sent a congestion indication to the Cisco PGW 2200 Softswitch.
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 the status of the links that are associated with the affected DPC, as described in the “Retrieving
Service State of C7/SS7 Links or Linksets” section on page 3-45.
If none of the links are out-of-service, this alarm occurred because the DPC is congested. Corrective
action is not necessary. Wait for the congestion condition to clear.
If any of the links are out-of-service, proceed to Step 3.
Step 3 Return the out-of-service links to service, as described in the “Setting the Service State of a C7/SS7 Link
or Linkset” section on page 6-105.
If that does not resolve the problem, 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.