Cisco Cisco Configuration Engine 3.5 Entwickleranleitung
2-10
Cisco Configuration Engine Software Development Kit API Reference and Programmer Guide 3.5
OL-17661-02
Chapter 2 Event Service and IMGW
IMGW Device Information Database
The table of HopInfo records is interpreted as follows. If an IP address exists in the record, it is
necessary to telnet into a new device at that point. If an IP address does not exist in the record, it is
considered to be a virtual hop, that is, an embedded line card is being accessed or an additional
authentication mode of the current device is necessary. These records can be chained to accomplish any
combination of logins.
necessary to telnet into a new device at that point. If an IP address does not exist in the record, it is
considered to be a virtual hop, that is, an embedded line card is being accessed or an additional
authentication mode of the current device is necessary. These records can be chained to accomplish any
combination of logins.
The port field identifies which port to use. This is especially useful when dealing with communication
servers (such as a 2511) because they reserve the port range 2001-2016 to access the sixteen outgoing
async lines. If the port field is not present, it defaults to 23 to allow a normal telnet (except in the case
of a Secure Shell (SSH) login where the default port is 22, as shown in
servers (such as a 2511) because they reserve the port range 2001-2016 to access the sixteen outgoing
async lines. If the port field is not present, it defaults to 23 to allow a normal telnet (except in the case
of a Secure Shell (SSH) login where the default port is 22, as shown in
Examples
Supported Device Types
The following tables describe the Hopinfo structure for Devices that are directly accessible on the
network by IMGW. For Access via Commserver please refer to Table 2-11, on page 11.
network by IMGW. For Access via Commserver please refer to Table 2-11, on page 11.
The fields marked with “X” are mandatory. Also, all the rows in Hopinfo Structure are mandatory even
though they may be null. The exception is the device_type field, which may not be null.
though they may be null. The exception is the device_type field, which may not be null.
While accessing the device through Commserver, port username must be null, because port username is
not supported.
not supported.
Table 2-3
Cisco IOS Device Directly Connected
device_type
ip_address
port
username
password
IOS_LOGIN
X
X
X
IOS_EN
X
X
Table 2-4
Cisco IOS Device Directly Connected, supporting SSH
device_type
ip_address
port
username
password
IOS_LOGIN:SSH
X
X
X
IOS_EN
X
X
Table 2-5
Catalyst Device Directly Connected
device_type
ip_address
port
username
password
CATALYST_LOGIN
X
X
X
CATALYST_EN
X
X
Table 2-6
Catalyst IOS MSFC Blade Directly Connected
device_type
ip_address
port
username
password
CATALYST_LOGIN
X
X
X
IOS_CAT_BLADE
X
X
X
IOS_EN
X
X
Table 2-7
CatIOS Device Directly Connected
device_type
ip_address
port
username
password
CATIOS_LOGIN
X
X
X
CATIOS_EN
X
X