On Thursday, 01/12/2006 at 02:56 CET, Pohlen Mailinglist <[EMAIL PROTECTED]> wrote: > For the traffic from zLinux to the LAN you should config the vswitch by > sharing your OSA between zOS-LPAR and zVM-LPAR or dedicating a separate OSA > to zVM. I would never send all the traffic from the LAN via zVM to zOS > because firstly it is slower and secondly if zVM fails or you have to > shutdown zVM for whatever reason you cannot reach your zOS. > > In short > > 1. remain the zOS OSA as it is for access from the LAN > 2. remain real hipersocket interface between zOS and zVM as it is for > communication between your zOS and the zLinux guests e.g. DB2 access (If you > haven't the requirement yet, it may occur at a later time) > 3. define vswitch in zVM for direct LAN access from your zLinux guests
I agree with these recommendations, however I suggest that you do not share the OSA. The Linux guests are in a different subnet than z/OS and sharing the OSA will require the use of IEEE VLANs in the switch and reconfiguration of z/OS TCP/IP and the VSWITCH to use different VLAN IDs. Doable, but more complicated and it requires that you always keep the other system in mind when playing with the network connection. Using VLANs, a single VSWITCH can securely carry traffic for multiple subnets at once and is deserving of a dedicated OSA for that purpose. (Unless the z/OS system is used only to provide service to the Linux guests, in which case a network outage on one side is a de-facto outage on the other side.) Alan Altmark z/VM Development IBM Endicott
