Configuring Resource Monitoring - Novell SUSE LINUX ENTERPRISE SERVER 10 SP2 HEARTBEAT Manual

Value is 0:
This is the default. The resource will be placed optimally in the system. This may
mean that it is moved when a "better" or less loaded node becomes available. This
option is almost equivalent to automatic failback, except that the resource may be
moved to a node that is not the one it was previously active on.
Value is greater than 0:
The resource will prefer to remain in its current location, but may be moved if a
more suitable node is available. Higher values indicate a stronger preference for a
resource to stay where it is.
Value is less than 0:
The resource prefers to move away from its current location. Higher absolute values
indicate a stronger preference for a resource to be moved.
Value is 100,000:
The resource will always remain in its current location unless forced off because
the node is no longer eligible to run the resource (node shutdown, node standby,
or configuration change). This option is almost equivalent to completely disabling
automatic failback, except that the resource may be moved to other nodes than the
one it was previously active on.
Value is -100,000:
The resource will always move away from its current location.
See also the crm_failcount command:

4.6 Configuring Resource Monitoring

Although Heartbeat can detect a node failure, it also has the ability to detect when an
individual resource on a node has failed. If you want Heartbeat to ensure that a resource
is running, you must configure resource monitoring for that resource. Resource moni-
toring consists of specifying a timeout and/or start delay value, and an interval. The
interval tells Heartbeat how often it should check the resource status.
To configure resource monitoring:
1 Start the HA Management Client and log in to the cluster as described in
tion 4.1, "Graphical HA Management Client"
crm_failcount(8) (page 81).
(page 29).
Configuring and Managing Cluster Resources
Sec-
35