bridge.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: "Ryan King" <ryank@globaldial.com>
To: 'Robert LeBlanc' <robert@leblancnet.us>,
	Ryan Whelan <ryan.whelan@tbamerica.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Bridging vSwitches in VMwares ESXi
Date: Wed, 7 Apr 2010 11:21:07 +0800	[thread overview]
Message-ID: <000101cad601$5d42a300$17c7e900$@com> (raw)
In-Reply-To: <n2hc5b98f841004062001ie80b2130ma08829633315c3c@mail.gmail.com>

> -----Original Message-----
> From: bridge-bounces@lists.linux-foundation.org [mailto:bridge-
> bounces@lists.linux-foundation.org] On Behalf Of Robert LeBlanc
> Sent: Wednesday, 7 April 2010 11:02 AM
> To: Ryan Whelan
> Cc: bridge@lists.linux-foundation.org
> Subject: Re: [Bridge] Bridging vSwitches in VMwares ESXi
> 
> On Tue, Apr 6, 2010 at 8:41 PM, Ryan Whelan <ryan.whelan@tbamerica.com>
> wrote:
> > oh good- glad to find out im not crazy. we do have 2 pNICs in the
> external
> > facing vSwitch.  Even when setting them as active/passive, its still
> an
> > issue.
> >
> > so its a confirmed issue with vmware- do they have any intention on
> > correcting it? do we know?
> >
> 
> Yes as long as the pNIC is attached, even if in standby mode it causes
> a problem.
> 
> It is an issue, but they won't fix it for two reasons. 1. They will
> never create a bridge between two vSwitches/VLANs, and 2. a fix would
> introduce more overhead and reduce flexibility and since they adhere
> to #1, it doesn't make sense. The flexibility they lose is multiple
> pNICs to one or more switches without having to have any trunking
> protocols.
> 
> You can get around the problem by buying the Cisco Nexus virtual
> switch, it's a real layer 3 switch, but it's a pricy option.
> 
> If you want a bridge in a VM, then only pNIC per switch (no
> redundancy). The other option, try to make the bridge a router
> instead. For us we wanted a transparent firewall, so it was easy to
> change the configuration to proxyarp for a transparent router instead.
> 

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).

Ryan King




  reply	other threads:[~2010-04-07  3:21 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 [this message]
2010-04-07  3:29             ` Robert LeBlanc
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='000101cad601$5d42a300$17c7e900$@com' \
    --to=ryank@globaldial.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=robert@leblancnet.us \
    --cc=ryan.whelan@tbamerica.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).