EPICenter Reference Guide
101
4
The EPICenter Alarm System
This chapter describes how to use the EPICenter Alarm System applet for:
●
Viewing the alarms that have occurred
●
Defining new alarms and modifying current alarm definitions
●
Configuring threshold-based alarms
Overview of the EPICenter Alarm System
The EPICenter Alarm System provides fault detection and alarm handling for the network devices
monitored by EPICenter. This includes Extreme Networks devices and some third-party devices. The
Alarm System provides a set of predefined, enabled alarms that immediately report conditions such as
authentication or login failures, device problems such as power supply or fan failures, reachability
problems, or device reboots (see
“Predefined Alarms” on page 102
).
The Alarm System also lets you define your own alarms that report errors under conditions you
specify, such as repeated occurrences or exceeding threshold values. You can enable and disable
individual alarms, and you can specify the actions to be taken when an alarm occurs, such as sending e-
mail, running a program, executing a Telnet macro, or sounding an audible alert.
Fault detection is based on Simple Network Management Protocol (SNMP) traps, syslog messages, and
some limited polling. The Alarm System supports SNMP Management Information Base-2 (MIB-2), the
Extreme Networks private MIB, Remote Monitoring (RMON) traps, and selected traps from other MIBs.
For selected third-party devices that have been integrated into EPICenter through it’s device integration
framework, EPICenter can support the full set of traps provided by the device. For other MIB-2
compatible devices, assuming they can be successfully added to EPICenter’s inventory database,
EPIcenter supports just the basic MIB-2 traps.
NOTE
EPICenter automatically configures Extreme Networks devices to send traps to the EPICenter server when those
devices are added to the EPICenter Inventory database; this is not true for non-Extreme Networks devices
—
you must
manually configure those devices to send traps to the EPICenter server.
To receive syslog messages from a device, the device must be configured to use EPICenter as a syslog receiver. This
is true for both Extreme devices and non-Extreme devices.
See the EPICenter Concepts and Solutions Guide for instructions on configuring devices to use EPICenter as a trap
receiver or a Syslog receiver.
Not all trap events are supported in older versions of the ExtremeWare software. Please refer to
Appendix A
,
“Event
Types for Alarms”
for information on the switch software required for specific traps.
Summary of Contents for EPICenter 6.0
Page 14: ...EPICenter Reference Guide 14 ...
Page 18: ...Preface EPICenter Reference Guide 18 ...
Page 19: ...1 EPICenter Basic Features ...
Page 20: ......
Page 24: ...EPICenter Overview EPICenter Reference Guide 24 ...
Page 44: ...Getting Started with EPICenter EPICenter Reference Guide 44 ...
Page 100: ...The Inventory Manager EPICenter Reference Guide 100 ...
Page 140: ...The EPICenter Alarm System EPICenter Reference Guide 140 ...
Page 172: ...Configuration Manager EPICenter Reference Guide 172 ...
Page 196: ...The Firmware Manager EPICenter Reference Guide 196 ...
Page 220: ...The Interactive Telnet Feature EPICenter Reference Guide 220 ...
Page 250: ...The Grouping Manager EPICenter Reference Guide 250 ...
Page 276: ...Real Time Statistics EPICenter Reference Guide 276 ...
Page 342: ...Using the VLAN Manager EPICenter Reference Guide 342 ...
Page 348: ...The ESRP Monitor EPICenter Reference Guide 348 ...
Page 446: ...EPICenter Reports EPICenter Reference Guide 446 ...
Page 447: ...2 Advanced Upgrade Features ...
Page 448: ......
Page 480: ...EAPS Protocol Monitoring and Verification EPICenter Reference Guide 480 ...
Page 508: ...Using the Policy Manager EPICenter Reference Guide 508 ...
Page 525: ...3 Appendices ...
Page 526: ......
Page 542: ...EPICenter Backup EPICenter Reference Guide 542 ...
Page 564: ...Voice over IP Manager EPICenter Reference Guide 564 ...
Page 580: ...EPICenter Reference Guide 580 ...