LACP bypass note updated to remove non-supported options

Author: cumulusAnia

content/cumulus-linux-37/Layer-2/LACP-Bypass.md

@@ -23,7 +23,7 @@ needs to be active.
 
 Keep in the mind the following caveats with all-active mode:
 
-- All-active mode is not supported on bonds that are not specified as bridge ports on the switch. To work around this limitation, do one of the following:
+- All-active mode is only supported on bonds that are specified as bridge ports on the switch. To work around this limitation, do one of the following:
 - Configure the layer 3 interface on the physical link instead of using a bond
 - Configure the LACP bond on the switch port so that the AS has neighbor LACP information
 - Configure the bond interface as {{<link url="Bonding-Link-Aggregation#enable-balance-xor-mode" text="balance-xor">}} mode instead of LACP

content/cumulus-linux-40/Layer-2/LACP-Bypass.md

@@ -12,11 +12,9 @@ In *all-active* mode, when a bond has multiple slave interfaces, each bond slave
 
 {{%notice note%}}
 
-- All-active mode is *not* supported on bonds that are *not* specified as bridge ports on the switch.
+- All-active mode is *only* supported on bonds that are specified as bridge ports on the switch.
 - STP does not run on the individual bond slave interfaces when the LACP bond is in all-active mode. Only use all-active mode on host-facing LACP bonds. Configure {{<link url="Spanning-Tree-and-Rapid-Spanning-Tree" text="STP BPDU guard">}} together with all-active mode.
 - In an {{<link url="Multi-Chassis-Link-Aggregation-MLAG" text="MLAG deployment">}} where bond slaves of a host are connected to two switches and the bond is in all-active mode, all the slaves of bond are active on both the primary and secondary MLAG nodes.
-- `priority mode`, `bond-lacp-bypass-period`, `bond-lacp-bypass-priority`, and `bond-lacp-bypass-all-active` are not supported.
-
 {{%/notice%}}
 
 ## Configure LACP Bypass

content/cumulus-linux-41/Layer-2/LACP-Bypass.md

@@ -12,11 +12,9 @@ In *all-active* mode, when a bond has multiple slave interfaces, each bond slave
 
 {{%notice note%}}
 
-- All-active mode is *not* supported on bonds that are *not* specified as bridge ports on the switch.
+- All-active mode is *only* supported on bonds that are specified as bridge ports on the switch.
 - STP does not run on the individual bond slave interfaces when the LACP bond is in all-active mode. Only use all-active mode on host-facing LACP bonds. Configure {{<link url="Spanning-Tree-and-Rapid-Spanning-Tree" text="STP BPDU guard">}} together with all-active mode.
 - In an {{<link url="Multi-Chassis-Link-Aggregation-MLAG" text="MLAG deployment">}} where bond slaves of a host are connected to two switches and the bond is in all-active mode, all the slaves of bond are active on both the primary and secondary MLAG nodes.
-- `priority mode`, `bond-lacp-bypass-period`, `bond-lacp-bypass-priority`, and `bond-lacp-bypass-all-active` are not supported.
-
 {{%/notice%}}
 
 ## Configure LACP Bypass

content/cumulus-linux-42/Layer-2/LACP-Bypass.md

@@ -12,12 +12,10 @@ In *all-active* mode, when a bond has multiple slave interfaces, each bond slave
 
 {{%notice note%}}
 
-- All-active mode is *not* supported on bonds that are *not* specified as bridge ports on the switch.
+- All-active mode is *only* supported on bonds that are specified as bridge ports on the switch.
 - STP does not run on the individual bond slave interfaces when the LACP bond is in all-active mode. Only use all-active mode on host-facing LACP bonds. Configuring {{<link url="Spanning-Tree-and-Rapid-Spanning-Tree-STP" text="STP BPDU guard">}} together with all-active mode is highly recommended.
 - In an {{<link url="Multi-Chassis-Link-Aggregation-MLAG" text="MLAG deployment">}} where bond slaves of a host are connected to two switches and the bond is in all-active mode, all the slaves of bond are active on both the primary and secondary MLAG nodes.
 - LACP bypass is supported with {{<link url="EVPN-Multihoming/#supported-features" text="EVPN multihoming">}}.
-- `priority mode`, `bond-lacp-bypass-period`, `bond-lacp-bypass-priority`, and `bond-lacp-bypass-all-active` are not supported.
-
 {{%/notice%}}
 
 ## Configure LACP Bypass

content/cumulus-linux-43/Layer-2/LACP-Bypass.md

@@ -12,11 +12,10 @@ In *all-active* mode, when a bond has multiple slave interfaces, each bond slave
 
 {{%notice note%}}
 
