Translate

Total Pageviews

My YouTube Channel

Tuesday, 14 April 2015

Limitations of LACP in VMware vSphere 5.5 (2051307)

Purpose

This article describes the technical and support limitations of the Link Aggregation Control Protocol (LACP) feature in vSphere Distributed Switches in vSphere 5.5.

Resolution

LACP or Link Aggregation Control Protocol support on vSphere Distributed Switches allow multiple vmnics to be bonded using dynamic link aggregation. Limited support for LACP in the vDS was introduced in vSphere 5.1 and a broader feature set is introduced in vSphere 5.5. However, vSphere 5.5 includes these LACP limitations:
  • LACP support is not compatible with software iSCSI multipathing. iSCSI multipathing should not be used with normal static etherchannels or with LACP bonds.
  • LACP configuration settings are not present in Host Profiles.
  • LACP support between two nested ESXi hosts is not possible (virtualized ESXi hosts).
  • LACP cannot be used in conjunction with the ESXi dump collector. For this feature to work, the vmkernel port used for management purposes must be on a vSphere Standard Switch.
  • Port Mirroring cannot be used in conjunction with LACP to mirror LACPDU packets used for negotiation and control.
  • The teaming health check does not work for LAG ports as the LACP protocol itself is capable of ensuring the health of the individual LAG ports. However, VLAN and MTU health check can still check LAG ports.
  • The enhanced LACP support is limited to a single LAG to handle the traffic per distributed port (dvPortGroup) or port group.
  • You can create up to 64 LAGs on a distributed switch. A host can support up to 64 LAGs. However, the number of LAGs that you can actually use depends on the capabilities of the underlying physical environment and the topology of the virtual network. For example, if the physical switch supports up to four ports in an LACP port channel, you can connect up to four physical NICs per host to a LAG.

LACP Compatibility with vDS

vCenter Server version
vDS version
Host version
Compatibility
vCenter Server 5.5vDS 5.5ESXi 5.5LACP v1 and v2 can be configured.
vCenter Server 5.5vDS 5.5ESXi 5.1ESXi 5.1 or older hosts can be added to vCenter Server 5.5, but cannot be added to vDS 5.5.
vCenter Server 5.5vDS 5.1ESXi 5.1vCenter Server 5.5 can create a vDS 5.1 and add an ESXi 5.1 host to it.
vCenter Server 5.5 can configure LACP v1 on a 5.1 vDS.
vCenter Server 5.5vDS 5.1ESXi 5.5ESXi 5.5 host can be added to vDS 5.1. Supports LACP v1 only.
vCenter Server 5.5vDS versions prior to 5.1ESXi 5.1LACP feature is not supported.
vCenter Server 5.1 or earliervDS 5.1 or earlier versionESXi 5.5ESXi 5.5 host cannot be added to vCenter Server 5.1 or earlier versions.

Note: v1 represents the LACP version introduced in vSphere 5.1 and v2 represents Enhanced LACP introduced in vSphere 5.5.
Source KB

No comments:

Post a Comment