Typically, the LACP port-channel members that do not receive LACP PDUs are set to Inactive state. However, in certain deployments, port-channel members that are in Inactive state must be isolated, so that they can be viewed as separate individual ports.
Individual ports are not a part of the port channel. Normal network traffic flows through these individual ports. The objective of this feature is to make the individual ports available for normal traffic flow, even though they remain as inactive members of the parent port-channel.
You can enable the LACP individual feature only on the port-channels. The isolated ports are known as LACP individual ports.
NOTE: You cannot configure the LACP individual ports and LACP fallback features on a port-channel at the same time as they are mutually exclusive.
If the peer switch connected to the port-channel that contains the LACP individual (isolated) ports do not switch or forward packets among its ports, Dell Technologies recommends enabling
port-fast and
bpdu-guard on that LACP individually enabled port-channel, so that, the LACP individual ports can move to the forwarding state ASAP.
If the peer switch connected to the port-channel that contains the LACP individual (isolated) ports switch or forward packets and is xSTP aware, Dell Technologies recommends enabling xSTP on LACP individually enabled port-channel. This way, data loops involving individual ports are prevented.
If the peer switch connected to the port-channel that contains the LACP individual (isolated) ports switch or forward packets and is xSTP unaware and switches xSTP BPDUs also (for example, a PXE booting device), Dell Technologies recommends enabling xSTP on that LACP individually enabled port-channel. As the peer switch forwards the xSTP BPDUs, loops caused by creating multiple individual ports are prevented.
Restrictions and Limitations
LACP fallback restrictions and limitations:
NOTE: You can avoid loops in VLAN deployments by enabling spanning tree protocol (STP) on LACP individual port-channels. But, the same is not possible in VXLAN deployments, as xSTP is not supported in VXLAN deployments.
VXLAN features have platform restrictions that apply to features configured with the LACP individual feature. Except for these restrictions, no other platform-specific dependencies exist for this feature.
You must enable the LACP individual feature on both VLT Peers.
The LACP individual feature is not supported on port-channels whose VXLAN configurations are managed by the NSX controller. The following configurations are mutually exclusive:
nve-controller and
lacp individual.
You can enable the LACP individual feature on port-channels with Layer2 modes. The following configurations are mutually exclusive:
no switchport and
lacp individual.
Auto-port channel is supported only in Fabric mode and is not available in Normal Full-switch mode. Because the LACP individual feature works only on Full-switch (Normal OS10) mode, the LACP individual and Auto-port channel features become mutually exclusive inherently by the modes on which they operate.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\