-- All-active mode is *not* supported on bonds that are *not* specified as bridge ports on the switch.
+- All-active mode is *only* supported on bonds that are specified as bridge ports on the switch.
 - STP does not run on the individual bond slave interfaces when the LACP bond is in all-active mode. Only use all-active mode on host-facing LACP bonds. Configure {{<link url="Spanning-Tree-and-Rapid-Spanning-Tree-STP" text="STP BPDU guard">}} together with all-active mode.
 - In an {{<link url="Multi-Chassis-Link-Aggregation-MLAG" text="MLAG deployment">}} where bond slaves of a host are connected to two switches and the bond is in all-active mode, all the slaves of bond are active on both the primary and secondary MLAG nodes.
 - LACP bypass is supported with {{<link url="EVPN-Multihoming/#supported-features" text="EVPN multihoming">}}.
-- `priority mode`, `bond-lacp-bypass-period`, `bond-lacp-bypass-priority`, and `bond-lacp-bypass-all-active` are not supported.
 
 {{%/notice%}}
 

content/cumulus-linux-44/Layer-2/LACP-Bypass.md

@@ -11,11 +11,10 @@ On Cumulus Linux, *LACP bypass* allows a {{<link url="Bonding-Link-Aggregation"
 In *all-active* mode, when a bond has multiple slave interfaces, each bond slave interface operates as an active link while the bond is in bypass mode. This is useful during PXE boot of a server with multiple NICs, when you cannot determine beforehand which port needs to be active.
 
 {{%notice note%}}
-- All-active mode is *not* supported on bonds that are *not* specified as bridge ports on the switch.
+- All-active mode is *only* supported on bonds that are specified as bridge ports on the switch.
 - STP does not run on the individual bond slave interfaces when the LACP bond is in all-active mode. Only use all-active mode on host-facing LACP bonds. Configure {{<link url="Spanning-Tree-and-Rapid-Spanning-Tree-STP" text="STP BPDU guard">}} together with all-active mode.
 - In an {{<link url="Multi-Chassis-Link-Aggregation-MLAG" text="MLAG deployment">}} where bond slaves of a host connect to two switches and the bond is in all-active mode, all the slaves of the bond are active on both the primary and secondary MLAG nodes. If multiple physical NIC interfaces or more than one physical NIC is present on the physical host, NVIDIA recommends that you define which physical NIC or interface runs the PXE boot inside the PXE boot configuration file. If you do not define a specific NIC or interface, the switch sends a PXE boot request on all the interfaces in the bond and the PXE request fails.
 - LACP bypass works with {{<link url="EVPN-Multihoming/#supported-features" text="EVPN multihoming">}}.
-- Cumulus Linux does not support `priority mode`, `bond-lacp-bypass-period`, `bond-lacp-bypass-priority`, and `bond-lacp-bypass-all-active`.
 {{%/notice%}}
 
 ## Configure LACP Bypass

content/cumulus-linux-50/Layer-2/LACP-Bypass.md

@@ -11,11 +11,10 @@ In Cumulus Linux, [LACP](## "Link Aggregation Control Protocol") bypass allows a
 In *all-active* mode, when a bond has multiple slave interfaces, each bond slave interface operates as an active link while the bond is in bypass mode. This is useful during PXE boot of a server with multiple NICs, when you cannot determine beforehand which port needs to be active.
 
 {{%notice note%}}
-- All-active mode is *not* supported on bonds that are *not* specified as bridge ports on the switch.
+- All-active mode is *only* supported on bonds that are specified as bridge ports on the switch.
 - [STP](## "Spanning Tree Protocol") does not run on the individual bond slave interfaces when the LACP bond is in all-active mode. Only use all-active mode on host-facing LACP bonds. Configure {{<link url="Spanning-Tree-and-Rapid-Spanning-Tree-STP" text="STP BPDU guard">}} together with all-active mode.
 - In an {{<link url="Multi-Chassis-Link-Aggregation-MLAG" text="MLAG deployment">}} where bond slaves of a host connect to two switches and the bond is in all-active mode, all the slaves of the bond are active on both the primary and secondary MLAG nodes. If multiple physical NIC interfaces or more than one physical NIC is present on the physical host, NVIDIA recommends that you define which physical NIC or interface runs the PXE boot inside the PXE boot configuration file. If you do not define a specific NIC or interface, the switch sends a PXE boot request on all the interfaces in the bond and the PXE request fails.
 - LACP bypass works with {{<link url="EVPN-Multihoming/#supported-features" text="EVPN multihoming">}}.
-- Cumulus Linux does not support `priority mode`, `bond-lacp-bypass-period`, `bond-lacp-bypass-priority`, and `bond-lacp-bypass-all-active`.
 {{%/notice%}}
 
 ## Configure LACP Bypass

content/cumulus-linux-51/Layer-2/LACP-Bypass.md

@@ -11,11 +11,10 @@ In Cumulus Linux, [LACP](## "Link Aggregation Control Protocol") bypass allows a
 In *all-active* mode, when a bond has multiple slave interfaces, each bond slave interface operates as an active link while the bond is in bypass mode. This is useful during PXE boot of a server with multiple NICs, when you cannot determine beforehand which port needs to be active.
 
 {{%notice note%}}
-- All-active mode is *not* supported on bonds that are *not* specified as bridge ports on the switch.
+- All-active mode is *only* supported on bonds that are specified as bridge ports on the switch.
 - [STP](## "Spanning Tree Protocol") does not run on the individual bond slave interfaces when the LACP bond is in all-active mode. Only use all-active mode on host-facing LACP bonds. Configure {{<link url="Spanning-Tree-and-Rapid-Spanning-Tree-STP" text="STP BPDU guard">}} together with all-active mode.
 - In an {{<link url="Multi-Chassis-Link-Aggregation-MLAG" text="MLAG deployment">}} where bond slaves of a host connect to two switches and the bond is in all-active mode, all the slaves of the bond are active on both the primary and secondary MLAG nodes. If multiple physical NIC interfaces or more than one physical NIC is present on the physical host, NVIDIA recommends that you define which physical NIC or interface runs the PXE boot inside the PXE boot configuration file. If you do not define a specific NIC or interface, the switch sends a PXE boot request on all the interfaces in the bond and the PXE request fails.
 - LACP bypass works with {{<link url="EVPN-Multihoming/#supported-features" text="EVPN multihoming">}}.
-- Cumulus Linux does not support `priority mode`, `bond-lacp-bypass-period`, `bond-lacp-bypass-priority`, and `bond-lacp-bypass-all-active`.
 {{%/notice%}}
 
 ## Configure LACP Bypass

content/cumulus-linux-510/Layer-2/LACP-Bypass.md

@@ -11,11 +11,10 @@ In Cumulus Linux, <span class="a-tooltip">[LACP](## "Link Aggregation Control Pr
 In *all-active* mode, when a bond has multiple slave interfaces, each bond slave interface operates as an active link while the bond is in bypass mode. This is useful during PXE boot of a server with multiple NICs, when you cannot determine beforehand which port needs to be active.
 
 {{%notice note%}}
-- All-active mode is *not* supported on bonds that are *not* specified as bridge ports on the switch.
+- All-active mode is *only* supported on bonds that are specified as bridge ports on the switch.
 - <span class="a-tooltip">[STP](## "Spanning Tree Protocol")</span> does not run on the individual bond slave interfaces when the LACP bond is in all-active mode. Only use all-active mode on host-facing LACP bonds. Configure {{<link url="Spanning-Tree-and-Rapid-Spanning-Tree-STP" text="STP BPDU guard">}} together with all-active mode.
 - In an {{<link url="Multi-Chassis-Link-Aggregation-MLAG" text="MLAG deployment">}} where bond slaves of a host connect to two switches and the bond is in all-active mode, all the slaves of the bond are active on both the primary and secondary MLAG nodes. If multiple physical NIC interfaces or more than one physical NIC is present on the physical host, NVIDIA recommends that you define which physical NIC or interface runs the PXE boot inside the PXE boot configuration file. If you do not define a specific NIC or interface, the switch sends a PXE boot request on all the interfaces in the bond and the PXE request fails.
 - LACP bypass works with {{<link url="EVPN-Multihoming/#supported-features" text="EVPN multihoming">}}.
-- Cumulus Linux does not support `priority mode`, `bond-lacp-bypass-period`, `bond-lacp-bypass-priority`, and `bond-lacp-bypass-all-active`.
 {{%/notice%}}
 
 ## Configure LACP Bypass

content/cumulus-linux-511/Layer-2/LACP-Bypass.md

@@ -11,11 +11,10 @@ In Cumulus Linux, <span class="a-tooltip">[LACP](## "Link Aggregation Control Pr
 In *all-active* mode, when a bond has multiple slave interfaces, each bond slave interface operates as an active link while the bond is in bypass mode. This is useful during PXE boot of a server with multiple NICs, when you cannot determine beforehand which port needs to be active.
 
 {{%notice note%}}
-- All-active mode is *not* supported on bonds that are *not* specified as bridge ports on the switch.
+- All-active mode is *only* supported on bonds that are specified as bridge ports on the switch.
 - <span class="a-tooltip">[STP](## "Spanning Tree Protocol")</span> does not run on the individual bond slave interfaces when the LACP bond is in all-active mode. Only use all-active mode on host-facing LACP bonds. Configure {{<link url="Spanning-Tree-and-Rapid-Spanning-Tree-STP" text="STP BPDU guard">}} together with all-active mode.
 - In an {{<link url="Multi-Chassis-Link-Aggregation-MLAG" text="MLAG deployment">}} where bond slaves of a host connect to two switches and the bond is in all-active mode, all the slaves of the bond are active on both the primary and secondary MLAG nodes. If multiple physical NIC interfaces or more than one physical NIC is present on the physical host, NVIDIA recommends that you define which physical NIC or interface runs the PXE boot inside the PXE boot configuration file. If you do not define a specific NIC or interface, the switch sends a PXE boot request on all the interfaces in the bond and the PXE request fails.
 - LACP bypass works with {{<link url="EVPN-Multihoming/#supported-features" text="EVPN multihoming">}}.
-- Cumulus Linux does not support `priority mode`, `bond-lacp-bypass-period`, `bond-lacp-bypass-priority`, and `bond-lacp-bypass-all-active`.
 {{%/notice%}}
 
 ## Configure LACP Bypass