Thanks to all that responded but I must confess that I am still somewhat
confused. I defined a dummy interface but can not get it to become active
because device dmy0 is an unknown interface. I am embarrassed to admit
this but I guess I need some hand holding. Here is what I have.
2 OSA/e Fast Ethernet shared between 3 lpars, one of the lpars is a Linux
native LPAR. I wish to configure a VIPA and have users connect to the VIPA
like the z/OS world.
I must define a dummy interface and assign it the VIPA address. I can
define one but cannot make it active.
I must start up zebra and ospfd. How do I advertise the VIPA route?
Can anyone provide some hand holding?
Peter
Vic Cross <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
02/29/2004 08:29 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Linux and OSA/e Ethernet Questions
Adam Thornton said:
> Run Zebra or Quagga with OSPF and configure a VIPA-advertised virtual
> address between your physical interfaces just like you do on z/OS.
Way back when we worked on "ISP/ASP Solutions", I described using the
dummy network device to create an interface that looks like a VIPA
interface. Unfortunately I don't think I went to the next step of
advertising that interface using a dynamic routing protocol -- this is
where Zebra/Quagga comes in as Adam suggests.
The other side of VIPA is the SOURCEVIPA function, where you make your
outgoing connections appear to come from the VIPA address. The src_vipa
wrapper, available for download from the Linux/390 DeveloperWorks site
(where the kernel patches come from), works nicely for this.
Cheers,
Vic Cross
PS: Thanks for the kind words, Alex!
