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.
.`NetworkManager` now supports configuration of the `ns_ip6_target` option for bond interfaces
This enhancement allows setting the `arp_interval` option by specifying a maximum of 16 IPv6 addresses as monitoring peers in `NetworkManager` for configuration of the `ns_i6_target` option for bond interfaces. Previously, it was not possible to specify IPv6 monitoring peers in `NetworkManager`. With this update, you can configure the `ns_ip6_target` option in the `bond.options` parameter by using the `nmcli` utility. `NetworkManager` applies this setting to the bond interface by enabling the specification of a maximum of 16 IPv6 addresses. This enhancement equally applies to IPv4 and IPv6 settings.
# uname -r
5.14.0-231.el9.x86_64
# rpm -q NetworkManager
NetworkManager-1.43.4-1.el9.x86_64
# nmcli con add type bond ifname team0 bond.options "mode=active-backup,arp_interval=200,arp_missed_max=15,ns_ip6_target=fe80::210:18ff:feaa:bbcc"
Error: Failed to add 'bond-team0' connection: bond.options: 'arp_interval' option requires 'arp_ip_target' option to be set
# ip link add bond0 type bond mode active-backup arp_interval 1000 arp_missed_max 15 ns_ip6_target fe80::210:18ff:feaa:bbcc
# echo $?
0
Comment 7Fernando F. Mancera
2023-03-24 09:50:14 UTC
Oh thanks for reporting this. I didn't know ns_ip6_target could satisfy that condition too. Let me fix it, it is simple. Thanks!
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
Description of problem: Please help add bond new option ns_ip6_target for NM. Here is the kernel doc[1] ns_ip6_target Specifies the IPv6 addresses to use as IPv6 monitoring peers when arp_interval is > 0. These are the targets of the NS request sent to determine the health of the link to the targets. Specify these values in ffff:ffff::ffff:ffff format. Multiple IPv6 addresses must be separated by a comma. At least one IPv6 address must be given for NS/NA monitoring to function. The maximum number of targets that can be specified is 16. The default value is no IPv6 addresses. 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=129e3c1bab24 [3] https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=9831202f