Alarm System - Extreme Networks EPICenter Guide Manual

Troubleshooting
Problem: Configuration fails when attempting to configure a VLAN with a modified protocol
definition.
EPICenter does not have a mechanism to modify protocols. When a VLAN is configured through
EPICenter to use a protocol that does not exist on the switch, the protocol is first created on the switch.
However, if a protocol with the same name but a different definition already exists on the switch, the
operation will fail.
Problem: An untagged port has disappeared from its VLAN.
Check to see if the port has been added as an untagged port to a different VLAN. In EPICenter, adding
an untagged port to a VLAN automatically removes the port from its previous VLAN if the port was
untagged, and the new and old VLANs used the same protocol. You should receive a warning message
when this happens, which lets you proceed with the auto-deletion or cancel the operation. This is
different behavior from the ExtremeWare CLI, where you must first delete the port from the old VLAN
before you can add it to the new VLAN.

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 the alarm scope.
●
Check that SNMP traps are enabled on the device.
●
For a non-Extreme device, make sure you have set EPICenter as a trap receiver on the device (see
●
Appendix B "Configuring Devices for Use With
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
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
Email 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
●
188
185). You can change the limits for the number of traps the server should accept (per
EPICenter").
EPICenter Concepts and Solutions Guide