Propagating The Configuration File: New Cluster; Starting The Cluster Software - Red Hat CLUSTER SUITE - CONFIGURING AND MANAGING A CLUSTER 2006 Manual

Chapter 3. Installing and Configuring Red Hat Cluster Suite Software
Note
To verify the existence of the IP service resource used in a cluster service, you must use
the
/sbin/ip addr list
/sbin/ip addr list
1: lo: LOOPBACK,UP
¦
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: BROADCAST,MULTICAST,UP
¦
link/ether 00:05:5d:9a:d8:91 brd ff:ff:ff:ff:ff:ff
inet 10.11.4.31/22 brd 10.11.7.255 scope global eth0
inet6 fe80::205:5dff:fe9a:d891/64 scope link
inet 10.11.4.240/22 scope global secondary eth0
valid_lft forever preferred_lft forever
3.11. Propagating The Configuration File: New Cluster
For newly defined clusters, you must propagate the configuration file to the cluster nodes
as follows:
1. Log in to the node where you created the configuration file.
2. Using the
scp
in the cluster.
Note
Propagating the cluster configuration file this way is necessary for the first time a
cluster is created. Once a cluster is installed and running, the cluster configuration
file is propagated using the Red Hat cluster management GUI Send to Cluster but-
ton. For more information about propagating the cluster configuration using the GUI
Send to Cluster button, refer to Section 4.4 Modifying the Cluster Configuration.

3.12. Starting the Cluster Software

After you have propagated the cluster configuration to the cluster nodes you can either
reboot each node or start the cluster software on each cluster node by running the following
commands at each node in this order:
command on a cluster node. The following output shows the
command executed on a node running a cluster service:
mtu 16436 qdisc noqueue
§
§
command, copy the
mtu 1356 qdisc pfifo_fast qlen 1000
/etc/cluster/cluster.conf
65
file to all nodes