Cisco Cisco Packet Data Gateway (PDG) Guia De Resolução De Problemas
Global Configuration Mode Commands
congestion-control ▀
Cisco ASR 5000 Series Command Line Interface Reference ▄
OL-22947-02
congestion-control
Enables/disables congestion control support on the system.
Product
All
Privilege
Security Administrator, Administrator
Syntax
Sets the congestion control to its default value.
Disables congestion-control functionality. This is the default setting.
Usage
Congestion control on the system is used to monitor the system for conditions that could potentially degrade
performance when the system is under heavy load. Typically, these conditions are temporary (i.e high CPU or
memory utilization) and are quickly resolved. However, continuous or large numbers of these conditions
within a specific time interval may impact the system‘s ability to service subscriber sessions. The purpose of
congestion control is to aid in the identification of such conditions and invoke policies for addressing the
situation.
Congestion control operation is based on the configuration of the following:
performance when the system is under heavy load. Typically, these conditions are temporary (i.e high CPU or
memory utilization) and are quickly resolved. However, continuous or large numbers of these conditions
within a specific time interval may impact the system‘s ability to service subscriber sessions. The purpose of
congestion control is to aid in the identification of such conditions and invoke policies for addressing the
situation.
Congestion control operation is based on the configuration of the following:
Congestion condition thresholds: Thresholds dictate the conditions for which congestion control is to
be enabled and establish limits for defining the state of the system (congested or clear). These
thresholds function in a similar fashion to the operation thresholds that can be configured for the
system (as described in later in this chapter). The primary difference is that when these thresholds
are reached, not only is an SNMP trap generated (starCongestion), but a service congestion policy is
invoked as well.
thresholds function in a similar fashion to the operation thresholds that can be configured for the
system (as described in later in this chapter). The primary difference is that when these thresholds
are reached, not only is an SNMP trap generated (starCongestion), but a service congestion policy is
invoked as well.
A threshold tolerance is configured to dictate the percentage under the configured threshold that must be
reached in order for the condition to be considered ―cleared‖. An SNMP trap (starCongestionClear) is then
triggered.
reached in order for the condition to be considered ―cleared‖. An SNMP trap (starCongestionClear) is then
triggered.
Service congestion policies: Congestion policies are configurable for each service (PDSN, GGSN, or
HA). These policies dictate how services respond should the system detect that a congestion
condition threshold has been crossed.
condition threshold has been crossed.
Because congestion control functionality on the system is disabled by default, this command should be
executed once congestion-control thresholds and policies have been configured. (Refer to the
executed once congestion-control thresholds and policies have been configured. (Refer to the
and
commands for more
information.)