Configuring HP DCE Cells

Integrating DCE Services with MC/ServiceGuard

First, the DCE service monitor checks to see if the server is running, and, if it is not, the DCE service monitor starts it. Then, the DCE service monitor goes into a loop and checks to ensure that the server process is running. Finally, the DCE service monitor performs a DCE level ping on the server interface.

rc.dcepkg.log—a log file that is created in the package directory during DCE package startup through MC/ServiceGuard, individual DCE services restart upon failure, and package failover.

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.

Planning and Configuring HP DCE 1.7

5-35