On Tuesday, 12/14/2004 at 04:30 CST, "Nix, Robert P." <[EMAIL PROTECTED]> wrote:
> 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. This reads, to me, like I have to make a hop outside > to get between systems connected directly to the Hipersocket. What's the good > of that? And this doesn't seem to be exactly true, since I can talk between zVM > and zLinux, and that would seem to be two systems directly connected via the > same Hipersockets. They just mean that the HiperSockets themselves (the chpids) are not interconnected within the box; you must route between them. All subchannels defined in a particular HiperSocket chpid are interconnected. > There has to be something simple I'm missing. 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? Is there a definition I'm missing? Double check your IP addresses and subnet masks. The HiperSocket must be treated like a separate LAN segment with its own IP subnet and unique IP addresses. Packets may be making their way to z/OS, but the responses may not be making their way back. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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
