Planning and Configuring HP DCE 1.8

Chapter 5 109
Configuring HP DCE Cells
Integrating DCE Services with MC/ServiceGuard
Supported Templates for MC/ServiceGuard
Integration with DCE
As part of the DCE product, HP DCE 1.8 provides a fileset
(DCE-SGUARD) that contains a set of customizable ServiceGuard
templates and scripts to integrate MC/ServiceGuard with DCE services.
This set of templates includes the DCE processes dced, cdsadv, secd,
and cdsd within a single package. Each process is monitored separately,
and local restart and local network switchover are supported.
NOTE Do not attempt to use the templates in an installation without first
customizing them.
The templates and scripts are as follows:
dcepkg.conf—package definition file generated by
MC/ServiceGuard. You must supply the ServiceGuard node names,
DCE services, and the network name and address.
rc.dcepkg—package control script generated by MC/ServiceGuard.
You must supply the ServiceGuard node names, DCE services, and
the network name and address. You can also specify customer defined
functions.
dce—DCE configuration file, which is copied from
/etc/rc.config.d/dce to the DCE/ServiceGuard package directory.
You can set the environment variable
RPC_SUPPORTED_NETADDRS to the package IP address.
dce.start—package startup script, which MC/ServiceGuard calls
when the package is activated.
dce.restart—package restart script, which the DCE service monitor
uses to start an individual DCE service.
dce.monitor—DCE Service monitor, which ServiceGuard launches
to monitor DCE daemons.
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.