Troubleshooting guide

6-9
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 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.
Step 6 Verify that the AS is not shutdown on the Cisco ITP. See the documentation for your Cisco ITP for more
information. If the AS is shut down, restart it. Otherwise, proceed to Step 7.
If tending to the AS corrects the problem, the procedure is complete. Otherwise, proceed to Step 7.
Step 7 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.
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.
All M3UA Assoc Fail
This alarm occurs when all M3UA associations transporting SS7 signaling have failed.
Note The XECfgParm.dat parameter, *.AllLinksFailCausesFailover, now controls the generation of this
alarm. When this parameter is set to false (the default value), this alarm is not generated when the alarm
condition occurs. For the Cisco PGW 2200 Softswitch to generate this alarm, set the parameter to true,
by using the procedure that is defined in the “Rebooting Software to Modify Configuration Parameters”
section on page 6-183.
If the Cisco PGW 2200 Softswitches are in separate geographic locations, set the value of
*AllLinksFailCausesFailover to true.
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 Verify that the Cisco ITPs are operating normally. See the documentation for your Cisco ITP for more
information.