HyperFabric Configuration Guidelines

Hyper Messaging Protocol (HMP)

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 "Enterprise (Database) -Transparent Local

Failover Supported Configuration" on page 33 and “Configuring

HMP for Transparent Local Failover Support - Using the clic_init

command” on page 46.

• Dynamic Resource Utilization (DRU): Partially Supported

If you add a new HyperFabric resource (node, cable or switch) 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.

However, DRU is not supported if you add or remove an adapter

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: Supported

When a HP 9000 HyperFabric cluster is running HMP applications,

the HyperFabric driver balances the load across all available

resources in the cluster including nodes, adapter cards, links, and

multiple links between switches.

• Switch Management: Not Supported

Switch Management is not supported. Switch management will not

operate properly if it is enabled on a HyperFabric cluster.

For more detailed information on HyperFabric switch management,

see Installing and Administering HyperFabric Part Number

B6257-90030 Edition E0601, HyperFabric Administrator’s Guide

Part Number B6257-90042 and HyperFabric Administrator’s Guide

Part Number B6257-90039.

• Diagnostics: Supported

Diagnostics can be run to obtain information on many of the

HyperFabric components via the clic_diag, clic_probe and

clic_stat commands, as well as the Support Tools Manager (STM).