As Dave mentioned it's always good to have a second TCPIP stack for testing and emergency access. The only thing I wanted to add was that all ports can have multiple devices defined - up to 256 I think. For example you define a vswitch on one port using device address 0,1,2 you can define a second vswitch using device addresses 3,4,5. A lot of flexibility here.
If you are using the port for load balancing you cannot share the port with other VSWITCHS so the extra devices do not help. Hans -----Original Message----- From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Dave Jones Sent: April 14, 2009 11:38 AM To: [email protected] Subject: Re: TCPIP couple with vswitch On Mon, 13 Apr 2009 18:51:22 -0500, Rich Smrcina <[email protected]> wrote: >> Does it work to couple the TCPIP, zVM tcpip userid, with a VSWITCH >> NIC and share the same segment of the rest of the zLinux guests? >Absolutely. It can be a way to provide redundancy for the TCP/IP stack >using multiple OSA ports And, if you have extra OSA adapters available, it is also a good idea to = connect one of them to the TCPIP stack directly. This will give you another path into your VM system if there is something wrong with the VSWITCH setup. Dave Jones V/Soft Software
