User guide

5-38 ExtremeWare EPICenter Software Installation and User Guide
The EPICenter Alarm System
6 The Synchronize functiondisplays a dialog box withstatus or error information.Click
OK to continue.
7 Click Close to exit the Synchronize RMON Rules window.
Configuring Other SNMP Trap Events
There are a number of SNMP events that require configuration on the switch before they
can be used in EPICenter alarm definitions. If the configuration is not done on the switch,
no trap events are generated, and therefore no EPICenter alarms for those events will
occur. The Ping and OSPF traps fall into this category.
To configure the switch to send one of these traps, you must use a tool that allows you to
set the value of the appropriate SNMP variable. Tools such as SNMPc can be used to
perform this function. The following information assumes that you have a thorough
understanding of SNMP and an appropriate SNMP utility.
Refer to the appropriate MIBs for details of the variable settings:
• Ping MIB: pingmib.mib (RFC 2925)
• OSPF v2 MIB: RFC 1850 or RFC 1850t
Setting EPICenter as a Trap Receiver
When Extreme devices are added to the EPICenter inventory, they are automatically
configured to send traps to the EPICenter server. However, third-party devices are not
automatically configured to do so.
If you want alarms to function for third-party devices, you must manually configure the
devices to send traps to the EPICenter server.
The information required to set up EPICenter as a trap receiver is the following:
• The IP address of the system where the EPICenter server is running.
• TheEPICenterservertrapport.By defaultthis is10550.(Thisis set in the propertiesfile
extreme.properties,foundinthe<epicenter_installdir>/extreme
subdirectory).
• The EPICenter server community string. This is a string in the form:
ST.<value of IP address>.<value of trap port>
The valueof the IP address is the decimalequivalentof the hex valueof the IP address.