Hitting bugs while installing Oracle CRS 10g on Solaris

While installing CRS 10.2.0.2 on Solaris 10 ( and probably other operating systems ) installation process may fail, reporting you a problem with setting up VIP adresses.
Why? Let's take a look..

At the and of CRS installation, OUI will dictate you to run two shell scripts as privileged user. The second one ( root.sh ) calls vipca to make your public addres accessible for database/cluster clients. Before configuring it as an alias for primary interface, vipca checks propriety of all given parameters.
If you decided to configure VIP as set of non-routable IP addreses ( RFC1918 ) from :

10.0.0.0 - 10.255.255.255 (10/8 prefix)
172.16.0.0 - 172.31.255.255 (172.16/12 prefix)
192.168.0.0 - 192.168.255.255 (192.168/16 prefix)

subnets - vipca will fail. Why? Is it a bug or just fussing "feature"? I don't know.. but in 10.2.0.3 Oracle Corporation decided to modify vipca not to check propriety of VIP IPs.

So, how to deal it?
The simpliest way is to install 10.2.0.2 CRS without setting up VIP ( force OK in OUI ), patch CRS software to 10.2.0.3 and finally run vipca by your own.

$CRS_HOME/bin/vipca -silent -nodelist $CRS_NODELIST -nodevips $CRS_NODEVIPS

Unluckily, in CRS 10.2.0.3 for Solaris 64-bit there is a bug in ONS makeing your cluster unstable.
I recommend you to install 5749953 patch asap. You can download it from metalink and follow up README.txt instructions.