Merge branch 'main' into rename-bf-p4cp

docs/apps/lnw/es2k/es2k-linux-networking-lag.md

@@ -261,7 +261,10 @@ The following configuration assumes that:
 - Underlay IDPF netdev has a VSI value 11 for second LAG member
 
 ```bash
-ip link add bond0 type bond miimon 100 mode active-backup
+# For static LAG:
+#     ip link add bond0 type bond miimon 100 mode active-backup
+# For dynamic LAG:
+#     ip link add bond0 type bond miimon 100 mode 802.3ad
 ip link set <IDPF netdev for VSI 10> down
 ip link set <IDPF netdev for VSI 10> master bond0
 ip link set <IDPF netdev for VSI 11> down
@@ -276,7 +279,10 @@ Create a LAG interface and assign IP to the LAG interface
 Assuming ens785f0np0 and ens785f1np1 ports are B2B connected to MEV.
 
 ```bash
-ip link add bond0 type bond miimon 100 mode active-backup
+# For static LAG:
+#     ip link add bond0 type bond miimon 100 mode active-backup
+# For dynamic LAG:
+#     ip link add bond0 type bond miimon 100 mode 802.3ad
 ip link set ens785f0np0 down
 ip link set ens785f0np0 master bond0
 ip link set ens785f1np1 down
@@ -293,13 +299,23 @@ ip link set bond0 up
 
 ### Test the ping scenarios
 
+For static LAG:
+
 - Verify the underlay ping is working fine via the active path.
 - Verify the overlay ping between VMs on same host is working fine via the active path.
 - Note the active link by using the command "cat /proc/net/bonding/bond0" on both MEV host and LP device.
 - Shut the active link on both MEV host and its peer Link Partner.
 - Verify the switchover happened from active to backup interface.
 - Verify both underlay and overlay ping are working fine and taking a backup path.
 
+For dynamic LAG:
+
+- Verify the underlay ping is working fine.
+- Verify the overlay ping between VMs on same host is working fine.
+- Note down the interface which is forwarding the traffic.
+- Bring down that interface.
+- Verify both underlay and overlay ping resume and traffic is forwarded via other LAG member.
+
 ## Limitations
 
 Current Linux Networking support for the networking recipe has following limitations:
@@ -312,5 +328,6 @@ Ex: vlan1, vlan2, vlan3 ... vlan4094.
 - VLAN-tagged packets are not supported.
 - For VxLAN tunneled packets only IPv4-in-IPv4 is supported.
 - LAG and ECMP are mutually exclusive. Both can't co-exist in the system configuration at the same time.
-- LAG configuration done via bonding driver is supported and the supported mode in active-backup.
-- Number of nexthop table entries cannot go beyond 8K, because nexthop table is now part of WCM block. 
+- LAG configuration done via bonding driver is supported.
+- The supported modes are active-backup and active-active with 802.3ad (LACP).
+- Number of nexthop table entries cannot go beyond 8K, because nexthop table is now part of WCM block.