vMotion not working only for DSS

We have 2 ESXi hosts on 192.168.100.x subnet with 4 NICs of the same configuration:

- 2 teamed NICs (active-active) are on 192.168.100.x subnet for VM Network and Management Network
- 2 teamed NICs (active-unused) are on 192.168.102.x for iSCSI Network

http://communities.vmware.com/servle...15-72504/1.gif

We have 2 iSCSI storage where QNAP is on 192.168.100.x subnet and Open-E DSS is on 192.168.102.x subnet:

QNAP has 2 NICs:
- 192.168.100.163
- 192.168.100.241

Open-E DSS has 4 NICs:
- 192.168.102.10
- 192.168.102.11
- 192.168.102.12
- 192.168.102.13

http://communities.vmware.com/servle...15-72503/2.gif

We also have 2 isolated switches where one is for 192.168.100.x subnet and the other is for 192.168.102.x subnet.

There is no problem cloning a VM from Open-E DSS to QNAP. However, cloning any VM from QNAP to Open-E DSS will fail.

There is also no problem doing a vMotion between 2 ESXi host for any VM running from QNAP. However, vMotion for any VM running from Open-E DSS will fail. I have try configure vMotion on both Management Network and iSCSI Network. The result is the same.

Since iSCSI subnet is isolated from the main subnet, I suspect that QNAP iSCSI storage is running from the Management Network instead of iSCSI network. Is the problem likely cause by misconfiguration of my iSCSI Network or Open-E DSS storage? What else can I do to narrow down the problem?

This is most likely a routing issue in the subnet. Try and use static routing tables.

I have setup static route but it didn't make any different.

However, the problem was solved after I reconfigure Open-E DSS MPIO to Round Robin and set iops to 1 using this command as instructed by the your guide [Open-E_DSS_V6_MPIO_with_ESX4i_4.1.pdf]:

esxcli nmp roundrobin setconfig --type "iops" --iops 1 --device <device UID>

:cool: nice job!

I just realize that DSS is no longer able to access internet for updates after setting up static route.

When I attempt to add gateway as instructed by multiple_ip.pdf, DSS said it's invalid. :confused:

Are you doing any VLANs, try to start from the beginning as it does work.

I am also having same issue!