Thanks all for the responses. As a starter I added the NICDEF in the zvm-L2 user id at first level. In the second level, I used ATTACHed the addresses for the linux guest I was experimenting with. With this set up I was able to get connectivity to the 2nd level linux guest.
My second level z/VM shuts down after a certain time. Is this because of class or some other missing parameter? The class is BEG. Thanks __________________________________________ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 David Boyes <[EMAIL PROTECTED]> Sent by: Linux on 390 Port <[email protected]> 05/09/2005 06:58 PM Please respond to Linux on 390 Port <[email protected]> To [email protected] cc Subject Re: How to share TCPIP and VSwitch from level 1 to level 2 Well, they're two separate systems (that's what virtualization buys you). If you want them to communicate, they need a TCP stack. You could define one VSWITCH 1st level and attach the NICs from the 2nd level system, but you still need a TCP stack for the NICs to talk to. Suggestion: Define the VSWITCH 1st level. On 1st level system, grant the level 2 userid access to the VSWITCH. 1st level: Create at least two NICs with the NICDEF statemetn in the directory entry for the level 2 userid and couple them to the VSWITCH either manually or in the PROFILE EXEC for the level 2 userid. 2nd level: Create a VSWITCH. Configure 2nd level TCPIP to control this vswitch using one of the NICs you defined in the directory entry 2nd level: configure TCPIP to use one of the NICs you defined int the 1st level directory entry. It will look like a real OSA to this stack. Assign it an address appropriate with the 1st level VSWITCH. 2nd level: treat it the same as your 1st level system and define stuff for guests, etc. If you think about the 2nd level VSWITCH as plugging in a small switch to your bigger network and using that for local traffic, you'll see how it works quickly. ---------------------------------------------------------------------- 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
