Interpreting the Threshold Editor

Element Type

At the topmost level is the Element Type for which the rule will apply: Interface, Node, Tunnel, CPUStats, LSPPingStats, LatencyStats, PingStats, and SLAStats

• Interface: Rules can be defined in this section for interface-related properties such as bandwidth and ingress and egress utilizations.
• Node: Rules can be defined in this section for node-related properties such as system up time, last up time, aaa, accounting, authentication, and sessions. These additional properties for aaa and sessions which are related to wireless collection data and may or may not apply to all device types.
• Tunnel: Rules can be defined in this section for LSP tunnel-related properties such as the delta in the ingress bytes.
• CPUStats: Rules can be defined in this section for CPU and memory stats such as CPU temperature, CPU utilization, memory used, total memory, and memory utilization.
• LSPPingStats: Rules can be defined in this section for LSP ping stats on average, max, min, and standard deviation values.
• LatencyStats: Rules can be defined in this section for latency stats on average, max, min, and standard deviation values.
• PingStats: Rules can be defined in this section for ping stats on average, max, min, and loss percentage values
• SLAStats: Rules can be defined in this section for SLA stats such as jitter, packet loss, packet timeout, and latency.

Scope

Underneath the element type, the next level is the scope, which defines the group of interfaces for which the threshold rule(s) will be applied to. An include condition can be specified to filter for only interfaces matching some user-specified criteria. An exclude condition can additionally be specified to exclude interfaces with some user-specified criteria. If no fields are specified for the scope, the rules of this scope will be applied to all elements of the given type. For example, a scope can be created underneath the Interface element type that only considers fast ethernet interfaces.

Figure 1: Example of a Threshold Editor Scope

Threshold Rule

Under the scope, are the actual threshold rules themselves. Here, users can specify the production name, the actual rule, a severity level, and a description. For example, the rule can be created to generate a threshold event when the interface utilization exceeds a particular percentage.

Figure 2: Example of a Threshold Editor Rule