THE WORLD DISCUSSES #PYTHIAN ON TWITTER. HAVE A QUESTION? USE OUR HASHTAG AND ASK AWAY.

Oracle 10g R2 RAC – vip on wrong interface

I was installing RAC, and during the clusterware install I picked up the wrong interfaces for public and private. I had 10.x.x.x for the public IP on eth0 and 192.x.x.x for the private IP (interconnect) on eth1. I also had 10.x.x.x for the VIP. During the install I choose eth1 to be the public interface. Right after the install I lost connection to the machine via the 10.x.x.x IP.

What had happened was I had a 10.x.x.x IP on both eth0 and eth1, which was messing up the routing.

The solution? Simply modify the VIP in the cluster configuration. There’s actually a metalink article about this. Here are the essential commands:

srvctl stop nodeapps -n NODE1
srvctl stop nodeapps -n NODE2
srvctl modify nodeapps -n NODE1 -A 10.5.5.101/255.255.255.0/eth0
srvctl modify nodeapps -n NODE2 -A 10.5.5.102/255.255.255.0/eth0
srvctl start nodeapps -n NODE1
srvctl start nodeapps -n NODE2

They worked just fine. So if you ever mess up the interfaces, this is how you fix it.

If you need to change the private interface, then you need to use oifcfg. To verify your current settings use:

oifcfg getif
eth0  10.5.5.0  global  public
eth1  192.168.0.0  global  cluster_interconnect

And use delif/addif to remove and re-create your private interface.

References:
Changing VIP
Changing interconnect

8 Responses

  1. Hi Christo,
    As far as I can recall I always had problem with VIP configuration in the end of CRS 10.2 installation on Linux. At first I thought it might be that I was running private interconnect on sub-NIC on top of pulic NIC but the same issue surfaced when I had separate NICs for private and public LANs. I didn’t go into indepth investigations and originally resolved it manually adding nodeapps interfaces but I found that it can be easilly fixed by running $ORA_CRS_HOME/bin/vipca.
    Regards,
    Alex

  2. Christo Kutrovsky says:

    The problem you are refering to is different. Note:316583.1 describes it. I hope that’s the one you are refering to. Extract:

    During CRS install while running root.sh, The following messages are displayed

    Oracle CRS stack installed and running under init(1M)
    Running vipca(silent) for configuring nodeapps
    The given interface(s), “eth0″ is not public. Public interfaces should be used to configure virtual IPs.

    Someone at Oracle decided that your public interfaces should be Internet routable IPs and your databases will not be running on internal networks only, thus this error message.

    The solution is to simply run vipca manually.

    The problem I am describing is when you have successfully configured the virtual IPs (either automatic or manual), but you later discover you had the wrong interfaces.

  3. Thanks for the Note number Christo. I’ve been following this note without knowing it. :) That explains it. And I have just checked – couldn’t use vipca again to _reconfigure_ nodeapps.

  4. jones says:

    I found another use for this command. I found a bug in Oracle that asks you to use this command if you encounter this error while starting vipca for the first time…

    The given interface(s), “eth0″ is not public. Public interfaces should be used to configure virtual IPs.

    When you get that error, Oracle says to use this command to manually add the VIP:

    srvctl add nodeapps -n NODE1 -o $ORACLE_HOME -A 10.200.20.60/255.255.255.0

    However, your post notes that you add the interface to the end. I could not get my vip’s started until I added the interface to the end…

    srvctl add nodeapps -n NODE1 -o $ORACLE_HOME -A 10.200.20.60/255.255.255.0/eth0

    After that, the vip’s came up like a charm…

  5. Arnold says:

    Thanks, it worked for me, too.
    I logged in as root,
    $export ORACLE_HOME=/home/oracle/app/oracle/product/10.1.0/db_1
    $cd $ORACLE_HOME
    $./srvctl add nodeapps -n aprac2 -o $ORACLE_HOME -A 192.168.18.0/255.255.255.0
    $./srvctl add nodeapps -n aprac1 -o $ORACLE_HOME -A 192.168.18.0/255.255.255.0
    and then user ‘retry’ in the install GUI, and all finished.

  6. Kevin says:

    Thank you very much. 2 years later and it is still helping.

  7. Manju says:

    It helped me too
    VIPCA was wrongly showing e1000g1 instead of e1000g0 while installing in vmware-solaris.
    Your note helped in simple steps.
    Thanks for the info

  8. onnee says:

    I am faceing problem on private,public and virtual names during ma installation of Rac 10g on window 2003 server. plz help

Leave a Reply

Start NowWith Pythian - database design, management and emergency handling capabilities...

Live Updates

pythian: RT @sheeri: #confoo talk "Bending Queries to your Will with EXPLAIN" slides http://bit.ly/explainslides & handout
more



Testimonials

  • Serge Racine

    DBA, Brookfield Energy

    We are very satisfied by the service given to us by Andre and Shakir in support of our recent data quality and reorganization initiative.... more