Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2069001

Summary:	[RFE] NM: please support bond new option lacp_active
Product:	Red Hat Enterprise Linux 9	Reporter:	Hangbin Liu <haliu>
Component:	NetworkManager	Assignee:	Fernando F. Mancera <ferferna>
Status:	CLOSED ERRATA	QA Contact:	Matej Berezny <mberezny>
Severity:	unspecified	Docs Contact:	Mayur Patil <maypatil>
Priority:	medium
Version:	9.1	CC:	bgalvani, ferferna, gfialova, lrintel, maypatil, mberezny, rkhan, sfaye, sukulkar, till, vbenes
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	9.1	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.43.3-1.el9	Doc Type:	Enhancement
Doc Text:	.`NetworkManager` now supports the `lacp_active` option in the bonding configuration By using `NetworkManager`, the `lacp_active` option in bonding configuration provides fine-grained control over Link Aggregation Control Protocol Data Units (LACPDU) frames. The `lacp_active` option also adjusts the behavior of LACPDU frames and controls periodic transmission of these frames in the bonding setup. To customize network configurations, you can enable or disable periodic transmission of LACPDU frames by setting `lacp_active` to `ON` or `OFF`.	Story Points:	---
Clone Of:		Environment:	https://bugzilla.redhat.com/show_bug.cgi?id=2149012
Last Closed:	2023-11-07 08:37:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1951910

Description Hangbin Liu 2022-03-28 04:13:55 UTC

Description of problem:

Please help add bond new option lacp_active for NM. Here is the kernel doc[1]

lacp_active
	Option specifying whether to send LACPDU frames periodically.

	off or 0
		LACPDU frames acts as "speak when spoken to".

	on or 1
		LACPDU frames are sent along the configured links
		periodically. See lacp_rate for more details.

	The default is on.

And kernel commit [2]. iproute2 commit [3] for reference.

[1] https://www.kernel.org/doc/Documentation/networking/bonding.rst
[2] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=3a755cd8b7c6
[3] https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6d0d35ba

Comment 2 sfaye 2022-11-28 11:01:03 UTC

*** Bug 2148685 has been marked as a duplicate of this bug. ***

Comment 8 errata-xmlrpc 2023-11-07 08:37:53 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6585