Managing Serviceguard Nineteenth Edition, Reprinted June 2011

3. Apply the configuration.
4. Run the package and ensure that it can be moved from node to node.
5. Halt the package.
6. Configure package IP addresses and application services in the control script.
7. Distribute the control script to all nodes.
8. Run the package and ensure that applications run as expected and that the package fails over
correctly when services are disrupted.
Editing the Package Configuration File
Edit the file you generated with cmmakepkg. Use the bullet points that follow as a checklist.
NOTE: HP strongly recommends that you never edit the package configuration file of a legacy
CVM/CFS multi-node or system multi-node package, although Serviceguard does not prohibit it.
Create SG-CFS-pkg by issuing the cmapplyconf command. Create and modify the legacy CFS
packages SG-CFS-DG-id# and SG-CFS-MP-id# using cfs commands.
For the CVM/CFS modular style packages, you cannot use the cfs commands. Instead, you must
edit the modular CFS package parameters in the package configuration files.
• PACKAGE_TYPE. Enter the package type; see “Types of Package: Failover, Multi-Node, System
Multi-Node” (page 217) and package_type (page 223).
NOTE: For modular packages, the default form for parameter names in the package
configuration file is lower case; for legacy packages the default is upper case. There are no
compatibility issues; Serviceguard is case-insensitive as far as the parameter names are
concerned.
Because this section is intended to be used primarily when you are reconfiguring an existing
legacy package, we are using the legacy parameter names (in upper case) for sake of
continuity. But if you generate the configuration file using cmmakepkg or cmgetconf, you
will see the parameter names as they appear in modular packages; see the notes below and
the “Package Parameter Explanations” (page 222) for details of the name changes.
• FAILOVER_POLICY. For failover packages, enter the failover_policy (page 226).
• FAILBACK_POLICY. For failover packages, enter the failback_policy (page 227).
• NODE_NAME. Enter the node or nodes on which the package can run; see node_name
(page 223).
• AUTO_RUN. Configure the package to start up automatically or manually; see auto_run
(page 224).
• LOCAL_LAN_FAILOVER_ALLOWED. Enter the policy for local_lan_failover_allowed
(page 229).
• NODE_FAIL_FAST_ENABLED. Enter the policy for node_fail_fast_enabled (page 224).
• RUN_SCRIPT and HALT_SCRIPT. Specify the pathname of the package control script
(described in the next section). No default is provided. Permissions on the file and directory
should be set to rwxr-xr-x or r-xr-xr-x (755 or 555).
(Script timeouts): Enter the run_script_timeout (page 224) and halt_script_timeout
(page 225).
SCRIPT_LOG_FILE. (optional). Specify the full pathname of the file where the RUN_SCRIPT
and HALT_SCRIPT will log messages. If you do not specify a path, Serviceguard will create
a file with “.log” appended to each script path, and put the messages in that file.
290 Cluster and Package Maintenance