The number of drive slots discovered exceeds the maximum number of drive slots supported for the current SubModel/Key.
What Caused the Problem?
The storage array has an Out of Compliance status because it contains more than the allowed number of drive slots. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
This problem typically occurs when you add an additional drive tray after you already have the maximum number of drive slots allowed.
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.
This problem may cause other problems to be reported in the Summary area, such as device limits exceeded, loss of redundancy, and errors for missing drives or volumes. If there are multiple problems reported in the Summary area, complete them in this order: 1) Feature Bundle Out of Compliance (see first bullet, above for more information), 2) This problem (Drive Slot Limit Exceeded), and then 3) any other problem. After you click the
Recheck
button after completing these recovery steps, some or all of the other problems may be resolved.
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
Change the segment size of a volume
Change the RAID level of a volume group
Activate mirroring features
Assign hot spares
Invoke the Automatic Configuration Wizard
Recovery Steps
1 | If you performed one of the following actions that resulted in the Out of Compliance state, then perform the associated tasks to resolve the issue:
| ||||||||||||
2 | If you altered your cabling configuration to add or remove the drive tray, refer to your cabling documentation and ensure that you have a recommended cabling configuration. | ||||||||||||
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 | 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_0368_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_DRIVE_SLOT_LIMIT_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.StateId2A0FCCF4453F3B10AEE985108F4782A2" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateIdEB51B3AF3097987C1A3EEAB4BF3DEF48" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>368</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>