Alarm Integration; Editing The Events.xml File - Extreme Networks Ridgeline Guide Manual

Book Title
</deviceType>
Note that in the case of 3COM, the Telnet integration is handled at the device type level, since it is the
same for all the 3COM devices. Therefore, it is not duplicated in each device ATL XML file, but
handled one at the device type (enterprise) level.

Alarm Integration

Alarm Integration for a third-party device will enable Ridgeline users to create Alarms based on trap
events from the third-party device. There are five steps to integrating third-party alarms:
1 The trap OID for each event must be added to the
2 The necessary MIBs must be placed in the
3 The third-party MIB filenames must be specified in the
directory
4 Restart the Ridgeline server
5 Each third-party device must be configured to send traps to Ridgeline. See
Trap Receiver" on page 310
Once this is done, the third-party event(s) should be selectable from the Event Name drop down list on
the Basic tab of the Alarm Definition Window (in the Alarm Manager). Alarms can then be defined to
take actions upon the occurrence of these events.

Editing the Events.xml file

CAUTION
Make a backup copy of this file before you start, and edit carefully. Do not edit the existing entries in this
file. Errors in this file may prevent the Ridgeline server from starting up.
The file is located in the
Events.xml
composed of the Type, SubType, TypeName and SubTypeName, followed by a SNMP V1 or V2
Mapping OID.
Table 11: Components of the an Events.xml event entry
Attribute Value(s)
Type A non-negative number for a
SNMP v1 trap (same as the
generic type value of the v1 trap)
-2 for an SNMP v2 trap
-3 for a syslog event
-1 for an Ridgeline event
SubType For v1 traps, this should be the
same as the specific type value
For syslog events, this should be
the same as the priority value of
the syslog message.
TypeName SNMP trap, Ridgeline, or syslog
316
events.xml
extreme.war/thirdPartyMibs
for information on how to accomplish this.
directory. Each event entry in the
extreme.war
file
directory
file in the
miblist.txt
"Setting Ridgeline as a
Comments
Identifies the type of event (SNMP v1 or v2 trap or
and Ridgeline or syslog event.
A trap that can be sent as either a v1 or v2 trap
should be represented as v1 trap.
Together with the Type, uniquely identifies an event.
The type of the event. For third-party integration this
would be SNMP trap.
Ridgeline Concepts and Solutions Guide
extreme.war
file is
Events.xml