How many systems do you need to connect? A few class Cs is a fair amount of address space (1 class C is 253 usable addresses), and you can easily optimize the use of addresses using NAT or a virtual router, etc. IPv6 is an interesting option, but keep in mind that there will need to be some kind of bridging between the IPv4 and IPv6 environments, which will require virtual router capabilities on both ends of the link. 6to4 code is in Linux, but it is very inefficient code, so it will hurt to run it for high performance networking, and most dedicated network hardware cannot perform this function.
If you can run an all-IPv6 subnet, that¹s interesting in itself, but be aware that many applications are not IPv6 tolerant (particularly on z/OS). There are good how-tos on how to set it up on Linux, but VM has almost no IPv6 capability in the supplied servers and clients so far (sorry, Miguel), so there¹s not a lot of exploitation in the VM TCP stack yet. On 1/14/09 11:55 AM, "Lionel B. Dyck" <lionel.b.d...@kp.org> wrote: > 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. > > I will go back and ask again. > > The suggestion on using IPV6 sounds interesting. Since the network would be > strictly within the CEC between z/vm, linux, and to/from z/os keeping it 'all > in the family' might be the way to go. Something to look at. Any advice? > > > Lionel B. Dyck, Consultant/Specialist >
