Extreme Networks EPICenter Guide User Manual

Configuring Devices for Use With EPICenter
EPICenter Concepts and Solutions Guide
196
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.
● The EPICenter server trap port. By default this is 10550. (This is set in the properties file
extreme.properties, found in the <EPICenter_installdir>/extreme.war subdirectory).
● The EPICenter server community string. This is a string in the form:
ST.<value of IP address>.<value of trap port>
The value of the IP address is the decimal equivalent of the hex value of the IP address.
For example, if the IP address of the EPICenter server is
10.0.4.1, you would calculate the decimal
equivalent by doing the following:
a Convert each quad of the IP address to its hex equivalent:
b Convert the hex value
a000401 into a decimal value, in this case 167773185
c Put the three components together to form the community string:
ST.167773185.10550
You can find and verify the value of the community string by using Telnet to log into an Extreme
Networks device that is being managed by EPICenter, and using the ExtremeWare CLI command
show management to display the list of trap receivers configured for that device. The EPICenter
server, and its community string, should be included in this list.
To receive RMON traps, you need to ensure that RMON is enabled on the device. For Extreme devices,
you can do this through the ExtremeWare CLI with the command
enable rmon.
The EPICenter Third-party Device Integration Framework
EPICenter’s third-party device integration framework (available in EPICenter 6.0 and later) provides a
generic mechanism for adding third-party device support with a minimum of configuration changes.
While EPICenter has always been able to discover any device running an agent that supports MIB-2, the
functionality provided was minimal: generic information in the Inventory applet, display on the
topology map, basic MIB-2 traps, and limited interactive Telnet support.
The EPICenter integration framework enables more extensive support:
● Basic feature support, including front and back panel views if available, in the Inventory Manager
● Third-party device trap support
Decimal Hex
10 a
0 00
4 04
1 01

Extreme Networks EPICenter Guide Specifications

General

Brand	Extreme Networks
Model	EPICenter Guide
Category	Software
Language	English