System information

Appendix A: Advanced Device Configuration 351
How the OnBoard Manages Communications With Devices
Additional Reasons for Creating Custom Expect Scripts
The following table lists some of the reasons an administrator might want to
create a custom Expect script.
Table A-3: Reasons for Customizing Expect Scripts
Purpose Notes
Change the device access
method from telnet to
ssh, or to some other
program.
Administrators would probably want to change the device
access method if devices must be connected to the public
ports on the OnBoard, because telnet is not encrypted.
See “HTTPS on the OnBoard” on page 24. Also see the
following files in the Alternate_Access directory:
• SSH_Access.txt
• bidilink_Access.txt
In addition, see the notes in the following files in the /
libexec/onboard directory:
• bidi_login.exp
• ssh_login.exp
Interact with the web
interface of a service
processor
The RSA_I.txt file in the application notes IBM
subdirectory and the talk_rsa_I.exp script address
accessing the RSA I web interface, and the instructions in
this file can be followed for accessing other device types’
web interfaces.
Add functionality to a
devconsole-type script to
access additional features
available through a device’s
console, such as logging in
and reporting on the event
log, sensors, or performing
power functions.
See the Devconsoles.txt file in the application notes
Devconsoles directory:
If the device console supports additional management
features, commands for the supported commands can be
added and the default devconsole script can be updated
with commands that use the supported command
interfaces.