netdev - bond failover doesn't happen when active slave link is up, but there is no connectivity

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 3 Mar 2014 18:49:04 +0200
From:	"Alex Lyakas" <alex@...arastorage.com>
To:	<netdev@...r.kernel.org>
Subject: bond failover doesn't happen when active slave link is up, but there is no connectivity

Greetings all,
We are using bonding interfaces in active-backup (1) mode, with 
"fail_over_mac" set to "active" (1), with miimon=100 and two slaves. The 
slaves are "either regular" network interfaces, or vlan interfaces created 
with "vconfig" over "regular" interfaces. One of the slaves is defined as 
primary. The purpose of this config is to ensure failover in case one of the 
interfaces dies. This config usually works as expected.

One scenario that doesn't work for us, is when link status of the active 
slave is up, but all the packets sent to it are dropped, e.g., because of
incorrect switch configuration. In that case bond failover doesn't happen. 
Can this scenario be addressed with bonding?

Thanks,
Alex.

I found a discussion, which looks relevant, labeled "How to check an 
inactive slave in a bond?" in 
http://www.spinics.net/lists/lartc/msg21434.html". But this discussion 
considers the inactive slave, while in my case, I would like to better 
handle problems with the active slave.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html