I'd compare the MVS LPARs "PROFILE.TCPIP"s to each other and see where they are different for starters. The fact that it worked several days ago may indicate that mvs configuration files may have changed - unless you were playing with the vm and linux config files in your quest for success. Sounds like a mask may be incorrectly coded somewhere. David ________________________________
From: Linux on 390 Port on behalf of Nix, Robert P. Sent: Thu 2/10/2005 5:10 PM To: [email protected] Subject: Hipersockets routing headaches I'm trying to set up a hipersockets link between our zOS LPARs and a linux image. The hipersockets devices are defined as 7a00-7a0f, on CHPid FA. zOS development is supposed to be using IP address 192.168.29.25, zOS techsupt is supposed to be using 192.168.29.30. The linux image is using 192.168.29.80. zVM is using 192.168.29.89. The two zOS images can ping each other. Traceroute shows a direct connection. Pinging to the linux image from a zOS LPAR times out, as does pinging to the zVM TCPIP stack. Now it gets fun. On the Linux image, ping works to zVM. Traceroute shows a direct connection. Pinging the zOS LPARS times out. Traceroute to one of the two zOS LPARS shows lines like "1 * * *", indicating a timeout. Traceroute to the other zOS gives the following line: 1 tux23.mayo.edu (192.168.29.80)(H!) 0.000 ms (H!) 0.000ms (H!) 0.000 ms A ping to the second zOS says that the "Destination Host Unreachable", and the H! seems to mean host unreachable also. The route command output shows: 192.168.29.0 * 255.255.255.0 U 0 0 0 hsi1 And this is what I expected. Why would a ping to 192.168.29.25 time out, but a ping to 192.168.29.30 yield host unreachable? Other than the zOS routing, which is supposed to be dynamic, I've been able to verify everything against the zSeries HiperSockets Redbook. The copy I have is from May 2002. We've been really close quite a few times. It actually worked (for a day or so) and we were able to run tests with DB2 Connect and DB2. Two days ago, the DB2 port was giving connection refused, but I could start telnet and get into the zOS box. Today, I can't even ping it. Everything works, zOS to zOS. Everything works Linux to zVM. Nothing works from Linux or zVM to zOS. Any ideas of what to try now would be really appreciated. We're out our wit's end. -- Robert P. Nix 507-284-0844 Mayo Foundation RO-CE-8-857 200 First St. SW Rochester, MN 55905 ---- "In theory, theory and practice are the same, but in practice theory and practice are different." <<Nix, Robert P..vcf>> ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
