Setting Ridgeline As A Trap Receiver; The Ridgeline Third-Party Device Integration Framework - Extreme Networks Ridgeline Guide Manual

Concepts and solutions guide
Hide thumbs Also See for Ridgeline Guide:
Table of Contents

Advertisement

Book Title

Setting Ridgeline as a Trap Receiver

When Extreme devices are added to the Ridgeline inventory, they are automatically configured to send
traps to the Ridgeline 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 Ridgeline server.
The information required to set up Ridgeline as a trap receiver is the following:
The IP address of the system where the Ridgeline server is running.
The Ridgeline server trap port. By default this is 10550. (This is set in the properties file
extreme.properties
The Ridgeline 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 Ridgeline server is
equivalent by doing the following:
a Convert each quad of the IP address to its hex equivalent:
Decimal
Hex
10
a
0
00
4
04
1
01
b Convert the hex value
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 Ridgeline, and using the ExtremeWare CLI command
to display the list of trap receivers configured for that device. The Ridgeline
show management
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
The Ridgeline Third-party Device Integration
Framework
Ridgeline's third-party device integration framework provides a generic mechanism for adding
third-party device support with a minimum of configuration changes. While Ridgeline has always been
able to discover any device running an agent that supports MIB-2, the functionality provided was
minimal.
The Ridgeline integration framework enables more extensive support:
Basic feature support, including front and back panel views if available
Third-party device trap support
310
, found in the
<Ridgeline_installdir>/extreme.war
into a decimal value, in this case
a000401
subdirectory).
, you would calculate the decimal
10.0.4.1
167773185
.
enable rmon
Ridgeline Concepts and Solutions Guide

Advertisement

Table of Contents
loading

This manual is also suitable for:

Ridgeline 3.0

Table of Contents