Cisco Cisco ASR 5000
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Serving Gateway Overview
▀ Features and Functionality - Base Software
▄ S-GW Administration Guide, StarOS Release 18
28
The action that is carried out due to this collision at eGTP-C is to abort (Abort Old) the Bearer Creation procedure and
carry on normally with the PDN Delete procedure. The Counter total of 1 indicates that this collision happened only
once.
carry on normally with the PDN Delete procedure. The Counter total of 1 indicates that this collision happened only
once.
Congestion Control
The congestion control feature allows you to set policies and thresholds and specify how the system reacts when faced
with a heavy load condition.
with a heavy load condition.
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:
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 establish limits for defining the state of the system (congested or clear). These thresholds function in a way
similar to operational 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, starCongestion, 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, starCongestionClear, is then triggered.
similar to operational 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, starCongestion, 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, starCongestionClear, is then triggered.
Port Utilization Thresholds: If you set a port utilization threshold, when the average utilization of all
ports in the system reaches the specified threshold, congestion control is enabled.
Port-specific Thresholds: If you set port-specific thresholds, when any individual port-specific
threshold is reached, congestion control is enabled system-wide.
Service Congestion Policies: Congestion policies are configurable for each service. These policies dictate how
services respond when the system detects that a congestion condition threshold has been crossed.
Important:
For more information on congestion control, refer to the Congestion Control chapter in the System
Administration Guide.
Dedicated Bearer Timeout Support on the S-GW
The S-GW has been enhanced to support a bearer inactivity timeout for GBR and non-GBR S-GW bearer type sessions
per Qos Class Identifier (QCI). This enables the deletion of bearers experiencing less data traffic than the configured
threshold value. Operators now can configure a bearer inactivity timeout for GBR and non -GBR bearers for more
efficient use of system resources.
per Qos Class Identifier (QCI). This enables the deletion of bearers experiencing less data traffic than the configured
threshold value. Operators now can configure a bearer inactivity timeout for GBR and non -GBR bearers for more
efficient use of system resources.
Downlink Delay Notification
This feature is divided between the following:
Value Handling
Throttling