Package Configuration Planning

The name of the package. The package name must be unique in the cluster. It is used to start, stop, modify, and view the package. In the ASCII package configuration file, this parameter is PACKAGE_NAME.

In the package ASCII file, the package name can be from 1 to 39 characters. It must not contain any of the following illegal characters: space, slash (/), backslash(\), and asterisk (*). All other characters are legal.

In Serviceguard Manager, more non-alphanumeric characters are not allowed. See the online help topic “Configuring Packages.”

The policy used by the package manager to select the node on which the package should be automatically started. In the ASCII package configuration file, this parameter is known as FAILOVER_POLICY.

Default is CONFIGURED_NODE, which selects the next available node in the list of node names for the package. The order of preference is the order of the node name entries in the package’s configuration file.

The alternate policy is MIN_PACKAGE_NODE, which creates a list of packages running on each node that can run this package, and selects the node that is running the fewest packages.

The policy used to determine what action the package manager should take if the package is not running on its primary node and its primary node is capable of running the package. In the ASCII package configuration file, this parameter is known as FAILBACK_POLICY.

Default is MANUAL, which means no attempt will be made to move the package back to its primary node when it is running on an alternate node. (This is the same behavior as in previous versions of Serviceguard.) The alternate policy is AUTOMATIC, which means that the package will be halted and restarted on its primary node as soon as the primary node is capable of running the package and, if MIN_PACKAGE_NODE has been selected as the Package Failover Policy, the primary node is now running fewer packages than the current node.

The names of primary and alternate nodes for the package. In the ASCII configuration file, this parameter is NODE_NAME. Enter a node name for each node on which the package can run.

The order in which you specify the node names is important. First list the primary node name, then the first adoptive node name, then the second adoptive node name, followed, in order, by additional node names. in a failover, control of the package will be transferred to the next adoptive node name listed in the package configuration file.

If all nodes in the cluster are to be used, and if order is not important, you can specify: NODE_NAME *

A node name can be up to 31 bytes long.

In the ASCII package configuration file, the AUTO_RUN parameter was formerly known as PKG_SWITCHING_ENABLED. If Automatic Switching is enabled (AUTO_RUN set to YES), Serviceguard will automatically start the package on an eligible node if one is available, and will automatically fail the package over to another node if it fails. If Automatic Switching is Disabled (AUTO_RUN set to NO), Serviceguard cannot automatically start the package up. The user must do it with the cmrunpkg command.

When a package starts up, the Package Switching flag is set to match the AUTO_RUN setting, but this flag can be changed temporarily with the cmmodpkg command while the package is running.

Default is AUTO_RUN YES. Check the box to enable auto-run in Serviceguard Manager; enter AUTO_RUN YES or NO in the ASCII file.

Enter Enabled or Disabled. In the event of a failure, this permits Serviceguard to switch LANs locally, that is, transfer the package IP address to a standby LAN card. The default is Enabled. In the ASCII package configuration file, this parameter is called LOCAL_LAN_FAILOVER_ALLOWED, and possible values are YES and NO.

Default is checked in Serviceguard Manager, or YES in the ASCII file.

In the event of the failure of the control script itself, or the failure of a subnet, or the report of an EMS (Event Monitoring Service) monitor event showing that a resource is down, if this parameter is set to Enabled, Serviceguard will issue a TOC on the node where the control script fails. In the ASCII package configuration file, this parameter is called NODE_FAIL_FAST_ENABLED, and possible values are YES and NO.

The default is Disabled, not checked in Serviceguard Manager, or NO in the ASCII file.

If NODE_FAIL_FAST_ENABLED is set to YES, the node where the package is running will be halted if one of the following failures occurs:

However, if the package halt script fails with “exit 1”, Serviceguard does not halt the node, but sets NO_RESTART for the package, which causes package switching (AUTO_RUN) to be disabled, thereby preventing the package from starting on any adoptive node.

Serviceguard Manager will automatically create and maintain a control script if you use Guided Mode, the Serviceguard Manager default. If you choose, you can edit the control script yourself, and name your own path. Once you leave Guided Mode, however, Serviceguard Manager cannot update your script.

Enter the full pathname of the package control script. (The script must reside in a directory that contains the string “cmcluster.”) Ensure that this script is executable. In the ASCII package configuration file, this parameter maps to the two separate parameters named RUN_SCRIPT and HALT_SCRIPT.

It is recommended that you use the same script as both the run and halt script. This script will contain both your package run instructions and your package halt instructions. If you wish to separate the package run instructions and package halt instructions into separate scripts, the package configuration file allows allows you to do this by naming two separate scripts. However, under most conditions, it is simpler to use the name of the single control script as the name of the RUN_SCRIPT and the HALT_SCRIPT in the ASCII file. When the package starts, its run script is executed and passed the parameter ‘start’; similarly, at package halt time, the halt script is executed and passed the parameter ‘stop’.

