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. The initial activity will be backups of the Linux guests using FDR/UpStream where the client resides in the Linux guest and the server runs on z/OS. Down the road we envision db2-connect and who knows what else that needs to communicate from Linux to z/OS. Lionel B. Dyck, Consultant/Specialist From: Ivica Brodaric <ivica.broda...@gmail.com> To: IBMVM@LISTSERV.UARK.EDU Date: 01/14/2009 10:00 AM Subject: Re: Private Subnet for Hipersocket connections Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> > All I know is that my network folks tell me they can't give me anything more > than a few class 'C' subnets and those require justification. Sounds like a standard, prudent, response from the Networking People - never give away too much of what you have too easily and never give an impression of having too much of something to give in the first place. :-) How many hipersockets do you have? You'll probably want one class C subnet per hipersocket, but depending on the number of hosts connected to the hipersocket, that might be a waste of addresses. Even if they give you only one class C subnet, you'll get 256 addresses which you can then divide into smaller subnets and use each of those for a particular hipersocket. Ivica Brodaric
