« crsctl start crs does not work in 10gR2 | Main | 10gR2 CRS case study: CRS would not start after reboot - stuck at /etc/init.d/init.cssd startcheck »

Considerations for virtual IP setup before doing the 10gR2 CRS install

Preface


Many a times, simple things can bite you when you are planning something really important, like a jumping the gun for virtual IP installing 10gR2 CRS.

The CRS installation assumes that the virtual IP hostname and IP information should be either in the DNS or in local /etc/hosts file ONLY.  It does not assume that the virtual IP is already tied up to a network interface on the RAC nodes.

A cryptic error...

If the virtual IP is already attached to network interface during the CRS install, it throws a cryptc error, saying " the virtual interface seems to be already assigned to another system in the network ", which can be pretty misleading. We faced this situation recently during one of our upgrades:

10gRAC error1.jpg: ,

The problem...

The problem was that the racprod1-vip virtual hostname was already associated with a network interface alias lan1:801:

10gRAC error2.jpg:

Please note: The hostnames, domain and IPs mentioned in this diagram are completely fictional and have been fudged from their original values. The current representation is enough for the sake of illustration.

The solution...

Needless to say, the solution was to dis-associate the racprod1-vip with lan1:801, after which the 10gR2 CRS installation proceeded fine.

Conclusion..

Many people do not appreciate the fineties involved in CRS installation, especially around virtual IP. The actual association of virtual IP hostname and network interface is done by the $ORA_CRS_HOME/bin/vipca script, which is automatically run as part of $ORA_CRS_HOME/root.sh

TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/2110

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on May 1, 2008 5:52 PM.

The previous post in this blog was crsctl start crs does not work in 10gR2.

The next post in this blog is 10gR2 CRS case study: CRS would not start after reboot - stuck at /etc/init.d/init.cssd startcheck.

Many more can be found on the main index page or by looking through the archives.

Top Tags

Creative Commons License
This weblog is licensed under a Creative Commons License.
Powered by
Movable Type and Oracle