If you choose to write separate package run and halt scripts, be sure to include identical configuration information (such as node names, IP addresses, etc.) in both scripts.

If the script has not completed by the specified timeout value, Serviceguard will terminate the script. In the ASCII configuration file, these parameters are RUN_SCRIPT_TIMEOUT and HALT_SCRIPT_TIMEOUT. Enter a value in seconds.

The default is 0, or no timeout. The minimum is 10 seconds, but the minimum HALT_SCRIPT_TIMEOUT value must be greater than the sum of all the Service Halt Timeout values. The absolute maximum value is restricted only by the HP-UX parameter ULONG_MAX, for an absolute limit of 4,294 seconds.

If the timeout is exceeded:

If the halt script timeout occurs, you may need to perform manual cleanup. See “Package Control Script Hangs or Failures” in Chapter 8.

	NOTE: VxVM disk groups are imported at package run time and exported at package halt time. If you are using a large number of VxVM disks in your package, the timeout must be high enough to allow all of them to finish the import or export.

This parameter is used for CVM disk groups that do not use VERITAS Cluster File System. Enter the names of all the CVM disk groups the package will use.

In the ASCII package configuration file, this parameter is called STORAGE_GROUP.

	NOTE: Do not use STORAGE_GROUP parameters to reference CVM disk groups in a cluster using the CFS file system. CFS resources are controlled by two multi-node packages, one for the disk group and one for the mount point.Use the parameter for CVM storage only. Do not enter CVM disk groups that are used in a CFS cluster. Additionally, do not enter the names of LVM volume groups or VxVM disk groups in the package ASCII configuration file.

Enter a unique name for each service. In the ASCII package configuration file, this parameter is called SERVICE_NAME.

Define one SERVICE_NAME entry for each service.You can configure a maximum of 30 services per package and 900 services per cluster. The service name must not contain any of the following illegal characters: space, slash (/), backslash (\), and asterisk (*). All other characters are legal. The service name can contain up to 39 characters.

Enter Enabled or Disabled for each service. This parameter indicates whether or not the failure of a service results in the failure of a node. If the parameter is set to Enabled, in the event of a service failure, Serviceguard will halt the node on which the service is running with a TOC. (An attempt is first made to reboot the node prior to the TOC.)The default is Disabled.

In the ASCII package configuration file, this parameter is SERVICE_FAIL_FAST_ENABLED, and possible values are YES and NO. The default is NO. Define one SERVICE_FAIL_FAST_ENABLED entry for each service.

In the event of a service halt, Serviceguard will first send out a SIGTERM signal to terminate the service. If the process is not terminated, Serviceguard will wait for the specified timeout before sending out the SIGKILL signal to force process termination. In the ASCII package configuration file, this parameter is SERVICE_HALT_TIMEOUT.

If you do not fill in a number, Serviceguard will not allow any timeout (0 seconds). The maximum value is restricted only by the HP-UX parameter ULONG_MAX, for an absolute limit of 4,294 seconds.

Define one SERVICE_HALT_TIMEOUT entry for each service.

Enter the IP subnets that are to be monitored for the package.

In the ASCII package configuration file, this parameter is called SUBNET.

The type of the package. This parameter indicates whether the package will run on one node at a time or on multiple nodes. Valid types are FAILOVER, MULTI_NODE, and SYSTEM_MULTI_NODE. Default is FAILOVER.

You cannot create a user-defined package with a type of SYSTEM_MULTI_NODE or MULTI-NODE. They are only supported for specific purposes designed by HP.

It is not recommended that you create the VERITAS Cluster File System packages by editing the ASCII configuration template; use the cfs admin commands in Appendix A.

The name of an Event Monitoring Service resource that is to be monitored by Serviceguard as a package dependency. In the ASCII package configuration file, this parameter is called RESOURCE_NAME.

A resource name is the name of an important attribute of a particular system resource. The resource name includes the entire hierarchy of resource class and subclass within which the resource exists on a system. Obtain the resource name from the list provided in Serviceguard Manager in the EMS (Event Monitoring Service) tab’s Browse button (“Available EMS resources”), or obtain it from the documentation supplied with the resource monitor.

A maximum of 60 resources may be defined per cluster. Note also the limit on Resource Up Values described below.

Maximum length of the resource name string is 1024 characters.

The frequency of monitoring a configured package resource. In the ASCII package configuration file, this parameter is called RESOURCE_POLLING_INTERVAL.

