Home
  •  

Monitor REC_MIRROR_DUAL_PRIMARY (51)

IBMStorageSubsystem.FailureID_0051_Monitor (UnitMonitor)

Monitor Description for (51)

Knowledge Base article:

Dual Primary Logical Drive Conflict

What Caused the Problem?

A role change from secondary to primary was attempted while there was a connection problem between the local and remote storage subsystems. The user chose to force the role change which promoted the local secondary logical drive's role to primary without demoting the remote primary logical drive's role to secondary. The connection problem was subsequently corrected making the remote logical drive visible again. This resulted in both logical drives being in a primary role. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.

Recovery Steps

1

Recreate the mirror relationship by performing the following steps:

a

Delete the mirror relationship from either storage subsystem by highlighting either primary logical drive in its respective Subsystem Management Window and selecting the

Logical Drive >> Remote Logical Drive Mirroring >> Remove Mirror Relationship

menu option.

Note: The mirror relationship for the remote logical drive will not be removed if there is a connection problem between the two storage subsystems. If the mirror relationship remains on the remote logical drive after the above action, highlight that logical drive from its respective Subsystem Management Window and select the Logical Drive >> Remote Logical Drive Mirroring >> Remove Mirror Relationship menu option.

b

In its respective Subsystem Management Window, highlight the logical drive you wish to be the primary logical drive and select the

Logical Drive >> Remote Logical Drive Mirroring >> Create

menu option. Follow the instructions in the Create Remote Logical Drive Mirror wizard to re-create the mirror relationship.

2

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:

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_MIRROR_DUAL_PRIMARY
Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="IBMStorageSubsystem.FailureID_0051_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_MIRROR_DUAL_PRIMARY_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.StateId97198CB40C0C4BD154498E645A97947A" MonitorTypeStateID="NoIssue" HealthState="Success"/>

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

  </OperationalStates>

  <Configuration>

    <FailureID>51</FailureID>

    <IntervalSeconds>59</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>