HP manual Configuring HyperFabric with ServiceGuard

Configuring HyperFabric

Configuring HyperFabric with ServiceGuard

NOTE

CAUTION

Configuring HyperFabric with ServiceGuard

HyperFabric supports the ServiceGuard HA product.

If you plan to configure HyperFabric with ServiceGuard, please read this section. Otherwise, skip this section and go on to the next chapter, Chapter 5, “Managing HyperFabric,” on page 93.

ServiceGuard lets you create HA clusters of HP 9000 server systems. Within the cluster, ServiceGuard allows you to group your application services (individual HP-UX processes) into packages. In the event of a single service, node, network, or other resource failure, ServiceGuard can transfer control of the package to another node in the cluster, allowing services to remain available with minimal interruption.

When applications use HMP to communicate between HP 9000 nodes in a HyperFabric cluster, the EMS monitor in conjunction with ServiceGuard can be configured to identify node failure and automatically fail-over to a functioning HP 9000 node. Although failure of an adapter card or a link will be detected, there will not be automatic fail-over if an adapter card or a link fails. See “Features” on page 23 for details on features available when HMP applications are run over HyperFabric.

ServiceGuard directly monitors cluster nodes, LAN interfaces, and services, which are the individual processes within an application. In addition, specialized monitors might be supplied by the developers of other components. The HyperFabric monitor is supplied with the HyperFabric product and is installed with it. To use the HyperFabric monitor with ServiceGuard, you configure the monitor as an ServiceGuard package dependency.

Although HyperFabric can be used by an application within a package to communicate with other nodes, it is not possible to use HyperFabric as a heartbeat LAN. So, in a package control script, do not specify HyperFabric IPs/subnets in the lines that contain the keywords IP[n] and SUBNET[n]. Also, cmquerycl will not “discover” and report HyperFabric IPs and subnets.

After you have configured HyperFabric as a package dependency, ServiceGuard’s package manager calls the Event Monitoring Service (EMS) to launch an external monitor for HyperFabric. The package will not start unless the monitor reports that HyperFabric is available, and the package will fail when HyperFabric’s status is DOWN (that is, when all HyperFabric adapters on a node become non-functional).

Complete instructions for configuring ServiceGuard clusters and packages are provided in Managing MC/ServiceGuard.

Figure 4-2 below shows a HyperFabric switch configuration with ServiceGuard. This example shows a four-node configuration with two HyperFabric switches, and redundant heartbeat Ethernet LANs.

76 Chapter 4