In an array with two controllers, the array lock keys are automatically synchronized. However, if a controller is replaced while the array is powered down, the controllers may be unable to determine which key to use. In this case, the array enters the Needs Attention state and user intervention is required to resolve the problem.
What Caused the Problem?
The drive security key information does not match between the two controllers and the database on the drives. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
This problem occurs when power is disrupted during the creation of the drive security key before both controllers' configuration settings (NVSRAM) and the database on the drives are completely updated with the drive security information. While the power was off, one of the controllers was replaced. When the power was restored and the storage array completed the startup operations, the drive security information no longer matches among the controllers and the database on the drives.
You can fix this problem by changing the drive security key.
If the Drive Security menu is not visible in the Storage Array top-level menu, ensure that one of the following conditions is met:
The "Drive Security" and "Enterprise Security Key Manager" premium features are enabled on the storage array.
At least one of the drives in the storage array is secure-enabled.
Recovery Steps
1 | Select the Storage Array > Security > Drive Security > Change Key menu option. |
2 | Complete the instructions in the dialog to change the security key and to save it to a file. |
3 | Click the Recheck button to rerun the Recovery Guru. The problem should no longer appear in the Summary area. If the problem appears again, contact your Technical Support Representative. |
| Target | NetAppSANtricity.StorageArray | ||
| Parent Monitor | NetAppSANtricity.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppSANtricity.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home<UnitMonitor ID="NetAppSANtricity.FailureID_0333_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppSANtricity.StorageArray" ParentMonitorID="NetAppSANtricity.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppSANtricity.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppSANtricity.REC_SECURITY_KEY_INCONSISTENT_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="NetAppSANtricity.StateIdDB7F9868FF52F2897DA2293AD21BC172" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateIdB18F53DEE4092ABDE8A870F77E6FC578" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>333</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>