Monitor REC_REMOVED_BATTERY (67)

NetAppESeries.FailureID_0067_Monitor (UnitMonitor)

The failure type is Removed Battery.

Knowledge Base article:

Battery Removed

What Caused the Problem?

A battery has been removed or is not present in the storage array. 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

 

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

Procedure for a Directly-Accessible Battery

.

The component requiring service is the controller that contains the battery

Go to

Procedure for a Battery Inside a Controller

.

Procedure for a Directly-Accessible Battery

1

Check the storage array for the presence of the affected battery.

If...

Then...

The battery is present

Remove the battery and check the connector for damaged or dirty connectors, then go to step 2.

You removed the battery

 

Go to step 2.

2

Reinsert the original battery or a replacement battery securely into place and wait for the storage array to detect and register the battery.

Note:

  • The time it takes to fully charge the battery depends on the model of the battery and its current state. While it is charging, the battery will report a Charging status. Consult the appropriate hardware manual for your model.

  • If you insert a replacement battery that is Smart Battery Data-capable (only applicable if the

    Smart battery

    field in the Details area is YES), then the battery will start an initial Learn Cycle once the battery is fully charged.  Depending on the model of your storage array, write caching may not be reinstated until the initial Learn Cycle is complete.

3

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 a Battery Inside a Controller

If...

Then...

Your storage array has one controller

Go to

Procedure for Storage Arrays with One Controller

.

Your storage array has two controllers

Go to

Procedure for Storage Arrays with Two Controllers

.

Procedure for Storage Arrays with One Controller

1

Stop all I/O from all hosts to this storage array. 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 array.

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

Check the controller canister for the presence of the affected battery.

If...

Then...

The battery is present

Perform the following steps:

a

Remove the battery and check the connector for damaged or dirty connectors.

b

Reinsert the original battery or a replacement battery securely into place.

c

Go to step 5.

You removed the battery

 

Reinsert the original battery or a replacement battery securely into place, and then go to step 5.

5

Insert the controller canister securely into place. After the controller appears on the

Hardware

tab in the AMW, go to step 6.

Note:

  • The time it takes to fully charge the battery depends on the model of the battery and its current state. While it is charging, the battery will report a Charging status. Consult the appropriate hardware manual for your model.

  • If the battery is SBD-capable (the

    Smart battery

    field in the Details area is YES), then the battery will also start an initial Learn Cycle once the battery is fully charged. Depending on the model of your storage array, write caching may not be reinstated until the initial Learn Cycle is complete.

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 Arrays with Two Controllers

1

If there are any hosts connected to this storage array that are NOT running a host-based, multi-path failover driver, stop I/O to the storage array from each of these hosts.

2

Place the affected controller offline.

a

Select the controller on the

Hardware

tab of the Array Management Window.

b

Select the

Hardware > Controller > Advanced > Place > Offline

menu option.

c

Follow the instructions in the dialog, then click the

Yes

button.

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

Check the controller canister for the presence of the affected battery.

If...

Then...

The battery is present

Perform the following steps:

a

Remove the battery and check the connector for damaged or dirty connectors.

b

Reinsert the original battery or a replacement battery securely into place.

c

Go to step 7.

You removed the battery

 

Reinsert the original battery or a replacement battery securely into place, and then go to step 7.

7

Complete the remaining "Offline Controller" recovery steps.

Note:

  • The time it takes to fully charge the battery depends on the model of the battery and its current state. While it is charging, the battery will report a Charging status. Consult the appropriate hardware manual for your model.

  • If the battery is SBD-capable (the

    Smart battery

    field in the Details area is YES), then the battery will also start an initial Learn Cycle once the battery is fully charged. Depending on the model of your storage array, write caching may not be reinstated until the initial Learn Cycle is complete.

Element properties:

TargetNetAppESeries.StorageArray
Parent MonitorNetAppESeries.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppESeries.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_REMOVED_BATTERY
The failure type is Removed Battery. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppESeries.FailureID_0067_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppESeries.REC_REMOVED_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="NetAppESeries.StateId51573FA72044CA09BC992CE4B9E3E035" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId1BD840062F7A45024658A70DF56887CA" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>67</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>