|
In your diagram replace the (GUEST) with a second instance of (HOST) and
there you have it. So your first statement is correct, just put the two
virtual LAN adapters on the same VLAN. Do be sure to use the correct one
for each task of course because one of them is set for bridging when
configured via the HMC and the second is not. Get them reversed and nobody
on the inside talks to a anybody on the outside.
DrFranken
Sent from my iPad
On Aug 20, 2013, at 3:19 PM, Evan Harris <auctionitis@xxxxxxxxx> wrote:
so:
In this scenario, how are the two virtual LIND's connected ? I'm guessing
you connect them by putting the virtual adapters on the same VLAN.
I have found that it is enough to specify the VLAN on the virtual adapter
that forms the virtual part of the bridge on the host. Adding a virtual
adapter into the same VLAN on the guest completes the connection. Like
->
Network <--> Phy Adapter <- bridge ID -> Virt Adapter (HOST) <- VLAN ID
Virt Adapter (GUEST)wrote:
On Wed, Aug 21, 2013 at 6:48 AM, DrFranken <midrange@xxxxxxxxxxxx>
the
So would that be a total of 3 lines on the first lpar? #1-physicalnetwork bridged to #2-virtual LIND, and #3-virtual LIND with LPAR#1's
intended IP address.
Yes! The first two lines pair up and create the Bridge while the third
line is the line used for IP on the host partition.
Advanced option is to create an EtherChannel to the switch using two
physical Ethernet ports and cables. This gives some redundancy and
additional bandwidth as well. For best redundancy you'd want these to be
different physical Ethernet adapters as well.
- Larry "DrFranken" Bolhuis
www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com
On 8/20/2013 2:39 PM, Mitchell, Dana wrote:
Thanks Doc!that bridge to the desired internal VLAN. Then you can put a virtual
<Quote>
You can use just one physical line on the IBM i Host partition and have
adapter on the host partition to that VLAN as well. The IP traffic for
gothost then goes to the internal VLAN and then back out across the bridge.
follow IBMs recommendations.
The bridge itself appears to use virtually no CPU at all as long as you
</Quote>network bridged to #2-virtual LIND, and #3-virtual LIND with LPAR#1's
So would that be a total of 3 lines on the first lpar? #1-physical
intended IP address.
warning of what *not* to do....
This would be a good tidbit to include in the article along with IBM's
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DrFranken
Dana
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
Sent: Tuesday, August 20, 2013 12:23 PM
To: Midrange Systems Technical Discussion
Subject: Re: Ethernet Bridging
First discontinuing the HEA was essentially unintentional. When they
theto the point where it was no longer supported they couldn't put it back.
Besides the HEA had other weird limitations of it's own. Future stuffmay fill that gap but it's done now so.....
works with 2 as well (or actually even 1!) And with the right magic
As to bridging it works great and it's not just for 3 or more LPARs, it
incantations the bridge with allow IBM i to use 802.1Q VLANs too!
and will burn CPU especially should you attempt any comm trace. At least
As you read, DO NOT put an IP address on the bridge itself. This is bad
IBM lets you, put an address on a bridge in Cisco gear and you shut down
the bridge!
learn who's on the inside and who's on the outside so it can bridge all
Remember it's the bridge operating in promiscuous mode so that it can
'interesting' packets and ignore the others that causes the issue here.
Because the adapter is seeing every packet if there is an IP addressthere then IP gets the packets too and that's a lot of extra work.
that bridge to the desired internal VLAN. Then you can put a virtual
You can use just one physical line on the IBM i Host partition and have
adapter on the host partition to that VLAN as well. The IP traffic for
listhost then goes to the internal VLAN and then back out across the bridge.
follow IBMs recommendations.
The bridge itself appears to use virtually no CPU at all as long as you
--
- Larry "DrFranken" Bolhuis
www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
listTo post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
Regards
Evan Harris
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.