Specifications

Ridgeline Concepts and Solutions Guide
313
The following are examples of the
3Com_SuperstackerII_1100.xml file and its parent, 3Com.xml.
The
3Com.xml file:
<?xml version="1.0" encoding="utf-8" ?>
<deviceType name="3Com"
version="1"
parent="3rd Party">
<identity>
<sysObjectID protocol="SNMP">43</sysObjectID>
</identity>
<attributes>
<vendor>3Com</vendor>
<imageIconsFileName>3comicons.gif</imageIconsFileName>
<CLI.LOGIN_PROMPT> login: </CLI.LOGIN_PROMPT>
<CLI.PASSWORD_PROMPT> password: </CLI.PASSWORD_PROMPT>
<CLI.SHELL_PROMPT> [#>$] </CLI.SHELL_PROMPT>
<CLI.MORE_PROMPT> Press|to continue or|to quit: </CLI.MORE_PROMPT>
</attributes>
</deviceType>
The 3Com_SuperstackerII_1100.xml file:
<?xml version="1.0" encoding="utf-8" ?>
<deviceType name="Super Stacker II 1100"
version="1"
parent="3Com">
<identity>
<sysObjectID protocol="SNMP">43.10.27.4.1.2.1</sysObjectID>
</identity>
<attributes>
<TELNET> true </TELNET>
</attributes>
</deviceType>
Note that in the 3Com.xml file, the sysObjectID is the enterprise OID for 3COM; in the
3Com_SuperstackerII_1100.xml file, it is the OID of the specific 3Com device. Many of the attributes
in the 3Com.xml file are related to integration into Telnet. These are discussed in “Telnet Integration” on
page 315.
SysobjectID The OID value of the device, or the enterprise OID (if a device
type)
Protocol Use SNMP as the default value
Attributes This contains the properties that define the features and
capabilities of the third-party device, such as enabling Telnet.
These are described later in this section.
ImageIconsFilename Provides the name of the image that is displayed in the
navigation frame for the device. This image must be present in
the dpsimages.zip file found in the extreme.war/gifs directory.
Vendor Device vendor name.
Table 9: Attributes Used in an ATL File (continued)
TAG Attribute Value