ESX3.5U4. Upgraded the VC from 2.5 to 4.0. We are getting heartbeat error now on one of the host. The VMs are all working fine too.
Error detected on host : Agent can't send heartbeats.msg size: 912, sendto() returned: Operation not
permitted. Any clues ?
yup we are getting this too:-
Agent can't send heartbeats.msg size: 66
the esx hosts and vcenter server are on the same lan, not nat or firewall involved. only happening since we upgraded to 3.5 U4 to 4.0 with lastest patches.
anyone have an idea whats going on?
HA and DRS enabled. all vms running fine, all hosts happy too. Dell 2950s x 5. EMC Clarion backend, RAID10 luns x 5 x 1Tb on 4Gb FC
You say you have upgraded your esx hosts and vcenter, but you don't say you upgraded virtual tools from vm's.
Sometimes you can find issues you can solve upgrading vmtools.
You can try.
Ran into the "agent can't send heartbeats.msg size 66" error today. All of the hosts in vCenter showed as disconnected. I was able to see the ESX hosts initiate the heartbeats to the vCenter server but vCenter couldn't see them. Checked the IT firewall and the proper rules were inplace. Turns out the Windows firewall was turned on and was blocking UDP 902 outbound.
Once the rule was added to the Windows firewall, all of the hosts were able to reconnect.
we have this strange feature too...
we have 3 clusters in our environment, and only one cluster with 2 esx show this message:
Agent can't send heartbeats.msg size: 66, sendto() returned: Operation not permitted
firewall on vc and between this 2 esx seem ok (still not blocking port 902...)
our esx servers:
esx4 with latest patches...
has anyone found an solution?