HP HyperFabric manual Application Availability, Features

Planning the Fabric

TCP / UDP / IP

TCP / UDP / IP

TCP/UDP/IP applications are supported on all HF2 (fibre) hardware. Although all HyperFabric adapter cards support HMP applications as well, our focus in this section will be on TCP/UDP/IP HyperFabric applications.

Application Availability

All applications that use the TCP/UDP/IP stack are supported such as Oracle 9i.

Features

•OnLine Addition and Replacement (OLAR): Supported

The OLAR feature allows the replacement or addition of HyperFabric adapter cards while the system (node) is running. For a list of systems that support OLAR, see the HyperFabric Release Notes (B6257-90056).

For more detailed information on OLAR, including instructions for implementing this feature, see “Online Addition and Replacement” on page 42 in this manual, as well as Interface Card OL* Support Guide (B2355-90698).

•Event Monitoring Service (EMS): Supported

In the HyperFabric version B.11.31.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 75 in this manual, as well as the EMS Hardware Monitors User’s Guide (B6191-90028).

•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. It is not possible to use HyperFabric as a heartbeat LAN. 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

Chapter 2 23