Default is 60 seconds. The minimum value is 1. The maximum value has no functional limit.

The Resource Polling Interval appears on the list provided in Serviceguard Manager’s package configuration screen, EMS Resource tab’s Browse button (“Description of selected EMS resource”), or you can obtain it from the documentation supplied with the resource monitor.

An attribute of a resource that determines whether it should start up before or after the package starts. In the ASCII package configuration file, this parameter is called RESOURCE_START.

Default setting is AUTOMATIC, which means that the resource starts at the time the node joins the cluster. The other possible setting is DEFERRED, which means that the package services will start up before the resource starts. If a resource is configured with DEFERRED startup, the name of the resource has to be added to the control script’s DEFERRED_RESOURCE_NAME parameter. (If you use Serviceguard Manager’s guided mode to create the control script automatically, it will be entered for you.)

The criteria for judging whether an additional package resource has failed or not. In the ASCII package configuration file, this parameter is called RESOURCE_UP_VALUE. The Resource Up Value appears on the “Description of selected EMS resources” list provided in Serviceguard Manager’s EMS Browse button, or you can obtain it from the documentation supplied with the resource monitor.

You can configure a total of 15 Resource Up Values per package. For example, if there is only one resource in the package, then a maximum of 15 Resource Up Values can be defined. If there are two Resource Names defined and one of them has 10 Resource Up Values, then the other Resource Name can have only 5 Resource Up Values.

The maximum length of the Resource Up Value string is 1024 characters.

You can configure package administration access for this package. Be sure the policy is not conflicting or redundant to an access policy defined in the cluster configuration file. For more information, see “Editing Security Files ”.

The script log file documents the package run and halt activities. The default location is /etc/cmcluster/pkgname/control_script.log. To specify another location, put the full pathname here.

Starting in Serviceguard A.11.17, a package can have dependencies on other packages. The package will not start on a node unless its dependencies are met on that node.

At the release of Serviceguard A.11.17, dependencies are only supported for use with certain applications specified by HP, such as with the multi-node and system multi-node packages that HP supplies for use with VERITAS Cluster File System.

DEPENDENCY_NAME - A unique identifier for the dependency
DEPENDENCY_CONDITION- pkgname = UP
DEPENDENCY_LOCATION - SAME_NODE

Specify the path to be used by the script.

Specifies the method of activation for LVM volume groups. Leave the default (VGCHANGE=“vgchange -a e”) if you want volume groups activated in exclusive mode. This assumes the volume groups have been initialized with vgchange -c y at the time of creation.

Use VGCHANGE=“vgchange -a e -q n” if your disks are mirrored on separate physical paths.

Use VGCHANGE=“vgchange -a e -q n -s” if your disks are mirrored on separate physical paths and you want the mirror resynchronization to occur in parallel with the package startup.

Use VGCHANGE=“vgchange -a y” if you wish to use non-exclusive activation mode. Single node cluster configurations must use non-exclusive activation.

Specifies the command for activation of VERITAS CVM disk groups.

Use the default CVM_ACTIVATION_CMD=“vxdg -g \$DiskGroup set activation=exclusivewrite” if you want disk groups activated in exclusive write mode.

Use CVM_ACTIVATION_CMD=“vxdg -g \$DiskGroup set activation=readonly” if you want disk groups activated in read-only mode.

Use CVM_ACTIVATION_CMD=“vxdg -g \$DiskGroup set activation=sharedread” if you want disk groups activated in shared read mode.

Use CVM_ACTIVATION_CMD=“vxdg -g \$DiskGroup set activation=sharedwrite” if you want disk groups activated in shared write mode.

	NOTE: VxVM disk groups do not allow you to select specific activation commands. The VxVM disk group activation always uses the same command.

Controls the method of mirror recovery for mirrored VxVM volumes.

Use the default VXVOL=“vxvol -g \$DiskGroup startall” if you want the package control script to wait until recovery has been completed.

Use VXVOL=“vxvol -g \$DiskGroup -o bg startall” if you want the mirror resynchronization to occur in parallel with the package startup.

This array parameter contains a list of the LVM volume groups that will be activated by the package. Enter each VG on a separate line.

This array parameter contains a list of the VERITAS CVM disk groups that will be used by the package. Enter each disk group on a separate line. Begin the list with CVM_DG[0], and increment the list in sequence. Do not use CVM and VxVM disk group parameters to reference devices used by CFS (VERITAS Cluster File System). CFS resources are controlled by the multi-node packages, SG-CFS-DG-id# and SG-CFS-MP-id#.

This array parameter contains a list of the VERITAS VxVM disk groups that will be activated by the package. Enter each disk group on a separate line.

