Monitor REC_ARVM_ROLE_CHANGE_PAUSED (447)

NetAppESeries.FailureID_0447_Monitor (UnitMonitor)

Role change has paused due to issues with required data synchronization.

Knowledge Base article:

Mirror Communication Error - Unable to Contact Storage Array

What Caused the Problem?

This storage array is able to communicate with the fabric to which it is connected, however it cannot communicate with the remote storage array that contains the remote volume in a mirror relationship. This problem can occur in the following situations:

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

Important Notes

 Caution: Possible Loss of Access to Data. Forcing the promotion of the local secondary volume to the Primary role can result in a dual primary role conflict if the remote storage array recovers. Therefore, the secondary volume should only be forced to the Primary role if it is required for disaster recovery or business continuance purposes.

Recovery Steps

1

Attempt to open the Array Management Window (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.

If...

Then...

The AMW can connect to the storage array

Open the Recovery Guru for the remote storage array.

If...

Then...

There are failures detected.

Perform the following steps:

a

Correct any problems reported in the Recovery Guru for the remote storage array.

b

After the problems are corrected on the remote storage array, go to step 4 in this procedure.

There are no failures detected

Go to step 3.

The AMW cannot connect to the storage array

Verify the remote storage array's power supplies are properly connected to an operating power source and that the power switch is in the on position.

If...

Then...

There is a power or power supply problem

Correct the problem and then go to step 2.

There is not a power or power supply problem

You may have an Ethernet network connection problem. Go to step 2.

2

Verify the network is operational.

If...

Then...

There is a problem with your network

Correct the problem and then go to step 1.

The network is operational

Do not continue with the remaining recovery steps and contact your Technical Support Representative.

3

Execute a port connections test to help identify specific connectivity problems.

a

Select the

Copy Services > Mirroring > View Mirroring Port Connections

menu option.

b

Select the affected remote storage array.

c

Click the

Start

button to run the test.

If...

Then...

The test indicates a disconnection problem

Check for the following and fix any problems found, and then go to step 4.

  • Loose, damaged, or disconnected cables

  • A faulty SFP on the host port or switch

The test indicates a cross connection problem

Verify that each controller is connected to the correct switch or switch zone, and then go to step 4.

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.

Element properties:

TargetNetAppESeries.StorageArray
Parent MonitorNetAppESeries.StorageArrayAvailability
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeNetAppESeries.FailureUnitMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
Alert: REC_ARVM_ROLE_CHANGE_PAUSED
Role change has paused due to issues with required data synchronization. Alert Value: {0}
RunAsDefault
CommentMachine generated entity

Source Code:

<UnitMonitor ID="NetAppESeries.FailureID_0447_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppESeries.REC_ARVM_ROLE_CHANGE_PAUSED_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="NetAppESeries.StateIdEEBEC587543E815C245A5E37A3198160" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId76F0D903B8825FE487E16121EB7D722" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>447</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>