So, what are the applications that had been talking to the server on the old address(es) supposed to do? Somehow magically know that they now have to start communicating with a new address? That's what VIPA buys you. You assign a virtual address, and the applications don't have to worry about stuff like this. If a path/interface fails, dynamic routing takes place to send the traffic to a different physical address, but the same Virtual IP Address.
Mark Post -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Tom Duerbusch Sent: Wednesday, November 02, 2005 10:53 AM To: [email protected] Subject: Re: Q.: VIPA implementation -snip- 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? ---------------------------------------------------------------------- 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
