Troubleshooting guide

6-63
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
If a rare spike in traffic causes this alarm, corrective action is not necessary. If this alarm occurs
regularly, you should ensure that your links and routes are properly configured for load sharing, as
described in the “SS7 Load Sharing Malfunction” section on page 6-97, and reroute some of your traffic
to other Cisco PGW 2200 Softswitches.
Note This alarm can occur when a provisioning session is active during peak busy hours. If this alarm occurs
during a provisioning session, you might clear the alarm by stopping the provisioning session. For more
information on the MML commands to manage a provisioning session, see the “Provisioning a Cisco
PGW 2200 Softswitch” section on page 3-64.
OverloadMedium
This alarm occurs when the system reaches the threshold for overload level 2. The system rejects a
percentage of new calls that are based on the call rejection percentage setting for overload level 2, until
the system reaches the abate threshold for overload level 2. The system automatically clears this alarm
at that time. For more information, see the “Managing Automatic Congestion Control” section on
page 3-77.
Corrective Action
If a a rare spike in traffic causes this alarm, corrective action is not necessary. If this alarm occurs
regularly, you should ensure that your links and routes are properly configured for load sharing, as
described in the “SS7 Load Sharing Malfunction” section on page 6-97, and reroute some of your traffic
to other Cisco PGW 2200 Softswitches.
Note This alarm can occur when a provisioning session is active during peak busy hours. If a provisioning
session is active, you can clear the alarm by stopping the provisioning session. For more information on
the MML commands to manage a provisioning session, see the “Provisioning a Cisco PGW 2200
Softswitch” section on page 3-64.
OverloadLight
This alarm occurs when the system reaches the threshold for overload level 1. The system rejects a
percentage of new calls that are based on the call rejection percentage setting for overload level 1, until
the abate threshold for overload level 1 is reached. The system automatically clears this alarm at that
time. For more information, see the “Managing Automatic Congestion Control” section on page 3-77.
Corrective Action
If a rare spike in traffic causes this alarm, corrective action is not necessary. If this alarm occurs
regularly, you should ensure that your links and routes are properly configured for load sharing, as
described in the “SS7 Load Sharing Malfunction” section on page 6-97, and reroute traffic to other Cisco
PGW 2200 Softswitches.