Advanced Device Configuration > How the OnBoard Manages Communications With Devices > Device Type Differences

Device Type Differences
The device type differences are summarized in the following table. Some of the device type differences that may need to be addressed by creating new templates or Expect scripts are described in the table. See also the additional information in the Troubleshooting.txt file under: /usr/share/docs/OnBoard/Application_Notes/Service_Processor_Related. Also see the Readme.txt file.
DRAC III/XT is the only version tested and proven to work with the default DRAC Expect script and command template. Compatibility with DRAC II or IV service processors is not guaranteed. Some DRAC service processors support sensors; modifications to the default DRAC template would be needed to support sensors; modifications to the default DRAC Expect script would be needed to take advantage of sensor alarms.
The OnBoard administrator can support IPMI 2.0 type service processors with the IPMI 2.0 RCMP+ encrypted protocol in either of the two following ways:
Identify the service processor as a IPMI 1.5 type which enables the OnBoard to communicate with the 2.0-type service processor in “v1.5 compatibility mode.”
Copy the talk_generic_ipmi.exp onto talk_customN.exp and follow the directions within the file to modify the script for IPMI 2.0 support.
Modify the default ipmi script to support OEM extensions
The RSA I card uses a curses-based interface. The OnBoard administrator can try to enable authorized users to perform IBM service processor console, power, and event log device management actions through a RSA I type service processor by copying the talk_rsa_I.exp Expect script to talk_customN.exp and following the directions within the script to modify the script for RSA I support. As stated in the RSA_I.txt application note, this script may not be compatible with all RSA I firmware versions, so it cannot be guaranteed to work.
The RSA II card uses a text-based interface. The card can be used in multiple IBM server platforms, and it requires a different firmware version or each platform. Simple features, such as switching power on and off, may not function if a card does not have the correct firmware version for the server in which it resides. In the discussion below, firmware for RSA II type service processors is referred to using the convention: version/platform. For example, firmware version1.03/x205, for example, is version 1.03 for the x205 platform. The versions differ between platforms, so that a later version of firmware for one platform may not have as many RSA II features as an earlier version for another platform. A comparison of some firmware versions for various platforms follows, for example:
1.07/x235 was released before 1.03/x306.
1.03/x360 is very different from 1.03/x205.
1.03/x205 supports neither event log nor sensors from the command line, whereas 1.03/x306 and 1.07/x235 both support event logs and sensors from the command line.
“power on” switches on the power for 1.03/x306 and 1.07/x235, but 1.03/x205 uses “power -on”.
Unknown sensor data on the 1.07/x235 is shown by using asterixes, while on the 1.03/x306 unknown sensor data is indicated by blank spaces.
Two RSA templates are available: rsa.default and rsa.limited.default. The rsa.limited.default template is for RSA II type devices that support only power commands through the device’s command line interface.
A custom Expect script can be created to provide support for RSA II service processors that do not work with the default rsa command templates.See the RSA_II.txt file in the application notes IBM subdirectory.

Advanced Device Configuration > How the OnBoard Manages Communications With Devices > Device Type Differences