VMware Cloud Community
Anunn
Contributor
Contributor

vMotion problem when using Broadcom HBA iSCSI initiator to connect to our SAN LUN

Hi, we have a vMotion problem when using Broadcom HBA iSCSI initiator to connect to our SAN LUN, when we tried to vMotion a running vm to another host we will get below error

The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network.  Check the vMotion network settings and physical network configuration.
vMotion migration [-1407254169:1317986304316814] failed to create a connection with remote host <172.31.1.101>: The ESX hosts failed to connect over the VMotion network
Migration [-1407254169:1317986304316814] failed to connect to remote host <172.31.1.101> from host <172.31.1.103>: Timeout
The vMotion failed because the destination host did not receive data from the source host on the vMotion network.  Please check your vMotion network settings and physical network configuration and ensure they are correct.
However when we connect to our SAN LUN with the software iSCSI initiator vMotion works just fine, we're having difficulties troubleshooting this issue.
We assign 2 Broadcom HBA iSCSI initiator on each host and we checkbox the vmotion on each HBA, it's also MPIO on 2 iSCSI network switch
http://www.d1.co.th
Tags (1)
0 Kudos
3 Replies
weinstein5
Immortal
Immortal

Welcome to the Community - Are you using the same VMkernel port for your VMotion and iSCSI networks? If you are that could be your issue - create a seperate VMkernel ports for iSCSI and vMotion Nedtworks

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
0 Kudos
Anunn
Contributor
Contributor

Hi weinstein5, thank you for the reply, yes both vmkernal (see attached) currently share iSCSI and vMotion traffic

VMkernal-1 ip:172.31.1.101 bind to vmnic3 which connect to iSCSI target and vMotion enable

VMkernal-2 ip:172.31.1.102 bind to vmnic2 which connect to iSCSI target and vMotion enable

Do I need to create another vmkernal port just for vmotion?

http://www.d1.co.th
0 Kudos
Anunn
Contributor
Contributor

I've managed to solve the issue by simply stacking the 2 iSCSI switches, suddenly the vMotion works like a charm,

http://www.d1.co.th
0 Kudos