Matt,

Each card can handle up to 256? (I think) device numbers.  Define them, then
assign them to each Linux guest like this (assuming a device number range of
0F00-F0F):
Guest 1: 0F00,0F01,0F0A
Guest 2: 0F02,0F03,0F0B
Guest 3: 0F04,0F05,0F0C
Guest 4: 0F06,0F07,0F0D
Guest 5: 0F08,0F09,0F0E

Or something along those lines.  You need to do it this way to avoid
"wasting" device numbers, since the device address for each guest must start
on an even address boundary.  Now, the _virtual_ addresses that your guests
see can all be the same, for every guest.  Gives a certain uniformity to
system setup.  So each guest could have it's OSA addresses be
0F00,0F01,0F02.


Mark Post

-----Original Message-----
From: Matt Lashley/SCO [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 07, 2003 12:42 PM
To: [EMAIL PROTECTED]
Subject: OSA, VLAN and Linux guests


I'm studying the picture on page 161 of the OSA-Express Implementation
Guide
http://publib-b.boulder.ibm.com/Redbooks.nsf/9445fa5b416f6e32852569ae006bb65
f/78796993019dfafe85256c38006f1d4e?OpenDocument&Highlight=0,osa


Right now I have a two levels of routers/firewalls in out penguin farm.
One single "master" router on the top level and four second level
routers/firewalls for each of the guest lans.  The master level router has
the OSA dedicated to it via the VM user directory.  I want to get rid of
the master level router because it does burn quite a few cycles handling
all the traffic and with the coming virtual switches in VM 4.4 (yahoo!) I
think a redesign and a re-think of our external network interface is
needed.

So, page 161 shows a picture of four Linux machines connected to a single
OSA (port).  Since the OSA supports trunking and zLinux can handle it as
well, I want to set up VLANs - like in the picture.

How do I share the OSA between four (or more) Linux guest images?   Are we
talking IODF/IOCDS changes?  Creating more CHIPDs/devices to be deicated to
each Linux?  When I read the text, the implementation doesn't jump out at
me.

Thanks,

Matt Lashley
Idaho State Controller's Office

Reply via email to