On Wednesday, 01/14/2009 at 01:10 EST, "Lionel B. Dyck" <lionel.b.d...@kp.org> wrote: > What we are planning is a single hipersocket connection between z/vm and z/os > with each linux guest having two IP addresses. One IP address would be on the > public side and connected to one guest lan. The other IP address would be on a > second guest lan and would be routed to a linux guest that would own the
> hipersocket connection. Thus the 2nd IP address range would never leave the CEC > as it would only be used for communication between an address space on z/OS and > the Linux guest under z/VM across the hipersocket. > > Hopefully this helps to clarify what I'm trying to do. It doesn't matter why you need an address or where the traffic flows. A subnet is a subnet is a subnet, whether physical or virtual, and is part of your company network. Traffic flow may be restricted or routes not advertised, but it Exists. When I said that your subnets may be too large, it is Ivica's point that I am addressing (no pun intended). If all your networking folks deploy are /24 (255.255.255.0) subnets, then it's no wonder they claim to not have any subnets. A /24 subnet holds 254 hosts. Except for the 'people LANs', you rarely find that many hosts. A /28 (255.255.255.240) subnet mask would yield 16 subnets, each holding 14 hosts. A /29 subnet gives you 32 subnets with 6 hosts each. But if all your Networking People want to do is to give you a /24 network, that's their business. You're just the guy who implements the networks They architect, if you know what I mean. Alan Altmark z/VM Development IBM Endicott
