Group,
I would be careful using VIPA on the same subnet as the real interfaces. On
a class 'C' subnet we had Vipa as 10.0.2.191 and the real interfaces
as 10.0.2.192 and 10.02.193. It didn't work. Our contractor changed the
subnet mask on the VIPA address and it "worked". However we were left with
overlapping IP addreses on the two subnets.
Just an experience from the past, Dave H.
Alan Altmark <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port
<LINUX-390@VM.MARIST.EDU>
To
LINUX-390@VM.MARIST.EDU
cc
10/19/2006 10:59 PM
Subject
Re: Is
OSPF limited on zLinux?
Please respond to
Linux on 390 Port <LINUX-390@VM.MARIST.EDU>
On Friday, 10/20/2006 at 11:19ZE10, Vic Cross <[EMAIL PROTECTED]> wrote:
> What I hope you're *not* suggesting is that the z/OS VIPA is in the same
> subnet as the interfaces. While this will work, you are not really
> providing an opportunity for OSPF to provide you with redundant pathways
> to your VIPA [1].
VIPAs, whether on z/OS or z/VM, can be same-subnet or different-subnet.
Same-subnet VIPA is quite common and gives you the equivalent of
adapter-level IP takeover. Since it existed before the introduction of
equal-cost multipathing and IP takeover, it is somewhat entrenched in the
psyche.
So same-subnet VIPA *does* provide redundant pathways. What it *doesn't*
do is protect you from a subnet outage.
Alan Altmark
z/VM Development
IBM Endicott
----------------------------------------------------------------------
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
