Bug 2148684

Summary:	[RFE] support the arp_missed_max bond option
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:	low	Docs Contact:	Marc Muehlfeld <mmuehlfe>
Priority:	medium
Version:	9.2	CC:	bgalvani, ferferna, lrintel, mberezny, rkhan, sfaye, sukulkar, till, vbenes
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	NetworkManager-1.43.3-1.el9	Doc Type:	Enhancement
Doc Text:	.NetworkManager supports defining after how many failed ARP checks the bonding driver marks a port as down This enhancement adds the `arp_missed_max` option to bond connection profiles in NetworkManager. If you use the Address Resolution Protocol (ARP) monitor to check if ports of a bond are up, you can now set `arp_missed_max` to define after how many failed checks the bonding driver marks the port as down.	Story Points:	---
Clone Of:		Environment:
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-11-27 03:48:02 UTC

Description of problem:

Please help add the arp_missed_max bond option. From [1]:

arp_missed_max

	Specifies the number of arp_interval monitor checks that must
	fail in order for an interface to be marked down by the ARP monitor.

	In order to provide orderly failover semantics, backup interfaces
	are permitted an extra monitor check (i.e., they must fail
	arp_missed_max + 1 times before being marked down).

	The default value is 2, and the allowable range is 1 - 255.

[1] https://www.kernel.org/doc/Documentation/networking/bonding.rst

Comment 4 sfaye 2023-01-22 14:36:32 UTC

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

Comment 15 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