Install guide

192.168.1.7 rac7-priv.example.com rac7-priv
192.168.1.8 rac8-priv.example.com rac8-priv
Tip
When doing initial testing, set the init level to 2 in the /etc/inittab file, to aid node testing. If
the configuration is broken and the node reboots back into init 3, the startup will hang, and this
impedes debugging. Open a window and tail the /var/log/messages file to track your
progress.
The qdiskd service is the first service to start and is responsible for parsing the cluster.conf file.
Any errors will appear in the /var/log/messages file and qdiskd will exit. If qdiskd starts up, then
cm an should be started next.
Assuming no glitches in configuration (consider yourself talented, if the node enters the cluster on first
attempt) we can now ensure that the qdisk and cman services will start on boot:
$ sudo chkconfig –level 3 qdiskd o n
$ sudo chkconfig –level 3 cman on
At this point, we should shut down all services on this node and repeat the steps in this chapter for our
second node. You can copy the m ultipath.conf and cluster.conf configuration files to the
second node to make things easier. Now the configuration process diverges to the point that further
configuration is very RAC/GFS or HA specific. For information on configuring a RAC/GFS cluster,
continue with Chapter 4, RAC/GFS Cluster Configuration. For information on configuring cold failover HA
cluster, continue with Chapter 5, Cold Failover Cluster Configuration.
Chapter 3. Software Installation and Configuration
29