IBM BladeCenter S SAS RAID Controller Module, Инструкция по установке и эксплуатации

Страница: 128 / 216

1102 Controller non-critical failure detected - RTC failed
Explanation: The controller real time clock (RTC) is not functioning properly.
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 when the controller is rebooted. The controller with the failed RTC can
continue to provide redundancy to the system and service host I/O requests. However, if the other controller fails
and this controller becomes survivor, the system time might be reported incorrectly.
Operator response: Replace the controller reporting this alert. See “Replacing a single controller using the CLI” on
page 154 or “Replacing a single controller using the SCM” on page 155.
This alert can be masked so that it does not trigger the SAS RAID Module system information indicator.
3100 Controller entering service mode to maintain volume availability.
Explanation: The non-survivor controller generates this alert when a failover has occurred because this controller
was providing access to volumes mapped to a non-redundant disk drive and has lost the ability to communicate
with that drive. The other controller does have access to the non-redundant disk drive and can provide access to the
host as a survivor controller. The root problem is asymmetric drive connectivity.
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. If connectivity to all drives is restored, this controller rebinds with the surviving
controller and redundant operation resumes. Alert clears when bound controller state is achieved.
Operator response: Perform an Asymmetrical Disk Connectivity Diagnosis. If the non-redundant drive is replaced,
restart this controller to return to redundant controller operation.
This alert can be masked so that it does not trigger the SAS RAID Module system information indicator.
3101 Controller entering service mode to maintain volume availability.
Explanation: The survivor controller generates this alert when a failover has occurred because the other controller
has lost connectivity to a non-redundant disk drive and can no longer provide access to the associated volumes. This
controller does have access to the non-redundant disk drive and can provide access to the host as a survivor
controller. The root problem is asymmetric drive connectivity.
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. If connectivity to all drives is restored, the controller in service mode rebinds with the
surviving controller and redundant operation resumes. The alert clears when bound controller state is achieved.
Operator response: Perform an Asymmetrical Disk Connectivity Diagnosis. If the non-redundant drive is replaced,
restart this controller to return to normal operation.
This alert can be masked so that it does not trigger the SAS RAID Module system information indicator.
4100 ZSS waiting for specified drive configuration
Explanation: RAID Zero Step Setup is a mechanism by which the controller detects that it has never before been
configured in a system, finds that no drives in the system contain configuration information (metadata), and is
enabled to run a factory installed configuration script when a minimum number of drives have been installed. This
alert is generated when the controller is ready to run the script, but has not yet discovered the minimum physical
configuration of drives required.
System action: By default, the SAS RAID Module system information indicator is turned on and the operator is not
notified of this alert by e-mail. In most cases, installing additional drives causes the controller to clear this alert and
proceed to automatically configure the system as per the Zero Step Setup feature.
Note: Because you might want to add more than the minimum number of drives, the controller does not initiate
Zero Step Setup configuration immediately after discovering a sufficient number of drives. Instead, the controller
waits for predefined period (the default is 60 seconds) after each drive insertion so that you have time to add more
drives. If that period elapses without further drive insertions, Zero Step Setup configuration begins.
Operator response: Use manual to determine proper drive configuration for Zero Step Setup. If the alert is still
active more than 60 seconds after you ensure that the correct drive configuration exists, perform a Disk Connectivity
Diagnosis.
1102 • 4100
118
IBM SAS RAID Controller Module: Installation and User's Guide IBM BladeCenter S SAS RAID Controller Module