Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Configuring Packages and Their Services
Creating a Disk Monitor Configuration
Chapter 6 209
is already running, cmresmond --restart should be run to apply this
new configuration. Use the following commands to complete the change
and active the new configuration:
# cmconfigres --delete
# cmconfigres --create
# cmresmond --restart
Configuring Disks on a Single Node for Monitoring
An alternate method for configuring monitoring is to use the sync option
to configure monitor requests for a single node. To avoid unexpected
results, this method should be used when a disk is added to a package or
when a new package is added that will have disk monitoring. It is not
necessary to halt the cluster or other monitored packages that are not
being changed. You may wish to configure the monitoring first on a node
that is not currently running the package, then test the configuration by
failing the package over to the node you have configured. If the
configuration is successful, the package will start with monitoring active,
after which you can do the configuration on the other nodes that can run
the package.
NOTE Using the sync option does not affect the monitoring configuration of any
package that is not being changed on the node.
The following is an example using the sync option to configure
monitoring of the disks that might at some time be activated on the
current node:
# cmconfigres sync
# cmresmond --reload
This will create or modify the $SGCONF/cmresmond_config.xml file and
ensure that the cmresmond reload uses the new configuration file on
the current node only. It is important that the commands be repeated on
all nodes where the new or changed package might run. (If NODE_NAME *
is specified in the package ASCII file, this means all nodes.)