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
