Managing Packages and Services

Managing packages and services involves the following tasks:

You can use SAM or HP-UX commands to start, halt, and move packages. You can also modify package failover options without bringing down the cluster or package node.

Starting a Package

Ordinarily, a package configured as part of the cluster will start up on its primary node when the cluster starts up. You may need to start a package manually after it has been halted manually. You can do this either in SAM or with HP-UX commands.

Using SAM to Start a Package

In SAM, select "Package Administration," then choose the package you wish to start. From the Actions menu, choose "Start Package." If you wish to start the package on a specific node, choose "Start a Package on a Specific Node." Otherwise, choose "Start Package," and reply Yes to the verification prompt.

Using HP-UX 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. Example:

# cmrunpkg -n node1 pkg1 
# cmmodpkg -e node1 pkg1

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

Halting a Package

You halt a package when you wish to bring the package out of use but wish the node to continue in operation. You can halt a package using SAM or using HP-UX commands. Halting a package has a different effect than halting the node. When you halt the node, its packages may switch to adoptive nodes (assuming that switching is enabled for them); when you halt the package, it is disabled from switching to another node, and must be restarted manually on another node or on the same node.

Using SAM to Halt a Package

In the SAM "Package Administration" area, choose a package from the list, then select "Halt Package" from the Actions menu. Choose OK in response to the verification prompt. When you halt the package in this way, it is disabled from switching to another node.

Using HP-UX Commands to Halt a Package

Use the cmhaltpkg command to halt a package, as follows:

# cmhaltpkg pkg1

This halts pkg1 and disables it from switching to another node.

Moving a Package

You can use SAM or HP-UX commands to move a package from one node to another.

Using SAM to Move a Running Package

From the Package Administration screen in SAM, choose a package, then select "Move a Package" from the Actions menu. Choose the node you wish to move the package to, then select OK. Reply Yes to the verification prompt.

Using HP-UX Commands to Move a Running Package.

Before you move the package, halt it on its original node using the cmhaltpkg command. This action not only halts the package, but also disables switching the package back to the node on which it halts.

After you have moved the package you must restart it and enable switching. You can do this in SAM or by issuing the cmrunpkg command followed by cmmodpkg -e package_name. cmmodpkg can be used with the -n option to enable a package to run on a node if the package has been disabled from running on that node due to some sort of error. If no node is specified, the node the command is run on is the implied node.

Example:

# cmhaltpkg pkg1 -n node1 
# cmrunpkg -n node2 pkg1 
# cmmodpkg -e pkg1

Resetting the Service Restart Counter

You can now reset the service restart counter to zero by using new options with the cmmodpkg command. Example:

# cmmodpkg -R -s svc1 pkg1

By using the new options, the originally configured number of service restart attempts will again be available for the service. For details, refer to the man page for cmmodpkg(1m).

Reconfiguring the Package

To make a permanent change in package configuration, you must use the following steps:

Halt packages.
On OPS 7.3.x systems, stop OPS. (This step is unnecessary with OPS 8.0.5.)
Deactivate volume groups used by OPS. (This step is unnecessary with OPS 8.0.5.)
Halt the cluster on all nodes.
On one node, reconfigure the package as described in the chapter "Chapter 6 “Configuring Packages and Their Services ”." You can do this by editing the package ASCII file or by using the "Modify Package Configuration" options in the "High Availability Clusters" area in SAM.
To modify the package control script, edit the package control script directly or use the "Edit a Package Control Script" option in SAM. Any changes in service names will also require changes in the package configuration file.
Use SAM or HP-UX commands to copy the modified control script to all nodes that can run the package.
Use SAM or the cmapplyconf command to copy the binary cluster configuration file to all nodes. This file overwrites any previous version of the binary cluster configuration file.
Use SAM or the cmruncl command to start the cluster on all nodes or on a subset of nodes, as desired. The package will start up as nodes come online.

Responding to Cluster Events Affecting Packages

MC/LockManager does not require much on-going system administration intervention. As long as there are no failures, your cluster will be monitored and protected. In the event of a failure, those packages that you have designated to be transferred to another node will be transferred automatically. Your ongoing responsibility as the system administrator will be to monitor the cluster and determine if a transfer of package has occurred. If a transfer has occurred, you have to determine the cause and take corrective actions.

The typical corrective actions to take in the event of a transfer of package include:

Determining when a transfer has occurred.
Determining the cause of a transfer.
Repairing any hardware failures.
Correcting any software problems.
Restarting nodes.
Transferring packages back to their original nodes.