System information

Appendix A: Advanced Device Configuration 361
How the OnBoard Manages Communications With Devices
Issues Affecting the Configuration of RSA-Type
Service Processors
RSA I devices work differently from RSA II devices and recognize different
commands. A RSA I type device may be made to work if the administrator
copies the talk_rsa_I.exp file to a custom script named
talk_custom_N.exp, modifies it as instructed in the script, and assigns
the customN type to the RSA I type device.
Some RSA II devices support management of event logs, sensors, and power
through their command line interfaces and work with the rsa.default
template. Some RSA II devices support only power commands through
their command line interfaces, do not give access to event logs or sensors
(although their web interfaces do provide event log and sensor access), and
work only with the rsa.limited.default template, which only
contains power commands. “To Find Out if An Existing Command Template
Works With a New Device” on page 353 describes steps the OnBoard
administrator can follow to find out whether one of the default RSA templates
works, and if neither template works, to create a new template.
The onbdtemplate Utility
If the default command template that applies to the type of device being
configured does not work, the administrator can use the onbdtemplate
utility to test a new device against another command template. If needed,
onbdtemplate can also be used to create a customized template to make
command changes that might make it possible to communicate with a service
processor whose firmware is slightly different from the tested version.
A template can be configured to keep repeating commands to achieve a goal
such as reading output from multiple classes of sensors on an RSA II device
or reading multiple event log files one by one until no more log files exist on
an iLO-type service processor. Commands may be repeated until a string,
such as “No more entries,” is returned. When commands are repeated, an
escape sequence can be used to autoincrement the number in the command,
which is needed, for example, when checking event log files.