As David Boyes said, it should be simple. And it is if all is setup right...
In a nutshell: - turn on IP forwarding in the router - add a route on z/OS to the guest LAN subnet via the router IP on the hipersocket - add a route on the Linux guests to the hipersocket subnet via the router IP on the guest LAN We had one subnet allotted to us for the hipersocket connections - 192.168.11.0. The normal subnet mask for that would be 255.255.255.0. But we really needed two networks - one using a hipersocket between z/OS and our Linux router, and a second network on a guest LAN connecting the Linux router to the Linux farm. So we logically split the 192.168.11.0 network into two - 192.168.11.0 and 192.168.11.128, both now using a subnet mask of 255.255.255.128 (or /25 if you use that notation). On z/OS: Home (for the hipersocket connection) 192.168.11.10 DEVICE IUTIQDE0 MPCIPA LINK HIPERLE0 IPAQIDIO IUTIQDE0 BEGINROUTES ;ROUTE Dest/Mask(#bits) Gateway Linkname MTU Pktsize ROUTE 10.0.0.0/8 = OSD1 MTU 1492 ROUTE 10.0.0.0/8 = OSD2 MTU 1492 ROUTE 192.168.11.0/25 = HIPERLE0 MTU 8192 ROUTE 192.168.11.128/25 192.168.11.2 HIPERLE0 MTU 8192 ROUTE DEFAULT 10.171.72.1 OSD1 MTU 1492 ENDROUTES On the Linux Router: eth0 - to the Vswitch for ssh access etc. eth1 (guest LAN) - 192.168.11.129 mask 255.255.255.128 hsi0 (hipersocket)- 192.168.11.2 mask 255.255.255.128 IP forwarding ON On the Linux Guests: eth0 - to the Vswitch for ssh access etc. eth1 (guest LAN) - 192.168.11.130 mask 255.255.255.128 add an extra route for 192.168.11.0 mask 255.255.255.128 gateway 192.168.11.129 Then it's just add Linux guests to the guest LAN and they all have z/OS access... Yes, the routing is a bit slower than a direct hipersocket connection, but it's lots faster than waiting for an IOCP change and POR... Our big killer that took forever to find was the z/OS routing. It was "supposed to be" right according to the z/OS guys. Once we got that fixed the rest flew... If that leaves more questions, drop me a note and I'll try to explain. Tim Hare wrote:
Lee - would you mind giving the list a (simplified) diagram of both sides, or copies of various settings in TCP/IP and/or z/OS (minus anything too uncomfortable for your organization to reveal of course)? might be instructive to others to see where things have to be set, where they have to match, etc. Tim Hare Senior Systems Programmer Florida Department of Transportation (850) 414-4209 ---------------------------------------------------------------------- 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
-- Lee Stewart, Senior SE Sirius Enterprise Systems Group Phone: (303) 798-2954 Fax: (720) 228-2321 [EMAIL PROTECTED] www.siriuscom.com ---------------------------------------------------------------------- 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
