EF & E-Series, SANtricity, and Related Plug-ins
EF & E-Series, SANtricity, and Related Plug-ins
Hi,
We are trying to establish a sync mirror on 2 2824 with CIsco MDS 9148. Everything looks fine on storage, I can choose the primary and secondary storage, but when I apply the seletion after 3`second I got the following error message: The operation cannot complete because the storage array cannot comunicate with the remote storage array to complete this request. Possible causes include network or connection problems, or no power to the storage array. Check these possible causes and then retry the operation. (API 180)
I found the following kb, which seems to fit my case, but it does not contain any information
Do you have any idea what can be the issue?
Thanks
David
try to check these causes:
Possible causes include:
Fibre Channel connection requirements are as follows:
and i'll check that kb too.
thanks for letting us know
Jeff
Hi Jeff,
Thanks for your help. It solved the main issue and now we could create the mirror.
We have one more issue left. We have 2 SAN switches and 2 storages.
When we simulate a disaster and turn off a switch1(where controller A ports connected), and Volume is owned by ControllerB, the controller change does not happen and the mirror fails.
After a manual controller change it starts to work.
We experienced it in normal operation when ownership loadbalance was enabled and when the ownership changed automatically on the primary volume, but not on the secondary, the mirror stopped. Manually change the owner of the volume on both storages solves the issue
Do you have an idea what can be the reason ?
Thanks
David
Hi Jeff,
Thanks for your help. It solved the main issue and now we could create the mirror.
We have one more issue left. We have 2 SAN switches and 2 storages.
When we simulate a disaster and turn off a switch1(where controller A ports connected), and Volume is owned by ControllerB, the controller change does not happen and the mirror fails.
After a manual controller change it starts to work.
We experienced it in normal operation when ownership loadbalance was enabled and when the ownership changed automatically on the primary volume, but not on the secondary, the mirror stopped. Manually change the owner of the volume on both storages solves the issue
Do you have an idea what can be the reason ?
Thanks
David