Troubleshooting guide

3-96
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 3 Cisco PGW 2200 Softswitch Platform Operations
Regular Operations
Performing a Manual Switchover
In a continuous service configuration, you can swap the roles of the active Cisco PGW 2200 Softswitch
and the standby Cisco PGW 2200 Softswitch by issuing the appropriate MML command from the
management interface of the active Cisco PGW 2200 Softswitch. You can accomplish a switchover only
from the active Cisco PGW 2200 Softswitch, because only the active Cisco PGW 2200 Softswitch can
command the standby Cisco PGW 2200 Softswitch to take over. If only one Cisco PGW 2200 Softswitch
is processing all calls, it will reject a manual switchover request.
Typically, manual switchovers are performed for the following reasons:
• To periodically switch the roles of the Cisco PGW 2200 Softswitches
• To upgrade the existing software to a new release
• To bring down a system for hardware maintenance
Caution Performing a manual switchover can severely impact the call processing performance of the system. All
established calls are retained, but any calls in the process of being set up might be dropped. Attempt a
manual switchover only during a maintenance period when traffic is minimal.
If you need to order a manual switchover to perform maintenance or upgrade procedures on one or both
of the Cisco PGW 2200 Softswitches, complete the following steps or the call engine might delete all
calls. With both the active and standby Cisco PGW 2200 Softswitches operating normally, you can
invoke a manual switchover from one system to the other by completing the following steps:
Step 1 Determine whether both the active and standby Cisco PGW 2200 Softswitches are operating normally,
as described in the “Verifying the Platform State of the Cisco PGW 2200 Softswitches” section on
page 3-2.
Step 2 Determine whether any alarms are pending on either system, as described in the “Monitoring the Alarms
Status” section on page 3-7.
If any alarms are pending, you must correct the situation that caused the alarms. Search for the corrective
actions that are required to clear any alarms in the “Alarm Troubleshooting Procedures” section on
page 6-4. If the alarms do not appear in that section, corrective action is not required for those alarms.
See Cisco PGW 2200 Softswitch Release 9 Messages Reference for more information on those alarms.
Step 3 Ensure that calls are being replicated from the active Cisco PGW 2200 Softswitch to the standby
Cisco PGW 2200 Softswitch, as described in the “Verifying Proper Replication of Calls” section on
page 3-52.
Step 4 Enter the following MML command to synchronize the provisioning data on the standby
Cisco PGW 2200 with the data on the active Cisco PGW 2200 Softswitch:
prov-sync
Caution Using the prov-sync MML command can severely impact the call processing performance of the system.
Enter this command only during a maintenance period when traffic is minimal.
Step 5 Determine the platform state of both Cisco PGW 2200 Softswitches, as described in the “Verifying the
Platform State of the Cisco PGW 2200 Softswitches” section on page 3-2.
Step 6 Check that all processes on the active Cisco PGW 2200 Softswitch are in the running state, as described
in the “Verifying That Processes Are Running” section on page 3-4.