Monitor REC_RVM_NOT_COMPLIANT (49)

Remote Mirroring Premium Feature - Out Of Compliance

What Caused the Problem?

The Remote Logical Drive Mirroring Premium Feature is out of compliance.

This problem can occur in the following scenarios:

• Scenario 1 (Most common scenario)

  - The current number of mirror relationships on the storage subsystem exceeds the number of mirror relationships allowed. See the Important Notes for more detail on this scenario.

• Scenario 2 (Less common scenario)

  - You connected drives to one or more controllers where 1) the controllers were NOT previously attached to any drives and 2) the drives were already previously configured while attached to other controllers where the Remote Logical Drive Mirroring feature was supported and enabled. In this Scenario, you can get this problem even if there are no mirror relationships on the storage subsystem.  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

• 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 subsystem. 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 Bundle Out of Compliance problem, then proceed with the Recovery Steps below.

• Scenario 1 typically happens because you:

  • Disabled the Remote Logical Drive Mirroring feature while mirror relationships are still present (in other words, the storage subsystem allows zero since the Remote Logical Drive Mirroring feature is disabled, and you currently have more than 0)

  • Enabled or Disabled a Feature Pack resulting in the storage subsystem allowing less mirror relationships than are currently present on the storage subsystem (See first bullet, above)

• Scenario 2 happens because the controllers were not previously attached to drives, so the controllers 'adopt' the configuration database of the first drive they encounter.  When drives are adopted by the controllers, the configuration database contained on the drives (which includes all of the information about the previous storage subsystem, including the Enabled/Disabled information of features) is used by the controllers.  Therefore, the information in the configuration database shows that the Remote Logical Drive Mirroring feature is enabled, but the feature is either disabled on this storage subsystem or not supported by the controllers. If the controllers had been previously attached to drives and then another set of drives are added, then the new drives would be 'imported' (overwriting the configuration database) rather than 'adopted' since the controller is using the configuration database of the existing drives.

• For Scenario 1, you can fix this problem in two ways:

  • You can re-enable the Remote Logical Drive Mirroring feature key

  • You can remove mirror relationships until you are below the limit allowed by the storage subsystem

• For Scenario 2, you can fix this problem in two ways:

  • You can disable the Remote Logical Drive Mirroring feature once all of the mirror relationships have been removed

  • You can enable the Remote Logical Drive Mirroring feature key if it is supported by this storage subsystem

• The following events will occur while this feature is in an Out of Compliance state:

• • This storage subsystem will remain in a Needs Attention state

  • A critical 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 logical drives, flashcopies, mirror relationships, logical drive copy pairs, and storage partitions

    • Assign hot spares

    • Change the segment size of a logical drive

    • Change the RAID level of an array

    • Expand the capacity of an array or logical drive

Recovery Steps

Procedure for Scenario 1

Procedure for Scenario 2