Troubleshooting guide

6-54
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
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.
LIF: LOST CTS
This alarm occurs when the physical line fails because its cable is broken or not plugged in. This is
reported for V.35 facilities only.
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 V.35 cables between the port and the far-end are working correctly.
If you find a problem with a V.35 cable, replace the cable. If that does not correct the problem, proceed
to Step 3.
If you do not find a problem with the V.35 cables, proceed to Step 3.
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.
M3UAKEY Ack Pending
This alarm occurs when the Cisco PGW 2200 Softswitch cannot send or receive traffic for the identified
SS7 signaling service via the Cisco ITP that has not acknowledged the M3UAKEY.
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 Determine the AS definitions on the associated Cisco ITP. See the documentation for your Cisco ITP for
more information.
Step 3 Retrieve the settings for the affected M3UA routing keys using the prov-rtrv MML command, as
described in the “Retrieving Provisioning Data” section on page 3-69.
Step 4 The AS definitions should match the routing contexts of the M3UA routing keys. If they match, proceed
to Step 6. Otherwise, proceed to Step 5.
Step 5 Open a dynamic reconfiguration session to modify the routing contexts of the M3UA routing keys, as
described in the “Invoking Dynamic Reconfiguration” section on page 3-66.
If modifying the routing contexts corrects the problem, the procedure is complete. Otherwise, proceed
to Step 6.