Linux on 390 Port <[email protected]> wrote on 05/07/2008 11:50:04
AM:

> >>> On Wed, May 7, 2008 at  1:45 AM, in message
> <[EMAIL PROTECTED]
> at>, Fuhrmann
> Anna <[EMAIL PROTECTED]> wrote:
> > Dear list,
> >
> > (this question is for z-linux in an LPAR, RHEL4)
> >
> > We use two OSA cards to connect 3 LPARs with the outside world.
> > Hipersockets for inter-LPAR-
> > communication defined per static route.
> >
> > Now we want to use VIPA also for the zlinux LPARs. To define VIPA we
> > used the documentation provided in the IBM device driver manual and
got
> > stuck with the example route command there stating:
> >
> > route add -host [VIPA address] gw [gateway address]
> >
> > Question:
> > what should be inserted here as "gateway address" - should it be
> > 1. the IP address of the OSA card or
> > 2. possibly something else? und if yes, what?
>
> You should ask your IP networking folks what the IP address of the
> gateway for that VIPA is, and put that IP address into your command.
> Normally, a gateway is the first-hop router that packets need to go
> to in order to reach their intended destination.  A "default
> gateway" is the first-hop router that packets go to that don't have
> an explicit route defined for them in the TCP/IP stack.  Without
> knowing the details of your setup, you could be looking for either of
those.
>
We tried to do something with this with SLES 8 at the time.  I can't
remember exactly we did but I do rememeber we had to have a VIPA gateway.
 We had an address of 10.207.1.112 on one OSA and 10.207.3.112 on the
other OSA.  The VIPA was 10.207.5.112 with I believe a gateway of
10.207.5.1.   We no longer have that system setup so I can't doublecheck
it.

When we couldn't get autofailover to work like we wanted, we stopped
working on it.

----------------------------------------------------------------------
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

Reply via email to