Bug 550 - Only one bond link is usable with 802.3ad LACP (mode 4)
Summary: Only one bond link is usable with 802.3ad LACP (mode 4)
Status: CONFIRMED
Alias: None
Product: DPDK
Classification: Unclassified
Component: ethdev (show other bugs)
Version: 20.11
Hardware: All All
: High major
Target Milestone: ---
Assignee: Declan Doherty
URL:
Depends on:
Blocks:
 
Reported: 2020-10-09 20:34 CEST by Kiran
Modified: 2020-10-09 20:34 CEST (History)
0 users



Attachments

Description Kiran 2020-10-09 20:34:05 CEST
This commit is causing only one bond slave link to forward traffic - https://github.com/DPDK/dpdk/commit/56cbc08173995d6d57bd5927dfe9b11ad269bf8d

Testing with Juniper QFX switch.

Only one link satisfies this condition -

		if (is_same_ether_addr(&partner->port_params.system,
			&internals->mode4.mac_addr)) {
			/* This LACP frame is sending to the bonding port
			 * so pass it to rx_machine.
			 */
			rx_machine(internals, slave_id, &lacp->lacpdu);
		}

For other links, the system id is different than the bond MAC and so rx_machine() never gets called.

Discussed this with Doherty, Declan <declan.doherty@intel.com>

Note You need to log in before you can comment on or make changes to this bug.