2V0-621 · Question #50
What are two limitations of Link Aggregation Control Protocol (LACP) on a vSphere Distributed Switch? (Choose two.)
The correct answer is B. Software iSCSI multipathing is not compatible. D. It does not support configuration through Host Profiles. LACP on a vSphere Distributed Switch has specific compatibility and management constraints that limit its use with certain storage and automation features.
Question
What are two limitations of Link Aggregation Control Protocol (LACP) on a vSphere Distributed Switch? (Choose two.)
Options
- AIP Hash load balancing is not a supported Teaming Policy.
- BSoftware iSCSI multipathing is not compatible.
- CLink Status Network failover detection must be disabled.
- DIt does not support configuration through Host Profiles.
How the community answered
(31 responses)- A6% (2)
- B81% (25)
- C13% (4)
Why each option
LACP on a vSphere Distributed Switch has specific compatibility and management constraints that limit its use with certain storage and automation features.
Route based on IP hash is actually the required load balancing policy for use with LACP on a VDS, making this statement false as a limitation.
Software iSCSI multipathing requires VMkernel port binding to individual physical NICs, which is architecturally incompatible with LACP's Link Aggregation Group (LAG) model that presents multiple links as a single logical uplink.
Link Status network failover detection is compatible with LACP and does not need to be disabled; LACP handles link-state negotiation independently through protocol data units.
LACP configuration on a VDS is not exportable or deployable via Host Profiles, which is a documented limitation that prevents automated, profile-driven LACP setup across multiple hosts.
Concept tested: LACP limitations on vSphere Distributed Switch
Source: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.networking.doc/GUID-0D1EF5B4-7581-480B-B99D-5714B42CD7A9.html
Topics
Community Discussion
No community discussion yet for this question.