Extreme Networks EPICenter 5.0, Manual

Page: 120 / 208

120 EPICenter Concepts and Solutions Guide
Tuning and Debugging EPICenter
Tuning the Alarm System
Alarm activity (processing traps and executing alarm actions) can consume a fairly significant amount
of system resources if you have a large number of devices in your network, with many alarms enabled
and scoped on all devices. Therefore, tuning the alarm system can have a significant impact on the
overall performance of the EPICenter server.
The steps you can take to help tune your EPICenter 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 EPICenter. The following set of
alarms are predefined in the EPICenter database, and all are enabled by default, scoped for all devices
and ports:
• Authentication failure (SNMP MIB-2 trap)
• Config Upload Failed (EPICenter event, indicates failure in an upload initiated by EPICenter)
• Device reboot (EPICenter event)
• Device Warning from EPICenter (EPICenter event)
• ESRP State Changed (Extreme proprietary trap)
• 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)
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.
To disable an alarm you must modify its alarm definition:
1 Go to the Alarm Definition tab in the Alarm System, and select the alarm you want to disable
2 Click the Modify button in the upper Toolbar to open the Alarm Modify Definition window with
the selected alarm definition displayed.