Title: Message
I'm not a guru by any means. I have done something like this in the past. The simpliest, easiest way, for me, was to simply EMIF the OSA and connect everybody to it. I.e. no hipersockets, no z/VM GUEST LAN. This way, each system had a single IP address for everybody. They way that your system is shown would require that z/OS route the packets to/from both the Linux and z/VM TCPIP stacks. What we did was given a subclassed class A subnet (equivalent to a class C subnet - 10.170.30.x to be exact) to the zSeries machine. This gave me more than enough IP addresses for everybody. It also made setting up our internal routers simpler. Before we had the OSA and were using a CISCO 7513, I did have the system set up as you said. The network people didn't really like it because they had to update their routers to make z/OS another intermediate router. It was extra work for them and they resented it.
 
I've heard of other people only allowing the z/VM and z/OS systems actually talking to the OSA with all guests under z/VM being part of a single GUEST LAN. This requires the z/VM TCPIP machine to route packets for the guests. Again, this seems complicated and generally unnecessary to me. I guess it could be useful if z/VM's TCPIP were to be set up as some sort of firewall. My personal feeling is that, for z/VM guests, I would use a GUEST LAN instead of hipersockets. Depending on the traffic, it might be well to use a hipersocket for "inter-zSeries resident systems" so that they don't use up any OSA resources. Remember that the OSA is a very smart box. If a packet is coming from an OSA user to another user on the same OSA, the packets do not "hit the wire" and are thus safe from snooping.
 
 

--
John McKown
Senior Systems Programmer
UICI Insurance Center
Information Technology

This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law.  If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited.
 

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Steve Gentry
Sent: Wednesday, October 12, 2005 2:57 PM
To: [email protected]
Subject: attn. Hipersocket/LPAR/IFL guru's


I know this probably isn't the list for this question but I figure it would get to the largest audience.  We are in the process of installing an IFL running VM 5.1 running Linux..
I've been a single LPAR kind of guy all of my life and am a newbie at setting up this type of configuration.  Below is a picture of what I want to do. 



Can I configure something like this or is there a better/different way to do this?  IP addresses have intentionally been left out at this point.
Thanks,
Steve

Reply via email to