System information

Administration Tasks Not Done in the Web Manager 73
Configuring SSH or Bidilink Instead of Telnet for Device Connections
For example, to use TCP without telnet commands being
intercepted, you would need to uncomment and modify the line that
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
created in Step 3.
7. To begin substituting ssh, add a line to source the ssh.login.exp
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”]
source [file join [file dirname [info script]] “common.exp”]
source [file join [file dirname [info script]] “ssh_login.exp”]