The evaluation license is about to expire.
What Caused the Problem?
A premium feature trial evaluation is expiring in three days and expiration will cause the feature to be Out of Compliance. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
The premium feature will be Out of Compliance upon expiration if the number of feature objects on the storage array exceeds the number of feature objects allowed for the premium feature.
You can fix this problem in two ways:
You can enable the premium feature
You can remove the feature objects before the trial evaluation expires
If the feature objects are not removed and the feature is in an Out of Compliance state, the following events will occur:
This storage array will remain in a Needs Attention state until the problem is resolved
A critical event will be logged once every 24 hours
Alert notifications will be sent, if configured
Depending on the premium feature that is Out of Compliance, you may 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
Rollback snapshots
Change the segment size of a volume
Change the RAID level of a volume group
Expand the capacity of a volume group, volume, or disk pool
Recovery Steps
1 | Identify the premium feature that is Out of Compliance in the Recovery Guru Details area. | ||||||
2 |
| ||||||
3 | Select the Storage Array > Premium Features menu option in the Array Management Window. | ||||||
4 | Retrieve the feature key identifier from the Premium Features and Feature Pack Information dialog. | ||||||
5 | Contact your Technical Support Representative to request a feature key file. | ||||||
6 | Click the Use Key File button to use the feature key file and enable the premium feature. | ||||||
7 | 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_0385_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_EVALUATION_LICENSE_EXPIRATION_IMMINENT_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.StateId6BDC68C1E3D0D53C2726B7E7B08C93F8" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateIdE49FC5C0606C0B6CB58DD691C06719F" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>385</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>