Installation guide

Note

To verify the existence of the IP service resource used in a cluster service, you must use the

/sbin/ip addr list command on a cluster node. The following output shows the

/sbin/ip addr list command executed on a node running a cluster service:

1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue

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> mtu 1356 qdisc pfifo_fast qlen 1000

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

5.8.1. Relocat ing a Service in a Clust er

Service relocation functionality allows you to perform maintenance on a cluster member while

maintaining application and data availability.

To relocate a service, drag the service icon from the Services Tab onto the member icon in the

Members tab. The cluster manager stops the service on the member on which it was running and

restarts it on the new member.

5.9. Propagat ing T he Configurat ion File: New Clust er

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 command, copy the /etc/cluster/cluster.conf file to all nodes 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 button.

For more information about propagating the cluster configuration using the GUI Send

to Cluster button, refer to Section 6.3, “ Modifying the Cluster Configuration” .

5.10. St art ing t he Clust er Soft ware

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:

Red Hat Ent erprise Linux 5 Clust er Administ rat ion