If the VSwitch will be on the same subnet as the current configuration,
you should not have to change anything, except the VM directory entry
(and maybe device numbers, if they will change).
That also assumes that you're using OSA Express connections now.
Tom Duerbusch wrote:
I have vswitch setup on the IFL with Linux images and the TCP/IP stack
connected to it. All seems to work well.
OSA
OSA
|
|
Vswctrl1
Vswctrl2
|
|
__________________________|________________|_______________________________________
| | |
|
Linux22 Linux40 Linux41 TCP/IP
Now I'm planning for the 390 side. It currently looks like:
OSA
|
TCP/IP
|
___________________________________________________________________________
| | |
| |
VSE1 VSE2 VSE3
VSE4 CMS
My first cut would be to bring up VSWITCH and connect TCP/IP to the
VSWITCH LAN. And then stop right there. My older VSE systems can't
connect to a Guest LAN. The VSE/ESA 2.7 systems can. So I will migrate
them from connection to TCP/IP to the Guest LAN at a later date.
But the question is...
When I move the entire IP network from the TCP/IP stack and the VSE
systems to run under a VSWITCH, will I have any routing problems that I
need to address? This is on a z/890 with z/VM 5.1.
Thanks
Tom Duerbusch
THD Consulting
--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service: 360-715-2467
rich.smrcina at vmassist.com
Catch the WAVV! http://www.wavv.org
WAVV 2007 - Green Bay, WI - May 18-22, 2007
