Table F.1: Default Family Names And Corresponding Expect Script Names - Avocent MERGEPOINT 53XX SP MANAGER Installer/User Manual

2. Go to the /etc/libexec/mergepoint directory.
3. A user can create a new script talk_customN.exp or copy an existing talk_<family_name>.exp
and name the new file in the format: talk_customN.exp.
NOTE: Use talk_custom1.exp for the first custom script, talk_custom2.exp for a second, up to a total of
three scripts.
4. Edit the script as desired.
5. Save and quit the file.
6. Make sure the permissions are still 755.
NOTE: Contact your Avocent representative if you need additional support for creating a custom Expect script.
Default family names and corresponding Expect script names

Table F.1: Default Family Names and Corresponding Expect Script Names

Family Name
alom
blade_center
iLO
rsa_II
drac
devconsole
ilom
drac_mc
hp_blade_system
custom1
custom2
custom3
NOTE: There are no corresponding Expect script files to families "dell_10g", "ipmi_1.5", "ipmi_2.0" and
"fsc_irmc".
Service processor/device Expect script arguments
With one exception, each of the Expect scripts used to control access to a service processor takes
exactly five arguments in the following format:
talk_type.exp ip user passwd spprofilename action
Expect Script Name
talk_alom.exp
talk_blade_center.exp
talk_ilo.exp
talk_rsa_II.exp
talk_drac.exp
talk_devconsole.exp
talk_ilom.exp
talk_drac_mc.exp
talk_hp_blade_system.exp
talk_custom1.exp
talk_custom2.exp
talk_custom3.exp
Appendices 173