From: Robert LeBlanc <robert@leblancnet.us>
To: Ryan King <ryank@globaldial.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridging vSwitches in VMwares ESXi
Date: Tue, 6 Apr 2010 21:29:12 -0600 [thread overview]
Message-ID: <s2xc5b98f841004062029oda188282r6f65c3559d1b5d8a@mail.gmail.com> (raw)
In-Reply-To: <000101cad601$5d42a300$17c7e900$@com>
On Tue, Apr 6, 2010 at 9:21 PM, Ryan King <ryank@globaldial.com> wrote:
> Just to clarify our setup:
>
> The physical server has 4 physical nics. vswitch1 uses 2 pnics in
> active/active. vswitch2 uses 2 pnics in active/active.
>
> The VM (running openvpn) has a bridge with one vnic on vswitch1 and one vnic
> on vswitch2. Since moving the 2nd interface to vswitch2, I have not
> experienced this issue any more (ie: previously, both vnics were on vswitch1
> - this was where we saw this issue).
We were using VLANs and bridging across VLANs, this may have
compounded our problem. We we put openvpn on it to connect two
datacenters, we got similar broadcasts storms over the VPN connection
as well.
I was going to do something similar to connect family networks using
openvpn at home until we ran into the problem. I think disbanded the
project, maybe I'll have to look into it again if VLANs were the
problem.
Robert LeBlanc
Life Sciences & Undergraduate Education Computer Support
Brigham Young University
next prev parent reply other threads:[~2010-04-07 3:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 21:02 [Bridge] Bridging vSwitches in VMwares ESXi Ryan Whelan
2010-04-06 23:17 ` Robert LeBlanc
2010-04-06 23:57 ` Ryan King
2010-04-07 1:08 ` Robert LeBlanc
2010-04-07 2:41 ` Ryan Whelan
2010-04-07 3:01 ` Robert LeBlanc
2010-04-07 3:21 ` Ryan King
2010-04-07 3:29 ` Robert LeBlanc [this message]
2010-04-07 13:08 ` Ryan Whelan
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=s2xc5b98f841004062029oda188282r6f65c3559d1b5d8a@mail.gmail.com \
--to=robert@leblancnet.us \
--cc=bridge@lists.linux-foundation.org \
--cc=ryank@globaldial.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).