Alarm System
EPICenter Concepts and Solutions Guide
173
Alarm System
Problem: Device is in a fault state that should generate a trap or syslog message, and an alarm is
defined to detect it, but the alarm does not appear in the EPICenter Alarm Log.
There are several possible reasons this can occur. Check the following:
•
Make sure that the alarm is defined and enabled.
•
Check that the device is in your alarm scope.
•
Check that SNMP traps are enabled on the device.
•
For a non-Extreme Networks device, make sure you have set EPICenter as a trap receiver on the device
(see Chapter 8).
•
For an RMON alarm, make sure you have RMON enabled on the device.
•
For Syslog messages, make sure that you have the EPICenter Syslog server enabled, and that remote
logging is enabled on the device with EPICenter set as a Syslog receiver.
•
The number of traps being received by the EPICenter server may exceed the number of traps it can
handle in a given time period, resulting in some traps being dropped (see the item on dropping traps
on page 170). You can change the limits for the number of traps the server should accept (per minute
and per 1/2 minute) in the Administration applet. See Chapter 15 in the
EPICenter Reference Guide
for
more information on setting EPICenter server properties.
Problem: The “Email to:” and “Short email to:” fields are greyed-out in the Actions tab of the New
Alarm Definition dialog.
You need to specify an e-mail server in order to send e-mail. Click the
Settings...
button next to the
to
field to set up your mail server.
Problem: An RMON rule is defined to monitor a counter variable, and to cause an alarm when the
counter exceeds a certain value. The counter has exceeded the threshold value but no alarm has
occurred.
There are several things to check:
•
Make sure the RMON rule and the alarm definition are set up correctly
•
If the value of the counter was already above the threshold value when you set up the RMON rule, and
you have the Sample Type set to Absolute, no alarm will ever be generated. This because the value
must fall below the Falling Threshold value before the before another Rising Threshold trap will be
sent, and this will never occur. You should consider using the Delta Sample Type instead.
Problem: When creating an RMON rule in the RMON Rule Configuration window, the MIB variable
I want to use is missing from the list of variables displayed when I click “Lookup...”
The MIB Variable list displays only the MIBs shipped with the EPICenter software. In addition, within
those MIBs the variable list will not display variables that are indexed by an index other than (or in
addition to) ifIndex. You can still use variables that do not appear in the Lookup... list, but you must type
the complete OID into the MIB Variable field, in numeric notation. If the variable is a table variable, you
will need to append the specific index and apply the variable to each target device, one at a time.
Summary of Contents for EPICenter 5.0
Page 12: ...12 EPICenter Concepts and Solutions Guide Preface...
Page 76: ...76 EPICenter Concepts and Solutions Guide Managing your Network Assets...
Page 92: ...92 EPICenter Concepts and Solutions Guide Managing VLANs...
Page 116: ...116 EPICenter Concepts and Solutions Guide Managing Wireless Networks...
Page 146: ...146 EPICenter Concepts and Solutions Guide VoIP and EPICenter Avaya Integrated Management...
Page 163: ...Appendices...
Page 164: ......
Page 178: ...178 EPICenter Concepts and Solutions Guide Troubleshooting...
