Which load-balancing policy will guarantee this requirement is met, even if additional management or virtual m

An administrator is creating a vSphere Standard Switch with virtual machine and VMkernel networking. The administrator has two uplinks attached to the switch and wants to make sure multiple sessions for a virtual machine can utilize both uplinks.

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

A.
Route based on IP hash

B.
Route based on source MAC hash

C.
Route based on the originating port ID

D.
Use explicit failover.

2 Comments on “Which load-balancing policy will guarantee this requirement is met, even if additional management or virtual m

  1. Raj says:

    IP Hashing uses IP address of the virtual machine. So the load balancing is done at VM level

    Within ESXi 5.0, there are 4 methods of Load Balancing. As stated in the help

    Route based on the originating port ID Select an uplink based on the virtual port where the traffic entered the standard switch.

    Route based on ip hash Select an uplink based on a hash of the source and destination IP addresses of each packet. For non-IP packets, whatever is at those offsets is used to compute the hash.

    Route based on source MAC hash Select an uplink based on a hash of the source Ethernet.

    Use explicit failover order Always use the highest order uplink from the list of Active adapters that passes failover detection criteria.

    The test below is to test and study what “Route based on IP hash” does and how it perform traffic load balancing.


Leave a Reply

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