vSphere Distributed Switch teaming matched status Alarm

[nettech1]

Hi,

We are seeing vSphere Distributed Switch teaming matched status alarm after enabling VLAN and MTU / Teaming and failover Health Check.

VMware Knowledge Base states that the alarm is a result of misconfiguration.

We have 3 Port Groups on this DS and all 3 are set to route based on the originating virtual port.

On the physical side the ports are not either channeled. Each port is a Trunk port with VLANs used by the port groups assigned.

What could be triggering the alarm?

Edit: VMware Knowledge Base​ describes our issue, however the KB was written for vCenter 5.1 and should be fixed in 5.5. We are on 6.7

Thanks

[Scott Vessey]

This may help: non-IP hash mismatch - distributed switch 6.5

[nettech1]

With all VMs migrated to a standard switch and host removed and then added to dvSwitch the error didn't come up.

The error comes back as soon as we add physical adapters to the uplink ports

[daphnissov]

Unfortunately, I've found that health check to be very problematic over the years to the point where it's basically useless and is rarely turned on. If you absolutely must have it for the minuscule value it provides, it might be worth it to open a support case with GSS and have them investigate its wonkiness.

[nettech1]

daphnissov​

Thanks for the response. We had heath check disabled, but enabled it as we were adding a new host to the cluster. Based on your comment and other forum posts where vcenter reports a problem while there may not be an issue with the configuration, we will check with VMWare support.

Thanks again

[mviel]

We are now in 2025 and on vSphere 7u3s and those status Alarm still hits sometime , I have seen in the Past that VMWARE Errors are a good indicator that someone on the SwitchSide should check as there where always issues . 

As that is "THE THREAD" which pops up if searching for "vSphere Distributed Switch MTU supported status" or "Non-IP Hash Mismatch"

 and all the KB Entries and deeplinks dont funktion any longer , thanks to the great change on the Support Side. I would like to update this  Thread so that current Information on the Situation could help others in the Future. 

Does anyone has more Insight what exactly VMWARE is checking there so I could give the Swicht Guys more Feedback ? 
Im will also open a case to share common Information if avaible.