Cisco Cisco Packet Data Interworking Function (PDIF) トラブルシューティングガイド
Global Configuration Mode Commands
congestion-control threshold ▀
Cisco ASR 5000 Series Command Line Interface Reference ▄
OL-22947-02
Default: 80
The average percent utilization of CPUs on which a Demux Manager software task instance is running as
measured in 10 second intervals.
percent can be configured to any integer value from 0 to 100.
The average percent utilization of CPUs on which a Demux Manager software task instance is running as
measured in 10 second intervals.
percent can be configured to any integer value from 0 to 100.
Default: 80
The average percent utilization for all PAC/PSC/PSC2 CPUs available to the system as measured in 10
second intervals.
percent can be configured to any integer value from 0 to 100.
This threshold setting can be disabled with
The average percent utilization for all PAC/PSC/PSC2 CPUs available to the system as measured in 10
second intervals.
percent can be configured to any integer value from 0 to 100.
This threshold setting can be disabled with
command. In case later you want to enable the same threshold setting
command will enable the CPU utilization
threshold to preconfigured level.
Default: 80
The average percent utilization of all CPU memory available to the system as measured in 10 second
intervals.
percent can be configured to any integer value from 0 to 100.
The average percent utilization of all CPU memory available to the system as measured in 10 second
intervals.
percent can be configured to any integer value from 0 to 100.
Default: 10
The percentage under a configured threshold that dictates the point at which the condition is cleared.
percent is an integer value from 0 to 100.
The percentage under a configured threshold that dictates the point at which the condition is cleared.
percent is an integer value from 0 to 100.
Usage
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.
The tolerance parameter establishes the threshold at which the condition is cleared. An SNMP trap
(starCongestionClear) is generated for the clear condition, as well.
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.
The tolerance parameter establishes the threshold at which the condition is cleared. An SNMP trap
(starCongestionClear) is generated for the clear condition, as well.
Example
The following command configures a system CPU utilization threshold of 75%.
The following command configures a system CPU utilization threshold of 75%.
This setting will remain in configuration unless you specify another threshold value in place of 75. This threshold
setting can be disabled with
setting can be disabled with
command
but can not be removed from configuration. Later if you want to enable the previously configured threshold value of
percent you only need to enter
command
without specifying any threshold value and it will enable the CPU utilization threshold to preconfigured level of
percent.