Using the EPICenter Alarm System
EPICenter Concepts and Solutions Guide
43
● Fan failure (EPICenter event)
● Health Check Failed (Extreme proprietary trap)
● Invalid login (Extreme proprietary trap)
● Overheat (EPICenter event)
● Power Supply Failed (EPICenter event)
● Rogue Access Point Found (EPICenter event)
● Redundant Power Supply (RPS) alarm condition (Extreme proprietary trap)
● SNMP unreachable (EPICenter event)
NOTE
When Extreme Networks devices are added to the EPICenter Inventory database, they are automatically configured to
send traps to the EPICenter server (unless you are running in non-intrusive Mode). To receive traps from non-
Extreme devices, you must manually configure those devices to send traps to the EPICenter server. See “Setting
EPICenter as a Trap Receiver” on page 196 for information on registering EPICenter as a trap receiver on non-
Extreme devices.
The Alarm Log Browser
You use the Alarm Log Browser to view a summary of the alarms that have occurred among the
devices you are managing. An alarm can be generated due to an SNMP or RMON trap, a syslog
message, or based on the results of a poll. By default, all the predefined alarms are enabled; therefore,
you may see alarm log entries the first time you display the Alarm Browser, even if you have not
defined any alarms of your own.