Re: VIOS and Shared Ethernet Adapter -- MIDRANGE-L

You can use trunking and VLAN with the SEA, it just needs a little more
tweaking at the parameter level, and you can still use a single PowerVM
switch. like i said, i would rather have the two physical ethernets bonded
as a channel and everything going redundantly thru them. Want more
redundancy? add a second VIOS and make that SEA a HA SEA, that means that
both VIOS handle the traffic for the SEA and if one goes down nothing is
lost....

On Fri, May 1, 2015 at 6:25 PM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:

So what is the best way to provide a 2nd NIC to a guest partition t hat
will be used on a completely different subnet? Say a 172.16.x.x vs a
10.10.x.x ? Will creating just another virtual adapter to get anohter CMNxx
at the guest work? How would you handle a switch that is VLAN'd need the
completely different subnets like above?

On Fri, May 1, 2015 at 12:08 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

With VIOS you can set it up just about any way you want. What was asked
about will work fine.

I could argue that the second SEA is not really needed except for

failover

if the card fails. (then again when was the last time you saw an

Ethernet

card just fail. Normally they give you fits first.)

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Kirk
Goins
Sent: Friday, May 01, 2015 11:18 AM
To: Midrange Systems Technical Discussion
Subject: Re: VIOS and Shared Ethernet Adapter

Forget IBMi on IBMi I meant to use it as ref and I know NOT to put an IP
on
the SEA just the guests.

Just to be clear on the setup plan
Dual Port GB NIC that VIOS owns
Port0 would have VIOS Address assigned
Port0 would also have a SEA that supports 1 or more IBM i guests
Port1 Would have another SEA that supports say another IBM i guest.

So based on your experience this will work fine.

Thanks

On Fri, May 1, 2015 at 7:21 AM, Mitchell, Dana <dmitche@xxxxxxxxxx>

wrote:

Kirk,

Yes we are doing exactly that with our VIOS lpars. We can access vios
via ip address on the same shared Ethernet as all the other guests on
the machine.

As far as doing it with i hosting i, it can be done, but don't put
the ip interface on the physical Ethernet, you need to put it on an
additional shared Ethernet line description. See a previous discussion

about it:

http://archive.midrange.com/midrange-l/201308/msg00691.html

Dana

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Kirk Goins
Sent: Thursday, April 30, 2015 7:30 PM
To: midrange-l@xxxxxxxxxxxx
Subject: VIOS and Shared Ethernet Adapter

With IBM i Hosting IBMi they say not to put an IP in the on the line
that is being used for the shared adapter on the host because of
performance reasons.

So Question Number 1 is. Is that true or VIOS. I am short ports and if
possible use the same port that my VIOS uses for it IP as Shared
Ethernet Adapter. I see in a doc that it warning if an IP on on that
device it won't be when done.

Question number 2 - Throwing Performance under the bus so to speak can
I get it to work long enough to test a theory?

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

Attention: This electronic document and associated attachments (if
any) may contain confidential information of the sender (SHAZAM
Network) and is intended solely for use by the addressee(s). Review by
unintended individuals is prohibited. If you are not the intended
recipient: (i) do not read, transmit, copy, disclose, store, or
utilize this communication in any manner; (ii) please reply to the
sender immediately, state that you received it in error and
permanently delete this message and any
attachment(s) from your computer and destroy the material in its
entirety if in hard copy format. If you are the intended recipient,
please use discretion in any email reply to ensure that you do not
send confidential information as we cannot secure it through this
medium. By responding to us through internet e-mail, you agree to hold
SHAZAM, Inc. and all affiliated companies harmless for any
unintentional dissemination of information contained in your message.

Thank you.

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

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

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

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