Installation guide

1. At the detailed menu for the cluster (below the clu st ers menu), click Services. Clicking
Services causes the display of services in the center of the page and causes the display of
menu items for services configuration: Ad d a Service, Ad d a Virt u al Mach in e Service,
and Co n f ig u re a Service.
2. To configure any service other than a virtual machine service, Click Ad d a Service. Clicking
Ad d a Service causes the Add a Service page to be displayed.
3. On the Add a Service page, at the Service n ame text box, type the name of the service.
Note
Use a descriptive name that clearly distinguishes the service from other services in the
cluster.
4. Below the Service n ame text box, enter the following parameters for this service.
Au t o mat ically st art t h is service — When the checkbox is checked, the service is
started automatically when a cluster is started and running. If the checkbox is not checked,
the service must be started manually any time the cluster comes up from the stopped state.
En ab le NFS lo ck wo rkaro u n d s — Setting this option will release NFS locks on a file
system in a soft attempt to unmount a file system, which may be necessary if your
filesystem is exported via NFS and occasionally fails to unmount (either during shutdown
or service relocation). You can also enable NFS daemon and lock workarounds for
individual file system resources, which will result in a hard attempt to unmount a file
system, as described in the table of file system resource parameters, Table C.3, “ File
System” , and the table of GFS resource parameters, Table C.4, “GFS” .
Ru n exclu sive — If enabled, this service (resource group) can only be relocated to run
on another node exclusively; that is, to run on a node that has no other services running
on it. If no nodes are available for a service to run exclusively, the service is not restarted
after a failure. Additionally, other services do not automatically relocate to a node running
this service as Run exclusive. You can override this option by manual start or relocate
operations.
Failo ver D o main — List of cluster members to try in the event that a service fails. For
information on configuring a failover domain with Conga, refer to Section 3.7,
“ Configuring a Failover Domain” .
Reco very po licy Provides the following options:
Disab le — D isables the resource group if any component fails.
Relo cat e — Tries to restart service in another node; that is, it does not try to restart in the
current node.
Rest art — Tries to restart failed parts of this service locally (in the current node) before
trying to relocate (default) to service to another node.
Rest art - D isab le — (Red Hat Enterprise Linux release 5.6 and later) The service will be
restarted in place if it fails. However, if restarting the service fails the service will be
disabled instead of being moved to another host in the cluster.
In addition, you can specify the Maximum nu mber o f rest art f ailu res b ef o re
relo cat in g and the Len g t h o f t ime in seco n d s af t er wh ich t o f o rg et a rest art .
Red Hat Ent erprise Linux 5 Clust er Administ rat ion
4 8