Mirror Communication Error - Unable to Contact Storage Subsystem
What Caused the Problem?
This storage subsystem is able to communicate with the fabric to which it is connected, but cannot communicate with the remote storage subsystem that contains the remote logical drive in the mirror relationship. Possible causes are:
- Faulty minihub or interface transceiver (GBIC or SFP) on the storage subsystem side of the fabric to remote storage subsystem connection
- Faulty switch, switch port, or interface transceiver (GBIC or SFP) on the switch side of the fabric to remote storage subsystem connection
- Loose, damaged, or disconnected fibre channel cables between the fabric and the remote storage subsystem
- Loose, damaged, or removed fibre channel cables between two switches in the fabric
- Remote storage subsystem 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 you know that your remote primary storage subsystem has experienced an unrecoverable catastrophic failure and is inaccessible by any hosts, you may want to promote your associated local secondary logical drive(s) to a primary role for disaster recovery and business continuance purposes.
Caution
Forcing the promotion of the local secondary logical drive to a primary role can result in a Dual Primary Logical Drive Conflict if the remote storage subsystem recovers. You should be sure that this role reversal is required for disaster recovery or business continuance purposes before performing the operation.
You can force this role reversal by highlighting the secondary logical drive in the local storage subsystem's Array Management Window and selecting the Logical Drive>>Remote Logical Drive Mirroring>>Change>>Role to Primary menu option.
Recovery Steps
1
|
Attempt to open an Subsystem Management Window for the remote storage subsystem by highlighting the remote storage subsystem in the Enterprise Management Window and selecting the Tools>>Manage Device menu option.
If...
|
Then...
|
The Subsystem Management Window can connect to the storage subsystem
|
Select the Recovery Guru button on the Subsystem Management Window of the remote storage subsystem.
If...
|
Then...
|
There are failures detected on the remote storage subsystem
|
Correct all failures listed in the Recovery Guru Summary area by selecting the failure and performing the displayed recovery procedure.
Go to Step 4.
|
There are no failures detected on the remote storage subsystem
|
Go to Step 2.
|
|
The Subsystem Management Window cannot connect to the storage subsystem
|
Check to see that the remote storage subsystem's power supplies are properly connected to an operating power source and has the power switch in the on position.
If...
|
Then...
|
You find a power or power supply problem
|
Correct the problem and go to Step 4.
|
You cannot find a power or power supply problem
|
You may also have an Ethernet network connection problem. Verify the network is operational.
If...
|
Then...
|
If you find a problem with your network
|
Correct the problem and go to Step 1.
|
If your network is operational
|
Contact your technical support representative.
|
|
|
|
2
|
Check the switch the remote storage subsystem is connected to for indications of a switch port, interface transceiver (GBIC or SFP), or other type of switch failure.
If...
|
Then...
|
There is a problem with the switch
|
Correct the problem.
Go to Step 4.
|
There is not a problem with the switch
|
Go to Step 3.
|
|
3
|
Verify that the cables connecting the switch and the remote storage subsystem are not loose, disconnected, or damaged.
If...
|
Then...
|
A damaged cable is detected
|
Replace the cable.
Go to Step 4.
|
A loose or disconnected cable is detected
|
Reconnect the cable.
Go to Step 4.
|
A loose, disconnected, or damaged cable is not detected
|
Verify your cabling configuration. If you believe that your configuration is valid but the problem still exists, contact your technical support representative
|
|
4
|
Select Recheck to rerun the Recovery Guru to ensure that the failure has been fixed.
|