4-33
Cisco PGW 2200 Softswitch Release 9.8 Software Installation and Configuration Guide
OL-18083-14
Chapter 4 Configuring the Cisco PGW 2200 Softswitch Software
Configuring the Execution Environment
Configuring Geographic Separation of Active and Standby Hosts
This subsection describes how to configure Cisco PGW 2200 Softswitch hosts that are geographically
separated and positioned on different subnets, such as for a campus or WAN.
Table 4-6
presents limitations, implications, and caveats taht pertain to remotely locating (physical
separation) the Cisco PGW 2200 Softswitch:
*.IP_Addr1
Enter the IP address of the bge0 interface.
*.IP_Addr2
Enter the IP address of the bge1 interface (if configured).
*.IP_Addr3
Enter the IP address of the bge2 interface (if configured).
*.IP_Addr4
Enter the IP address of the bge3 interface (if configured).
*.Virtual_IP_Addr1
Enter a virtual IP addresses for the
Cisco PGW 2200 Softswitch used for SIP Failover Support
(optional).
*.Virtual_IP_Addr2
Enter a virtual IP addresses for the
Cisco PGW 2200 Softswitch used for SIP Failover Support
(optional).
Parameter
Modification
Table 4-6
Geographic Separation Requirements
Condition
Requirement
Software release version
Cisco PGW 2200 software 9.3(2) or later (with
associated operating system and hardware
requirements).
Total end-to-end delay, one way
Delay is the length of time it takes to send a message
from a source to a destination, such as from Cisco
PGW 2200 to SLT, Cisco PGW2200 to GW, or Cisco
PGW 2200 to Cisco PGW 2200.
Must be less than 150 milliseconds.
Packet loss
Packet loss is defined as missing packets with a message.
Must not exceed 1% (preferably, less than 0.5%).
Note
For packet loss rates below 0.5%, increase the
RUDP receive window size (*. rudpWindowSz)
to 64 for increased performance.
Bandwidth limitation
Directly related to end-to-end delay. There are no special
requirements.
If improved SIP automatic switchover
support is enabled...
Both the Cisco PGW 2200s should be part of the same IP
subnet.