Cisco Cisco Packet Data Interworking Function (PDIF)
Global Configuration Mode Commands (T-threshold phspc)
▀ threshold cpu-session-throughput
▄ Command Line Interface Reference, StarOS Release 16
5498
threshold cpu-session-throughput
Configures alarm or alert thresholds for CPU session throughput within 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
threshold cpu-session-throughput high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold session throughput that must be met or exceeded within the polling interval to
generate an alert or alarm.
Specifies the high threshold session throughput that must be met or exceeded within the polling interval to
generate an alert or alarm.
high_thresh
is measured in kilobytes per second (Kbps) and is an integer from 0 through 1000000000. A
value of 0 disables the threshold.
clear
low_thresh
Default: 0
Specifies the low threshold session thereabout that maintains a previously generated alarm condition. If the
throughput falls below Specifies the low threshold within the polling interval, a clear alarm will be generated.
Specifies the low threshold session thereabout that maintains a previously generated alarm condition. If the
throughput falls below Specifies the low threshold within the polling interval, a clear alarm will be generated.
low_thresh
is measured in kilobytes per second (Kbps) and is an integer from 0 through 1000000000. A
value of 0 disables the threshold.
Important:
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm
model, the system assumes it is identical to the high threshold.
Usage
CPU session throughput thresholds generate alerts or alarms based on total throughput for all Session
Manager tasks running on each packet processing card CPU during the polling interval. Although, a single
threshold is configured for all CPUs, separate alerts or alarms can be generated for each CPU.
Alerts or alarms are triggered for CPU session throughput based on the following rules:
Manager tasks running on each packet processing card CPU during the polling interval. Although, a single
threshold is configured for all CPUs, separate alerts or alarms can be generated for each CPU.
Alerts or alarms are triggered for CPU session throughput based on the following rules:
Enter condition: Actual CPU session throughput is greater than or equal to the high threshold.
Clear condition: Actual CPU session throughput is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end
of the polling interval.
of the polling interval.