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: | VERIFIED --- | QA Contact: | Matej Berezny <mberezny> |
| Severity: | unspecified | Docs Contact: | Mayur Patil <maypatil> |
| Priority: | medium | ||
| Version: | 9.1 | CC: | bgalvani, ferferna, lrintel, maypatil, mberezny, rkhan, sfaye, sukulkar, till, vbenes |
| Target Milestone: | rc | Keywords: | FutureFeature, Triaged |
| Target Release: | 9.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-1.43.3-1.el9 | Doc Type: | Enhancement |
| Doc Text: |
Feature:
NetworkManager now extends support for the "lacp_active" option in bonding configurations. This option controls the periodic transmission of Link Aggregation Control Protocol Data Units (LACPDU) frames.
Reason:
The inclusion of "lacp_active" enhances NetworkManager's ability to manage bonding configurations that require fine-grained control over LACPDU frames, complying with the kernel documentation.
Result:
Users can now leverage this feature to adjust the behavior of LACPDU transmissions in bonding setups. By setting "lacp_active" to 'on' or 'off', they can respectively enable or disable the periodic transmission of LACPDU frames, adding to the flexibility and customization of their network configurations.
|
Story Points: | --- |
| Clone Of: | Environment: |
https://bugzilla.redhat.com/show_bug.cgi?id=2149012
|
|
| Last Closed: | 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
*** Bug 2148685 has been marked as a duplicate of this bug. *** |