Hi Buck

The quick guide I use:

1. Create Line on Hosting partition using Comms resource from physical
adapter; assign bridge ID to the line description
2. Create virtual eth adapter description in HMC on Host LPAR with allow
access to external network set to "true"
3. Create Line on Hosting partition using virtual eth resource created in
(2) and assign bridge ID from (1) to the line description;

4. Create virtual eth adapter description in HMC on Guest LPAR with allow
access to external network set to "false"
5. Create line on Guest partition with virtual eth resource created in (4)
6. Assign IP address to line created in 5

Because you only have the one guest I think you can mostly ignore the VLAN
ID - just check that both virtual ethernet adapters are on the same VLAN

Vary everything on.

Note that:
- IP Address is assigned on guest; no ip addresses on host as bridge
handles that
- bridge connects physical and virtual adapters on host

Hope this helps



On Wed, Aug 12, 2015 at 8:30 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 8/11/2015 4:15 PM, Kevin Bucknum wrote:
It's been 8 years since we set our up I believe. Don't remember the
details, but maybe something in here triggers something. It seems like
we have the same setup as you.

Thanks; looks very similar. I'll look closer tomorrow when I'm feeling
less frustrated with myself.

--
--buck

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

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].