While using the new vSphere 5.1 Web Client, I have got a vCenter 5.1 with Distributed Network Switches. I have enabled "VLAN and MTU health check" and "Teaming and failover health check". However, when looking at the "Status" columns, nearly all show a status of "Unknown" for all the Hosts. All my Hosts are vSphere 5.1.
I'd appreciate any advice.
Has anyone got any ideas please ?
I haven't seem this myself yet, I suggest calling support and filing a request.
ive had the same issue... are you sure your uplinks are all synced across your hosts? a mismatch can give an error like that as well. Have you been moving hosts around in the cluster? ive seen the healtheck do some random things before and it usually comes right after a while
All Hosts NICs are matching, I am not sure what you mean by moving Hosts around in the cluster. If you mean by switch ports, then no. It is a strange one and I don't know if anyone else has experienced this.
You don't perhaps have any alerts pending for the dvswitch? I am busy with a brand new implementation and I fixed this issue yesterday by resetting all alerts to green. This might be a stupid thing to check but its something I also noticed these alerts only showed in the web client...
Thanks for the suggestion but unfortunately the problem still persists.
Did you solve this? I just noticed I have the same problem on all hosts except one which is in manteniance mode. (it used to work)
This is apparently a bug when you have the health monitor enabled...
Did they tell you when a fix would be avaible ? And when can this bug occure?
As far as I know there is no fix as of yet. Ill try and find the link to the blog post where future updates should be posted on the issue
I've had the same problem and after about a few weeks with support I was told it's a known bug. I've been told the fix will not be until mid 2014. One thing I did notice is a vDS with Uplink ports not connected to Physical NICs has someting to do with the problem. I've had vDS with 4 Uplink ports but only one pysical nic connected one of teh Uplinks the others are empty. They are left blank as preperation for a migration over from a standard switch. None of the vDS like this have shown information for vLAN/MTU and or course don't work for fail over health check since there is only a single uplink nic. I've created vDSs with a single Uplink and NIC just to test vLAN/MTU for clusters still on standard switches. Even thought this is unsupported and documentation tells you is will not work, I've found it does but would only use it for testing vLAN/MTU. I've done this a number or times and so far not had a problem as long as I don't leave an Uplink portgroup with out a physical nic during vDS creation.
Yup... epicness...
...and a full YEAR is a long time to wait for an alleged fix. Buzzkill.
Having the same issue as well. I noticed the health was showing properly, but once I rebooted the vCenter services due to the quick stats message, most network health monitors show unknown. This is on a fresh 5.5 install.
WWhen I add a port group to a vds the health monitors work again though a restart will make the monitors unknown
Hi
Welcome to the communities.
I had same problem while testing this but couldnt resolve the use open source to manage this .
Seeing the same thing with one twist
I was monitoring the network with ESXTOP and notice dropped packets on every VM. The %DRPRX column would show all zeros for a few seconds, then every VM would show some packet loss for a few seconds, then all back to zeros. After opening a ticket with VMWare support and spending a lot of time doing packet captures, finally determined it was health check. As soon as I turned of Network Health Check from my vDS switches, the packets loss stopped.
Is anyone else seeing this?
The health check on my 5.5 install shows that VLAN 0 is unavailable on the LINK even though on the vDS I have only specified VLAN 30,150 and same on the switch side. Not sure where it's getting VLAN 0 from... I turn off health check and it stays on with warning...
Hi All,
I had same issue but disable- enable Health Check did the trick for me and now Health Check works fine.
Thanks,
Greg