Which load-balancing policy will guarantee this requirement is met?

An administrator is creating a vNetwork Standard Switch with virtual machine and VMkernel networking. The administrator has two uplinks attached to the switch but wants to separate the virtual machine and VMKernel traffic to the two uplinks.

Which load-balancing policy will guarantee this requirement is met, even if additional management or virtual machine traffic is added to the switch

An administrator is creating a vNetwork Standard Switch with virtual machine and VMkernel networking. The administrator has two uplinks attached to the switch but wants to separate the virtual machine and VMKernel traffic to the two uplinks.

Which load-balancing policy will guarantee this requirement is met, even if additional management or virtual machine traffic is added to the switch?

A.
Route based on IP hash

B.
Router based on source MAC hash

C.
Route based on the originating port ID

D.
Use explicit failover

Explanation:

Page 44 from vsphere-esxi-vcenter-server-50-networking-guide.pdf

 



Leave a Reply 3

Your email address will not be published. Required fields are marked *


anon

anon

The Explination clearly shows that the selected correct answer is incorrect. Originating port ID should be the correct answer

Jackie

Jackie

As the question mentioned the admin wants to separate the virtual machine and VMKernel traffic to the two uplinks the auto load balancing protocol won’t be able to do that. The admin should set load balancing at the port group level to explicitly define which NIC to be used for the vmkernel port group and set the other NIC to be fail over one, same for the virtual machine port group.

Jon

Jon

Jackie is correct. The originating port ID is going to be different for every VM that connects to the vSwitch. If you were to go with that routing method, one VM could use the first uplink for it’s traffic and another VM might use the second uplink, there’s no way to control it using that method.