The failure type is Remote No 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:
There is a faulty interface transceiver (GBIC or SFP) on the storage array side of the fabric to remote storage array connection.
There is a faulty switch, switch port, or interface transceiver (GBIC or SFP) on the switch side of the fabric to remote storage array connection.
There are loose, damaged, or disconnected fibre channel cables between the fabric and the remote storage array.
There are loose, damaged, or removed fibre channel cables between two switches in the fabric.
The remote storage array has lost power or is not functioning.
The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
If the remote storage array has experienced an unrecoverable catastrophic failure and is inaccessible by any hosts, it may be necessary to force promote the associated local secondary volumes to the Primary role for disaster recovery and business continuance purposes.
If the volumes are mirrored through Asynchronous Mirroring, the role can be force promoted by highlighting the secondary volume and selecting the
Copy Services > Mirroring > Asynchronous Mirroring > Mirrored Pair > Change > Role to Primary
menu option.
If the volumes are mirrored through Synchronous Mirroring, the role can be force promoted by highlighting the secondary volume and selecting the
Copy Services > Mirroring > Synchronous Mirroring > Change > Role to Primary
menu option.
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.
| ||||||||||||||||||||||
2 | Verify the network is operational.
| ||||||||||||||||||||||
3 | Execute a port connections test to help identify specific connectivity problems.
| ||||||||||||||||||||||
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. |
Target | NetAppESeries.StorageArray | ||
Parent Monitor | NetAppESeries.StorageArrayAvailability | ||
Category | Custom | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Alert Auto Resolve | True | ||
Monitor Type | NetAppESeries.FailureUnitMonitorType | ||
Remotable | True | ||
Accessibility | Internal | ||
Alert Message |
| ||
RunAs | Default | ||
Comment | Machine generated entity |
<UnitMonitor ID="NetAppESeries.FailureID_0055_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_REMOTE_NO_ARRAY_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.StateId9FEFDA887DD57F3B3CC5D83A03EFB812" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateId6D6BFCC0DF6230C53DE1891B5EFC078D" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>55</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>