Redundancy Support - Cisco ASR 5000 Administration Manual

▀ Product Overview
Congestion control operation is based on configuring the following:
 Congestion Condition Thresholds: Thresholds dictate the conditions for which congestion control is enabled
and establishes limits for defining the state of the system (congested or clear). These thresholds function in a
way similar to operation thresholds that are configured for the system as described in the Thresholding
Configuration Guide. The primary difference is that when congestion thresholds are reached, a service
congestion policy and an SNMP trap are generated.
A threshold tolerance dictates the percentage under the configured threshold that must be reached in order for
the condition to be cleared. An SNMP trap is then triggered.
 Port Utilization Thresholds: Congestion thresholds for utilization of all ports in the system.
 Service Congestion Policies: Congestion policies are configurable for each service. These policies
 License Utilization: Congestion thresholds for license utilization on the system.
 Maximum Sessions-per-Service Utilization: Congestion thresholds for maximum number of sessions
Important:
the System Administration Guide.

Redundancy Support

Important:
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 ASR5000 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 D-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 D-eWAG Session Recovery support, apart from common access-side attributes (common between D-eWAG and R-
eWAG sessions), attributes specific to D-eWAG session such as Default-GW-IP address, UE-MAC, and so on are
supported. D-eWAG GTP context information is recovered similar to R-eWAG as Gn' interface is used by both.
▄ Cisco ASR 5000 Enhanced Wireless Access Gateway Administration Guide
86
 Port-specific Thresholds: Congestion thresholds for individual ports.
dictate how services respond when the system detects that a congestion condition threshold has been
crossed.
allowed per service.
For more information on the Congestion Control feature, refer to the Congestion Control chapter in
In this release, D-eWAG supports basic Session Recovery, ICSR is not supported.
In this release Line Card Switchover is not supported.
DHCP-based Enhanced Wireless Access Gateway Overview