Cisco Cisco Packet Data Interworking Function (PDIF)
Sample L2 Interchassis HA Configuration
▀ Configuration Overview
▄ SecGW Administration Guide, StarOS Release 18
96
Configuration Overview
Interchassis Layer 2 redundancy supports hot standby redundancy between two VPC-VSM instances in different ASR
9000 chassis. The standby instance is ready to become active once a switchover is triggered. SA re-negotiation is not
required and traffic loss is minimal.
9000 chassis. The standby instance is ready to become active once a switchover is triggered. SA re-negotiation is not
required and traffic loss is minimal.
The route database on the standby VSM must contain only the routes that were successfully injected by the active VSM.
Because of the asymmetric assignment of VSM resources among StarOS VMs, an operator should configure one-to-one
mapping between StarOS VMs across active/standby VSMs in different ASR 9000 chassis. See the table below.
mapping between StarOS VMs across active/standby VSMs in different ASR 9000 chassis. See the table below.
Table 4. Recommended Mapping of Interchassis StarOS VMs
Active VSM
Standby VSM
VM1 – SecGW1
VM1 – SecGW1
VM2 – SecGW2
VM2 – SecGW2
VM3 – SecGW3
VM3 – SecGW3
VM4 – SecGW4
VM4 – SecGW4
Each VM will be monitored via separate HSRP configurations and connected to separate oneP (CA) sessions so that
switchover of one VM will not affect the other VMs.
switchover of one VM will not affect the other VMs.
Sample ASR 9000 chassis RSP configurations are provided for primary and standby chassis.
The sample configurations provided for an SecGW VM (Virtual Machine) configuration must be replicated on each
CPU-VM complex on both the active and standby VSMs. Each VSM supports four CPU-VM complexes (SecGWs).
CPU-VM complex on both the active and standby VSMs. Each VSM supports four CPU-VM complexes (SecGWs).