Managing Serviceguard 11th Edition, Version A.11.16, Second Printing June 2004

Troubleshooting Your Cluster
Solving Problems
Chapter 8 345
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>
where <ip-address> is the address in the “Address” or the
“Address/Prefix column and <subnet> is the corresponding entry in
the “Network” column for IPv4, or the prefix (which can be derived
from the IPV6 address) for IPv6.
3. Ensure that package volume groups are deactivated. First unmount
any package logical volumes which are being used for filesystems.
This is determined by inspecting the output resulting from running
the command bdf -l. If any package logical volumes, as specified by
the LV[] array variables in the package control script, appear under
the “Filesystem” column, use umount to unmount them:
# fuser -ku <logical-volume>
# umount <logical-volume>
Next, deactivate the package volume groups. These are specified by
the VG[] array entries in the package control script.
# vgchange -a n <volume-group>
4. Finally, re-enable the package for switching.
# cmmodpkg -e <package-name>
If after cleaning up the node on which the timeout occurred it is
desirable to have that node as an alternate for running the package,
remember to re-enable the package to run on the node:
# cmmodpkg -e -n <node-name> <package-name>
The default Serviceguard control scripts are designed to take the
straightforward steps needed to get an application running or stopped. If
the package administrator specifies a time limit within which these steps
need to occur and that limit is subsequently exceeded for any reason,
Serviceguard takes the conservative approach that the control script
logic must either be hung or defective in some way. At that point the