Home
  •  

Monitor REC_PARTITIONS_NOT_COMPLIANT (30)

NetAppSANtricity.FailureID_0030_Monitor (UnitMonitor)

This is obsolete.

Knowledge Base article:

SANshare Storage Partitioning Premium Feature - Out Of Compliance

What Caused the Problem?

The SANshare Storage Partitioning Premium Feature is Out of Compliance. This problem can occur in the following scenarios:

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

Important Notes

Recovery Steps

If...

Then...

This problem occurred due to Scenario 1

Go to

Procedure for Scenario 1

.

This problem occurred due to Scenario 2

Go to

Procedure for Scenario 2

.

Procedure for Scenario 1

1

If...

Then...

You want to resolve this problem by enabling the SANshare Storage Partitioning feature key

Go to step 2.

You want to resolve this problem by removing partitions until you are below the limit allowed by the storage array

Reduce the number of partitions to equal to or less than the number of partitions allowed. The maximum number of partitions allowed is listed in the Details area.

a

Select the

Host Mappings

tab in the Array Management Window.

b

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

The right-side of the screen displays all the mappings for this storage array and also provides a tally of the SANshare 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: Potential loss of data access. Removing or changing mappings may cause any host attached to the storage array to lose visibility of a file system mounted on the storage array. Stop I/Os on the affected volumes before changing or removing them.

c

Highlight a mapping and use either the

Host Mappings > LUN Mapping > Change

or

Host Mappings > LUN Mapping > Remove

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 4.

2

Select the

Storage Array > Premium Features

menu option in the Array Management Window.

If...

Then...

The SANshare Storage Partitioning feature appears in this dialog (regardless of status)

A feature key file is needed to enable the feature.

If...

Then...

The feature has already been enabled at any time for this storage array

AND

You have the feature key file

Go to step 3.

The feature has not been enabled for this storage array

OR

The feature has been enabled, but you do not have the feature key file

Perform the following steps:

a

Identify the feature key identifier from the "Premium Features and Feature Pack Information" dialog.

b

Contact your Technical Support Representative to request a feature key file.

c

After you have the feature key file, go to step 3.

The SANshare Storage Partitioning feature does NOT appear in this dialog

Your storage array cannot support this feature.

You can contact your Technical Support Representative to see if your storage array can be upgraded to a different feature pack, or you can repeat step 1 to remove partitions.

3

Click the

Use Key File

button to use the feature key file and enable the premium feature.

4

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.

 

Procedure for Scenario 2

1

If...

Then...

You want to enable the SANshare Storage Partitioning feature

Go to step 2.

You want to disable the SANshare Storage Partitioning feature

Go to step 4.

2

Select the

Storage Array > Premium Features

menu option in the Array Management Window.

If...

Then...

The SANshare Storage Partitioning feature appears in this dialog (regardless of status)

A feature key file is needed to enable the feature.

If...

Then...

The feature has already been enabled at any time for this storage array

AND

You have the feature key file

Go to step 3.

The feature has not been enabled for this storage array

OR

The feature has been enabled, but you do not have the feature key file

Perform the following steps:

a

Identify the feature key identifier from the "Premium Features and Feature Pack Information" dialog.

b

Contact your Technical Support Representative to request a feature key file.

c

After you have the feature key file, go to step 3.

The SANshare Storage Partitioning feature does NOT appear in this dialog

Your storage array cannot support this feature.

You can contact your Technical Support Representative to see if your storage array can be upgraded to a different feature pack, or you can go to step 4 to remove partitions.

3

Click the

Use Key File

button to use the feature key file and enable the premium feature, and then go to step 6.

4

Refer to the Details area to see how many partitions are present.

If...

Then...

There are currently partitions that need to be removed before disabling the feature

Remove all of the partitions.

a

Select the

Host Mappings

tab in the Array Management Window.

b

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

The right-side of the screen displays all the mappings for this storage array and also provides a tally of the SANshare Storage Partitions allowed and currently used.

 Caution: Potential loss of data access. Removing or changing mappings may cause any host attached to the storage array to lose visibility of a file system mounted on the storage array. Stop I/Os on the affected volumes before changing or removing them.

c

Highlight a mapping and use the

Host Mappings > LUN Mapping > Remove

option.

d

Repeat step c to remove all mappings, and then go to step 5.

 

There are no partitions

Go to step 5.

 

5

Disable the SANshare Storage Partitioning feature.

a

Select the

Storage Array > Premium Features

menu option in the Array Management Window.

b

Select the SANshare Storage Partitioning feature from the list.

c

Click the

Disable

button.

6

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.

Element properties:

TargetNetAppSANtricity.StorageArray
Parent MonitorNetAppSANtricity.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppSANtricity.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_PARTITIONS_NOT_COMPLIANT
This is obsolete. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppSANtricity.FailureID_0030_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppSANtricity.StorageArray" ParentMonitorID="NetAppSANtricity.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppSANtricity.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="NetAppSANtricity.REC_PARTITIONS_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="NetAppSANtricity.StateId4CF8698847D2AF2A62A9FBD51019D697" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="NetAppSANtricity.StateId5686DCCE8C95C0105CB2F5AA2A365329" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>30</FailureID>

    <IntervalSeconds>361</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>