Strange Issue :-)
I spent lot of time to find this.
Symptom of this issue is HA will not start VMs once Host fail.
http://kb.vmware.com/kb/1013013
I spent lot of time to find this.
Symptom of this issue is HA will not start VMs once Host fail.
http://kb.vmware.com/kb/1013013
Filed under failover, HA, ip_address, vSphere
1. To the physical switch, attach only the network cable used for the service console.
2. List all of the network adapters from the ESX Server service console and locate the name of the vmnic# that has a link status of up.
esxcfg-nics –l
3. If vmnic0 has a link status of up, stop now. Otherwise, remove vmnic0 from vSwitch0.
esxcfg-vswitch -U vmnic0 vSwitch0
4. Associate the vmnic# that has a link status of up from step 2.
esxcfg-vswitch -L vmnic# vSwitch0
Use the following commands to determine where the ESX Server service console portgroup is (if you are doing a repair after changing physical NICs or similar activity, for example):
* esxcfg-nics -l
Determines which NICs are link up esxcfg-vswif -l to ensure Service Console is the port group, and the settings are correct.
* esxcfg-vswitch -l
Shows which vSwitch the service console port group is in.
* esxcfg-vswitch -L
Links the vmnic and service console together.
1. To restart Management services
service mgmt-vmware restart
2. Restart VC agent on ESX host. vmware-vpxa is installed only when connected to VC
service vmware-vpxa resrtart
3. Restart Network on ESX host
service network restart
Filed under hostd, mgmt-vmware, vc_agent, vic_agent, vmware-vpxa