HP HyperFabric manual Hyper Messaging Protocol HMP

Planning the Fabric

Hyper Messaging Protocol (HMP)

Starting with the December 2000 releases B.11.00.11 and B.11.11.01, 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 97 in this manual, as well as the EMS Hardware Monitors User’s Guide Part Number B6191-90028 September 2001 Edition.

•MC ServiceGuard: Supported

Within a cluster, MC/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 MC/ServiceGuard transfers control of the package to another node in the cluster, allowing services to remain available with minimal interruption. MC/ServiceGuard via EMS, directly monitors cluster nodes, LAN interfaces, and services (the individual processes within an application). MC/ServiceGuard uses a heartbeat LAN to monitor the nodes in a cluster. MC/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 MC ServiceGuard, see “Configuring HyperFabric with MC/ServiceGuard” on page 98 in this manual, as well as Managing MC/ServiceGuard Part Number B3936-90065 March 2002 Edition.

•High Availability (HA): Partially 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. 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.

For more detailed information on HA when running HMP applications, consult with your HP representative.

•Dynamic Resource Utilization (DRU): Partially Supported

When a new HyperFabric resource (node, cable or switch) is added to a cluster running an HMP application, the HyperFabric subsystem will dynamically identify the added resource and start using it. The same process takes place when a resource is removed from a cluster. The distinction for HMP is that DRU is supported when a node with adapters installed in it is added or removed from a cluster running an HMP application, but DRU is not supported when an adapter is added or removed from a node that is running an HMP application. This is consistent with the fact that OLAR is not supported when an HMP application is running on HyperFabric.

•Load Balancing: Partially Supported

When an HP 9000 node that has multiple HyperFabric adapter cards is running HMP applications, the HyperFabric driver only balances the load across the available adapter cards on that node. Load Balancing is not extended to multiple links between switches or other HyperFabric resources.

38 Chapter 2