vSwitch (Standard Switches) teaming Load balancing change to port id after ESXi 7.0.3l update
searchcancel
vSwitch (Standard Switches) teaming Load balancing change to port id after ESXi 7.0.3l update
book
Article ID: 318490
calendar_today
Updated On: 12-13-2024
Products
VMware vSphere ESXi 7.0
Issue/Introduction
Symptoms:
After upgrading to ESXi 7.0U3l (build 21424296), under certain conditions, the Load balancing configuration on vSwitch (Standard Switches) port groups gets overridden to route based on originating virtual port
Environment
VMware vSphere ESXi 7.0.3
Cause
If all the below said conditions are met, upon upgrade to ESXi 7.0U3l, the teaming policy at the Port Group level is overridden and set to route based on originating virtual port.
Under Teaming and Failover, the vSwitch has non-default Load balancing value set (options other than route based on originating virtual port)
The Port Group under the vSwitch inherits the Load balancing option from the vSwitch
The override checkbox under Failover order is checked at least once for the port group
Resolution
This behavior is modified when upgrading from ESXi 7.0 Update 3L to ESXi 7.0 Update 3M release.
Use the workaround from KB 318509 if planning to upgrade past ESXi 7.0 Update 3M.
The original issue will be fixed in a future release.
Workaround:
As a workaround, set the Load balancing at the port group level to the original value via UI or CLI
To regain control of the host in case the management port group is impacted, set the link down on all but one of the vmnics of the port-channel facing the ESXi host vSwitch
Due to a mismatch of the Load balancing configuration at the Port Group level, the host or the VMs running on the vSwitch might lose total or partial connectivity.
The impact is only seen on vSphere Standard Switches only