The good news: Our VM's gone VIPA. The bad news? I can't reach my Linux/390 system.
Our TCPIP file has the following: DEVICE VDEV1 VIRTUAL 0 LINK VLINK1 VIRTUAL 0 VDEV1 DEVICE CIP2 CLAW 7060 ROCVM LLCISCO NONE 20 20 4096 4096 LINK CHIP2 IP 0 CIP2 DEVICE CIP3 CLAW 7860 ROCVM MMCISCO NONE 20 20 4096 4096 LINK CHIP3 IP 0 CIP3 DEVICE LNX1 CTC 5500 LINK LINUX1 CTC 1 LNX1 HOME 192.168.36.1 VLINK1 192.168.30.6 CHIP2 192.168.31.6 CHIP3 192.168.37.3 LINUX1 GATEWAY 192.168.37 = LINUX1 4096 0.0.0.255 0 ; BSDROUTINGPARMS TRUE VLINK1 4096 1 255.255.255.0 0 CHIP2 4096 0 255.255.255.0 192.168.30.1 CHIP3 4096 0 255.255.255.0 192.168.31.1 ; LINUX1 4096 0 255.255.255.0 192.168.37.2 ENDBSDROUTINGPARMS We've tried this with and without the GATEWAY statement and BSDROUTE for LINUX1. W/o it, LINUX1 doesn't show up in NETSTAT GATE at all. With it, it shows up, and we can ping the Linux system from VM and VM from Linux. But Linux can't get to anything past VM and nothing outside of VM can get to Linux. Any ideas would be greatly appreciated. ---- Robert P. Nix internet: [EMAIL PROTECTED] Mayo Clinic phone: 507-284-0844 200 1st St. SW page: 507-255-3450 Rochester, MN 55905 ---- "In theory, theory and practice are the same, but in practice, theory and practice are different."
