Which two configuration changes should the administrator make?

— Exhibit —

— Exhibit —

The administrator needs to modify the problematic configuration shown in the exhibit to meet the
following requirements:
1. Uplink ports must connect to a 2-port Etherchannel connection. 2. Traffic must pass, even in
the event of a port failure.
Which two configuration changes should the administrator make? (Choose two.)

— Exhibit —

— Exhibit —

The administrator needs to modify the problematic configuration shown in the exhibit to meet the
following requirements:
1. Uplink ports must connect to a 2-port Etherchannel connection. 2. Traffic must pass, even in
the event of a port failure.
Which two configuration changes should the administrator make? (Choose two.)

A.
Change the Load balancing algorithm to Route based on ip hash

B.
Change the Load balancing algorithm to Route based on physical NIC load

C.
Move Uplink 1 into Active Uplinks and Uplink 2 into Standby Uplinks

D.
Move both uplinks into the Active Uplinks

Explanation:



Leave a Reply 6

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


JanK

JanK

Route Based on IP Hash –
Network adapter redundancy. If a NIC fails and the link-state goes down, the remaining NICs in the team continue passing traffic

Bart

Bart

NOTE: Load balancing on Etherchannel ONLY works with IP Hash(nothing else)!

Edwin.Castellanos

Edwin.Castellanos

A & D are required. As mentioned about etherchannel requires Route Based on IP Hash and per the image both uplinks require to be “moved” to the active status.

razvan

razvan

Configuration of EtherChannel
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004048

Note: The LACP support in vSphere Distributed Switch 5.1 supports only IP hash load balancing. In vSphere Distributed Switch 5.5, all the load balancing algorithms of LACP are supported:

Do not use beacon probing with IP HASH load balancing.
Do not configure standby or unused uplinks with IP HASH load balancing.
vSphere Distributed Switch 5.1 only supports one EtherChannel per vNetwork Distributed Switch (vDS). However, vSphere Distributed Switch 5.5 supports multiple LAGs.