Administration Tasks Not Performed in the Web Manager : Configuring SSH or Bidilink Instead of Telnet for Device Connections

Configuring SSH or Bidilink Instead of Telnet for Device Connections
The root user can replacing Telnet with SSH or bidilink, as described in the following procedure.
To substitute SSH or bidilink for Telnet for device connections:
1.
2.
[root@OnBoard onboard] cd /libexec/onboard
3.
a.
[root@OnBoard onboard]# cp bidi_login.exp soe_login.exp
b.
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 screen example shows the line to change.
This example shows the comment (#) sign removed and PORT changed to 3301.
c.
4.
For example, if you want the OnBoard appliance to use ssh or bidilink to communicate with iLO-type devices, copy the contents of talk_ilo.exp into the talk_custom1.exp file.
[root@OnBoard onboard]# cp talk_ilo.exp talk_custom1.exp
5.
source [file join [file dirname [info script]] “common.exp”]
6.
source [file join [file dirname [info script]] “soe_login.exp”]
7.
source [file join [file dirname [info script]] “ssh_login.exp”]
8.
9.
Assign the new custom type to the appropriate SPs. For example, if you have created a talk_custom1.exp for iLO SPs, configure the iLO SPs as custom1 type. If you are substituting bidilink, you are done.
10.
a.
Use ssh to connect to the SP as an administrator.
A prompt similar to the following appears.
b.
c.