Table of Contents
Advertisement
9100
Controller controller_ID FW update failed
Explanation: The controller firmware update process has failed.
System action: By default, the SAS RAID Module system information indicator is turned on and the operator is
notified of this alert by e-mail. Alert clears when a firmware update completes successfully.
Operator response: Perform the following steps:
1. Reboot the controller.
2. Try again to perform a concurrent controller firmware update. You might have to use a different firmware set.
9101
Controller incompatible with survivor controller - Unable to bind
Explanation: Normally, if a redundant controller attempts to enter redundant operation with another controller
currently in survivor mode, the survivor controller will ensure that the firmware revision level of the redundant
controller matches the survivor firmware revision level. If the firmware does not match, the survivor controller
transfers its own firmware to the redundant controller to correct the mismatch. However, if the redundant controller
hardware is not compatible with the survivor firmware, the operation is aborted and the redundant controller reports
alert 9101.
System action: By default, the SAS RAID Module system information indicator is turned on and the operator is
notified of this alert by e-mail. Alert clears when the controller is rebooted.
Operator response: Correct the firmware version mismatch. Possible solutions:
v Obtain a replacement redundant controller that is compatible with the survivor controller.
v Replace the survivor controller with hardware that is compatible with the redundant controller (see "Replacing a
single controller using the CLI" on page 154).
9103
Unable to determine machine identity - machine initialization is required
Explanation: On boot-up, the controller detected that the backplane has not been initialized with Enclosure IDs and
the controller identities or states do not match or are not initialized.
System action: By default, the SAS RAID Module system information indicator is turned on and the operator is
notified of this alert by e-mail. The controller enters service mode. The alert clears after the operator loads the genesis
file via FTP and reboots.
Operator response: Load genesis file via FTP and then reboot.
Battery informational alert history log events
The alerts in this section are generated for logging battery status. These operator
never sees them as active alerts.
Chapter 11. Troubleshooting and support
9100 • 9103
123
Advertisement
Table of Contents
Troubleshooting
