Cisco Cisco Packet Data Gateway (PDG)
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Global Configuration Mode Commands (A-K)
congestion-control ▀
Command Line Interface Reference, StarOS Release 17 ▄
5283
congestion-control
This command enables and disables the congestion control functionality on the system.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
[ default | no ] congestion-control
default
Sets the congestion control to its default value.
no
Disables the congestion control functionality. This is the default behavior.
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:
Call disconnections on overload: With this functionality, the system enables and disables the policy
for disconnecting passive calls (chassis-wide) during an overload situation. It also configures and
fine-tunes the overload-disconnect congestion control policy for an entire chassis.
fine-tunes the overload-disconnect congestion control policy for an entire chassis.
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.
must be reached in order for the condition to be considered “cleared”. An SNMP trap
(starCongestionClear) is then triggered.