Yep, that is the hard way, now a days.

Vswitch is the way to go.  Much, much easier to setup and better performance 
along with automatic fall over, being VERY easy to setup.

No longer will you be using your TCPIP stack on VM for routing packets to guest 
OSs.  The VM stack will only be used for CMS client/servers.

Now, converting over, is a small pain.  Nothing is as easy as leaving 
everything alone <G>.

You will need another set of OSA addresses (I think your z/890 has a few to 
spare).

Vswitch is basically, DTCVSW1 and DTCVSW2 service machines (controllers for 
failover).

And something similar to the following in your system config file:

DEFINE VSWITCH VSW1 RDEV  2000 2003 PRIROUTER  
MODIFY VSWITCH VSW1 GRANT TCPIP                
MODIFY VSWITCH VSW1 GRANT LINUX24              
MODIFY VSWITCH VSW1 GRANT LINUX27              
MODIFY VSWITCH VSW1 GRANT DOSESA2              
MODIFY VSWITCH VSW1 GRANT Y2KESA2              
MODIFY VSWITCH VSW1 GRANT NEWESA4              
MODIFY VSWITCH VSW1 GRANT TSTESA4              
MODIFY VSWITCH VSW1 GRANT GEACESA4             
MODIFY VSWITCH VSW1 GRANT GEACESA5             
MODIFY VSWITCH VSW1 GRANT GEACESA6             
MODIFY VSWITCH VSW1 GRANT STLESA2              
MODIFY VSWITCH VSW1 GRANT STLESA2F             
MODIFY VSWITCH VSW1 GRANT TSTESA5              
MODIFY VSWITCH VSW1 GRANT TSTESA5F             
MODIFY VSWITCH VSW1 GRANT HIGHAVL              
MODIFY VSWITCH VSW1 GRANT TSTESA3              
VMLAN MACPREFIX 030001                         

(there are dynamic versions to these commands, so you don't have to cycle VM to 
bring it up)

The Linux machine has something similar to the following in its directory:

NICDEF 600 TYPE QDIO LAN SYSTEM VSW1     

And then in Linux, you configure an qeth type device.

You network does change.  You are no longer routing thru TCPIP.   Your default 
gateway may now be your router (xxx.xxx.xxx.001 address), instead of the IP 
address for TCPIP.  

It is easiest to create a new Linux image (if you are not an IP geek), to play 
and test with.  For me, it took a while for the change in routing, to really 
sink in my mind (or sink my mind).

Tom Duerbusch
THD Consulting

>>> Gene Walters <[EMAIL PROTECTED]> 5/8/2007 12:36 PM >>>
Hi All,

I know this is a broad question, but I am trying to understand some
things.

We currently are using CTC connections for our network access to our
Linux Instances running under VM.  We were told that CTC's were doing it
the hard way.  So I am trying to figure out what the other way is.

We have Z/VM 5.1 running on an IFL and an OSA-Express card.  What
should we be using instead of CTC's for network connection, VGuest,
VSwitch VLAN?  I'm confused as to what each actually does.

Any help would be appreciated.

Thanks
Gene

Gene Walters
System Programmer
WV Dept of Administration - OT
304-558-5914 ext 8902
Fax 304-558-1351

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to