Home
  •  

Monitor REC_VG_CLONED (216)

IBMStorageSubsystem.FailureID_0216_Monitor (UnitMonitor)

The drives for a volume group that were removed from an array with no export performed, have been re-inserted back into that array, after having been imported into another array where the volume group's configuration was changed in various ways.

Knowledge Base article:

Array Cloned

What Caused the Problem?

The storage subsystem is reporting that the same array is appearing more than once in the configuration. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Caution: Electronic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.

Important Notes

Recovery Steps

If...

Then...

This problem was a result of Scenario 1 (refer to the Important Notes, above)

Go to

Recovery Steps for Scenario 1

.

This problem was a result of Scenario 2 (refer to the Important Notes, above)

Go to

Recovery Steps for Scenario 2

.

 

Recovery Steps for Scenario 1

1

Refer to the Details area to find which drives are associated with the affected array.

2

Remove each drive listed in the Details area until all of them have been removed from the storage subsystem.

3

Highlight the Missing Logical Drive in the Logical View of the Subsystem Management Window (AMW) that corresponds to the affected logical drive in the Details area.

4

Select the

Array >> Delete

menu option.

Note: By completing this step, you are removing the storage subsystem's reference to the array.  When you re-insert the drives in the next steps, the storage subsystem will view the array as a new foreign array.

5

Reinsert the drives that you removed in step 2.

6

As you insert the drives, a Contingent array should appear in the Logical View. When ALL of the drives are spun up and recognized, the Contingent array should transition to an Exported logical drive.

Select the Exported array in the Logical View, and then select the Advanced >> Maintenance >> Import Array menu option.

7

Follow the instructions in the Import Array dialog to properly import the array into the storage subsystem.

8

Click

Recheck

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.

 

Recovery Steps for Scenario 2

1

If...

Then...

You are certain that the foreign drives listed in the details area should be in the same array as the native drives

Go to step 2.

You are NOT certain that the foreign drives listed in the details area should be in the same array as the native drives

Contact your technical support representative to assist you with fixing this problem.  Do not continue with the remaining Recovery Steps.

2

Mark the drives as Native by completing the following steps:

a

Open a Command Prompt, and type the following command:

SMcli -n <storageSubsystem_name>;

where storageSubsystem_name is the name of the storage subsystem listed in the Details area.

Note: If you receive an error from this command, change your working directory to the directory that contains the SMcli executable.

b

Execute the following command in order to mark the drives as native to this storage subsystem:

Important: The following command should not be used in any other circumstance other than to correct this specific problem.  If used in the wrong situation, this command could result in data loss.

set allDrives toNative;

c

When the operation completes, exit the Command Prompt, and go to step 3.

3

Click

Recheck

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:

TargetIBMStorageSubsystem.StorageSubsystem
Parent MonitorIBMStorageSubsystem.StorageSubsystemAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeIBMStorageSubsystem.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_VG_CLONED
The drives for a volume group that were removed from an array with no export performed, have been re-inserted back into that array, after having been imported into another array where the volume group's configuration was changed in various ways. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="IBMStorageSubsystem.FailureID_0216_Monitor" Accessibility="Internal" Enabled="true" Target="IBMStorageSubsystem.StorageSubsystem" ParentMonitorID="IBMStorageSubsystem.StorageSubsystemAvailability" Remotable="true" Priority="Normal" TypeID="IBMStorageSubsystem.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="IBMStorageSubsystem.REC_VG_CLONED_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="IBMStorageSubsystem.StateId5C0B6D10C4FD1BE52718636FBF5009FD" MonitorTypeStateID="NoIssue" HealthState="Success"/>

    <OperationalState ID="IBMStorageSubsystem.StateId2CAD52F0B5EF935FF087C120CBB90F7E" MonitorTypeStateID="IssueFound" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <FailureID>216</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>