Telnet Integration - Extreme Networks EPICenter Guide Manual

Concepts and solutions guide
Hide thumbs Also See for EPICenter Guide:
Table of Contents

Advertisement

The dpsimages.zip File
The
file contains the images used in the Component Tree that appears in places such as
dpsimages.zip
the Inventory Manager.
If you are adding a completely new device or device type with its own unique image, you must add
that image to this file.
The image itself can be the same as the MapView.gif image you added into the OID folder (see
OID folder" on page
200) but it must be named to match the name specified in the
tag in the XML file for the device or device type (see
imageIconsFileName
an ATL File" on page
198.
For example, the dpsimages.zip file included the file
in the
file:
3Com.xml
<imageIconsFileName>3comicons.gif</imageIconsFileName>
If individual devices do not require unique icons, this can be specified in the parent XML file (for the
device type) and can be left out of the XML files for individual devices of that type.

Telnet Integration

EPICenter's 3rd party integration framework can be used to provide additional features within the
Telnet applet, including the use of Telnet macros. Telnet integration can enable the following:
Auto-login when a user (with the appropriate role/permissions) connects to the device from the
EPICenter Interactive Telnet application
Support for execution of Telnet macros on the device, both from within the Telnet Macro Player, and
from the right-click Telnet Macro menu.
Telnet integration involves adding some additional tags to the ATL XML file for the device or device
type. The following tags may be used to specify Telnet features:
Table 9: Tags used for Telnet integration
TAG
TELNET_MACROS
CLI.LOGIN_PROMPT
CLI.PASSWORD_PROMPT
CLI.SHELL_PROMPT
EPICenter Concepts and Solutions Guide
The EPICenter Third-party Device Integration Framework
3comicons.gif
Value
TRUE or FALSE
A value (string) to be
displayed as the prompt
during login to the device.
A value (string) to be
displayed as the password
prompt during login to the
device.
Provide the pattern that
matches the CLI prompt, for
example: summit450#
Table
8,
, which matches the name specified
Comments
If the value is TRUE, users will be able to execute
Telnet macros. If the value is false, telnet
macros are not supported, and users are so
informed if they try to execute a macro on the
device. This tag is required for Telnet support.
If the device normally displays a specific login
prompt, you can enter it here to provide the same
interface when logging in from EPICenter. This
tag is required if the device supports Telnet.
Similar to the login prompt; you can enter the
same prompt used by the device. This tag is
optional.
Specify the format of the device CLI prompt. You
can specify multiple patterns, such as
\S[ ][#>] [Test] [EPICenter] $
This tag is required for Telnet support.
"The
"Attributes Used in
201

Advertisement

Table of Contents
loading

This manual is also suitable for:

Epicenter 6.0

Table of Contents