Disabling Unnecessary Alarms - Extreme Networks Ridgeline Guide Manual

Tuning and Debugging Ridgeline
and scoped on all devices. Therefore, tuning the alarm system can have a significant impact on the
overall performance of the Ridgeline server.
The steps you can take to help tune your Ridgeline server's alarm system involve the following types of
actions:
Disabling alarms you don't care about
●
Scoping alarms so they only function on for devices you care about
●
Identifying individual devices that generate a lot of alarm activity, and either correcting the situation
●
that may be producing these alarms, or removing the device from the scope of alarms that aren't
necessary for the device.

Disabling Unnecessary Alarms

There are several situations where you may want to disable alarms that are unnecessary and are
consuming system resources.
One immediate place to look is at the alarms that are predefined within Ridgeline. The following set of
alarms are predefined in the Ridgeline database, and all are enabled by default, scoped for all devices
and ports:
Authentication failure (SNMP MIB-2 trap)
●
Config Download Failed (Ridgeline event, indicates failure in an download initiated by Ridgeline)
●
Config Upload Failed (Ridgeline event, indicates failure in an upload initiated by Ridgeline)
●
Device reboot (Ridgeline event)
●
Device Warning from Ridgeline (Ridgeline event)
●
EAPS State Change-Error (Ridgeline event)
●
EAPS State Change-Warning (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)
●
Stack Member down (Ridgeline event)
●
Stacking Link down (Ridgeline event)
●
If there are any of these alarms that you know are not of interest, you can disable the alarm as a whole
through the Alarm Log Browser. For example, if you are not concerned about SNMP security you can
disable the Authentication Failure alarm. If your network connectivity tends to be problematic or you
have very slow devices, you may want to disable the SNMP unreachable alarm.
218
Ridgeline Concepts and Solutions Guide