The cluster must be running, and if the package is dependent on other packages, those packages must be either already running, or started by the same command that starts this package (see the section that follows, and “About Package Dependencies” (page 137).)

Starting a Package that Has Dependencies

Before starting a package, it is a good idea to use the cmviewcl command to check for package dependencies.

You cannot start a package unless all the packages that it depends on are running. If you try, you’ll see a Serviceguard message telling you why the operation failed, and the package will not start.

If this happens, you can repeat the run command, this time including the package(s) this package depends on; Serviceguard will start all the packages in the correct order.

Using Serviceguard Commands to Start a Package

Use the cmrunpkg command to run the package on a particular node, then use the cmmodpkg command to enable switching for the package. For example, to start a failover package:

cmrunpkg -n ftsys9 pkg1

cmmodpkg -e pkg1

This starts up the package on ftsys9, then enables package switching. This sequence is necessary when a package has previously been halted on some node, since halting the package disables switching.

Starting the Special-Purpose CVM and CFS Packages

Use CFS administration commands to start the special-purpose multi-node packages used with CFS. For example, to start the special-purpose multi-node package for the disk group package (SG-CFS-DG-id#), use the cfsdgadm command. To start the special-purpose multi-node package for the mount package (SG-CFS-MP-id#) use the cfsmntadm command. Check to see if your package has a dependency; before you can start your dependent package, you must start all the packages it depends on.

Halting a Package

You halt a Serviceguard package when you want to bring the package out of use but want the node to continue running in the cluster. You can halt a package using Serviceguard Manager or on the Serviceguard command line.

Halting a package has a different effect from halting the node. When you halt the node, its failover packages may switch to adoptive nodes (assuming that switching is enabled for them); when you halt a failover package, it is disabled from switching to another node, and must be restarted manually on another node or on the same node.

System multi-node packages run on all cluster nodes simultaneously; halting these packages stops them running on all nodes. A multi-node package can run on several nodes simultaneously; you can halt it on all the nodes it is running on, or you can specify individual nodes.

Halting a Package that Has Dependencies

Before halting a package, it is a good idea to use the cmviewcl command to check for package dependencies.

You cannot halt a package unless all the packages that depend on it are down. If you try, you’ll see a Serviceguard message telling you why the operation failed, and the package will remain up.

If this happens, you can repeat the halt command, this time including the dependent package(s); Serviceguard will halt all the packages in the correct order. First, use cmviewcl to be sure that no other running package has a dependency on any of the packages you are halting.

Managing Packages and Services 285

Page 285
Image 285
HP Serviceguard manual Starting a Package that Has Dependencies, Halting a Package that Has Dependencies