I haven't been following this thread, but when it came to VSWITCH.... My previous goal was to do VIPA. I wanted to be protected from a card/cable/switch failure.
Last month, I brought up VSWITCH in a second lpar. Kind of playing around, but I wanted to start using it for Linux images. Funny, when I cancelled "VSWCTRL1", then "VSWCTRL2" seemed to be active and had taken over communications. VSWCTRL2 was using a different set of addresses (which would have been on our second card, if I had defined it so). Seems to me that I got what I wanted without VIPA...can someone confirm that? So, that leads me to the question, what is, or why is VIPA available? Is it older technology, that got replaced by vswitch? Is it a LPAR type technology, for those that don't have VM? Is it for those that have VM and just don't know any better? (I'm in that boat more times that I would like<G>) Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 11/02/05 9:12 AM >>> On Nov 2, 2005, at 3:35 AM, Vic Cross wrote: > One thing I forgot to mention last time is for those who are running > Linux under z/VM 5.1, give more-than-serious thought to using VSWITCH > instead of Linux guests with multiple interfaces and VIPA. z/VM will > do the heavy-lifting as far as interface redundancy is concerned, and > you don't have the processor overhead of a bunch of Linux guests > chattering to each other and to the routers nor the storage overhead > of all those additional qeth devices. Oh, I'd say that chatter is still necessary. But what you do is define two different TCPIP VSWITCH controllers, on (by definition) different physical OSA ports, with different cables connecting them to the switch(es, ideally). Then configure two eth interfaces on each Linux guest, one coupled to each VSWITCH. Then run quagga to advertise a dummy interface spanning those two via OSPF. That way you can lose one OSA card, one VSWITCH controller, or one VSWITCH interface on any guest without any interruption of service. You can even pull the same trick with the VM TCPIP interface itself, by giving your TCPIP (not necessarily a VSWITCH controller) machine two virtual NICs, each coupled to a different VSWITCH. Adam ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
