On Wednesday, 04/18/2007 at 03:19 ZE2, Shimon Lebowitz <[EMAIL PROTECTED]> wrote: > Our VM system is still connected to the LAN > via an ESCON attached 2216. > > +----+ > | | 10.0.0.6 > | VM |----[2216]--------(LAN....) > | | 10.1.5.1 10.0.x.x > +----+ > 10.1.5.2 > > VM - 10.1.5.2 > 2216 VM side - 10.1.5.1 > 2216 LAN side - 10.0.0.6 > LAN - 10.0.x.x > VM default gateway: > DEFAULTNET 10.1.5.1 T2216 1500 0
A picture! Yea!!! No subnet masks! Boooo! (Though I infer that 10.0.x.x means mask 255.255.0.0.) > I have an OSA and an IP address on the LAN > available to me, 10.0.0.7 . I would like to add > the DEVICE/LINK, HOME, and GATEWAY statements > to put VM directly on the LAN as 10.0.0.7, > but I do not want to cause any disruptions in > current service. > > If I use this GATEWAY statement: > 10 = OSA2LAN 1500 0.255.0.0 0 > I *think* this will use OSA2LAN for all traffic > going to 10.0.x.x , right? Yes. > Will this cause problems when incoming traffic > from that LAN arrived on the 10.1.5.2 network? You don't say what the 2216 subnet is, so I can't say. (Did I mention the lack of subnet masks?) If you just have a host route, then respones to traffic coming from the 2216 may go out through the OSA. Alan Altmark z/VM Development IBM Endicott
