Using The Ridgeline Alarm Manager; Predefined Alarms - Extreme Networks Ridgeline Guide Manual

Using the Ridgeline Alarm Manager

The Ridgeline Alarm Manager provides fault detection and alarm handling for the network devices
monitored by Ridgeline. This includes Extreme devices as well as some third-party devices—those that
Ridgeline can include in its database.
The Alarm Manager provides a set of predefined, enabled alarms that will immediately report
conditions such as authentication or login failures, device problems such as power supply or fan
failures, reachability problems, or device reboots. You can also define your own alarms that will report
errors under conditions you specify, such as repeated occurrences or exceeding threshold values. You
can specify the actions that should be taken when an alarm occurs, and you can enable and disable
individual alarms.
Fault detection is based on SNMP traps, syslog messages, and some limited polling. The Alarm
Manager supports SNMP MIB-2, the Extreme Networks private MIBs, RMON traps, and selected traps
from other MIBs. When an alarm occurs you can specify actions such as sending e-mail, running a
program, running a script, sending a page or sounding an audible alert. You can also forward the trap
to another trap receiver.
To view alarms in Ridgeline, expand the list of folders under Network Administration, and click Alarm
Manager.

Predefined Alarms

For convenience, the Ridgeline Alarm Manager provides a number of predefined alarms. These alarms
are enabled by default and are active as soon as the Ridgeline server starts up. These include the
following alarms:
Authentication failure (SNMP MIB-2 trap)
●
Config Upload Failed (Ridgeline event, indicates failure in an upload initiated by Ridgeline)
●
Device reboot (Ridgeline event)
●
Device Warning from Ridgeline (Ridgeline event)
●
ESRP State Changed (Extreme proprietary trap)
●
Fan failure (Ridgeline event)
●
Health Check Failed (Extreme proprietary trap)
●
Invalid login (Extreme proprietary trap)
●
Overheat (Ridgeline event)
●
Power Supply Failed (Ridgeline event)
●
Rogue Access Point Found (Ridgeline event)
●
Redundant Power Supply (RPS) alarm condition (Extreme proprietary trap)
●
SNMP unreachable (Ridgeline event)
●
NOTE
When Extreme Networks devices are added to the Ridgeline, they are automatically configured to send
traps to the Ridgeline 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 Ridgeline server. See
Ridgeline Concepts and Solutions Guide
2
"Configuring Devices
45