Solution
Workaround
Note: To reduce the chance of network connection loss please change the vSwitch load balancing to Route based on IP hash using this method
- Shutdown all ports in the team from the physical switch leaving a single port as active.
- Change the load balancing to Route based on ip hash on the vSwitch and Management Portgroup.
- Configure the port channel on the physical switch.
- Enable the ports on the physical switch.
Notes: Using this method will prevent a connection loss when changing to a port channel. Also make sure that under the portgroup properties for vmk# used for management network you check mark the box "Enabled".
If you have already changed the vSwitch load balancing to Route based on IP hash, then set the same for Management Network portgroup.
- Login to Virtual Center/vCenter Server using VI/ vSphere Client.
- Select the ESXi Server host.
- Click the Configuration tab.
- Click the Networking link.
- Click Properties link for the management network portgroup.
- Highlight the virtual switch in the Ports tab and click Edit.
- Click the NIC Teaming tab.
- Choose Route based on IP hash from the Load Balancing dropdown menu.
- Verify that there are two or more network adapters listed under Active Adapters.
Use these commands if the host does not stay connected to vCenter Server after the vSwitch load balancing policy change:
# vim-cmd hostsvc/net/vswitch_setpolicy --nicteaming-policy=loadbalance_ip vSwitch0
# vim-cmd hostsvc/net/portgroup_set --nicteaming-policy=loadbalance_ip vSwitch0 "Management Network"Based on VMware KB 1022751
