EqualLogic replication

Question

Hello We are having issues configuring volume replication between our two new EQL groups. Two groups:  SAN10.0.0.178SAN-1 (PS6100E)10.0.0.176SAN-2 (PS6100X)10.0.0.177  SAN-DR10.1.1.15SAN-DR1 (PS6100E)10.1.1.16 I configured replication partners and now receive these messages: SAN Subject: SAN: 1 events http://10.0.0.178/ ----------------------------------------- ERROR event from storage array SAN-2 subsystem: MgmtExec event: 7.4.78 time: Tue Mar 26 12:33:35 2013 Partner SAN-DR: iSCSI: login timed out. Make sure the partner IP address is correct and reachable. and SAN Subject: SAN: 1 events http://10.0.0.178/ ----------------------------------------- ERROR event from storage array SAN-1 subsystem: MgmtExec event: 7.4.78 time: Tue Mar 26 12:33:35 2013 Partner SAN-DR: iSCSI: login timed out. Make sure the partner IP address is correct and reachable. The firewall on both ends has been opened to allow traffic to and from all addresses above. When I configure replication for a volume from inside group manager I get an error iSCSI: login timed out. Make sure the partner IP address is correct and reachable. From another post I did the following ping and tracert tests: SAN> ping '-I 10.0.0.176 10.1.1.16' PING 10.1.1.16 (10.1.1.16): 56 data bytes64 bytes from 10.1.1.16: icmp_seq=0 ttl=253 time=10.000 ms64 bytes from 10.1.1.16: icmp_seq=1 ttl=253 time=0.000 ms----10.1.1.16 PING Statistics----2 packets transmitted, 2 packets received, 0.0% packet lossround-trip min/avg/max/stddev = 0.000/5.000/10.000/7.071 msSAN> ping '-I 10.0.0.177 10.1.1.16'cli-child: Can't set source interface/address: Can't assign requested addressSAN> ping '-I 10.0.0.178 10.1.1.16'PING 10.1.1.16 (10.1.1.16): 56 data bytes64 bytes from 10.1.1.16: icmp_seq=0 ttl=253 time=0.000 ms64 bytes from 10.1.1.16: icmp_seq=1 ttl=253 time=0.000 ms----10.1.1.16 PING Statistics----2 packets transmitted, 2 packets received, 0.0% packet lossround-trip min/avg/max/stddev = 0.000/0.000/0.000/0.000 msSAN> ping '-I 10.0.0.178 10.1.1.15'PING 10.1.1.15 (10.1.1.15): 56 data bytes64 bytes from 10.1.1.15: icmp_seq=0 ttl=253 time=10.000 ms64 bytes from 10.1.1.15: icmp_seq=1 ttl=253 time=0.000 ms----10.1.1.15 PING Statistics----2 packets transmitted, 2 packets received, 0.0% packet lossround-trip min/avg/max/stddev = 0.000/5.000/10.000/7.071 msSAN> ping '-I 10.0.0.177 10.1.1.15'cli-child: Can't set source interface/address: Can't assign requested addressSAN> ping '-I 10.0.0.176 10.1.1.15'PING 10.1.1.15 (10.1.1.15): 56 data bytes64 bytes from 10.1.1.15: icmp_seq=0 ttl=253 time=0.000 ms64 bytes from 10.1.1.15: icmp_seq=1 ttl=253 time=0.000 ms----10.1.1.15 PING Statistics----2 packets transmitted, 2 packets received, 0.0% packet lossround-trip min/avg/max/stddev = 0.000/0.000/0.000/0.000 ms And the traceroute output: SAN> support traceroute '-s 10.0.0.176 10.1.1.15'You are running a support command, which is normally restricted to PS Series Technical Support personnel. Do not use a support command without instruction from Technical Support.cli-child to 10.1.1.15 (10.1.1.15) from 10.0.0.176, 30 hops max, 40 byte packets 1 10.0.0.129 (10.0.0.129) 0.000 ms 10.000 ms 0.000 ms 2 10.2.1.150 (10.2.1.150) 0.000 ms 10.000 ms 0.000 ms 3 10.1.1.15 (10.1.1.15) 0.000 ms 10.000 ms 0.000 ms SAN> support traceroute '-s 10.0.0.176 10.1.1.16'You are running a support command, which is normally restricted to PS Series Technical Support personnel. Do not use a support command without instruction from Technical Support.cli-child to 10.1.1.16 (10.1.1.16) from 10.0.0.176, 30 hops max, 40 byte packets 1 10.0.0.129 (10.0.0.129) 0.000 ms 0.000 ms 10.000 ms 2 10.2.1.150 (10.2.1.150) 0.000 ms 0.000 ms 10.000 ms 3 10.1.1.16 (10.1.1.16) 0.000 ms 0.000 ms 10.000 ms SAN> support traceroute '-s 10.0.0.177 10.1.1.16'You are running a support command, which is normally restricted to PS Series Technical Support personnel. Do not use a support command without instruction from Technical Support.cli-child to 10.1.1.16 (10.1.1.16) from 10.0.0.177, 30 hops max, 40 byte packetscli-child: sendto: No route to hostcli-child: wrote 10.1.1.16 40 chars, ret=-1 ^CSAN> support traceroute '-s 10.0.0.177 10.1.1.15'You are running a support command, which is normally restricted to PS Series Technical Support personnel. Do not use a support command without instruction from Technical Support.cli-child to 10.1.1.15 (10.1.1.15) from 10.0.0.177, 30 hops max, 40 byte packetscli-child: sendto: No route to hostcli-child: wrote 10.1.1.15 40 chars, ret=-1 ^CSAN> support traceroute '-s 10.0.0.178 10.1.1.15'You are running a support command, which is normally restricted to PS Series Technical Support personnel. Do not use a support command without instruction from Technical Support.cli-child to 10.1.1.15 (10.1.1.15) from 10.0.0.178, 30 hops max, 40 byte packets 1 10.0.0.129 (10.0.0.129) 10.000 ms 0.000 ms 10.000 ms 2 10.2.1.150 (10.2.1.150) 0.000 ms 0.000 ms 10.000 ms 3 10.1.1.15 (10.1.1.15) 0.000 ms 0.000 ms 10.000 ms SAN> support traceroute '-s 10.0.0.178 10.1.1.16'You are running a support command, which is normally restricted to PS Series Technical Support personnel. Do not use a support command without instruction from Technical Support.cli-child to 10.1.1.16 (10.1.1.16) from 10.0.0.178, 30 hops max, 40 byte packets 1 10.0.0.129 (10.0.0.129) 0.000 ms 10.000 ms 0.000 ms 2 10.2.1.150 (10.2.1.150) 0.000 ms 10.000 ms 0.000 ms 3 10.1.1.16 (10.1.1.16) 0.000 ms 0.000 ms 0.000 msSAN> Any suggestions for other things to try? Do jumbo packets need to be enabled? We have the data ports on a discrete network on both sides (a dedicated switch) the IP's above are the management IPs. There is no internet access for the iSCSI traffic ports. Thanks, -Travis

