Problem with Oracle 10g RAC VIP network setting at Solaris 9

Question

Dear All,
I have tried to set up a Oracle 10g RAC Release 2.
With OS solaris 9, and 2 nodes.
The nodes setting as the following:
nodes 1:
Public address: 172.16.0.121
Private address: 192.168.0.121, 192.168.1.121 (dual path for heart beat)
nodes 2:
Public address: 172.16.0.122
Private address: 192.168.0.122, 192.168.1.122
And i have assigned two IP adress 172.16.0.131, 172.16.0.132 as the VIP address for the
RAC.
And the following is the /etc/hosts file:
root@shk01 # cat /etc/hosts
# Internet host table
127.0.0.1 localhost
# public address
172.16.0.121 shk01 loghost
172.16.0.122 shk02
# heart beat
192.168.0.121 shk01-priv1
192.168.1.121 shk01-priv2
192.168.0.122 shk02-priv1
192.168.1.122 shk02-priv2
# VIP address
172.16.1.131 vip-shk01
172.16.1.132 vip-shk02
But when i run the command "$ ./runcluvfy.sh comp nodecon -n shk01,shk02 -verbose"
it shows the error:
ERROR:
Could not find a suitable set of interfaces for VIPs.
Result: Node connectivity check failed.
I did try to add the VIP address on bge0:1, as i using bge0 for the public address.
Both nodes i did using the same interface name for it.
Anyone have idea for me to check out the error?
Also, I have other question about the raw device.
As there is option for setting for ASM or raw device. If choosing raw device, does it mean that it just need to
format the storage disk but without newfs it? And then the Oracle program will able to handle it?
Thanks,
Xentar

Answer 1

You don't seem to state categorically that you are using Solaris Cluster, so I'll assume it since this is mainly a forum about Solaris Cluster (and IMHO, Solaris Cluster with Clusterware is better than Clusterware on its own).
Clusterware has to see the same device names from all cluster nodes. This is why Solaris Cluster (SC) is a positive benefit over Clusterware because SC provides an automatically managed, consistent name space. Clusterware on its own forces you to manage either the symbolic links (or worse mknods) to create a consistent namespace!
So, given the SC consistent namespace you simple add the raw devices into the ASM configuration, i.e. /dev/did/rdsk/dXsY. If you are using Solaris Volume Manager, you would use /dev/md/<setname>/rdsk/dXXX and if you were using CVM/VxVM you would use /dev/vx/rdsk/<dg_name>/<dev_name>.
Of course, if you genuinely are using Clusterware on its own, then you have somewhat of a management issue! ... time to think about installing SC?
Tim
---