Managing Serviceguard Fifteenth Edition, reprinted May 2008

Troubleshooting Your Cluster
Solving Problems
Chapter 8 431
• AUTO_RUN (automatic package switching) will be disabled.
• The current node will be disabled from running the package.
Following such a failure, since the control script is terminated, some of
the package's resources may be left activated. Specifically:
• Volume groups may be left active.
• File systems may still be mounted.
• IP addresses may still be installed.
• Services may still be running.
NOTE Any form of the mount command (for example, mount -o cluster,
dbed_chkptmount, or sfrac_chkptmount) other than cfsmount or
cfsumount in a HP Serviceguard Storage Management Suite
environment with CFS should be done with caution. These non-cfs
commands could cause conflicts with subsequent command operations on
the file system or Serviceguard packages. Use of these other forms of
mount will not create an appropriate multi-node package which means
that the cluster packages are not aware of the file system changes.
In this kind of situation, Serviceguard will not restart the package
without manual intervention. You must clean up manually before
restarting the package. Use the following steps as guidelines:
1. Perform application-specific cleanup. Any application-specific actions
the control script might have taken should be undone to ensure
successfully starting the package on an alternate node. This might
include such things as shutting down application processes,
removing lock files, and removing temporary files.
2. Ensure that package IP addresses are removed from the system.
This step is accomplished via the cmmodnet(1m) command. First
determine which package IP addresses are installed by inspecting
the output resulting from running the command netstat -in. If any
of the IP addresses specified in the package control script appear in
the netstat output under the “Address” column for IPv4 or the
“Address/Prefix” column for IPv6, use cmmodnet to remove them:
cmmodnet -r -i <ip-address> <subnet>