Had a similar issue updating to 5.1U1. I'm running a 6 cluster c7000 HP blade chassis. All hosts running 5.0. I used update manager to update one server to 5.1U1. The installation was completed successfully and was able to log into ESX reconnect to vCenter the whole 9. All my network settings transferred over no issues except vMotion failing at 14%. I logged a support ticket with VMware and they told me my vmotion NICs were not able to see the vlan associated to those vmotion NICS, however, he put 1 NIC into standy and vmotion worked...or so I thought. I updated my second host to 5.1U1 and same vmotion issue after upgrading, however, this time placing one nic into standby did not resolve the vmotion error. It was at this point the first host I put on 5.1 u1 starting acting really strange. Console was showing fork errors, couldn't change any settings on vCenter, recconnect, restarting management services didn't help only a hard boot corrected those issues but vmotion still fails at 14%. The strange part is that even tho vMotion failed and anything else I did failed when I rebooted the host the guest VMs did transfer over without a reboot of the guest. I placed another call into VMWare today but i'm really feeling a rollback may be in order to maintain some stability of my systems.
↧