> What is best network design > for a z800 with two OSAx cards.
Ooh, that's a *very* big question. It depends a lot on what you're trying to do and how. Below is one way to do it, but there are dozens of others. Contact me offline if you'd like to discuss it in detail. > This system will have: > > 1 OS/390 2.9 prod lpar > 1 z/OS 1.3 test lpar > 1 z/VM 4.3 lpar with 30-50 guest Linux images. > 1 z/VM TCPIP lpar????? I would suggest creating two real hipersocket LANs in the box and creating two small LPARs containing only a stripped-down Linux system each for use as routers. Attach one real OSA to each Linux LPAR and create a second interface on each Linux system and attach it to one of the two real hipersocket LANs. Also define a real CTC between the two Linux LPARs. This effectively gives you a DMZ LAN as a distribution point for your other LPARs, and allows you to work with the other setups as they need updating. The Linux guests should have 'zebra' installed for dynamic routing protocol support and also the advanced IP routing RPM loaded to let you do some network based load-balancing. You may also want to configure ipchains/iptables for additional traffic shaping and packet management. For each of the other systems that understand hipersockets (the z/OS 1.3, z/VM 4.3, and the z/VM TCPIP LPAR), define a hipersocket chpid for each LPAR on both of the real HS LANs and use the real HS interface of the Linux guests as their default route. Since OS/390 2.9 doesn't grok HS, use a CTC connection to the z/VM 4.3 LPAR to connect it, with a backup CTC to the z/VM TCPIP LPAR to ensure that your production systems have some path redundancy. Enable dynamic routing support on all the systems (at least in listen mode). This should get you good performance and some additional RAS if you set up the routing properly. > Should the two OSAx cards be placed on different network > segments for any > reason? Yes. Physical path redundancy, and also to simplify routing convergence. > I'm confused on the use of hipersockets, guest lans, iucv, > the z/VM tcpip > "hub" etc. > Are there any good presentations that will help me????? Ignore the issues of HS, gLANs, etc. This is purely the same problem as designing this with discrete routers and switches. The only dependency on HS or gLANs is whether the end server OS supports access to the HS/gLAN or not. > If anyone wants to give me a basic starter design, > "that would be great" (from OfficeSpace :) See above. The attached PDF is a simplified illustration of what this might look like - apologies to those of you who don't handle attachments well, but it's hard to illustrate this in text mode.
Visio-TW Cable Notional.pdf
Description: Adobe PDF document
