Introduction
21
Telnet on the OnBoard
defines the bidilink PORT. The following screen example shows the
line to change.
This example shows the comment (#) sign removed and changes
PORT
to
3301
.
c.
When you are done editing the appropriate options, save and quit the
file.
4.
Copy the appropriate Expect script for the desired device type to a custom
script name.
For example, if you want the OnBoard to use
ssh
or
bidilink
to
communicate with iLO-type devices, copy the contents of
talk_ilo.exp
into the
talk_custom1.exp
file.
5.
Open the custom expect script for editing, and find the line that sources
the
common.exp
file.
6.
To continue substituting
bidilink
, add a line to source the new file
# spawn bidilink tcp-client::PORT
spawn bidilink tcp-client::3301
[root@OnBoard onboard]# cp talk_ilo.exp talk_custom1.exp
source [file join [file dirname [info script]] “common.exp”]
source [file join [file dirname [info script]] “common.exp”]
source [file join [file dirname [info script]]
“soe_login.exp”]
Summary of Contents for AlterPath OnBoard
Page 36: ...xxxvi AlterPath OnBoard Administrator s Guide...
Page 108: ...Understanding How Configuration Changes Are Handled 72 AlterPath OnBoard Administrator s Guide...
Page 116: ...Overview of Web Manager Menus 80 AlterPath OnBoard Administrator s Guide...
Page 146: ...Configuring Regular Users Wizard 110 AlterPath OnBoard Administrator s Guide...
Page 160: ...Upgrading AlterPath PM IPDU Software 124 AlterPath OnBoard Administrator s Guide...
Page 194: ...Configuring an Alternate Help File Location 158 AlterPath OnBoard Administrator s Guide...
Page 292: ...Configuring Private Subnets and Virtual Networks 256 AlterPath OnBoard Administrator s Guide...
Page 344: ...Using the create_cf Command When Troubleshooting 308 AlterPath OnBoard Administrator s Guide...