Specifications

Ridgeline Concepts and Solutions Guide
317
The following is a sample entry for an SNMP V1 trap:
<Event Type="6" SubType="117" TypeName="SNMP Trap" SubTypeName="Cisco config changed">
<SNMP_V1_Mapping OID=".1.3.6.1.4.1.9.9.43.2" Generic="6" Specific="1"/>
</Event>
Adding the MIB(s) to Ridgeline
To incorporate the MIBs into Ridgeline:
1 Place the MIB file(s) into the
extreme.war/thirdPartyMibs directory.
The MIB file name must match the MIB definition name.
The MIB file names do not need to include file extensions. If they do not have file extensions, .mib
will be appended to the file name internally. However, if you do provide an extension, it must be
.mib or .MIB.
2 Add the MIB file names to the
miblist.txt file found in the extreme.war directory.
Add any new entries to the end of the file only, do not add them in between existing entries.
Make sure each entry is unique
Make sure each MIB file name matches the MIB definition name.
You must restart the Ridgeline server to have these changes take effect.
Launching Third Party Applications
Ridgeline can launch an external application for a third-party device under the following conditions:
Ridgeline and the third-party application client and server are installed on the same system
Ridgeline and the third-party client are installed on the same system
Ridgeline is installed on one system, and a remote (web-based) third-party client and server is
installed on a different system.
The third-party application must be added to the
Tool.xml file found in the extreme.war/ATL/Device
Types
directory. The format of the entry in the XML file is as follows (using the Summit WM as an
example):
<?xml version="1.0" encoding="UTF-8"?>
<tools>
<tool oid="Summit WM" description="Summit WM launch tool" name="Launch Summit WM">
<contents>
https://$deviceIP:5825
</contents>
<variable/>
<role roleid="3 2 1"/>
<context type="device"/>
</tool>
</tools>
SubTypeName The name of the specific event,
e.g. “link down”
Together with the Type name, it forms the event
name e.g. “SNMP trap link down”
Table 11: Components of the an Events.xml event entry (continued)
Attribute Value(s) Comments