On Tue, Dec 14, 2004 at 04:30:12PM -0600, Nix, Robert P. wrote: > ... wait a minute... It's all confusing.
> I've found the statement in the book that "Direct connectivity > between the four Hipersockets is not provided; however, connecting > them via routing of any TCP/IP stack that has a connection to the > specific Hipersockets devices is permitted." Huh? I thought the > whole point was to allow things to talk together and avoid an > outside hop. All they're saying there is that each hipersocket is a separate network segment. It's like having 4 different wires; things connected to the same wire can talk to each other, but not to the things on the other wires unless there is something connecting wire A to wire B, eg a virtual machine or external device acting as a router. > What do I need to do to talk to the > zOS machine in the other LPAR? Is there something that needs to be > done on / for the zOS TCP/IP stack? You need a network interface on both systems, and a connectivity path between the two. If you connect the network interface on VM or Linux to the same hipersocket to which the network intface on z/OS is connected, the two can talk directly. If they are on different hipersockets, then you need another TCP stack that connects the two hipersockets and acts as a router OR you need to exit the box to a dedicated router and back in. Bad ASCII pictorial: VM ------ hipersocket ------- z/OS for same hipersocket VM --hs1-- virtual machine router --hs2-- z/OS for diff hipersocket -- db ---------------------------------------------------------------------- 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
