From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: "Finer, Howard" <hfiner@rbbn.com>
Cc: "andy@greyhouse.net" <andy@greyhouse.net>,
"vfalico@gmail.com" <vfalico@gmail.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: bonding driver issue when configured for active/backup and using ARP monitoring
Date: Mon, 04 Jan 2021 18:51:25 -0800 [thread overview]
Message-ID: <9069.1609815085@famine> (raw)
In-Reply-To: <MN2PR03MB47524C92E45EB4C1B70D595CB7D20@MN2PR03MB4752.namprd03.prod.outlook.com>
Finer, Howard <hfiner@rbbn.com> wrote:
>Please advise if there is any update here, and if not how we can go about
>getting an update to the driver to rectify the issue.
As it happens, I've been looking at this today, and have a
couple of questions about your configuration:
- Is there an IP address on the same subnet as the arp_ip_target
configured directly on the bond, or on a VLAN logically above the bond?
- Is the "arp_ip_target" address reachable via an interface
other than the bond (or VLAN above it)? This can be checked via "ip
route get [arp_ip_target]", i.e., if the target address for bond0 is
1.2.3.4, the command "ip route get 1.2.3.4" will return something like
1.2.3.4 dev bond0 src [...]
If an interface other than bond0 (or a VLAN above it) is listed,
then there's a path to the arp_ip_target that doesn't go through the
bond.
The ARP monitor logic can only handle a limited set of
configurations, so if your configuration is outside of that it can
misbehave in some ways.
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2021-01-05 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 18:05 bonding driver issue when configured for active/backup and using ARP monitoring Finer, Howard
2020-12-04 20:43 ` Jay Vosburgh
[not found] ` <MN2PR03MB4752855F586F7CC5811E9B67B7CE0@MN2PR03MB4752.namprd03.prod.outlook.com>
2020-12-07 15:49 ` Finer, Howard
2021-01-04 23:08 ` Finer, Howard
2021-01-05 2:51 ` Jay Vosburgh [this message]
2021-01-05 16:49 ` Finer, Howard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9069.1609815085@famine \
--to=jay.vosburgh@canonical.com \
--cc=andy@greyhouse.net \
--cc=hfiner@rbbn.com \
--cc=netdev@vger.kernel.org \
--cc=vfalico@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).