HP-UX HB v13.00 Ch-15 - Serviceguard

HP-UX Handbook – Rev 13.00 Page 45 (of 108)
Chapter 15 Serviceguard
October 29, 2013
root@Node1:/ # cmhaltpkg sw-pkg
2. If it is not already available, you can obtain a copy of the package's ASCII configuration
file by using the cmgetconf command, specifying the package name.
root@Node1:/ # cmgetconf -p sw-pkg sw-pkg.ascii
3. Edit the ASCII package configuration file.
4. Verify your changes as follows:
root@Node1:/ # cmcheckconf -v -P sw-pkg.ascii
5. Distribute your changes to all nodes:
root@Node1:/ # cmapplyconf -v -P sw-pkg.ascii
6. Copy the package control script to all nodes that can run the package.
Reconfiguring a Package on a Halted Cluster
You can also make permanent changes in package configuration while the cluster is not running.
Use the same steps as mentioned above.
Adding a Package on a Running Cluster
You can create a new package and add it to the cluster configuration while the cluster is up and
while other packages are running. The number of packages you can add is subject to the value of
Maximum Configured Packages in the cluster configuration file. To create a package
configuration template see section “Create configuration templates” above.
For example, to use Serviceguard commands to verify the configuration of newly created pkg1
on a running cluster:
root@Node1:/ # cmcheckconf -P /etc/cmcluster/sw-pkg/sw-pkg.conf
Use a command such as the following to distribute the new package configuration to all nodes in
the cluster:
root@Node1:/ # cmapplyconf -P /etc/cmcluster/sw-pkg/sw-pkg.conf
Remember to copy the control script to the /etc/cmcluster/pkg1 directory on all nodes that can
run the package.
Deleting a Package on a Running Cluster
Serviceguard will not allow you to delete a package if any other package is dependent on it. To
check for dependencies, use the cmviewcl -v –l package command. System multi-node packages
cannot be deleted froma running cluster.