TeamPolicyUpDelay is not working as expected when beacon probing is enabled on a DVPG in DVS.

Products

• VMware NSX
• VMware vSphere ESXi

Issue/Introduction

• When beacon probing is enabled on a DVPG in DVS, TeamPolicyUpDelay setting is not honored for other DVPGs/Segments that do not use Beacon Probing. As a result, uplinks that transition from DOWN to UP state is immediately considered to be UP by ESX. \
• Uplink transitions from DOWN state to UP state immediately for a DVPG even though it is configured to come up at a higher TeamPolicyUpDelay time. 
  
  

Environment

ESX 7.0, 8.0
NSX 3.2.x, 4.1.x, 4.2.0. 4.2.1
VCF 9.0

Cause

This issue has been identified as a known problem, and VMware by Broadcom is aware of it.

Resolution

This issue is fixed in NSX 4.2.2 and future VCF release. 

Workaround :

Disable beacon probing on all DVPGs in the host switch and use Link status only.
TeamPolicyUpDelay value should work as expected after applying the changes.

Additional Information

Impact : TeamPolicyUpDelay defines the time, in milliseconds, that the ESX host waits after detecting that a pNIC has transitioned from a down state to an up state before the host starts using the pNIC again for network traffic. This delay helps to ensure that the pNIC has fully recovered and stabilized before it is put back into use.
Usually TeamPolicyUpDelay is modified when physical switch upgrades are happening. By bringing an uplink to UP state immediately, it can impact the traffic as the connections may not reset immediately via the new uplink.