Planning and Configuring HP-UX DCE 1.9

Chapter 6
Configuring HP-UX DCE Cells
Integrating DCE Services with MC/ServiceGuard
70
Planning for the DCE Package
When planning for a DCE-MC/ServiceGuard installation, keep the following considerations in mind:
• Enough disk space to hold the DCE installation, log files, and core files should be allocated in the logical
volumes assigned to the package. See Chapter 3 of this manual for recommendations regarding disk space
requirements.
• Every node in the cluster will need to be configured with adequate swap space for a DCE server
configuration. The minimum recommended swap space is 100MB, but this figure may need to be modified
based on actual need. The kernel configuration should be validated on an operational system and
adjusted if necessary.
• Network switching and package switching should normally be enabled. Depending on the services
included in the package and the requirements of the system, node and service fail fast may be enabled as
well.
• There are a number of different ways to define the DCE package. The simplest way is to include the
execution of the rc.dce start script at the end of the package run script, the dce_shutdown utility at the
start of the package stop script, and a definition of a simple monitoring script as the "service" to be
executed This simple monitoring script should periodically check for the existence of the configured DCE
servers, and return with a non-zero exit status if any of the servers fail.
DCE Configuration for Integration with ServiceGuard
Following are the steps to integrate DCE Configuration with ServiceGuard:
1. Configure the ServiceGuard cluster
2. Configure DCE
3. Configure the package
4. Distribute the package
5. Start the ServiceGuard cluster
6. Start the package on the ServiceGuard cluster
The following subsections describe these steps in more detail.
Configuring the ServiceGuard Cluster
Before configuring DCE for integration with ServiceGuard, you must install ServiceGuard. Then, install the
DCE software on the primary and secondary nodes separately.
1. To configure the primary and secondary nodes in a ServiceGuard cluster, enter the following command:
cmquerycl -v -C /etc/cmcluster/cmclconfig.ascii \ -n primary_node -n secondary_node1 \
-n secondary_node2
This command creates the template script /etc/cmcluster/cmclconf.ascii. Modify the script
parameters to reflect your desired configuration, after which, the script seldom needs modification.
2. To determine if ServiceGuard daemons are running so that the DCE initial configuration program
(dce_config) detects the presence of ServiceGuard enter the following command:
cmruncl -v -n primary_node -n secondary_node
3. Identify the hostname and IP address to be dedicated to the packages. To manually add the IP address to
the cluster's primary node, enter the following command
cmmodnet -a -i package_IP SUBNET