1108
Controller critical failure detected - Mirror bus failed
Explanation:
The system uses a dedicated high-speed dual lane mirror bus to maintain redundant controller
operation. If this bus fails, each the controllers use the serial port interconnect to determine the controller most
qualified to enter survivor mode and the other controller enters service mode. Both controllers might report alert
1108, and it can be difficult to determine which controller is at fault.
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 cannot be masked or cleared and persists until one controller is removed or until
the mirror bus becomes functional.
Operator response:
Perform the following troubleshooting procedure:
1.
Remove and reinsert the controller in service mode. If the reinserted controller boots up and binds with the
survivor controller, either the controller was not well inserted before, or the connector between the controller and
the backplane might have intermittent connectivity.
2.
If the reinserted controller again reports alert 1108, shut down the system and reseat the survivor controller (see
“Replacing a single controller using the CLI” on page 154 or “Replacing a single controller using the SCM” on
page 155).
3.
If reseating the survivor controller does not clear the conditions, replace the controller in service mode with a new
controller.
4.
If the problem persists, replace the other controller with the removed original service mode controller.
5.
If the problem is still not resolved, either the remaining controller needs to be replaced or the backplane is
defective and needs to be replaced.
1109
Controller
controller_ID
critical failure detected, replace controller
Explanation:
The path used to communicate with disk drives is nonfunctional.
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 different controller rebinds with the survivor controller or the
system is rebooted.
Operator response:
Replace the controller. See “Replacing a single controller using the CLI” on page 154 or
“Replacing a single controller using the SCM” on page 155.
5100
Controller unable to continue redundant operation
Explanation:
This alert is generated by a controller in service mode in conjunction with when two controllers are
unable to bind. In order to bind, both controllers must be able to communicate properly via the dedicated mirror bus,
the list of drives discovered by each controller must match, and the firmware revisions must match.
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 alert clears automatically when the controller enters redundant operation or
reboots as a survivor controller.
Operator response:
Look for additional alerts to determine the reason why the controllers cannot bind.
1108 • 5100
122
IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module
Summary of Contents for BladeCenter S SAS RAID Controller Module
Page 2: ......
Page 7: ...Taiwan Class A compliance statement 199 Index 201 Contents v...
Page 101: ...host get Chapter 8 Using the RAID Controller command line interface 91...
Page 209: ...Taiwan Class A compliance statement Notices 199...
Page 215: ......
Page 216: ...Part Number 00D9332 Printed in USA 1P P N 00D9332...
