Home
  •  

Monitor REC_REMOTE_NO_LUN (54)

NetAppSANtricity.FailureID_0054_Monitor (UnitMonitor)

The failure type is Remote No LUN.

Knowledge Base article:

remoteNoLun

What Caused the Problem?

This storage array is able to communicate with the remote storage array but cannot communicate with the remote volume on that storage array. Possible causes are:

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

Recovery Steps

1

If...

Then...

You wish to retain the mirror relationship

Go to step 2.

You do not wish to retain the mirror relationship

Delete the mirror relationship from both the local and remote storage arrays by highlighting each mirrored volume in its respective Array Management Window (AMW) and selecting the

Copy Services > Mirroring > Synchronous Mirroring > Remove Mirror Relationship

menu option.

Note: You will not need to remove the mirror relationship from the remote volume if it has been deleted or the remote volume's mirror relationship has been removed.

Go to step 5.

2

Open the AMW for the remote storage array by highlighting the remote storage array in the Enterprise Management Window and selecting the

Tools > Manage Storage Array

menu option.

3

Open the remote storage array's Recovery Guru by clicking on the Recovery Guru button on the remote storage array's AMW.

If...

Then...

The remote storage array's Recovery Guru shows problems associated with the volume listed in this Recovery Guru's Details area

Fix all errors associated with the affected remote volume by performing the steps listed in the Recovery Guru procedures.

Go to step 5.

The remote storage array doesn't show any problems associated with the volume listed in this Recovery Guru's Details area

-OR-

The remote volume has been deleted

Go to step 4.

4

a

Delete the mirror relationship from both the local and remote storage arrays by highlighting each mirrored volume in its respective AMW and selecting the

Copy Services > Mirroring > Synchronous Mirroring > Remove Mirror Relationship

menu option.

Note: You will not need to remove the mirror relationship from the remote volume if it has been deleted or the remote volume's mirror relationship has been removed.

b

If...

Then...

The remote volume has been deleted

Create a new remote volume the same size as the local volume.

Go to step c.

The remote volume has not been deleted

Go to step c.

c

Re-establish the mirror relationship by highlighting the volume you wish to be the primary volume and selecting the

Copy Services > Mirroring > Synchronous Mirroring > Create Mirrored Pair

menu option.

5

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_REMOTE_NO_LUN
The failure type is Remote No LUN. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppSANtricity.FailureID_0054_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_REMOTE_NO_LUN_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.StateId95ECF99D77FC6967A97E07C5B1C5C3BF" MonitorTypeStateID="NoIssue" HealthState="Success"/>

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

  </OperationalStates>

  <Configuration>

    <FailureID>54</FailureID>

    <IntervalSeconds>361</IntervalSeconds>

    <TimeoutSeconds>300</TimeoutSeconds>

    <Trace>0</Trace>

  </Configuration>

</UnitMonitor>