These array parameters, entered together as triplets into array variables. Each triplet specifies a filesystem, a logical volume, and a mount option string for a file system used by the package. In the package control script file, these variables are arrays, as follows: LV, FS and FS_MOUNT_OPT.

On starting the package, the script may activate one or more storage groups, and it may mount logical volumes onto file systems. At halt time, the script unmounts the file systems and deactivates each storage group. All storage groups must be accessible on each target node (CVM disk groups must be accessible on all nodes in the cluster). For each file system (FS), you must identify a logical volume (LV).

A logical volume can be built on an LVM volume group, a VERITAS CVM disk group, or a VERITAS VxVM disk group. LVs can be entered in any order, regardless of the type of storage group that is used.

The number of unmount attempts allowed for each filesystem during package shutdown. Default is 1.

The number of mount retrys for each filesystem. The default is 0. During startup, if a mount point is busy and FS_MOUNT_RETRY_COUNT is 0, package startup will fail and the script will exit with 1. If a mount point is busy and FS_MOUNT_RETRY_COUNT is greater than 0, the script will attempt to kill the user responsible for the busy mount point for the number of times specified in FS_MOUNT_RETRY_COUNT. If the mount still fails after this number of attempts, the script will exit with 1.

Specifies the number of concurrent volume group activations or deactivations to allow during package startup or shutdown. The default is 1. Setting this variable to a higher value may improve performance if you are using a large number of volume groups. If a value less than 1 is specified, the script defaults the variable to 1 and writes a warning message in the package control script log file.

Specifies the number of concurrent fsck commands to allow during package startup. The default is 1. Setting this variable to a higher value may improve performance when checking a large number of file systems. If a value less than 1 is specified, the script defaults the variable to 1 and writes a warning message in the package control script log file.

Specifies the number of mounts and umounts to allow during package startup or shutdown. The default is 1. Setting this variable to a higher value may improve performance while mounting or unmounting a large number of file systems. If a value less than 1 is specified, the script defaults the variable to 1 and writes a warning message in the package control script log file.

These are the IP addresses by which a package is mapped to a LAN card. Indicate the IP addresses and subnets for each IP address you want to add to an interface card. Package IP addresses may be either IPv4 addresses or IPv6 addresses. For more details of IPv6 address format, see the “IPv6 Address Types”

In the package control script file, these variables are entered in pairs. An IPv4 example is IP[0]=192.10.25.12 and SUBNET[0]=192.10.25.0. (In this case the subnet mask is 255.255.255.0.) An IPv6 examples is IP[0]=2001::3 and SUBNET[0]=2001::/64. (In this case the subnet mask is ffff:ffff:ffff:ffff::.)

Enter a unique name for each specific service within the package. All services are monitored by Serviceguard. You may specify up to 30 services per package. Each name must be unique within the cluster. The service name is the name used by cmrunserv and cmhaltserv inside the package control script. It must be the same as the name specified for the service in the package ASCII configuration file.

In the package control script file, enter values into an array known as SERVICE_NAME. Enter one service name for each service. The SERVICE_NAME, SERVICE_CMD, and SERVICE_RESTART parameters are set in the package control script in groups of three.

The service name must not contain any of the following illegal characters: space, slash (/), backslash (\), and asterisk (*). All other characters are legal. The service name can contain up to 39 characters.

For each named service, enter a Service Command. This command will be executed through the control script by means of the cmrunserv command.

In the package control script file, enter values into an array known as SERVICE_CMD. Enter one service command string for each service. The SERVICE_NAME, SERVICE_CMD, and SERVICE_RESTART parameters are set in the package control script in groups of three.

Enter a number of restarts. One valid form of the parameter is “-r n” where n is a number of retries. A value of “-r 0” indicates no retries. A value of “-R ” indicates an infinite number of retries. The default is 0, or no restarts.

In the package control script file, enter values into an array known as SERVICE_RESTART. Enter one restart value for each service. The SERVICE_NAME, SERVICE_CMD, and SERVICE_RESTART parameters are set in the package control script in groups of three.

For each deferred resource specified in the package configuration ASCII file, you must enter the resource name in this array in the control script. The name should be spelled exactly as it is spelled in the RESOURCE_NAME parameter in the package ASCII configuration file.

In the package control script file, enter the value into the array known as DEFERRED_RESOURCE_NAME. This name must match the resource name listed with the RESOURCE_START parameter in the package ASCII configuration file.

Enter a DTC Name for each DTC. For information on using a DTC with Serviceguard, see the chapter entitled “Configuring DTC Manager for Operation with Serviceguard” in the manual Using the HP DTC Manager/UX.