Extreme Networks EPICenter Guide Manual page 198

Configuring Devices for Use With EPICenter
XML files in the ATL are organized in a hierarchy, with properties of the device types and devices
specified at various levels in this hierarchy.
EPICenter discovers a device, it navigates this hierarchy searching for a match that will provide the
properties for the device.
XML files for 3rd-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
EPICenter 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 78: ATL XML file hierarchy
etc.
Extreme
Summit
etc.
Summit_48.xm
Summit_WM_100.xml
The 3COM SuperStacker II 1000 is an example of how a 3rd party device is integrated into EPICenter
for Inventory Manager and Telnet functionality.
There are actually three 3COM devices integrated into EPICenter, all of which share a number of
properties. Therefore, these properties are specified in the
parent in the
The key attributes in an ATL XML file are the following:
Table 8: Attributes Used in an ATL File
TAG
Device Type
198
Extreme.xml
Extreme
Unmanaged
l
Summit_WM.xml
Summit_WM_1000.xml
3Com_SuperstackerII_1100.xml
Attribute
Name
Version
Figure 78 shows portions of the general hierarchy. When
All Devices
3Com.xml
etc.
etc.
3Com_SuperStackerII_1100.xml
3com.xml
file.
Value
The name of the device type of the device. This is the main Tag
in the file.
Must be specified as "1"
3rd Party.xml
Avaya.xml
AvayaIPPhone.xml
etc.
AvayaIPPhone_4610.xml
file, which is referenced as the
EPICenter Concepts and Solutions Guide
etc.
etc.
etc.