Lost pings and delays in the physical switch during NIC teaming failback
search cancel

Lost pings and delays in the physical switch during NIC teaming failback


Article ID: 310812


Updated On:


VMware vSphere ESXi


This article provides information about minimizing the delay for a physical switch to detect NIC teaming failback.

  • Pings are lost during NIC teaming failback
  • There is a delay in the physical switch detecting NIC teaming failback

accessing-network cannot-ping-host nic-team-failback nic-team-failover no-ping ping-esx ping-failure ping-service-console ping-vm


VMware ESX Server 3.5.x
VMware ESXi 6.7.x
VMware ESXi 5.0.x
VMware ESXi 5.1.x
VMware ESXi 5.5.x
VMware ESXi 3.5.x Embedded
VMware ESXi 4.0.x Embedded
VMware ESXi 4.0.x Installable
VMware ESXi 4.1.x Embedded
VMware ESXi 6.0.x
VMware ESX Server 3.0.x
VMware vSphere ESXi 7.0.x
VMware ESX 4.0.x
VMware ESX 4.1.x
VMware ESXi 6.5.x
VMware ESXi 3.5.x Installable
VMware ESXi 4.1.x Installable


Packet loss is expected during failback.
If the primary physical adapter is experiencing intermittent failures, the failback setting can lead to frequent changes in the adapter in use. The physical switch sees frequent changes in MAC address, and the physical switch port may not accept traffic immediately when a particular adapter comes online.
To minimize delays or lost pings, disable the following on the physical switch:

Alternatively, set Failback to No. This option determines how a physical adapter is returned to active duty after recovering from a failure. A failover event triggers the network traffic to move from one NIC to another. When a link up state is detected on the originating NIC, traffic automatically reverts to the original network adapter when Failback is set to Yes. When Failback is set to No, a manual failback is required.

Additional Information

For related information, see VMware Virtual Networking Concepts.