getting vSphere HA errors please help

[nflnetwork29]

We have 4 ESXi hosts

I have ensured that they can all ping each other successfully using vSwitch0 (which purpose is the MGMT + vMotion)

I am seeing the following errors:

"The vSphere HA agent on this host cannot reach some of the management network addresses of other hosts, and HA may not be able to restart VMs if a host failure occurs: server.domain.local; 192.168.x.x"

"The vSphere HA availability state of this host has changed to Slave"

"vSphere HA detected that this host is in a different network partition than the master to which vCenter Server is connected"

Any help is appreciated.

[a_p_]

Please provide some configuration details, like the vCenter/Host versions as well as the IP-Addresses and subnet masks of the ESXi hosts.

André

[nflnetwork29]

vCenter  version 5.1.0, 1064983

Hosts

esx01version  5.1.0, 1065491   IP: 192.168.0.144 subnet mask: 255.255.255.0

esx02 version 5.1.0,  1065491   IP: 192.168.0.145 subnet mask: 255.255.255.0

esx03 version 5.1.0,  1065491   IP: 192.168.0.146 subnet mask: 255.255.255.0

esx04 version 5.1.0,  1065491   IP: 192.168.0.147 subnet mask: 255.255.255.0       

[a_p_]

This looks ok. Does the message show up on only one of the hosts?

How did you configure the Management Network's port group, the virtual switch and the uplinks?

André

[nflnetwork29]

each vSwitch has 2 VMKernal ports and two uplinks.

1 x vMotion

1 x MGMT

the errors show up on the other hosts as well.

[sajaldebnath]

Hello nflnetwork29,

can you try to do a vmkping from each host? Also the IP's you have shown are the management IP's or vMotion IP's? Please check the vMotion IP's. Please double check the vMotion IP's and and subnet mask in each. But to be sure just check vmkping from each host console to all the other hosts using the vMotion IP's to be sure that vMotion IP's are correctly set and everything works fine.

[nflnetwork29]

yes i can vmkping every other from all hosts.

they IPs listed are management IP's.

[sajaldebnath]

I mean vmkping using vMotion IPs?

Did you already double check the network settings? Are the hosts running in the same subnet?

You can also try to right click the host in the inventory and run "Reconfigure for HA" to see whether this solves the issue.

Check for IPv6 as well.

Though it seems that all the vMotion IPs are in same subnet still want to check is there any firewall between them? Can you check for port 8182.

If these does not work then definitely check for the configurations once again (after this needs to check logs)

[GMCON]

Are all the vmotion vmkernel ports on the same subnet as management or different?  You can do vmkping -I to specify the vmkernel port you want it to go over and do it by ip and not host name over the vmotion network.  Another cause of this that I see a lot is that one host is configured with an extra vmkernel interface on a subnet the other hosts do not have and you will see this message.  Check all your hosts so they only have the 2 vmkernel interfaces.