Troubleshooting guide

6-10
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
If ensuring that the Cisco ITPs operate normally corrects the problem, the procedure is complete.
Otherwise, proceed to Step 3.
Step 3 Verify that the Ethernet interfaces between the Cisco PGW 2200 Softswitch and the Cisco ITPs are
working properly.
Note For information on verifying the proper operation of an Ethernet interface on the Cisco PGW
2200 Softswitch, see the Sun Microsystems documentation that came with your system. For
information on verifying the proper functioning of an Ethernet interface on a Cisco ITP, see the
documentation for the Cisco ITP.
If an element of the Ethernet connection (such as a cable or an Ethernet interface card) is not working
properly, replace it. Otherwise, proceed to Step 4.
Note For information on removing and replacing an Ethernet interface card on the Cisco PGW 2200
Softswitch, see the Sun Microsystems documentation that came with your system. For
information on removing and replacing an Ethernet interface card on the Cisco ITP, see the
documentation for the Cisco ITP.
Step 4 Verify that the M3UA provisioning data on the Cisco PGW 2200 Softswitch is correct.
If the provisioning data is correct, proceed to Step 6. Otherwise, proceed to Step 5.
Step 5 Open a dynamic reconfiguration session to modify the M3UA provisioning data, as described in the
“Invoking Dynamic Reconfiguration” section on page 3-66.
If modifying the M3UA provisioning data corrects the problem, the procedure is complete. Otherwise,
proceed to Step 6.
Step 6 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.
All SUAKEY Ack Pending
This alarm occurs when the Cisco PGW 2200 Softswitch cannot send or receive traffic for the identified
SS7 subsystem.
Corrective Action
To correct the problem that this alarm identifies, 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 SUA 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 SUA routing keys. If they match, proceed
to Step 6. Otherwise, proceed to Step 5.