On Monday, 11/14/2005 at 01:36 CST, Tom Duerbusch <[EMAIL PROTECTED]> wrote: > It seems to be a routing problem, but I don't understand why. > > If a LAN user can be routed as: > > LAN > TCPIP > NEWESA4 > TSTESA4 > > what difference is there when Vswitch in put in the mix as: > > LAN > Vswitch > TCPIP > NEWESA4 > TSTESA4 > > As NEWESA4 is directly connected to TCPIP, no one has problems > connecting to it. > > I would like to be able to understand just what "networking" changes > went into effect with the addition of vswitch. > > I can ping from TCPIP to all the machines, which means I have active > connections. It is only when I added vswitch to the mix, that machines > that were 2 hops over from TCPIP, had problems communicating. > > Thanks for any insight.
When you defined the VSWITCH, did you specify PRIROUTER? NEWESA4 is a routing guest. Ideally, you will move the routed guest LAN segment into a separate VLAN and stop using NEWESA4 as a router. Alan Altmark z/VM Development IBM Endicott
