User's Guide

Planning the Fabric
Hyper Messaging Protocol (HMP)
Chapter 2
31
• Event Monitoring Service (EMS): Supported
The HyperFabric EMS monitor allows the system administrator to separately
monitor each HyperFabric adapter on every node in the fabric, in addition to
monitoring the entire HyperFabric subsystem. The monitor can inform the user if
the resource being monitored is UP or DOWN. The administrator defines the
condition to trigger a notification (usually a change in interface status). Notification
can be accomplished with a SNMP trap or by logging into the syslog file with a choice
of severity, or by email to a user defined email address.
For more detailed information on EMS, including instructions for implementing this
feature, see “Configuring the HyperFabric EMS Monitor” on page 75 in this manual,
as well as 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 link. Instead, a separate
LAN must be used for the heartbeat.
For more detailed information on configuring ServiceGuard, see “Configuring
HyperFabric with ServiceGuard” on page 76 in this manual, as well as Managing
MC/ServiceGuard Part Number B3936-90065 March 2002 Edition.
• High Availability (HA): Supported
When applications use HMP to communicate between HP 9000 nodes in a
HyperFabric cluster, MC/ServiceGuard and the EMS monitor can be configured to
identify node failure and automatically fail-over to a functioning HP 9000 node.
For more detailed information on HA when running HMP applications, consult with
your HP representative.
• Transparent Local Failover: Supported
When a HyperFabric resource (adapter, cable, switch or switch port) fails in a cluster,
HMP transparently fails over traffic using other available resources. This is
accomplished using card pairs, each of which is a logical entity that comprises a pair
of HF2 adapters on a HP 9000 node. Only Oracle applications can make use of the
Local Failover feature. HMP traffic can only fail over between adapters that belong
to the same card pair. Traffic does not fail over if both the adapters in a card pair fail.
However, administrators do not need to configure HF2 adapters as card pairs if
TCP/UDP/IP is run over HF2.
When HMP is configured in the local failover mode, all the resources in the cluster
are utilized. If a resource fails in the cluster and is restored, HMP does not utilize
that resource until another resource fails.
For more information on Transparent Local Failover while running HMP
applications, see “Configuring HMP for Transparent Local Failover Support” on page
96.