asked on SRM 5.0 Problem Adding Array
Problem: Attempting to add an array to SRM from the VS Client SRM Plugin and it fails saying "SRA command 'discoverArrays' failed. Failed to connect to Group
Make sure the address is accessible, username and password are correct" We are unable to get it to recognize the arrays.
Environment: VSphere 5.0 Enterprise all the way through. The protected side has Dual hosts with VCenter server running as a a VM on a single 24tb EQL PS 4100. The Management network is on Subnet A which also hosts all our other servers and the ISCSI is isolated on Subnet B.
The recovery side looks much the same except there are two EQL PS4000's (1 4tb and 1 8TB). We are connected to the recovery side via WAN tunnel. The Management Network on the recovery side is on Subnet C while the ISCSI is isolated on Subnet D.
The arrays are currently replicating across the wan using Cereon's aCelera Sync. The Hosts can see their respective arrays just fine. The arrays are accessible on their management interfaces from each VC and the group IP of each array is ping-able from each VC. The VC's are both running SRM 5.0. We are currently using the SRA's from Vmware but we have tried the ones from Equallogics even through I'm sure they were the same. We have progressed through the SRM setup step by step and have been successful with each step until this point.
We've been through it with VMWare, they are clueless. Equallogics support won't touch it without paying for consulting fees. The consultants we do pay for said to call support. We are using the group IP of the Protected array as the entry for the group Ip Address in the managed group properties of the add array wizard. We are using the group IP address of the recovery array for the Partner name in the partner group area. We are sure that we are using the correct accounts for both sides to the best of our knowledge.
Any help on what we might be missing or what we're doing wrong is appreciated.
Make sure the address is accessible, username and password are correct" We are unable to get it to recognize the arrays.
Environment: VSphere 5.0 Enterprise all the way through. The protected side has Dual hosts with VCenter server running as a a VM on a single 24tb EQL PS 4100. The Management network is on Subnet A which also hosts all our other servers and the ISCSI is isolated on Subnet B.
The recovery side looks much the same except there are two EQL PS4000's (1 4tb and 1 8TB). We are connected to the recovery side via WAN tunnel. The Management Network on the recovery side is on Subnet C while the ISCSI is isolated on Subnet D.
The arrays are currently replicating across the wan using Cereon's aCelera Sync. The Hosts can see their respective arrays just fine. The arrays are accessible on their management interfaces from each VC and the group IP of each array is ping-able from each VC. The VC's are both running SRM 5.0. We are currently using the SRA's from Vmware but we have tried the ones from Equallogics even through I'm sure they were the same. We have progressed through the SRM setup step by step and have been successful with each step until this point.
We've been through it with VMWare, they are clueless. Equallogics support won't touch it without paying for consulting fees. The consultants we do pay for said to call support. We are using the group IP of the Protected array as the entry for the group Ip Address in the managed group properties of the add array wizard. We are using the group IP address of the recovery array for the Partner name in the partner group area. We are sure that we are using the correct accounts for both sides to the best of our knowledge.
Any help on what we might be missing or what we're doing wrong is appreciated.
VMware
Last Comment
mis_gsc
ASKER
All LUN ID's are 0 on both arrays for all datastores.
We are replicating SAN to SAN through Certeon's aCelera Sync
We are replicating SAN to SAN through Certeon's aCelera Sync
I remember someone having an issue such as this where all the LUNs were the same LUN ID. This was with a HP P4000 unit but something to try.
Try creating a LUN with a different LUN ID, replicating it and adding to SRM
Try creating a LUN with a different LUN ID, replicating it and adding to SRM
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Poor labeling and Misunderstanding how the the array should be added. A little experimentation and we figured it our on our own.
Are you replicating SAN to SAN or using VMWare replication?