No, you aren't missing anything.  I was mistaken about the two OSA's in
the same vswitch.   I have two osas and two vswitches, and the two osas
are on different networks, hence the need for ospfd and such.   

My original goal was to use the single vswitch with a failover osa, but
as I pursued this problem I discovered from the network group that it
wasn't configured the way I had originally thought.

Tim 

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
David Kreuter
Sent: Thursday, March 08, 2007 5:27 PM
To: [email protected]
Subject: Re: Help with Virtual IP's.

good news. But I have a question for you: if you are using two OSA cards
in the same vswitch, they are on the same network.  Do the osa cards
plug into the same physical switch or bridged switches?  Unless you are
planning a second vswitch on a different network, I'm not sure what the
vipa is gaining. Of course I could be missing something - David

-----Original Message-----
From: Linux on 390 Port on behalf of Moeur Tim C
Sent: Thu 3/8/2007 4:48 PM
To: [email protected]
Subject: Re: Help with Virtual IP's.
 
To anyone in the midst of composing a reply, thank you, but I've figured
out the solution.   To those following this thread the solution lies in
a command:

        qethconf vipa add vipaaddress device

I ran the command and now my vipa address is pingable every where.

Tim





        I'm setting up VIPA's, zebra, quagga, and ospfd under my Redhat
AS 4 zLinux running under VM 5.2   It nearly works, but not quite and
I'm hoping to get some insight from this list group.

        I have an environment with two OSA's into a single Vswitch.   On
the zlinux machine I have two devices:

        eth0            10.1.100.17
        Dummy0  10.0.17.10      

        Both devices start and can be pinged from within the zlinux
machine.  Pings from the zlinux machine to anything on my network all
work.

         -- But -- 
        10.1.100.17 is pingable from outside the zlinux machine but on
my network (i.e, my desktop)
        10.0.17.10 is not pingable from outside the zlinux machine.

         -- Except --

        10.0.17.10 is pingable from a sister zLinux machine (a guest of
the same VM).  Both use the same vswitch.

        I've talked to my network guys and they report that the ospfd
daemon is working properly.  They see it as a neighbor router and more
so they see a learned route table entry of:

        10.0.17.0/24  10.1.100.17

        It appears that my pings for 10.0.17.10 are indeed being
properly routed to the real address of 10.1.100.17, but after that I
can't tell what becomes of them.  Thanks in advance 

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

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