Extreme Networks EPICenter 6.0, Reference Manual

Page: 136 / 580

The EPICenter Alarm System
EPICenter Reference Guide
136
●
The sample value becomes greater than or equal to the Rising Threshold, after having become less than
or equal to the Falling Threshold (80% of the Rising threshold).
If you define an alarm for CPU Utilization Falling Threshold events, an event is generated each time the
sample value becomes less than or equal to 80% of the Rising Threshold,
after having become greater than
or equal to the Rising Threshold .
It is important to understand that, except for the initial occurrence of a Rising Threshold alarm, a CPU
Utilization alarm is generated
only the when the sample value of the variable crosses the target
threshold for the first time after having crossed the other threshold.
The startup condition for a CPU Utilization event is always predefined to be Rising.
See the EPICenter Concepts and Solutions Guide for a more detailed explanation of Threshold-based
alarms, including examples of CPU Utilization events.
Configuring Rules for the Predefined RMON Event Types
NOTE
When you modify a Port Utilization, Temperature or Topology Change rule, you can modify all the fields available for
general RMON Rules. See
“Configuring an RMON Rule” on page 133 for the details on the fields you can change.
The Port Utilization, Temperature, and Topology Change configuration types are actually RMON
utilization rules with a predefined configuration interface. The New Configuration and Modify
Configuration windows are the same of the Configuration windows for a CPU Utilization event, (see
Figure 59 ), except that you must provide a name for the rule.
NOTE
STP Topology Change traps are only supported on switches running ExtremeWare 6.2.2 or later.
The fields in this window are defined as follows:
The Falling Threshold is automatically defined as 90% of the rising threshold value.
Rule Name The name for this rule. For these events, this is user-defined.
Rising Threshold A threshold value that triggers a trap event when the value of relevant variable rises past this
value. The thresholds are specified based on the configuration type as follows:
• Port Utilization
—
A threshold value, in 100ths of a percent, that triggers an event when
the port utilization rises past this value.
• Temperature
—
A threshold value, in degrees celsius, that triggers an Overheat event when
the temperature rises past this value.
• Topology Change
—
An integer threshold value that triggers a topology change event when
the total number of topology changes seen by this device since the management entity
was last reset or initialized, rises past this value.
Description The description of the relevant MIB variable for the selected rule type.