Cisco Cisco ASR 5000
Global Configuration Mode Commands (T-threshold phspc)
▀ threshold monitoring
▄ Command Line Interface Reference, StarOS Release 18
5708
saegw-service
Enables threshold monitoring for SAEGW services.
Refer to the
Refer to the
threshold total-saegw-sessions
for more information on SAEGW thresholds.
sess-flow-count
Enables threshold monitoring for Session Flow Count.
Default: 90%
Refer to the
Default: 90%
Refer to the
threshold sess-flow-count
for more information on Session Flow Count Thresholds
sgw-service
Enables threshold monitoring for S-GW services.
Refer to the
Refer to the
threshold total-sgw-sessions
for more information on S-GW thresholds.
subscriber
Enables threshold monitoring for the subscriber and session values.
Refer to the
Refer to the
threshold subscriber active
,
threshold subscriber total,
threshold total-
ggsn-sessions
,
threshold total-gprs-sessions, threshold total-gprs-pdp-sessions,
threshold total-ha-sessions, threshold total-lns-sessions, threshold total-pdsn-
sessions, threshold total-pgw-sessions, threshold total-sgw-sessions,
sessions, threshold total-pgw-sessions, threshold total-sgw-sessions,
threshold
total-saegw-sessions, threshold total-sgsn-sessions
,
threshold total-sgsn-pdp-
sessions
,
threshold per-service-ggsn-sessions
,
threshold per-service-ha-sessions
,
t
hreshold per-service-lns-sessions
, and
threshold per-service-pdsn-sessions
commands
for additional information on these values.
system
Enables system (chassis) thresholds monitoring.
Usage
Thresholding on the system is used to monitor the system for conditions that could potentially cause errors or
outage. Typically, these conditions are temporary (i.e high CPU utilization, or packet collisions on a network)
and are quickly resolved. However, continuous or large numbers of these error conditions within a specific
time interval may be indicative of larger, more severe issues. The purpose of thresholding is to help identify
potentially severe conditions so that immediate action can be taken to minimize and/or avoid system
downtime.
Thresholding reports conditions using one of the following mechanisms:
outage. Typically, these conditions are temporary (i.e high CPU utilization, or packet collisions on a network)
and are quickly resolved. However, continuous or large numbers of these error conditions within a specific
time interval may be indicative of larger, more severe issues. The purpose of thresholding is to help identify
potentially severe conditions so that immediate action can be taken to minimize and/or avoid system
downtime.
Thresholding reports conditions using one of the following mechanisms:
SNMP traps: SNMP traps have been created that indicate the condition (high threshold crossing and/or
clear) of each of the monitored values. Complete descriptions and other information pertaining to
these traps is located in the starentMIB(8164).starentTraps(2) section of the SNMP MIB Reference.
these traps is located in the starentMIB(8164).starentTraps(2) section of the SNMP MIB Reference.
The generation of specific traps can be enabled or disabled on the system allowing you to view only those
traps that are most important to you.
traps that are most important to you.
Logs: The system provides a facility called threshold for which active and event logs can be generated.
As with other system facilities, logs are generated Log messages pertaining to the condition of a
monitored value are generated with a severity level of WARNING.
monitored value are generated with a severity level of WARNING.
Alarm System: High threshold alarms generated within the specified polling interval are considered
“outstanding” until a the condition no longer exists and/or a condition clear alarm is generated.
“Outstanding” alarms are reported to through the system’s alarm subsystem and are viewable through the
CLI.
CLI.