Joe S586 · Accepted Answer

Replication is only over the iSCSI network. I’ve noticed that the documentation isn’t very clear on this point in that it only references the "Group IP" when creating the Partnership. This is the iSCSI Group IP, as listed on the Group Configuration> General Tab> General Settings seciton.

To Replicate to a remote site, the two groups must be connected through a TCP/IP network with all partner IP’s reachable (Group IP, and all of the member eth interfaces that are on the iSCSI subnets). Also ICMP and Ports 3260 need to be open. Obviously, this link MUST be secured, with a firewall, VPN or encryption (or a mixture of them).

Also, you cannot use a NAT’ed IP address from Site A to Site B.

-joe

Joe S586 · Answer

No, Jumbo isn't required. The message 'No route to host' from the .177 to both .15. and .16 is a problem.  Check your default gateway IP address for all three of these members. Did you ping/traceroute from the DR back to the SAN group? -joe

quelx · Answer

Pings from the DR site to production:

SAN-DR> ping "-I 10.1.1.15 10.0.0.176"
PING 10.0.0.176 (10.0.0.176): 56 data bytes
64 bytes from 10.0.0.176: icmp_seq=0 ttl=253 time=0.000 ms

----10.0.0.176 PING Statistics----
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.000/0.000/0.000/0.000 ms
SAN-DR> ping "-I 10.1.1.15 10.0.0.177"
PING 10.0.0.177 (10.0.0.177): 56 data bytes
64 bytes from 10.0.0.177: icmp_seq=0 ttl=253 time=10.000 ms

----10.0.0.177 PING Statistics----
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 10.000/10.000/10.000/0.000 ms
SAN-DR> ping "-I 10.1.1.15 10.0.0.178"
PING 10.0.0.178 (10.0.0.178): 56 data bytes
64 bytes from 10.0.0.178: icmp_seq=0 ttl=253 time=10.000 ms

----10.0.0.178 PING Statistics----
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 10.000/10.000/10.000/0.000 ms
SAN-DR> ping "-I 10.1.1.16 10.0.0.176"  
PING 10.0.0.176 (10.0.0.176): 56 data bytes
64 bytes from 10.0.0.176: icmp_seq=0 ttl=253 time=10.000 ms

----10.0.0.176 PING Statistics----
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 10.000/10.000/10.000/0.000 ms
SAN-DR> ping "-I 10.1.1.16 10.0.0.177"
PING 10.0.0.177 (10.0.0.177): 56 data bytes
64 bytes from 10.0.0.177: icmp_seq=0 ttl=253 time=10.000 ms

----10.0.0.177 PING Statistics----
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 10.000/10.000/10.000/0.000 ms
SAN-DR> ping "-I 10.1.1.16 10.0.0.178"
PING 10.0.0.178 (10.0.0.178): 56 data bytes
64 bytes from 10.0.0.178: icmp_seq=0 ttl=253 time=0.000 ms

----10.0.0.178 PING Statistics----
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.000/0.000/0.000/0.000 ms
SAN-DR>

quelx · Answer

The default gateway is on a different netword from the above management ports. The iSCSI traffic is completely segregated from the internet (we put a default GW in because the config said we needed one to continue the setup, the address we put on is not a real gateway).

Do the iSCSI addresses need to be routable to the DR location?

I was thinking the replication would happen over the management network.

Thank you Joe,

-Travis

EqualLogic

Was this post helpful?