6.5.1

Table 8‑1. Steps to Complete the Conversion to the Enhanced LACP Manually
Conversion Stage Target Configuration State Solution
1. Create a new LAG. A newly created LAG must be
present on the distributed switch.
Check the LACP configuration of the distributed switch and
create a new LAG if there is none.
2. Create a an intermediate
LACP teaming and failover
configuration on the
distributed port groups.
The newly created LAG must be
standby that lets you migrate
physical NICs to the LAG without
losing connectivity.
Check the teaming and failover configuration of the distributed
port group. Set the new LAG as standby if it is not.
If you do not want to use a LAG to handle the traffic for all
distributed port groups, revert the teaming and failover
configuration to a state where standalone uplinks are active
and the LAG is unused .
3. Reassign physical NICs
from standalone uplinks to
LAG ports.
All physical NICs from the LAG
ports must be reassigned from
standalone uplinks to the LAG
ports
Check whether physical NICs are assigned to the LAG ports.
Assign a physical NIC to every LAG port.
Note The LAG must remain standby in the teaming and
failover order of the distributed port groups while you reassign
physical NICs to the LAG ports.
4. Create the final LACP
teaming and failover
configuration on the
distributed port groups.
The final LACP teaming and
failover configuration is the
following.
n
Active: only the new LAG
n
Standby: empty
n
Unused: all standalone
uplinks
Check the teaming and failover configuration of the distributed
port group. Create a valid LACP teaming and failover
configuration for all distributed port groups for which you want
to apply LACP.
For example, suppose you verify that a new LAG has been created on the distributed switch and that an
intermediate teaming and failover configuration has been created for the distributed port groups. You
continue with checking whether there are physical NICs assigned to the LAG ports. You find out that not
all hosts have physical NICs assigned to the LAG ports, and you assign the NICs manually. You complete
the conversion by creating the final LACP teaming and failover configuration for the distributed port
groups.
Unable to Remove a Host from a vSphere Distributed
Switch
Under certain conditions, you might be unable to remove a host from the vSphere distributed switch.
Problem
n
Attempts to remove a host from a vSphere distributed switch fail, and you receive a notification that
resources are still in use. The notification that you receive might look like the following:
The resource '16' is in use.
vDS DSwitch port 16 is still on host 10.23.112.2 connected to MyVM nic=4000 type=vmVnic
vSphere Troubleshooting
VMware, Inc. 87