I keep getting confused when we talk about addresses. There are two types of addresses in this discussion (ok, maybe more)...
1. The IP address of your node in the Guest LAN . 2. The CUA address that addresses your NIC. VSWCNTRL1 and VSWCNTRL2 only knows about the CUA address. If one goes down, the other picks up on a different CUA, which can be on the same card, like I have for testing, or a different card, which is the primary reason for doing this type of stuff. The IP addresses don't change. I don't see any need for the IP addresses to need to change or different routing or anything. But then, once I start using both OSA cards, and I do by test by unplugging a GBE cable, perhaps I will be in for a rude awakening. But in my case, there is one more item that may have made the difference, the networking people gave me a supernet and/or a vseg 3. Perhaps that changes the entire routing/new IP addresses discussion. Tom Duerbusch THD Consulting >>> [EMAIL PROTECTED] 11/02/05 11:13 AM >>> 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 ---------------------------------------------------------------------- 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
