On 22/09/2016 17:08, Gleb Smirnoff wrote:
On Thu, Sep 22, 2016 at 04:52:35PM +0100, Steven Hartland wrote:
S> > S> > S> > Does lagg(4) hardware address change when it failovers?
S> > S> > S> >
S> > S> > S> It moves the address between interfaces which typically moves it
between
S> > S> > S> switches too.
S> > S> >
S> > S> > So, the address doesn't change, which means ARP cache doesn't need to
S> > S> > change as well. If it moves between switches, all that needs to be
done
S> > S> > is to send whatever packet from proper hardware address to broadcast.
S> > S> >
S> > S> That would be nice but unfortunately in the wild that won't work as
S> > S> without GARP devices can and do ignore :(
S> >
S> > You can create a fake gratious ARP packet, if you want. Switches must not
S> > require IP addresses matching the reality in the packet.
S> >
S> > P.S. I always read GARP as Generic Attribute Registration Protocol.
S> >
S> We could but then what happens when its IPv6 or $other protocol that
S> needs to know? That would require lagg to be edited with all the special
S> cases instead of allowing the protocol to handle it they way it needs.
You just said that "without GARP devices can and do ignore", didn't you?
Let's take this as truth, although I doubt. So, if this is the truth, that
means that if you are running IPv6 only, the switches won't recondigure
theirselves due to lack of gratious ARP.
Not sure I follow you, gratuitous ARP is required for IPv4 to work, for
IPv6 you need an unsolicited neighbour announcement.
Other protocols, where PPPoE is good example simply doesn't have any
analogs of ARP or ND. So what would your switches do in that case? And
what other layers are you going to hack, if you are going to run PPPoE
service with lagg failover?
Good question, surely that's a good reason to have each protocol handle
it and not to teach LAGG about every possible protocol?
In reality, a layer 2 device must forward layer 2 traffic, and must
reconfigure its forwarding table based on source addresses seen on ports.
And that's what all devices I've seen do. So what if we actually try
the approach, I suggested? I can write the patch for you if you want.
The main problem with LAGG in failover mode is ensuring the traffic is
sent to the correct port.
When you have the scenario where a switch stack believes MAC XYZ is
accessible by port ABC then unless you tell it otherwise it will
continue to believe that and hence send traffic to said port. I'm sure
we'll agree that the standard for doing this for IPv4 is ARP and for
IPv6 is NA.
When using LAGG and we loose the master port we need correct the
connected devices view (both direct and remote) of the world such that
traffic is now sent to a different physical port.
Back in the day, when switches weren't so "smart", sending a correctly
address packet from the new port would potentially help, but with
smarter switches and stacking in the mix sticking to the "standards"
helps maintain compatibility and hence functionality with things like LAGG.
Having tested with a number of vendor switches Cisco, Extreme and more
recently Arista only sending gratuitous ARP for IPv4 and unsolicited NA
for IPv6 reliably resulted in rapid failover between LAGG ports.
Other methods like sending correctly addressed output from the new port
helped, we tested this with outbound pings from IPMI, but still resulted
in noticeable recovery delay.
S> Overall, while the proposed change (https://reviews.freebsd.org/D4111)
S> does involve changes to multiple layers it still feels like the right
S> approach as it has the right layer dealing with the change instead of
S> hard-coded assumptions.
Sorry, it doesn't feel like the right approach. :(
Out of interest why has your opinion changed since your post here:
https://lists.freebsd.org/pipermail/freebsd-net/2012-February/031340.html ?
_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
