Extreme Networks EPICenter 6.0, Reference Manual

Page: 118 / 580

The EPICenter Alarm System
EPICenter Reference Guide
118
Event Types
EPICenter alarms can be triggered by SNMP traps, RMON rising or falling traps, EPICenter events, or
Syslog messages.
An EPICenter event is generated by EPICenter based on the results of its periodic polling. In some cases,
a condition that causes an EPICenter event may also generate an SNMP or other trap. Creating an alarm
triggered by an EPICenter event guarantees that the condition is eventually detected by polling even if
the corresponding trap is missed.
See Appendix A , “Event Types for Alarms” for a description of the EPICenter and SNMP events
supported by the EPICenter Alarm System.
SNMP traps are notifications from a device of events that occur on a device. EPICenter must be
configured as a trap receiver on the device in order to be notified of these events; this happens
automatically on Extreme devices. Certain SNMP events may require additional configuration on the
switch in order to enable specific trap conditions.
RMON Trap Rising and RMON Trap Falling events are triggered by RMON or CPU utilization traps.
RMON events, including Port utilization, temperature, or STP topology change events, and events
based on CPU utilization, are defined through the
Threshold Configuration page of the EPICenter
Alarm System (see “Threshold Configuration” on page 127 ). RMON event rules can be configured only
on switches running ExtremeWare 6.1 or later. CPU Utilization rules can only be configured on switches
running ExtremeWare 6.2 or later.
NOTE
RMON must be enabled on the switch in order for RMON trap events to be generated.
Syslog messages may also be used to trigger alarms. To receive Syslog messages, the Syslog receiver
function of EPICenter must be enabled, and remote logging must be enabled with EPICenter configured
as a Syslog receiver on the devices from which you want to receive Syslog messages. See the
EPICenter
Concepts and Solutions Guide for information about configuring devices to use EPICenter as a Syslog
server. Syslog messages received from devices not managed by EPICenter are ignored.
For certain other events, you must do the configuration on the switch using an SNMP configuration tool
such as SNMPc. See the
EPICenter Concepts and Solutions Guide for more information.
Table 10: EPICenter Alarm Variables
Variable Name Description
alarmID An integer number assigned by the EPICenter Alarm System based on the order in
which the alarm occurred
alarmName The name of the alarm as defined in the Name field
alarmCategory The user-defined alarm category assigned to the alarm
alarmSeverity The severity level assigned to the alarm
alarmRepeatTimes The number of times the event must occur before an alarm is generated
alarmRepeatPeriod The time frame within which the repeated events must occur for the alarm to be
generated
alarmSourceDeviceName The name of the device on which the event(s) occurred (taken from the EPICenter
database)
alarmSourceIP The IP address of the device on which the event(s) occurred