The alternate controller is in a lockdown state as a result of an IOC diagnostic failure.
What Caused the Problem?
A controller-initiated diagnostic detected a failed on-board I/O controller on one of the controllers in the storage array. 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. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.
Important Notes
If the remaining controller in the storage array is not present or is not Optimal, the affected controller will continue to operate. If the remaining controller in the storage array is Optimal, then all operations will fail over to the remaining 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 the controller, the battery might be integrated inside the controller canister, rather than residing in a separate module. If the controller you are replacing contains a battery, you might have to insert the battery from the old controller canister into the replacement controller canister. Refer to the hardware documentation for details.
Recovery Steps
1 | Review the Recovery Guru Details area to identify the affected controller. | ||||||||||
2 | Check the replacement part number of the failed controller to ensure that the new controller has the same replacement part number.
| ||||||||||
3 | Remove the failed controller. | ||||||||||
4 | Wait at least 1 minute. | ||||||||||
5 | Insert the new controller securely into place. | ||||||||||
6 | Insert the controller canister securely into place. After the controller appears on the Hardware tab in the AMW, confirm that the controller has an Optimal status. | ||||||||||
7 | 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.
| ||||||||||
8 | 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 |
Home
<UnitMonitor ID="NetAppESeries.FailureID_0394_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_OFFLINE_CTL_IOC_FAIL_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.StateId2E4C0B66758E9A955888A35A8AF5286" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId2B20C93BEE3B886970D4DC70F42E2C8D" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>394</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>