You get to use ipchains/iptables, port forwarding/load balancing software, etc., etc. I.e., you have a lot more choices and flexibility. It also minimizes the amount of workload that requires z/VM skills in favor of Linux skills. Both may be uncommon in your shop, but you're more likely to find Linux skills easily.
You should be able to get a 32MB virtual guest doing those chores. Don't use the SuSE "network" install, you don't want to be running all that software. Pick and choose your own software, or create your own profile if you think you'll be creating more than a few of these images. I believe zebra is commonly mentioned for Linux/390 dynamic routing. Mark Post -----Original Message----- From: Dave Myers [mailto:[EMAIL PROTECTED]] Sent: Monday, September 09, 2002 11:52 AM To: [EMAIL PROTECTED] Subject: Re: H50 sandbox - followup questions In a message dated 9/5/2002 10:23:12 PM Mountain Daylight Time, [EMAIL PROTECTED] writes: > > Given that scenario, what network setup would make more sense? > > If you have a bigger machine than a H50, use the Linux systems in > separate LPARs to isolate the router from the OSes it is routing. For > the H50 that you have, run VM in basic mode on the iron and dedicatete > the adapters to Linux guests running under that VM as routers, and run > everything else as VM guests. 1. What are the benefits of using Linux for these "gateways" instead of just using z/VM TCPIP itself? 2. How much memory resource will these Linux "gateways" require and should we use "stripped-down kernel" Linux images or just inactivate unnecessary services on these images (and use the SuSE 'network' install for example). 3. What linux routing software should we use on these "gateways" for dynamic routing?? Tia Dave Myers
