RADIUS-based Enhanced Wireless Access Gateway Overview
Important:
System Administration Guide.
Redundancy Support
Important:
Session Recovery feature provides a mechanism to recover failed Session Manager (SessMgr) task(s) without any call
loss. Recovery framework is same as used by other products. A minimum of four PSCs (three active and one standby) is
required in an ASR 5000 chassis to support the Session Recovery feature. This is because the DEMUX Manager and
VPN Manager tasks run on a PSC where no SessMgr runs when session recovery is enabled and one PSC is used as
standby PSC. The other two PSCs run SessMgr and AAAMgr tasks.
Session Recovery is a licensed feature and can be controlled from the CLI, that is enabled/disabled Session Recovery
across the whole chassis. When the CLI is used to configure the Session Recovery feature, Session Controller updates
each SessMgr task.
In the case of R-eWAG, the IPSG Manager, SGTPC Manager, and VPN Manager run on one PSC. SessMgr runs on one
separate PSC. AAAMgr runs on one separate PSC and on one standby PSC. Therefore, a minimum of four PSCs (three
active and one standby) are required.
For R-eWAG Session Recovery support, existing IPSG Session Recovery framework is reused for recovering access
side attributes common between IPSG and R-eWAG sessions. New fields are added in IPSG Session Recovery record to
recover attributes specific to R-eWAG session such as WLAN IP address, MPC IP address, R-eWAG GTP information,
and so on. R-eWAG GTP context information will be recovered similar to TTG since Gn' interface is used by both.
For more information on Congestion Control feature, refer to the Congestion Control chapter in the
In this release, R-eWAG supports basic Session Recovery, ICSR is not supported.
Cisco ASR 5000 Enhanced Wireless Access Gateway Administration Guide ▄
Feature Description ▀
29