Extreme Networks EPICenter 4.1, Руководство по установке программного обеспечения

Страница: 148 / 546

148 EPICenter Software Installation and User Guide
The EPICenter Alarm System
Note that in order to have any of these events cause an alarm in the EPICenter Alarm System, you need
to define an alarm that responds to a CPU Utilization Rising Threshold or CPU Utilization Falling
Threshold event.
• If you define an alarm based on the CPU Utilization Rising Threshold event, an EPICenter alarm will
occur at the initial sample, and at points A and C. Because the alarm was defined to respond to CPU
Utilization Rising Threshold events, the falling threshold trap events that occur at points X and Y do
not trigger an EPICenter alarm.
• If you also define an alarm based on a CPU Utilization Falling Threshold event, then EPICenter
alarms would be generated at points X and Y.
Rule Configuration for the Predefined RMON Event Types
The Port Utilization, Temperature and Topology Change configuration types are actually RMON
utilization rules with a predefined configuration interface. The New Configuration window is the same
(see Figure 61), 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:
• Rule Name: The name for this rule. For these events, this is user-defined.
• Rising Threshold:
A threshold value that will trigger 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 will trigger an event when the
port utilization rises past this value.
— Temperature — A threshold value, in degrees celsius, that will trigger an Overheat event when
the temperature rises past this value.
— Topology Change — An integer threshold value that will trigger 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.
For these rules, like a CPU utilization rule, the falling threshold is automatically defined based on
the value of the rising threshold. The falling threshold is set to be 90% of the rising threshold value.
• Description: The description of the relevant MIB variable for the selected rule type.
The other parameters that you can set when you configure an RMON event, are predefined in the
Extreme switch agent for these three events. These are:
• MIB Variable : The MIB variable is predefined to be one of the following:
— For Port utilization:
extremeRtStatsUtilization.0
— For Temperature:
extremeCurrentTemperature.0
—
For Topology Change:
dot1dStpTopChanges.0
• Falling Threshold : This is predefined as 90% of the rising threshold.
• Startup Alarm : The Startup condition is predefined to be Rising or falling.
• Sample Interval: The sample interval is also predefined, and is set to 15 seconds.
• Sample Type : The sample value is an absolute value.