System information

How the OnBoard Manages Communications With Devices
352 AlterPath OnBoard Administrator’s Guide
Custom scripts can also be deployed for the following purposes:
To handle changes in service processor firmware on a supported service
processor type
To provide some limited functionality with other types of devices,
including Sun ALOM, ILOM, and RSC, and IBM BladeCenter and
RILOe
To provide access to new service processor types
Assigning a Command Template to a New Device
When configuring a new device, the OnBoard administrator should not assign
a command template when the device is either of the following two types of
devices:
Any IPMI-type device (IPMI devices are managed using ipmitool
commands)
Any device being configured only for Native IP access
When adding any other kind of new device, the OnBoard administrator needs
to do the following:
Find out if the new device and its firmware have been tested and proven to
work with the applicable default command template.
Read any application notes that relate to that type of device.
If the new device is running untested firmware, test whether the firmware
is compatible with the applicable default command template.
If communications cannot be established with the new device using the
default command template, use the onbdtemplate utility to create and
test a new command template, after making any needed changes to the
commands that manage communications between the device and the
OnBoard.
If a new template cannot be made to work, create a custom Expect script
to handle the device’s requirements.
See “To Find Out if An Existing Command Template Works With a New
Device” on page 353” for how to perform the above-listed steps.