Extreme Networks EPICenter Guide User Manual

Configuring Devices for Use With EPICenter
EPICenter Concepts and Solutions Guide
198
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. Figure 78 shows portions of the general hierarchy. When
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
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
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 8: 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”
All Devices
3rd Party.xml
Extreme.xml
Extreme
Summit Unmanaged
Extreme
Summit _ 48.xml Summit _ WM.xml
Avaya.xml
AvayaIPPhone.xml
Summit _ WM_100.xml
3Com.xml
AvayaIPPhone_4610.xml
3Com_SuperStackerII_1100.xml
Summit _ WM_1000.xml
etc.
etc.
etc.
etc.
etc.
etc.
etc.
etc.

Extreme Networks EPICenter Guide Specifications

General

Brand	Extreme Networks
Model	EPICenter Guide
Category	Software
Language	English