Troubleshooting guide

6-62
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
OOS TRAFFIC RE-ROUTE
This alarm occurs when the traffic channels (bearer channels, IP network) on one side of the Cisco PGW
2200 Softswitch are lost, which causes the Cisco PGW 2200 Softswitch to reroute channels away from
the affected component. Usually, this alarm is generally because of a network or equipment failure, but
might be because of a provisioning failure.
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 The Cisco PGW 2200 Softswitch should display the other alarms that are associated with the affected
component. Resolve those alarms first.
If resolving those alarms does not clear this alarm, proceed to Step 3.
Step 3 Verify that the traffic channel settings that are provisioned for the Cisco PGW 2200 Softswitch and the
affected media gateway are correct.
Note Use the prov-rtrv MML command, as described in the “Retrieving Provisioning Data” section
on page 3-69, to retrieve the traffic channel provisioning data for the Cisco PGW 2200
Softswitch. See the documentation for the media gateway for information on retrieving the
traffic channel data.
If the configuration of the Cisco PGW 2200 Softswitch is incorrect, begin a dynamic reconfiguration
session, as described in the “Invoking Dynamic Reconfiguration” section on page 3-66.
If the configuration of the affected media gateway is incorrect, modify the provisioning data for your
system. See the documentation for the media gateway for more information.
If the configuration of both the Cisco PGW 2200 Softswitch and the affected media gateway are correct,
then 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.
OverloadHeavy
This alarm occurs when the system reaches the threshold for overload level 3. The system performs an
automatic switchover operation. If the call rejection percentage setting for overload level 3 is unchanged
from its default value, the system rejects all new calls until the abate threshold for overload level 3 is
reached. The system automatically clears the alarm at that time. For more information, see the
“Managing Automatic Congestion Control” section on page 3-77.