The exhibit shows how two NICs on a physical server connect to two HP 5820 switches. The
server supports eight virtual machines (VMs) with VMware version 5.1. The VMware standard
virtual switch is bound to NIC and NIC2. This switch implements source MAC load balancing for
the NIC team.
What is the proper configuration for ports 1/0/1 and 2/0/1?

A.
Place the ports in a bridge aggregation group that does not use LACP
B.
Place the ports in a bridge aggregation group that uses LACP
C.
Enable LACP on the individual ports
D.
Do not place the ports in a bridge aggregation group
Explanation:
C is not correct.
The question states that the standard vSwitch is implementing source MAC load balancing for
the NIC team. LACP on a port that is not a member in a channel group doesnt make sense – there is no aggregation Lacp could control if the port is not in any group.
Because VMware KB1004088 states that, “If the physical switch is using link aggregation, >>Route based on IP hash< any answer with port group is incorrect. –> A and B are incorrect.
Besides that, according to vmware KB2034277: in vSphere 5.1 LACP is only supported using Source IP based Load sharing. Further more KB1004088 states that LACP support has been introduced with version 5.1 distributed switches –> question says “standard vSwitch” –> B is also not correct
We Let vSwitch decide where to send out the frame and simply do not place the ports in a bridge agg. LoadSharing will be done on the vSwitch and the pys. Switch will remember where it learned the mac address by looking up its mac address table.
–>> D is correct
0
0
Only D is correct
0
0
for comware (5800), put ports in bridge aggregation static mode (no lacp)
RPTA: A
0
0
Source port y source MAC – no link aggregation
Source IP – link aggregation static (no LACP).
VMware standard virtual switch.
D correct
0
0