Advanced Device Configuration > How the OnBoard Manages Communications With Devices > OnBoard Expect Scripts

OnBoard Expect Scripts
The Expect scripts are located in the /libexec/onboard directory identified with the .exp suffix. The following table lists each of the defined device types with the name of the associated Expect script.
iLO
Three additional custom types (custom1, custom2, and custom3) allow OnBoard administrators to create up to three customized scripts. The following table shows the names of the Expect scripts associated with each of the custom types.
By default, the talk_customN.exp scripts contain warnings that they have not been configured along with some brief instructions on how to get them to work.
Note: Do not assign a customN type to a device unless you have created a custom script with the same number in its name.
All Expect scripts reside in /libexec/onboard, as shown in the following listing.
[root@OnBoard /] cd /libexec/onboard/
bidi_login.exp sensors.exp talk_generic_ipmi.exp
The files fall into three categories:
talk_ devicetype .exp scripts are the Expect scripts for the various types of service processors.
talk_custom[1-3].exp scripts are placeholders.
The administrator can create a customized Expect script by copying, renaming, and modifying talk_generic.exp, talk_generic_ipmi.exp or one of the default Expect scripts. The administrator should set the file permissions to allow reading and execution by all users and writing by members of the admin group. The format of a custom Expect script’s file name should be: talk_customN.exp.
Up to a total of three custom Expect scripts are supported. They must use the names of the placeholder custom scripts.
*_login.exp scripts are special extension scripts that can be used to change how service processors are accessed from using telnet to another access method.
Script templates are named talk_generic.exp and talk_generic_ipmi.exp.
All other Expect scripts are used to handle tasks common to other Expect scripts, such as providing local logging services or processing the command templates.

Advanced Device Configuration > How the OnBoard Manages Communications With Devices > OnBoard Expect Scripts