One of the controllers
in this storage array is incompatible with the other controller.
The alternate controller is locked down.
What Caused the Problem?
One of the controllers in this storage array is incompatible with the other controller. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Caution: Possible loss of data accessibility. Do not remove a component when either (1) the Service Action (removal) Allowed (SAA) field in the Details area of this recovery procedure is NO (), or (2) the SAA LED on the affected component is OFF (note that some products do not have SAA LEDs). Removing a component while its SAA LED is OFF may result in temporary loss of access to your data. Refer to the following Important Notes for more detail.
Caution: Electrostatic discharge can damage sensitive components. Use a grounding wrist strap or other anti-static precautions before removing or handling components.
Important Notes
You must correct this problem before the power is cycled on the storage array. You will not be able to access the storage array using the Array Management Window (AMW) if the storage array boots with an incompatible controller.
The storage array currently does not have redundant controllers. The storage array will continue to operate with the remaining controller. However, failure of the remaining controller will result in a loss of access to the storage array. Therefore, make sure you correct this problem as soon as possible.
Depending on the model of your controller, the battery may be integrated inside the controller canister, rather than residing in a separate module. If the controller you are replacing contains a battery, you may have to insert the battery from the old controller canister into the new replacement controller canister. Consult your hardware documentation for details.
Service Action Allowed Important Information:
The
Service Action (removal) Allowed
field in the Details area indicates whether or not you can safely remove the component. If the SAA field is NO (
), then the affected component must remain in place until you service another component first.
The
Service action LED on Component
field in the Details area indicates whether or not a physical SAA LED is present on the hardware component. This field does NOT indicate whether the LED is ON or OFF (that indication is provided by the Service action (removal) allowed field).
If a component does not have an SAA LED, then it is OK to remove the component when its fault LED is lit and the
Service Action (removal) Allowed
field = YES (
) in the Details area.
The
Service Action (removal) Allowed
field shown in the Details area and the physical SAA LED on the hardware component (if supported) MUST match before you remove the affected component. In rare cases (such as multiple problems), the status of the LED and the SAA field may not match. If there is a mismatch, then you should NOT remove the component until these indications match.
Recovery Steps
1 | Remove the incompatible controller (identified in the Details area). Note: There is nothing wrong with the incompatible controller and that it may be compatible with another storage array. It can be used as a replacement for a controller that has the same replacement part number. | ||||||||||
2 |
| ||||||||||
3 | Check the replacement part number of the affected controller to ensure that the new controller has the same replacement part number.
| ||||||||||
4 | Make sure at least 1 minute has elapsed. Insert the new (compatible) controller canister securely into place. After the controller appears on the Hardware tab in the AMW, confirm that the controller has an Optimal status. | ||||||||||
5 | It may be necessary to redistribute the volumes to their preferred controller. Navigate to the Storage > Volume > Advanced > Redistribute Volumes menu option in the AMW.
| ||||||||||
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. |
Target | NetAppESeries.StorageArray | ||
Parent Monitor | NetAppESeries.StorageArrayAvailability | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | NetAppESeries.FailureUnitMonitorType | ||
Remotable | True | ||
Accessibility | Internal | ||
Alert Message |
| ||
RunAs | Default | ||
Comment | Machine generated entity |
<UnitMonitor ID="NetAppESeries.FailureID_0079_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_CTL_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="NetAppESeries.StateId42B64E1799245861F03656528A268D26" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateIdD45F32B0B1EFD5D075ED6358210C9964" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>79</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>