What are two network load-balancing policies for a vSphere Distributed Switch? (Choose two

What are two network load-balancing policies for a vSphere Distributed Switch? (Choose two.)

A.
Route based on source MAC hash

B.
Route using physical NIC load

C.
Route based on the destination virtual port ID

D.
Route based on port ID hash

5 Comments on “What are two network load-balancing policies for a vSphere Distributed Switch? (Choose two

  1. Raj says:


    Route based on the originating virtual port — Choose an uplink based on the virtual port where the traffic entered the distributed switch.

    Route based on ip hash — Choose 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 — Choose an uplink based on a hash of the source Ethernet.

    Route based on physical NIC load — Choose an uplink based on the current loads of physical NICs.

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

  2. Baher says:

    A is one of the correct answers, Route Based on Source MAC Hash

    B Route based on physical NIC load is a feature of vDS only!

    C doesn’t look like a correct answer as it is talking about “destination” virtual port ID

    D “port ID hash” .. doesn’t sound the same as “originating port ID”

    So, A & B

  3. Scott says:

    I agree with Baher. just adding some more details on same info.

    Of the answers listed here is why i believe they are as they are..

    A.
    Route based on source MAC hash (valid LB tech for std and dist switches)

    B.
    Route using physical NIC load (valid for distr. switches)

    C.
    Route based on the destination virtual port ID (wrong name, originating port ID)

    D.
    Route based on port ID hash (wrong name, its IP Hash not port, or ID hash)

    so, that leaves A and B..


Leave a Reply

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