Cisco Cisco Packet Data Gateway (PDG) Documentation Roadmaps
Redundancy and Availability Features
▀ Service Availability Features
▄ Cisco ASR 5000 Series Product Overview
OL-22938-01
PDSN PDIF services supporting simple IP, Mobile IP, and Proxy Mobile IP
HA services supporting Mobile IP and/or Proxy Mobile IP session types with or without per-user Layer 3 tunnels
GGSN services for IPv4 and PPP PDP contexts
LNS session types
With this feature enabled, there is no loss of session information as described in table above. Session recovery consists
of the migration and recreation of control and data packet state information, subscriber session statistics, or session time
parameters such as idle timer and others.
of the migration and recreation of control and data packet state information, subscriber session statistics, or session time
parameters such as idle timer and others.
Typical recovery time for a single session manager failure is not expected to exceed 10 seconds. Should a processing
card hardware failure occur during a migration, then the time to recover all tasks and subscriber sessions should not
exceed 60 seconds.
card hardware failure occur during a migration, then the time to recover all tasks and subscriber sessions should not
exceed 60 seconds.
This feature is enabled/disabled on a chassis-wide basis and requires additional processing card hardware to ensure that
enough reserve resources (memory, processing, etc.) are available to fully recover session in the event of a software or
hardware failure.
enough reserve resources (memory, processing, etc.) are available to fully recover session in the event of a software or
hardware failure.
Interchassis Session Recovery
The Interchassis Session Recovery feature provides the highest possible availability for continuous call processing
without interrupting subscriber services. This is accomplished through the use of redundant chassis. The chassis are
configured as primary and backup with one being active and one inactive. Both chassis are connected to the AAA
server. When calls pass the checkpoint duration timer, checkpoint data is sent from the active chassis to the inactive
chassis. If the active chassis handling the call traffic goes out of service, the inactive chassis transitions to the active
state and continues processing the call traffic without interrupting the subscriber session.
without interrupting subscriber services. This is accomplished through the use of redundant chassis. The chassis are
configured as primary and backup with one being active and one inactive. Both chassis are connected to the AAA
server. When calls pass the checkpoint duration timer, checkpoint data is sent from the active chassis to the inactive
chassis. If the active chassis handling the call traffic goes out of service, the inactive chassis transitions to the active
state and continues processing the call traffic without interrupting the subscriber session.
The chassis determine which is active through a propriety TCP-based connection called a redundancy link. This link is
used to exchange status messages between the primary and backup chassis and must be maintained for proper system
operation. In the event the redundancy link goes out of service, interchassis session recovery is maintained through the
use of authentication probes and BGP peer monitoring. BGP routing must be enabled.
used to exchange status messages between the primary and backup chassis and must be maintained for proper system
operation. In the event the redundancy link goes out of service, interchassis session recovery is maintained through the
use of authentication probes and BGP peer monitoring. BGP routing must be enabled.
Interchassis Session Redundancy is currently supported on chassis configured for GGSN service or HA services in
support of Mobile IP and Proxy Mobile IP session types.
support of Mobile IP and Proxy Mobile IP session types.