Srinivasa R Chamarthy wrote:
Yu Safin wrote:
Is there a VIPA concept with Linux and, if so, how do I
set it up?
Yes there is. There are two parts to it. One is all packets leaving
your Linux must have the VIPA IP address as a source. The other is
that all packets going to your Linux must be sent to your VIPA.
When we implemented zVM, we eliminated this set up but used it for 2
years.
For the VIPA implementation we wrote a perl program to make sure
everything was done automatically during the INIT process.
I am sure we have it somewhere if it is needed.
--
Yours truly,
Yu
----------------------------------------------------------------------
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 VIPA setup you need to do the following:
Load the module dummy (# modprobe dummy)
then define a dummy0 interface with a IP address and netmask and bring
up the interface using ifconfig. After defining the interface add the
dummy ip address to the ethernet interface at
/sys/class/net/eth<n>/device/vipa/add4 or you can use qethconf to add
the dummy address to the ethernet interface. This should do.
An alternative approach to registering the VIPA (dummy) address with the
OSA via qethconf, is to use IP routing. quagga (http://www.quagga.net)
the derivative routing suite from zebra (http://www.zebra.org), can
provide such capability on Linux.
We have used quagga and the ospf daemon to provide routing of VIPA
addressses (in a different subnet to the OSA interfaces). The latest
versions of quagga also have David Stevens (IBM) additions to ip route
maps (set src) which can handle the source-vipa requirements.
Mark
----------------------------------------------------------------------
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
