Storage Partitioning Premium Feature - Out Of Compliance

What Caused the Problem?

The Storage Partitioning Premium Feature is out of compliance. This normally occurs if an array with storage partitions data has been moved into this storage subsystem and one of the following conditions exists.

The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Recovery Steps

1

Use the table below and the information in the Recovery Guru Details area to determine what actions to take.

If...

Then...

The Storage Partitioning Feature is not authorized for this storage subsystem

Do one of the following:

  • Disable the feature using the Storage Subsystem>>Premium Features>>Disable option in the Subsystem Management Window and then delete the partitions using the Mappings>>Delete option.

    -OR-

  • Go to step 2 to enable an authorized version of this feature.

The Storage Partitioning Feature is authorized, but the current number of partitions on the storage subsystem exceeds the number of partitions allowed for this storage subsystem

Do one of the following:

  • Go to step 2 to obtain and enable the appropriate Storage Partitioning Feature which allows a larger number of partitions.

    -OR-

  • Complete steps 3 - 5 to change the number of partitions so that the total does not exceed the allowed number of partitions for this storage subsystem.

2

A separate Feature Key File is needed to enable each level of storage partitions. To increase or enable Storage Partitioning Feature, you will need to perform the following:

  • Retrieve the Feature Enable Identifier by selecting Storage Subsystem>>Premium Features>>List in the Subsystem Management Window.
  • Contact your technical support representative to request a Feature Key File.
  • Once you have obtained the appropriate Feature Key File from your technical support representative, select Storage Subsystem>>Premium Features>>Enable in the Subsystem Management Window to enable it.
  • Go to step 6.

3

Display the Mappings View by selecting the View>>Mappings option.

4

Highlight the storage subsystem (root) node on the left-side of the screen.

The right-side of the screen displays all the mappings for this storage subsystem and also provides a tally of the Storage Partitions allowed and currently used. There are three rules you should be aware of when considering what mappings need to change to reduce the number of partitions to the allowable limit.

Rule 1

Each host group or host that has a specific mapping represents one partition. If there are two or more mappings on the same host group or host, those mappings still represent just one partition.

Rule 2

If a host group has mappings and a host that is part of the host group also has mappings of its own, the host group and host (and their associated mappings) represent two distinct partitions.

Rule 3

The default host group does not constitute one of the partitions.

Caution
Deleting or changing mappings may cause any host attached to the storage subsystem to lose visibility of a filesystem mounted on the storage subsystem. Stop I/Os on the affected logical drives before changing or deleting them.

5

Delete and/or change a mapping one at a time until the number of partitions is reduced to the allowable limit. Highlight a mapping and use either the Mappings>>Change>>Mapping or Mappings>>Delete option. If you change a mapping, either move the mapping to another host group or host that already has mappings, or move it to the default group.

After making the appropriate changes, go to step 6.

6

Select Recheck to rerun the Recovery Guru to ensure that the failure has been fixed.

If...

Then...

Another type of failure is reported,

Follow the recovery procedures given for that failure.

No failures are reported.

You are finished with the recovery procedure.