HP HyperFabric manual ServiceGuard Supported, High Availability HA Supported

Planning the Fabric

TCP/UDP/IP

—Logging into a user specified log file with a choice of severity

—Email to a user defined email address.

For more information on EMS, including instructions for implementing this feature, see “Configuring the HyperFabric EMS Monitor” on page 85 and the EMS Hardware Monitors User’s Guide Part Number B6191-90028 September 2001 Edition.

•ServiceGuard: Supported

Within a cluster, ServiceGuard groups application services (individual HP-UX processes) into packages. In the event of a single service failure (node, network, or other resource), EMS provides notification and ServiceGuard transfers control of the package to another node in the cluster, allowing services to remain available with minimal interruption.

ServiceGuard via EMS, directly monitors cluster nodes, LAN interfaces, and services (the individual processes within an application). ServiceGuard uses a heartbeat LAN to monitor the nodes in a cluster. ServiceGuard cannot use the HyperFabric interconnect as a heartbeat LAN. Instead, use a separate LAN for the heartbeat.

For more information on configuring ServiceGuard, see “Configuring HyperFabric with ServiceGuard” on page 87, and Managing MC/ServiceGuard Part Number B3936-90065 March 2002 Edition.

•High Availability (HA): Supported

To create a highly available HyperFabric cluster, there should not be any single point of failure. Once the HP 9000 nodes and the HyperFabric hardware have been configured with no single point of failure, ServiceGuard and EMS can be configured to monitor and fail over nodes and services using ServiceGuard packages.

If any HyperFabric resource in a cluster fails (adapter card, cable or switch port), the HyperFabric driver transparently routes traffic over other available HyperFabric resources with no disruption of service.

The ability of the HyperFabric driver to transparently fail over traffic reduces the complexity of configuring highly available clusters with ServiceGuard, because ServiceGuard has to take care of node and service failover only.

Chapter 2 15