High Performance Tier Premium Feature - Out of Compliance
The causes and resolutions refer to the Dell Modular Disk Storage Manager recovery guru. Launch Dell Modular Disk Storage Manager to diagnose and fix the recovery failure as follows:
Open Start >> Programs >> Dell >> MD Storage Manager >> Modular Disk Storage Manager Client.
If the MD Storage Array is already being managed by MDSM, you can proceed with the Causes and Resolution sections.
From Edit -> Add Storage Array, provide the IP address of the MD Storage Array and Add it to the discovered devices configuration in order to manage it.
Select the MD Storage Array and follow the steps specified in this recovery guru.
The High Performance Tier Premium Feature is Out of Compliance. This problem occurs because you connected physical disks to one or more RAID controller modules where 1) the RAID controller modules were NOT previously attached to any physical disks, and 2) the physical disks were already previously configured while attached to other RAID controller modules where the High Performance Tier feature was supported and enabled. However, it is either not supported or not enabled on this storage array.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
This problem happens because the RAID controller modules were not previously attached to physical disks, so the RAID controller modules 'adopt' the configuration database of the first physical disk they encounter. When physical disks are adopted by the RAID controller modules, the configuration database contained on the physical disks (which includes all of the information about the previous storage array, including the enabled/disabled information of features) is used by the RAID controller modules. Therefore, the information in the configuration database shows that the High Performance Tier feature is enabled, but the feature is either disabled on this storage array or not supported by the RAID controller modules. If the RAID controller modules had been previously attached to physical disks and then another set of physical disks are added, then the new physical disks would be 'imported' (overwriting the configuration database) rather than 'adopted' since the RAID controller module is using the configuration database of the existing physical disks.
You can fix this problem by enabling the High Performance Tier feature key it if 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 virtual disks, snapshots, replication relationships, virtual disk copy pairs, and storage partitions
Assign hot spares
Change the segment size of a virtual disk
Change the RAID level of a disk group
Expand the capacity of a disk group or virtual disk
1 | Select the Storage Array > Premium Features... menu option in the Array Management Window.
| ||||||||||||||||||
2 | Click the Use Key File... button to use the feature key file and enable the premium feature. | ||||||||||||||||||
3 | 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 | Microsoft.SystemCenter.ManagementServer | ||
Category | Alert | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
|
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.ScriptGenerated.EventProvider | Default |
Alert | WriteAction | System.Health.GenerateAlert | Default |
WriteToDW | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishEventData | Default |
<Rule ID="Dell.MDStorageArray.ABBXMLEvent209" Enabled="onEssentialMonitoring" Target="SystemCenter!Microsoft.SystemCenter.ManagementServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.ScriptGenerated.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ScriptName>RBODEventGenerator</ScriptName>
<EventNumber>209</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent209.StringResource"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/EventDisplayNumber$</SuppressionValue>
<SuppressionValue>$Data/Channel$</SuppressionValue>
<SuppressionValue>$Data/PublisherName$</SuppressionValue>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
<SuppressionValue>$Data/EventCategory$</SuppressionValue>
<SuppressionValue>$Data/EventLevel$</SuppressionValue>
<SuppressionValue>$Data/UserName$</SuppressionValue>
<SuppressionValue>$Data/EventNumber$</SuppressionValue>
<SuppressionValue>$Data/EventDescription$</SuppressionValue>
</Suppression>
<Custom1/>
<Custom2/>
<Custom3/>
<Custom4/>
<Custom5/>
<Custom6/>
<Custom7/>
<Custom8/>
<Custom9/>
<Custom10/>
</WriteAction>
<WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>
</WriteActions>
</Rule>