Cisco Cisco Packet Data Gateway (PDG)
SaMOG Gateway Overview
Features and Functionality - Base Software ▀
SaMOG Administration Guide, StarOS Release 16 ▄
27
Threshold Crossing Alerts (TCA) Support
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 util ization, 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.
Typically, these conditions are temporary (i.e high CPU util ization, 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.
The system supports Threshold Crossing Alerts for certain key resources such as CPU, memory, IP pool addresses, etc.
With this capability, the operator can configure threshold on these resources whereby, should the resource depletion
cross the configured threshold, a SNMP Trap would be sent.
With this capability, the operator can configure threshold on these resources whereby, should the resource depletion
cross the configured threshold, a SNMP Trap would be sent.
The following thresholding models are supported by the system:
Alert:A value is monitored and an alert condition occurs when the value reaches or exceeds the configured high
threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of
the polling interval.
the polling interval.
Alarm:Both high and low threshold are defined for a value. An alarm condition occurs when the value reaches
or exceeds the configured high threshold within the specified polling interval. The alert is generated then
generated and/or sent at the end of the polling interval.
generated and/or sent at the end of the polling interval.
In addition to the existing generic StarOS system level TCA threholds, an SaMOG service session count threshold is
available to check if the total number of subscribers have exceeded the high threshold.
available to check if the total number of subscribers have exceeded the high threshold.
Thresholding reports conditions using one of the following mechanisms:
SNMP traps: SNMP traps have been created that indicate the condition (high threhold crossing and clear) of
each of the monitored values.
Generation of specific traps can be enabled or disabled on the chassis. Ensuring that only important faults get
displayed. SNMP traps are supported in both Alert and Alarm modes.
displayed. SNMP traps are supported in both Alert and Alarm modes.
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.
generated with a severity level of WARNING.
Logs are supported in in both the Alert and the Alarm models.
Alarm System: High threshold alarms generated within the specified polling interval are considered outstanding
until a condition no longer exists or a condition clear alarm is generated. Outstanding alarms are reported to the
systems’s alarm subsystem and are viewable through the Alarm Management menu in the Web Element
Manager.
systems’s alarm subsystem and are viewable through the Alarm Management menu in the Web Element
Manager.
Important:
For more information on threshold crossing alert configuration, refer to the Thresholding
Configuration Guide.