Configuring HP DCE Cells
Integrating DCE Services with MC/ServiceGuard
important is that you read and understand the section in Chapter 4 entitled “Writing Network Applications as HA Services” before beginning the planning process.
Hardware Requirements for a
By their very nature, DCE and DCE applications are distributed, and therefore depend heavily on network resources. Each node in the cluster should have multiple redundant LAN cards connected to multiple LANs. Also, all the normal hardware configuration guidelines outlined in Managing MC/ServiceGuard should be followed when planning for your hardware configuration.
Implementation Alternatives for a
The basic configuration, which is supported by the templates, is the DCE host failover. In this configuration, ServiceGuard moves an entire DCE host from one physical node to another.
An alternative configuration is the individual core server failover. In this configuration, the DCE cluster includes a primary host and several smaller hosts. Each of the smaller hosts can perform one or more of the functions normally performed by the primary host. In the event of a system failure for the primary host, ServiceGuard moves only the core servers on the smaller hosts from their individual physical nodes to other physical nodes. For example, in a DCE cluster with individual server hosts for the Security Service and the Name Service, ServiceGuard can move the secd or cdsd servers individually to a new host rather than moving the entire primary host to another node.
Another alternative configuration is the redesignation of master servers through ServiceGuard scripts. This approach involves changing the role of the existing replicas, making them the master servers, instead of moving the databases to new locations.
Other alternative configurations are possible, but they are not discussed here. See Managing MC/ServiceGuard
The remaining sections in this chapter describe the basic configuration only.
Planning and Configuring HP DCE 1.7 |