Installation guide
7. Select a recovery policy to specify how the resource manager should recover from a service
failure. At the upper right of the Service Management dialog box, there are three Recovery
Policy options available:
Restart — Restart the service in the node the service is currently located. T he default setting
is Restart. If the service cannot be restarted in the the current node, the service is relocated.
Relocate — Relocate the service before restarting. Do not restart the node where the service
is currently located.
Disable — Do not restart the service at all.
8. Click the Add a Shared Resource to this service button and choose the a resource
listed that you have configured in Section 5.7, “Adding Cluster Resources”.
Note
If you are adding a Samba-service resource, connect a Samba-service resource directly to
the service, not to a resource within a service. T hat is, at the Service Managem ent
dialog box, use either Create a new resource for this service or Add a
Shared Resource to this service; do not use Attach a new Private
Resource to the Selection or Attach a Shared Resource to the
selection.
9. If needed, you may also create a private resource that you can create that becomes a subordinate
resource by clicking on the Attach a new Private Resource to the Selection button.
The process is the same as creating a shared resource described in Section 5.7, “Adding Cluster
Resources”. The private resource will appear as a child to the shared resource to which you
associated with the shared resource. Click the triangle icon next to the shared resource to display
any private resources associated.
10. When finished, click OK.
11. Choose File => Save to save the changes to the cluster configuration.
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. T he 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.9. Propagating The Configuration File: New Cluster
Chapter 5. Configuring Red Hat Cluster With system-config-cluster
73