Monitor REC_EXTERNAL_KMS_NOT_COMPLIANT (371)

NetAppESeries.FailureID_0371_Monitor (UnitMonitor)

When (1) the premium feature controller enters a Key Needed state (2) the array does not contain an External Key Management SAFE key; and (3) the key request is satisfied through an installLockKey procedure call; a Needs Attention state results. When . The Needs Attention condition is cleared by applying the appropriate SAFE key to the array or through a feature bundle migration.

Knowledge Base article:

External Key Management System - Out of Compliance

What Caused the Problem?

The Enterprise Security Key Manager Premium Feature is Out of Compliance. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Important Note

The storage array is out of compliance when the feature is enabled, but the Storage Array Feature Enable (SAFE) key was removed.

Recovery Steps

1

Apply the appropriate SAFE key in one of the following three ways:

  • to the storage array

  • through a feature bundle migration

  • disabling external key management and using local key management instead

2

Click the

Recheck

button to rerun the Recovery Guru. The failure should no longer appear in the Recovery Guru Summary area. If the failure appears again, contact your Technical Support Representative.

Element properties:

TargetNetAppESeries.StorageArray
Parent MonitorNetAppESeries.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppESeries.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_EXTERNAL_KMS_NOT_COMPLIANT
When (1) the premium feature controller enters a Key Needed state (2) the array does not contain an External Key Management SAFE key; and (3) the key request is satisfied through an installLockKey procedure call; a Needs Attention state results. When . The Needs Attention condition is cleared by applying the appropriate SAFE key to the array or through a feature bundle migration. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppESeries.FailureID_0371_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_EXTERNAL_KMS_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.StateId756B1D63B61D8313C15E39D7EF7160C1" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId39F0798A5B4D009913454248B2F703D4" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>371</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>