bonding with two switches

Hello,

is it possible to activate bonding with the two NICs of a server
connected to two different switches ?

Are there special protocols the switch must support to let me do this ?

Is there documentation on how to do this with Enterasys switches ?

Thank you very much
Andreas

Andreas Moroder <andreas.moroder@[nospam]sb-brixen.it> wrote:

> Hello,
>
> is it possible to activate bonding with the two NICs of a server
> connected to two different switches ?
>
> Are there special protocols the switch must support to let me do this ?
>
> Is there documentation on how to do this with Enterasys switches ?

You probably want active-backup mode.
Here is the documentation:

http://www.linuxfoundation.org/colla...orking/bonding

Bruce Richardson wrote:

> the pair fails). Really, if you want to connect to multiple switches
> for redundancy, you want not bonding but bridging, with switches that
> support spanning tree. What you do then is create a bridged interface,
> add the individual interfaces to the bridge, activate spanning tree on
> the bridge (and on all your switches) and let spanning tree decide which
> interface to use. This is the most resilient solution because the
> spanning tree protocol will detect the situation where your host is
> connected to an isolated switch and switch to using the other link, to
> the switch which is still properly connected.
>
> Since you should be using spanning tree in any resilient network with
> multiple switches, I'd recommend the bridge approach. Of course, you
> could have four interfaces (two dual port NICs, say), create two bonded
> interfaces (with each bond connecting to only one switch) and then add
> those two interfaces to a bridge. That would be belt and braces and an
> extra pair of trousers just in case.

The problem with bridging is that failover time is in the order of 30
seconds or so since linux bridging does not support anything else than plain
old STP (ie, no RSTP etc.). Of course the STP parameters can be tuned, but
you must know what you're doing, and you still can't get less than a few
seconds failover time.

Active-backup bonding, on the other hand, can failover in hundredths of
second with no special configuration.

But I agree with most of what you said, and I think the OP should choose
what he thinks is best for him.

Bruce Richardson <(E-Mail Removed)> wrote:
> pk <(E-Mail Removed)> wrote:
> > You probably want active-backup mode.

> It's the simplest way to configure it, in the desired solution, but
> there can be problems. Active-backup over two switches is fine *as
> long as you never see a cable failure*. As soon as the active link
> fails, any device which was connected to the same switch is going to
> fail to connect to anything until the switch decides it no longer
> has a connection to the relevant mac address, because the switch
> will not try forwarding any ethernet frames to other switches until
> then. This is something you should test.

The switches need to be in the same broadcast domain right? If there
is a gratuitous ARP on the failover, won't that propagate around and
cause the switch in question to relearn where that destination MAC
resides (assuming the failover preserves the MAC rather than causes a
new IP-MAC translation)

> Active-backup can also be a problem if the connection between the
> host and the switch is fine, but the switch loses connectivity to
> other parts of your network. The result is an isolated host,
> happily remaining connected to a switch that can't forward its
> traffic on.

Wouldn't that that also be an issue for active-active?

rick jones
--
a wide gulf separates "what if" from "if only"
these opinions are mine, all mine; HP might not want them anyway...
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...

Bruce Richardson <(E-Mail Removed)> wrote:
> Rick Jones <(E-Mail Removed)> wrote:
> >
> > The switches need to be in the same broadcast domain right? If there
> > is a gratuitous ARP on the failover, won't that propagate around and
> > cause the switch in question to relearn where that destination MAC
> > resides (assuming the failover preserves the MAC rather than causes a
> > new IP-MAC translation)

> OP didn't say anything about gratuitous ARP, which isn't something that
> automatically comes with bonding.

Sorry about that - I was projecting what I'm told HP-UX APA (Auto Port
Aggregation) does in LAN Monitor mode (what it calls active-standby)
onto Linux bonding.

rick jones
--
denial, anger, bargaining, depression, acceptance, rebirth...
where do you want to be today?
these opinions are mine, all mine; HP might not want them anyway...
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...

> The problem with bridging is that failover time is in the order of 30
> seconds or so since linux bridging does not support anything else than plain
> old STP (ie, no RSTP etc.). Of course the STP parameters can be tuned, but
> you must know what you're doing, and you still can't get less than a few
> seconds failover time.
>
Hello,

according to

http://kerneltrap.org/mailarchive/li...08/7/9/2403834

RSTP should already be available for linux as userspace daemon.

Someone has tested this ?

Bye
Andreas