hi after upgrading my hosts from esxi4.1 to esxi 5.0 i build a new cluster and added my hosts. added all the vmx files form alll my vm's to the inventory and was up and running....until i tested the vMotion function. i found allready some articles about the issues but could not figure out what is wrong. my vMotion stopt at 9%, it says the host can not reach the other managment network. this is really strange because managment is enabled as well as Vmotion. see topic .. http://communities.vmware.com/message/1826805 i have the same problem.

at the bottom there are talking about "a non-existing IP range for use with the vmotion kernel switch". this is not possible to create with an empty gateway.. and even when i put in a gateway it doesn t fix anything..

after i reinstalled my hosts from scratch (NOT UPGRADE) it works.. but strange... no explanation at this moment. there is something in the vMotion network, which hold the enviroment from totally fail over, but it stops at 9%, it could have to do something with the network adapter default ESXi5 driver. Inside there is a RT8111E onboard and not a RT8168 adapters which ESXi5 default installs. it works until you use MTU 9000, then all the problems starts. and after a host reboot card is not connected to the switch anymore.. is there my problem...???

Could be either your NIC, or your switch, or the port on your switch, or your network cable, or a combination of one or more of those.

... or something else entirely.

HI AHHH,got reaction, no it has nothing to do with the hardware the same config had worked for a long time with 4.1 never any problems.after upgrading the hosts to esxi5 problems... after a clean install all problems gone ...

and i found problems in the rt 8168 driver for the onboard eth.. mtu 9000 ->> eth port disconnected after host reboot.... mtu 1500 no problems.