From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <000001cad5e4$fcc81030$f6583090$@com> Date: Wed, 7 Apr 2010 09:08:56 -0400 Message-ID: From: Ryan Whelan Content-Type: multipart/alternative; boundary=001485e7c950c015840483a54314 Subject: Re: [Bridge] Bridging vSwitches in VMwares ESXi List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: bridge@lists.linux-foundation.org --001485e7c950c015840483a54314 Content-Type: text/plain; charset=ISO-8859-1 it seems the fix for this would be for vmware to do a better job 'fencing' the secondary pNIC when in an active/passive setup im really disappointed to find out this isn't an issue i can work around (without compromising redundancy, or replacing the vSwitch etc) On Tue, Apr 6, 2010 at 11:01 PM, Robert LeBlanc wrote: > On Tue, Apr 6, 2010 at 8:41 PM, Ryan Whelan > 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. > > Robert LeBlanc > Life Sciences & Undergraduate Education Computer Support > Brigham Young University > > > _____________________________________ > This e-mail and any attachments from Toyota Boshoku America > (TBA), TrimMasters Inc. (TMI), or other affiliated companies may > contain confidential and privileged information. > > If you are not the intended recipient, please notify the sender > immediately by return e-mail, delete this e-mail and destroy any > copies. > > Any dissemination or use of this information by a person other > than the intended recipient is unauthorized and may be illegal. > --001485e7c950c015840483a54314 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable it seems the fix for this would be for vmware to do a better job 'fenci= ng' the=A0secondary pNIC when in an active/passive setup

=
im really=A0disappointed=A0to find out this isn't an issue i can w= ork around (without compromising redundancy, or replacing the vSwitch etc)<= br>
On Tue, Apr 6, 2010 at 11:01 PM, Robert LeBl= anc <robert@le= blancnet.us> wrote:
On Tue, Apr 6, 2010 at 8:41 PM, Ryan Whelan <ryan.whelan@tbamerica.com> wro= te:
> oh good- glad to find out im not crazy. we do have 2 pNICs in the exte= rnal
> facing vSwitch.=A0 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 cause= s
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.

Robert LeBlanc
Life Sciences & Undergraduate Education Computer Support
Brigham Young University


_____________________________________
This e-mail and any attachments from Toyota Boshoku America
(TBA), TrimMasters Inc. (TMI), or other affiliated companies may
contain confidential and privileged information.

If you are not the intended recipient, please notify the sender
immediately by return e-mail, delete this e-mail and destroy any
copies.

Any dissemination or use of this information by a person other
than the intended recipient is unauthorized and may be illegal.

--001485e7c950c015840483a54314--