A battery is physically
present when the storage array is configured to operate without
batteries.
What Caused the Problem?
A battery was inserted into a storage subsystem that is configured to operate without batteries. The Recovery Guru Details area provides specific information you will need as you follow the Recovery Steps.
Caution: Electrostatic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage equipment.
Important Note
The controllers in this storage subsystem CANNOT be configured to operate with batteries. If you require batteries to preserve cached data in this storage subsystem, contact your technical support representative.
Recovery Steps
Refer to the 'Component requiring service' field in the Details area to determine which Recovery Steps you need to complete.
If... | Then... |
The component requiring service is the battery | Go to "Recovery Steps for a Directly-Accessible Battery." |
The component requiring service is the controller that contains the battery | Go to "Recovery Steps for a Battery Inside a Controller." |
Recovery Steps for a Directly-Accessible Battery
1 | Remove the affected battery. Note: The Service Action Allowed status in the Details area is always NO for this problem because the component is not yet expired or failed. In this situation, it is acceptable to remove the component even though the Service Action Allowed is NO. |
2 | Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative. |
Recovery Steps for a Battery Inside a Controller
If... | Then... |
Your storage subsystem has one controller | Go to "Procedure for Storage Subsystems with One Controller." |
Your storage subsystem has two controllers | Go to "Procedure for Storage Subsystems with Two Controllers." |
Procedure for Storage Subsystems with One Controller
1 | Stop all I/O from all hosts to this storage subsystem. When the Cache Active LED on the controller is no longer active (up to 5 minutes), proceed to step 2. Caution: Risk of Data Loss. You must wait for the Cache Active LED to stop blinking to ensure that all cache has been written to the drives in the storage subsystem. |
2 | Click the Save As button in the Recovery Guru dialog to save the remaining steps to a file. These steps may no longer be accessible from the Recovery Guru dialog after you complete step 3. |
3 | Remove the controller canister that contains the affected battery. |
4 | Remove the battery. Refer to your hardware documentation for the battery removal procedure. |
5 | Insert the controller canister securely into place. After the controller appears in the Physical View of the AMW, go to step 6. |
6 | Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your technical support representative. |
Procedure for Storage Subsystems with Two Controllers
1 | If there are any hosts connected to this storage subsystem that are NOT running a host-based, multi-path failover driver, stop I/O to the storage subsystem from each of these hosts. | ||||||
2 | Place the affected controller offline.
| ||||||
3 | Click the Save As button in the Recovery Guru dialog to save the remaining steps to a file. These steps may no longer be accessible from the Recovery Guru dialog after you complete step 4. | ||||||
4 | Click the Recheck button to rerun the Recovery Guru. There should be an Offline Controller problem reported in the Summary area. | ||||||
5 | Follow the Offline Controller Recovery Steps, until you have removed the controller. After you have removed the controller, do not continue with the Offline Controller Recovery steps until you are instructed to do so later in this procedure. | ||||||
6 | Remove the affected battery from the controller canister. Refer to your hardware documentation for the battery removal procedure. | ||||||
7 | Complete the remaining Offline Controller Recovery Steps. |
| Target | IBMStorageSubsystem.StorageSubsystem | ||
| Parent Monitor | IBMStorageSubsystem.StorageSubsystemAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | IBMStorageSubsystem.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home<UnitMonitor ID="IBMStorageSubsystem.FailureID_0103_Monitor" Accessibility="Internal" Enabled="true" Target="IBMStorageSubsystem.StorageSubsystem" ParentMonitorID="IBMStorageSubsystem.StorageSubsystemAvailability" Remotable="true" Priority="Normal" TypeID="IBMStorageSubsystem.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="IBMStorageSubsystem.REC_BATTERY_CONFIG_MISMATCH_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="IBMStorageSubsystem.StateId4B7AD7AEB5E36473D428FCF793084002" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="IBMStorageSubsystem.StateIdD6D7AA47D74653C29A72201D66470A9" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>103</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>