Configuring Devices for Use With EPICenter
EPICenter Concepts and Solutions Guide
202
The 3Com.xml file provides an example of the prompts used for Telnet integration:
<?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>
<TELNET_MACROS> true </TELNET_MACROS>
</attributes>
</deviceType>
Note that in the case of 3COM, the Telnet integration is handled at the device type level, since it is the
same for all the 3COM devices. Therefore, it is not duplicated in each device ATL XML file, but
handled one at the device type (enterprise) level.
Alarm Integration
Alarm Integration for a 3rd party device will enable EPICenter users to create Alarms based on trap
events from the 3rd party device. There are five steps to integrating 3rd party alarms:
1 The trap OID for each event must be added to the
events.xml file
2 The necessary MIBs must be placed in the
extreme.war/thirdPartyMibs directory
3 The 3rd party MIB filenames must be specified in the
miblist.txt file in the extreme.war directory
4 Restart the EPICenter server
5 Each 3rd party device must be configured to send traps to EPICenter. See “Setting EPICenter as a
Trap Receiver” on page 196 for information on how to accomplish this.
Once this is done, the 3rd party event(s) should be selectable from the Event Name drop down list on
the Basic tab of the Alarm Definition Window (in the Alarm Manager). Alarms can then be defined to
take actions upon the occurrence of these events.
CLI.MORE_PROMPT Provide the pattern that
matches the prompt used by
the device to prompt when
paging is enabled on the
device.
This tag is optional.
Table 9: Tags used for Telnet integration
TAG Value Comments