Appendices : Device Configuration : OnBoard appliance Expect scripts

OnBoard appliance Expect scripts
The Expect scripts are located in the /libexec/onboard directory identified with the .exp suffix. Table D.4 lists each of the defined device types with the name of the associated Expect script.
Three additional custom types (custom1, custom2 and custom3) allow OnBoard appliance administrators to create up to three customized scripts. Table D.5 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.
The files fall into three categories:
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.
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.
Contact your Avocent representative if you need additional support for creating a custom Expect script.