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 EDT, Hans Rempel <h...@hmrconsultants.com> wrote:As Dave mentioned it's always good to have a second TCPIP stack fortestingand emergency access. The only thing I wanted to add was that all portscanhave multiple devices defined - up to 256 I think. For example youdefine avswitch 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 portwithother VSWITCHS so the extra devices do not help.Consider also OSA-ICC as your other way in. Alan Altmark z/VM Development IBM Endicott -- Jim Bohnsack Cornell University (972) 596-6377 home/office (972) 342-5823 cell jab...@cornell.edu |
- TCPIP couple with vswitch Lim Ming Liang
- Re: TCPIP couple with vswitch Rich Smrcina
- Re: TCPIP couple with vswitch Dave Jones
- Re: TCPIP couple with vswitch Hans Rempel
- Re: TCPIP couple with vswitch Alan Altmark
- Re: TCPIP couple with vswitch Alan Altmark
- Re: TCPIP couple with vswitch Brian Nielsen
- Re: TCPIP couple with vswitch Jim Bohnsack