This failure type is obsolete.
What Caused the Problem?
The Gold Key feature is Out of Compliance. This problem can occur in the following scenarios:
Scenario 1 (Most common scenario)
- One or more premium features are enabled that require the Gold Key feature to be enabled, yet the Gold Key is currently disabled.
Scenario 2 (Less common scenario)
- The storage array MAY or MAY NOT have Gold Key-dependent features enabled, however, you connected drives to one or more controllers where 1) the controllers were NOT previously attached to any drives, and 2) the drives were already previously configured while attached to other controllers where the Gold Key feature was supported and enabled.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
This problem can occur if you disable a feature pack key. Disabling a feature pack key can result in multiple individual features transitioning to an Out of Compliance state since you may have globally lowered the limits supported by the storage array. If there is a "Feature Pack - Out of Compliance" problem in the Summary Area, complete those recovery steps first. If this problem still appears after you complete the recovery steps for the "Feature Pack - Out of Compliance" problem, then proceed with the recovery steps below.
Scenario 1 typically happens because you:
Disabled the Gold Key feature while Gold Key-dependent features are still enabled
Enabled or Disabled a feature pack resulting in a change to individual feature's dependency on the Gold Key feature.
Scenario 2 happens because the controllers were not previously attached to drives, so the controllers 'adopt' the configuration database of the first drive they encounter. When drives are adopted by the controllers, the configuration database contained on the drives (which includes all of the information about the previous storage array, including the enabled/disabled information of features) is used by the controllers. Therefore, the information in the configuration database shows that the Gold Key feature is enabled, but the feature is either disabled on this storage array or not supported by the controllers. If the controllers had been previously attached to drives and then another set of drives are added, then the new drives would be 'imported' (overwriting the configuration database) rather than 'adopted' since the controller is using the configuration database of the existing drives.
For Scenario 1, you can fix this problem in two ways:
You can re-enable the Gold Key feature
You can disable the Gold Key-dependent features
For Scenario 2, you can fix this problem in two ways:
You can disable the Gold Key feature once all of the Gold Key-dependent features have been disabled
You can enable the Gold Key feature if it is supported by this storage array
While this feature is in an Out of Compliance state, you will NOT be able to:
Create new configuration objects (automatically or manually) - such as volumes, snapshots, mirror relationships, volume copy pairs, and storage partitions
Assign hot spares
Change the segment size of a volume
Change the RAID level of a volume group
Expand the capacity of a volume group or volume
Recovery Steps
If... | Then... |
This problem occurred due to Scenario 1 | Go to Procedure for Scenario 1 . |
This problem occurred due to Scenario 2 | Go to Procedure for Scenario 2 . |
Procedure for Scenario 1
1 |
| ||||||||||||||||||
2 | Select the Storage Array > Premium Features menu option in the Array Management Window.
| ||||||||||||||||||
3 | Click the Use Key File button to use the feature key file and enable the premium feature. | ||||||||||||||||||
4 | 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 Scenario 2
1 |
| ||||||||||||||||||
2 | Select the Storage Array > Premium Features menu option in the Array Management Window.
| ||||||||||||||||||
3 | Click the Use Key File button to use the feature key file and enable the premium feature, and then go to step 6. | ||||||||||||||||||
4 | Refer to the Details area to see how many Gold Key-dependent features are currently enabled.
| ||||||||||||||||||
5 | Disable the Gold Key feature.
| ||||||||||||||||||
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_0093_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_GOLD_KEY_NOT_COMPLIANT_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.StateId404E024768330E4ED32689EE655D0E85" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateIdDAFD167E117AB0227EDD34103D5E5F6F" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>93</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>