Thanks for replying
I did see that article but it mentioned about 5.1 and not 5.5 so I was hoping if there is any resolution in 5.5
which teaming policy are you using on your vSwitch or it's port groups whereever you are facing this issue? if it not ip hash then it might be originating virtual port ID or mac hash or LBT. then check your physical network configuration that NIC teaming is configured or not because this should not be configured and check this KB
1 person found this helpful
Thanks for asking your question to my blog sorry about the delayed response. Health check is a little odd sometimes. VMware recommends using to identify issue and not constantly. Health check is not supported on any type of virtual nics on the platform see:
This includes HP FlexFab or UCS. I would assume that the virtual nic in workstation may also be throwing this for a loop. I would consider the following options:
- Check your switch teaming policy
- Check each port group teaming policy
--Ensure none are set for IP hash (For home lab source based mac is your best bet or load based teaming)
-If everything is not IP hash then I would turn off the feature and back on you might find new results
-In the end the fact that you are using workstation may be the cause of the issue because the ESXi hosts see a virtual nic.
Notes on screenshots:
-First shot is normal this is the message while it's still doing the tests
-Second and Third are either related to a real mismatch or the issue in the KB above
That's my best guess... the truth is I have seen all kinds of crazy on anything with virtual nics. I saw a situation where health check was running a CAM table out of entries (500,000 entries) with health check on UCS... it is really bad on UCS don't use it.
Hope it helps.
Thanks for explaining in detail -- it helps