Troubleshooting guide

3-100
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
that a bearer circuit is in use and discovers that the bearer device does not show that circuit is in use, the
Cisco PGW 2200 Softswitch does not attempt to rebuild the call, but releases all associated resources.
Although the Cisco PGW 2200 Softswitch is the controlling authority, when it discovers a discrepancy
during a circuit audit, the Cisco PGW 2200 Softswitch releases all allocated resources and drops all calls.
Checkpointing
Checkpointing of calls ensures that established calls are preserved if a switchover occurs. The Call
Engine sends checkpoint events to the local checkpoint process at one point during call setup and at one
point in the call release phase.
Checkpointing is also applied to the following protocol supervisory messages and MML commands that
change the logical state of the bearer circuits:
• Blocking and Unblocking Messages and Commands
• Circuit Reset Messages and Commands
The local checkpointing process is responsible for securing these events to disk if the standby
Cisco PGW 2200 is unavailable and for forwarding those events to the remote checkpointing process
when it does become available. If the standby Cisco PGW 2200 Softswitch is running, checkpoint events
are batched and forwarded to the remote checkpointing process.
The remote checkpointing process is responsible for processing the checkpoint events from the active
Cisco PGW 2200 Softswitch, delivering only established calls to the remote call engine. The remote call
engine process begins checkpointing events for calls when it begins active call processing.
The following scenarios are supported:
• Standalone (no standby Cisco PGW 2200 Softswitch available)—Specify the activation or
deactivation of checkpointing. If checkpointing is activated, all checkpoint events are secured to
disk.
• Startup (standby Cisco PGW 2200 Softswitch unavailable)—Local checkpointing process retains or
secures all events until the standby Cisco PGW 2200 Softswitch is available and a request for
synchronization is completed.
• Synchronization—Request synchronization of the configurations of the two Cisco PGW 2200s.
This request is required after startup and transition from the standalone Cisco PGW 2200 Softswitch
to the standby available configuration.
• Switchover—If a switchover occurs, the standby Cisco PGW 2200 Softswitch assumes the primary
responsibility for processing calls and securing checkpoint events.
Checkpointing is also implemented to support forward Cisco PGW 2200 Softswitch software migration
by one release. Manually direct the standby Cisco PGW 2200 Softswitch out of service, upgrade the
software to the new release, and resynchronize calls with the active Cisco PGW 2200 Softswitch. For
detailed procedures on upgrading the Cisco PGW 2200 Softswitch software, see Cisco PGW 2200
Softswitch Release 9.8 Software Installation and Configuration Guide.
Verifying the Patch Level of the Cisco PGW 2200 Softswitch
As of Release 9.2 of the Cisco PGW 2200 Softswitch software, you can verify the patch level of your
Cisco PGW 2200 Softswitch software by performing the following steps:
Step 1 Display the current patch level of your system by logging into the active Cisco PGW 2200 Softswitch as
root and entering the following UNIX command:
pkginfo | grep Patch