On Mon, 13 Apr 2009 18:51:22 -0500, Rich Smrcina rsmrc...@wi.rr.com
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
On Monday, 04/13/2009 at 07:51 EDT, Rich Smrcina rsmrc...@wi.rr.com
wrote:
Absolutely. It can be a way to provide redundancy for the TCP/IP stack
using
multiple OSA ports.
You need z/VM V5.4 if you want to use layer 2 VSWITCH.
Alan Altmark
z/VM Development
IBM Endicott
On Tuesday, 04/14/2009 at 12:41 EDT, Hans Rempel h...@hmrconsultants.com
wrote:
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
On Tue, 14 Apr 2009 13:21:55 -0400, Alan Altmark alan_altm...@us.ibm.com
wrote:
On Tuesday, 04/14/2009 at 12:41 EDT, Hans Rempel h...@hmrconsultants.co
m
wrote:
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
Since I'm working remotely now (Cornell is in the frozen north and I'm
working from balmy Plano, TX), I put a 2nd stack on both of our systems
so that I could bounce the primary stack and still have connectivity
thru the other one.
Jim
Alan Altmark wrote:
On Tuesday, 04/14/2009 at 12:41
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?
Lim Ming Liang 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.
--
Rich Smrcina