Feature Pack Out of Compliance
What Caused the Problem?
The Feature Pack that is enabled for this storage array is Out of
Compliance.
This problem can occur in the following scenarios:
- Scenario 1 (Most common scenario) - The storage array has one or more features that do not comply with the limits set
(or the features are not supported) by the current feature pack.
- Scenario 2 (Less common scenario) - 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 a different Feature Pack existed. See the Important Notes for more detail on this scenario.
The Recovery Guru Details area provides specific information you will need as you follow the Recovery Steps.
Important Notes
- A feature pack defines the features supported by the storage
array and also defines the limits of those features. Upgrading to
a higher feature pack can increase the limits of the features
while disabling a feature pack (which is not recommended),
decreases the limits of some of the features or possibly remove
support of some features completely.
- This problem may result in other reported problems in the Summary area, such as
individual out of
compliance features or device limits exceeded. Complete the Recovery
Steps for
THIS problem first before addressing any other problem. After you click the Recheck button, some or all of the other problems may be resolved.
- Scenario 1 typically happens because you performed one of the
following actions:
- You disabled a Feature Pack key which lowered the limits of one
or more features.
- You enabled a Feature Pack key which downgraded the limits of
one or more features.
- One or more features exceed their individual limit, causing the
overall Feature Pack to be Out of Compliance.
- Scenario 2 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 Feature Pack and Enabled/Disabled information of
features) is used by the RAID controller modules. Therefore, the
information in the configuration database shows a different Feature
Pack that supported different limits than the RAID controller modules currently
support. 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.
- The following events will occur while the storage array has an Out of Compliance status:
- This storage array will remain in a Needs Attention state
- A critical MEL event will be logged once every 24 hours
- Alert notifications will be sent, if configured
- You will NOT be able to:
- Create new configuration objects (Automatically or
Manually) - such as virtual disks, snapshots, mirror
relationships, virtual disk copy pairs, and storage partitions
- Change the segment size of a virtual disk
- Change the RAID level of a disk group
- Activate the Remote Virtual Disk Mirroring premium feature
- Assign hot spares
- Invoke the Automatic Configuration Wizard
Recovery Steps
| 1 |
| If... |
Then... |
| You recently disabled
a Feature Pack OR
You recently enabled a Feature Pack that
downgraded the limits of one or more features |
Go to step 2. |
| You did NOT recently disable or
enable a Feature Pack (You should choose this
option if this problem occurred due to Scenario 2,
above) |
Follow the Recovery Steps for each individual
Feature Out of Compliance problem
listed in the Summary area to make sure all
features comply with the existing limits set by
the Feature Pack. Once all individual
features are compliant, this problem should also
be resolved. Do not continue with the
remaining Recovery Steps for this problem. |
|
| 2 |
| If... |
Then... |
| You want to re-enable
the previous Feature Pack |
A separate Feature Pack key
file is needed to enable the Feature Pack. Since the
Feature Pack has
already been enabled at one time for this storage array, you
should already have a Feature Key File. If you
cannot locate it, you will need to perform the following:
- From the Tools tab, click the View/enable premium features
link, and retrieve the Feature Enable Identifier.
- Contact your technical support representative to
request a Feature Pack key file.
- Once you have located your existing Feature Pack key
file or obtained the appropriate Feature Pack key file
from your technical support representative, click the
Enable Feature Pack link from the Tools tab to enable it.
- When you are finished enabling
the Feature Pack, go to step 3.
|
| You need the individual
features to comply with the new limits (leave the
Feature Pack as-is) |
Follow the Recovery Steps for each individual
Feature Out of Compliance problem
listed in the Summary area to make sure all
features comply with the existing limits set by
the Feature Pack. Once all individual
features are compliant, this problem should also
be resolved. Do not continue with the
remaining Recovery steps for this problem. |
|
| 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. |
Note: Additional information on this issue may be available. Please visit the Dell support website at support.dell.com and select your product model. Choose "troubleshooting" as your tool option, then search by this procedure title.