vMotion not working after vCenter 4.1 Upgrade.

[MikeS1983]

Hi All,

I have an issue with vMotion and HA on one of my 2 host clusters since upgrading vCenter to 4.1.

The virtual networking for the 2 hosts is as follows.

1 pnic connected to vswitch0 (Vlan6)

SC, VM, FT and VM port group.

1 pnic connected to vswitch1 (Vlan186)

2nd SC and VM port group.

Both hosts are still on ESX 4.0.

I know this is not an ideal setup and I am looking to reconfigure this completley.

Both pnics are connected at 1Gbps and both HA and vMotion worked before the 4.1 upgrade,

Thanks

Mike.

[idle-jam]

what's the error message you're getting? also why not reconfigure/reset vmotion afterall it's just a few steps ..

[MikeS1983]

Hi,

Thanks for your reply.

I have already tried recreating the vMotion ports which was unsuccessful.

Message on vmname: VMotion
[c0a80625:1305632314222583] failed to receive
72/72 bytes from remote host <hostip>:
Timeout VMotion [c0a80625:1305632314222583]
failed to send 'pre-copy start' message to remote
host <hostip> Migration to host
<<unknown>> failed with error Timeout
(0xbad0021).
info

No other configuration changes have being made other that the vCenter upgrade.

Mike.

[dquintana]

Hello

MikeS,

One of the best way to troubleshoot this is using vmkping command if th vmkernel port are working good.

See this article http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100372...

Regards

Diego Quintana

[AndreTheGiant]

See also on KB:

http://kb.vmware.com/kb/1003734

[MikeS1983]

SOLVED!!!!!!!

I moved the Service Console and vMotion port groups onto a dedicated VLAN (As it should be) and it worked......

Thanks for the replies.

Mike.