A few things: - when defining the replication partner, the SAN doesn't 'test' if your information is right, so if you defined the partner incorrectly, you wouldn't know till you try to replicate an actual volume - when defining a replication partner, the connection is case sensitive for the group name - just to ensure the 2nd SAN is set up, you could add that group IP to the iSCSI initiator on one of your ESX boxes, create a dummy volume and verify that the ESX box can see the volume (don't need to format it or so, just verify that it's visible under the storage adapters)
Hi. Probably just some configuration I have missed, but I cant get any further.    We just bought a new PS6000 SAN to setup replication from a production PS5000 SAN. 3 VMware host uses to the PS5000.   I installed the PS6000 SAN following the manual and connected to the same switch as the ps5000 SAN. Then, on both SANS i added the other SAN as a replication partner using the Group name and the group IP address, and respective passwords.    SANPS5000(4 volumes) Group Name: san1 Group IP: 192.168.1.1   Replication partner: Group name: san2 Replication partner IP: 192.168.1.2 **************************************************************************** SANPS6000(no volumes added) Group name: san2 Group IP: 192.168.1.2   Replication partner: Group name: san1 Replication partner IP: 192.168.1.1   For some reason, when I try to setup replication on a volume on San1, I get a "No connection could be established. Verify that the partner IP address is correct" error message at the end.    I have verified that the IP's is correct, both SAN's are connected to only one switch(switch ports are unconfigured), the computer I use to setup replicaton is attached to the san switch and both group IP's can be pinged from this computer.  Firmware is 4.2 on ps5000 and 4.3 on ps6000 Any advice that might help me would be much appreciated.   \\Tor [IMAGE]
Replication setup between PS5000X and PS6000XV