Monitor Description for (40)
What Caused the Problem?
A battery has failed. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Electrostatic charges can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.
Important Notes
Contact your customer service representative if you do not have a replacement battery available.
The purpose of the battery is to preserve cached data in the event of a power failure. Therefore, you should replace the battery as soon as possible.
Write caching for all logical drives has been automatically suspended (if previously enabled). Write caching will be reinstated (if applicable for each logical drive) once you replace the battery and the replacement battery is charged to a sufficient level to support cached data in the event of a power failure.
The battery replacement procedure varies depending on the type of storage subsystem you have. Some batteries are directly accessible while some batteries are inside the controller which require you to remove the controller first before servicing the battery. Consult the appropriate hardware manual if you need details on locating and replacing the battery.
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. | ||||||
2 | Insert the new battery securely into place. Notes:
| ||||||
3 | Select the Storage Subsystem >> Change >> Battery Settings menu option. | ||||||
4 |
| ||||||
5 | Record the installation date (today's date) and the new replacement date (according to the battery's warranty). | ||||||
6 | Select the battery you just replaced, and then click the Reset button to set the affected battery's age to zero. | ||||||
7 | 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 | Replace the affected battery with a new battery. Refer to your hardware documentation for the battery replacement procedure. | ||||||
5 | Insert the controller canister (containing the new battery) securely into place. After the controller appears in the Physical View of the AMW, go to step 6. Notes:
| ||||||
6 | Select the Storage Subsystem >> Change >> Battery Settings menu option. | ||||||
7 |
| ||||||
8 | Record the installation date (today's date) and the new replacement date (according to the battery's warranty). | ||||||
9 | Select the battery you just replaced, and then click the Reset button to set the affected battery's age to zero. | ||||||
10 | 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 | Replace affected battery with a new replacement battery. Refer to your hardware documentation for the battery replacement procedure. Notes:
| ||||||
7 | Complete the remaining Offline Controller Recovery Steps. Once you have completed the Offline Controller Recovery Steps, go to step 8. | ||||||
8 | Select the Storage Subsystem >> Change >> Battery Settings menu option. | ||||||
9 |
| ||||||
10 | Record the installation date (today's date) and the new replacement date (according to the battery's warranty). | ||||||
11 | Select the battery you just replaced, and then click the Reset button to set the affected battery's age to zero. | ||||||
12 | 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. |
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 |
<UnitMonitor ID="IBMStorageSubsystem.FailureID_0040_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_NON_FRU_FAILED_BATTERY_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.StateIdE0EC81DCF579DB8518511CE5A8CC79A" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="IBMStorageSubsystem.StateId7CF478A14188600124362C38E75ECDB2" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>40</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>