Specifications

Book Title
Ridgeline Concepts and Solutions Guide
312
XML files for third-party devices extend and further specify properties unique to each device type and
device. Extreme Networks devices are also recognized through this same ATL mechanism. When
Ridgeline discovers a device, it searches this hierarchy for a match to the device or device type that will
provide the properties for the device.
Figure 252: ATL XML file hierarchy
The 3COM SuperStacker II 1000 is an example of how a third-party device is integrated into Ridgeline
for Telnet functionality.
There are actually three 3COM devices integrated into Ridgeline, all of which share a number of
properties. Therefore, these properties are specified in the
3com.xml file, which is referenced as the
parent in the
3Com_SuperstackerII_1100.xml file.
The key attributes in an ATL XML file are the following:
Table 9: Attributes Used in an ATL File
TAG Attribute Value
Device Type Name The name of the device type of the device. This is the main Tag
in the file.
Version Must be specified as “1”
Parent The parent XML file. For an individual device model, this may be
the device type XML file (e.g. in the
3Com_SuperstackerII_1100.xml file, the parent is “3Com.xml”).
For a device type XML file, such as the 3COM.xml file, the
parent is “3rdParty.xml”.
Identity Contains the sysObjectId tag
All Devices
3rd Party.xml
Extreme.xml
Extreme
Summit Unmanaged
Extreme
Summit _ 48.xml Summit _ WM.xml
Summit _ WM_100.xml
3Com.xml
3Com_SuperStackerII_1100.xml
Summit _ WM_1000.xml
etc.
etc.
etc.
etc.