From: Sander Klein <roedie@roedie.nl>
To: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
Cc: Bridge <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] Bridge - vlan - bond
Date: Sat, 05 Dec 2009 20:47:19 +0100 [thread overview]
Message-ID: <b1701dff411230cfdd4137a1275ec32a@localhost> (raw)
In-Reply-To: <4B1AA541.2030500@free.fr>
Hi,
> Can you please also describe what you try to achieve, and not only your
> setup ?
>
> What are the expected effects ?
Sorry, I will. What I am trying to achieve is high availability. The host
I'm building this on will be a kvm host with virtual machines which runs
the images from a nfsmount. I need to have multiple vlans on this host
which are then bridged to the virtual machines. What I want is that if the
switch connected to eth0 fails, all traffic will go through eth1. The final
setup will be the following:
+------+ +------+
| core |---|blade | +-----+
|switch| |switch|---|eth0 |
+------+ +------+ | |
| |Host |
+------+ +------+ | |
| core |---|blade |---|eth1 |
|switch| |switch| +-----+
+------+ +------+
> Your bonding setup (active-backup) will lead to one port enabled and one
> disabled.
That's okay with me. I don't need the speed, only the redundancy. I could
use alb or tlb but since I'm testing right now active-backup it easier.
> Why don't you simply use eth0.101 and eth1.101 as two ports of br101,
and
> enable stp ?
Since the switches that connect to eth0 and eth1 have a crappy stp
implementation (its a supermicro blade chassis) it's pain to get it
working. Moreover, converging with stp is a bit slow. Bonding will do this
in 100ms or faster while stp might take 30 seconds or so.
The setup works perfectly as long as I don't use bridging. But I need the
bridging to get the network to the virtual machines.
Greets,
Sander Klein
next prev parent reply other threads:[~2009-12-05 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-05 16:30 [Bridge] Bridge - vlan - bond Sander Klein
2009-12-05 16:58 ` Sebastian Gottschall (DD-WRT)
2009-12-05 18:24 ` Nicolas de Pesloüan
2009-12-05 19:47 ` Sander Klein [this message]
2009-12-09 22:21 ` Nicolas de Pesloüan
2009-12-06 17:17 ` richardvoigt
2009-12-06 20:14 ` Sander Klein
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=b1701dff411230cfdd4137a1275ec32a@localhost \
--to=roedie@roedie.nl \
--cc=bridge@lists.linux-foundation.org \
--cc=nicolas.2p.debian@free.fr \
/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