Troubleshooting guide

1-8
Cisco PGW 2200 Softswitch Release 9.8 Operations, Maintenance, and Troubleshooting Guide
OL-0800-14
Chapter 1 Cisco PGW 2200 Softswitch Platform Overview
Cisco PGW 2200 Softswitch Software Architecture
Rendezvous Routing Daemon (RVRD)—Used when the management system and the Cisco
PGW 2200 Softswitches are not on the same network. You must configure the RVRD routing
table and start RVRD manually before activating the interface on the Cisco PGW 2200
Softswitch. See the TIBCO user documentation for information on configuring the RVRD
routing table.
Note Typically, you activate the TIBCO interface during initial installation or during an
upgrade. For more information on activating the TIBCO interface, see Cisco PGW 2200
Softswitch Software Release 9 Installation and Configuration Guide.
Cisco MGC Node Manager (MNM)—Optional application for network element management.
Cisco Voice Services Provisioning Tool (VSPT)—Optional application for provisioning the Cisco
PGW 2200 Softswitch.
Billing and Measurements Server (BAMS)—Optional application for collecting CDRs and
operational measurements.
H.323 Signaling Interface (HSI)—Optional application that provides an interface to H.323
networks.
Fault Tolerance Subsystem
The fault tolerance subsystem exists to preserve calls if the Cisco PGW 2200 Softswitch encounters a
fault condition. There are two processes that ensure this:
Switchover daemon—Monitors Cisco PGW 2200 Softswitch processes by using a heartbeat
mechanism. If the switchover daemon receives no response to its process polling in a fault-tolerant
hardware configuration, the control transfers to the standby unit.
Replicator—Allows processes to checkpoint critical call information, such as signaling and bearer
states, as well as call data across the active and standby processors. The replicator duplicates enough
information to enable established calls to survive a switchover. Checkpointing events are generated
at two points in a call:
When the call is answered, to update the full duplex path.
When the call is released, after the physical resources are de-allocated.
An operator who is performing maintenance by issuing MML commands using an SNMP client, or
by circuit supervision, can generate connectionless (noncall) signaling.
Certain signaling can also generate checkpointing events:
Blocking or unblocking of circuits
Circuit reset
Note The replicator mechanism does not try to replicate program or data storage. Service features are not
checkpointed across processors; there is just enough information to maintain the voice or data path
between the call originator and the call terminator.
If a switchover occurs before the voice path is established during call processing, the call cannot be
checkpointed to the standby Cisco PGW 2200 Softswitch. Calls that are not established during call setup
are lost in the Cisco PGW 2200 Softswitch that becomes active after the switchover.