Congestion Control Support - Cisco ASR 5000 Administration Manual

▀ Feature Description
Generation of specific traps can be enabled or disabled on the chassis. Ensuring that only important faults get
displayed. SNMP traps are supported in both Alert and Alarm modes.
 Logs: The system provides a facility called threshold for which active and event logs can be generated. As with
other system facilities, logs are generated. Log messages pertaining to the condition of a monitored value are
generated with a severity level of WARNING.
Logs are supported in both the Alert and the Alarm models.
 Alarm System: High threshold alarms generated within the specified polling interval are considered
"outstanding" until a the condition no longer exists or a condition clear alarm is generated. "Outstanding"
alarms are reported to the system's alarm subsystem and are viewable through the Alarm Management menu in
the Web Element Manager.
The Alarm System is used only in conjunction with the Alarm model.
Important:

Congestion Control Support

The Congestion Control feature enables to specify how the system reacts in a heavy load condition. Congestion control
operation is based on configuring congestion condition thresholds and service congestion policies.
Important:
Congestion Control monitors the system for conditions that could potentially degrade performance when the system is
under heavy load. Typically, these conditions are temporary (for example, high CPU or memory utilization) and are
quickly resolved. However, continuous or large numbers of these conditions within a specific time interval may have an
impact the system's ability to service subscriber sessions. Congestion control helps identify such conditions and invokes
policies for addressing the situation.
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
▄ Cisco ASR 5000 Enhanced Wireless Access Gateway Administration Guide
28
For more information on thresholds, refer to the Thresholding Configuration Guide.
Overload Disconnect is not supported.
 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.
RADIUS-based Enhanced Wireless Access Gateway Overview