On Wednesday, 11/16/2005 at 08:40 CST, Tom Duerbusch <[EMAIL PROTECTED]> wrote: > PRIROUTER? Perhaps.. > > In the startup deck "zvmv5r10 tcpip", I have: > > 00068 DEVICE [EMAIL PROTECTED] OSD 2110 PRIROUTER > 00069 LINK QDIO1 QDIOETHERNET [EMAIL PROTECTED] MTU 1500 > > > Sure, the goal is to have all the VSE systems directly attached to the > VSwitch/Guest LAN...but baby steps.. Plus I might not be able to > directly attach VSE/ESA 2.3 to it. There were apars on 2.5, but I don't > think they went back to VSE 2.3.
When you issued DEFINE VSWITCH, the default setting of the VSWITCH is NONROUTER. That means the VSWITCH will only pull packets from the OSA that match the IP addresses of those guests who are directly using the VSWITCH. Guests that aren't on the VSWITCH will have their packets discarded by OSA. It is the same reason you specified PRIROUTER in PROFILE TCPIP. If any guest coupled to a VSWITCH is performing routing, you must define the VSWITCH with "PRIROUTER". So, once you move the guests off the the Guest LAN and directly onto a VSWITCH, you can remove PRIROUTER from the VSWITCH definition. Alan Altmark z/VM Development IBM Endicott
