VMware Cloud Foundation - Design Decision - Do not use EtherChannel (LAG, LACP, or vPC) configuration for ESXi host uplinks
Article ID: 318064
Updated On:
Products
VMware
VMware Cloud Foundation
Issue/Introduction
Design Decision: Do not use EtherChannel (LAG, LACP, or vPC) configuration for ESXi host uplinks
Resolution
Design Justification:
- Simplifies configuration of top of rack switches.
- Teaming options available with vSphere Distributed Switch and N-VDS provide load balancing and failover.
- EtherChannel implementations might have vendor-specific limitations.
Design Implication: None
This design decision is supported in the following Domains.
• Management Domain
• VI Workload Domain
This design decision is supported on VCF version 4.1 and higher.
Note: To search for additional information on this design decision please search on the design decision text in https://docs.vmware.com/. For example https://docs.vmware.com/en/search/#/%22Enable%20Network%20I%2FO%20Control%20on%20all%20distributed%20switches.%22
- Simplifies configuration of top of rack switches.
- Teaming options available with vSphere Distributed Switch and N-VDS provide load balancing and failover.
- EtherChannel implementations might have vendor-specific limitations.
Design Implication: None
This design decision is supported in the following Domains.
• Management Domain
• VI Workload Domain
This design decision is supported on VCF version 4.1 and higher.
Note: To search for additional information on this design decision please search on the design decision text in https://docs.vmware.com/. For example https://docs.vmware.com/en/search/#/%22Enable%20Network%20I%2FO%20Control%20on%20all%20distributed%20switches.%22
Additional Information
Please reference the VMware Cloud Foundation version you are running and if this design decision is applicable to you.
VMware Validated Design (VVD) Bill of Materials
Feedback
Yes
No
Powered by
