12.07.2015 Views

Version 3.1 SP2 Reference Guide - Extreme Networks

Version 3.1 SP2 Reference Guide - Extreme Networks

Version 3.1 SP2 Reference Guide - Extreme Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

AppendixThe Ridgeline integration framework enables more extensive support:●●●Basic feature support, including front and back panel views if availableThird-party device trap supportLaunching of third-party proprietary device-related toolsThrough this framework, integration of third-party devices can be accomplished independently ofRidgeline product releases. The integration is achieved by adding or editing XML, text and images filesto accomplish different levels of integration.Each aspect of device integration can be performed independently; that is, you can integrate a deviceinto Ridgeline but may elect not to integrate trap support in the Alarm System, for example.CAUTIONThe device integration process may require editing of certain Ridgeline files that can affect the functionalityof the Ridgeline server. In some cases, editing these files incorrectly may prevent the Ridgeline server from running.It is strongly recommended that device integration be undertaken only under the supervision of <strong>Extreme</strong> <strong>Networks</strong>support personnel.Ridgeline Inventory IntegrationThe basic features of Ridgeline inventory integration include:●●●●The ability to discover the device when the MIB-2 option in Discovery is selectedThe device image can be viewed (front panel, and back panel if appropriate)Device information like OID, device name, IP address, MAC address, device type, device groupshould be presentedShould be able to modify the device contact username and password from Ridgeline.To accomplish this integration, there are three basic steps:1 Create an Abstract Library Type (ATL) file (an XML file) and save it in thedeploy/extreme.war/ATL/Device Types directory.2 Create a folder in the deploy/extreme.war/gifs directory which is named with theOID of the new Device Type.3 Create gif-format (Compuserve Graphics Interchange Format) images for the device, and place thesein the OID folder created under the deploy/extreme.war/gifs directory.4 Create a “deviceInfo.txt” file for the device and place this in the OID folder created under thedeploy/extreme.war/gifs directory.5 If it does not already exist, create a device icon gif file, named to match the file name provided in theimageIconsFileName tag in the ATL XML file, and add this to the dpsimages.zip file (found in thedeploy/extreme.war/gifs directory.The Abstract Type Library XML fileThe Abstract Type Library is a repository for information about the types of devices Ridgeline canrecognize. For each device type, an XML file is placed in the deploy/extreme.war/ATL/Device Typesdirectory. (There are also ATL subdiretories for Interface Types and Slot Types).Ridgeline <strong>Reference</strong> <strong>Guide</strong>665

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!