vSphere Distributed Switch teaming matched status alarm triggered in vCenter Server
book
Article ID: 325396
calendar_today
Updated On:
Products
VMware vCenter ServerVMware vSphere ESXi
Issue/Introduction
Symptoms: When ESXi hosts are connected to a vSphere Distributed Switch and the Network Health Check is enabled, you experience these symptoms:
The Events view in the vCenter Server Tasks & Events tab reports constant alarms similar to:
Alarm 'vSphere Distributed Switch teaming matched status' on x.x.x.x changed from Green to Red
In the /var/log/hostd.log file of the ESXi host, you see this entries similar to:
Teaming configuration in the vSphere Distributed Switch on host hostname does not match the physical switch configuration in ha-datacenter. Detail: No loadbalance_ip teaming policy matches.
The vSphere Distributed Switch NIC teaming is using the IP Hash load balance policy. For more information, see NIC teaming in ESXi and ESX (1004088).
SR-IOV is not in use on any of the ESXi Uplinks configured for the DVS, SR-IOV is not compatible with the DVS Teaming health check due to beacon filtering that occurs with SR-IOV ports
Additional Information
Depending on the options that you select, vSphere Distributed Switch Health Check can generate a significant number of MAC addresses for testing teaming policy, MTU size, VLAN configuration, resulting in extra network traffic. For more information, see Network health check feature limitations in vSphere (2034795).
After you disable the vSphere Distributed Switch Health Check, the generated MAC addresses age out of your physical network environment according to your network policy. For more information, see the Enable or Disable vSphere Distributed Switch Health Check section of the vSphere Networking Guide,