Thank you for the response, it is appreciated.
I wanted to do a personal follow-up to understand better since my knowledge
of networking is basic and to keep traffic off the freelist. We're running
RH 3.0 Update 4 so I'm asssuming this is possible. I was not sure if I
could bond two NICS with separate subnets together, but from your response
this is possible.
So if we configure the bonding module for the 118 and 119 subnets into one
single logical interface (e.g. bond0), from your response below we could
make the Virtual IP to use different subnet (e.g. 120) address. This also
implies that if I lose a NIC (e.g. NIC on the 118 subnet) or the entire 118
network, everything should still be working fine. Are these two assumptions
correct?
One other question, when reconfiguring the Virtual IPs, what is the best way
to change the virtual IPs since I already have them configured in the
system. I have two metalink docs 285046.1 and 283684.1 that I'm
referencing, but both docs seem to perform the task differently.
Thanks JPD
-----Original Message-----
From: K Gopalakrishnan [mailto:kaygopal@xxxxxxxxx]
Sent: Thursday, July 21, 2005 3:09 PM
To: jpdubovecky@xxxxxxxxxx; racdba@xxxxxxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Multiple Virtual IP Addresses in 10g RAC on Linux
Jeffrey:
You didn't mention the linux kernel version. NIC Bonding module is
available from 24.12 and higher versions. If you have already
installed bonding driver, you can configure the 118 and 119 subnets to
a single bondIP (120.x) and use the VIPCA to configure the Virtual IP.
In this case your eth0 and eth1 will be a new bonded interface and can
be used against interconnect failures.
On 7/21/05, Dubovecky, Jeffrey P <jpdubovecky@xxxxxxxxxx> wrote:
I'm looking for assistance in configuring multiple virtual IP addresses
for
my Linux Oracle 10g RAC environment. Currently I have a 2 node RAC
environment already setup with 10g running, however I would like to add
another virtual IP address in the event my one subnet goes down. My
current
network looks like the following:
Server 1
xxx.xxx.118.65 (Server 1) db1
xxx.xxx.118.68 (Virtual IP) db1-v
xxx.xxx.119.65 (Server 1) db1 -e2
xxx.xxx.119.68 (Proposed 2nd VIP, would like this to be db1-v2)
xxx.xxx.121.65 (Private interconnect)
Server 2
xxx.xxx.118.66 (Server 2) db2
xxx.xxx.118.69 (Virtual IP) db2-v
xxx.xxx.119.66 (Server 2) db2 -e2
xxx.xxx.119.66 (Proposed 2nd VIP, would like this to be db2-v2)
xxx.xxx.121.66 (Private interconnect)
The reason for the second Virtual IP is if my 118 subnet goes down, I can
still access the database via the 119 subnet.
When I run VIPCA, it shows my Virtual IP for the one subnet, however I can
not add the second Virtual IP addresses. I've been told that this may
work
using the Linux Kernel Bonding Module, but I cant confirm whether or not
Thanks for any assistance - JPD
Jeff Dubovecky
Consulting Engineer/DBA
Union Switch and Signal
Phone: (412) 688-2881
jpdubovecky@xxxxxxxxxx
--
//www.freelists.org/webpage/oracle-l
--
Best Regards,
K Gopalakrishnan
Co-Author: Oracle Wait Interface, Oracle Press 2004
http://www.amazon.com/exec/obidos/tg/detail/-/007222729X/
