Introduction to HP Serviceguard with Integrity VM

After you set up Integrity VM, you can install HP Serviceguard on either the VM Host or the HP-UX guest. Do not use Serviceguard on both the VM Host and the guest at the same time. Table 11-1 lists the Serviceguard versions that are supported on the VM Host and on the guests.

Table 11-1 Serviceguard Version Support

Serviceguard Version	Supported on	Notes
A.11.16	VM Host or HP-UX guest
A.11.17	VM Host or HP-UX guest
A.11.18	VM Host or HP-UX guest	Requires HP-UX 11i v3 on the VM Host.

The Serviceguard version must be appropriate to the version of HP-UX. For more information, see the Managing Serviceguard manual.

To protect guest applications, install Serviceguard on the HP-UX guest. Applications on a guest can fail over to any of the following:
- Another guest configured as a Serviceguard node that is running on the same VM Host system (see Section )
- Another guest configured as a Serviceguard node running on a different VM Host system (see Section )
- Another server or partition that is not running Integrity VM (see Section )
Windows guests do not support HP Serviceguard; therefore, Serviceguard cannot be installed on Windows guests applications or configured into a Serviceguard cluster.
To protect guests, install HP Serviceguard on the VM Host system. Guests configured as Serviceguard packages (guests) are subsequently managed using HP Serviceguard commands. If the VM Host system fails, the distributed guest automatically fails over to another node in the Integrity VM multiserver environment. Integrity VM guests which can be relocated between Integrity VM Hosts are configured into an Integrity VM multiserver environment that contains the same set of servers as is in the Serviceguard cluster. (For more information, see Section ). Guests of any operating system (HP-UX, Linux, and Windows) can be configured as Serviceguard packages.

Each Serviceguard configuration provides a level of protection against failure. Choose the configuration that best meets your needs, and keep the following requirements in mind:

Storage requirements
To make sure the Serviceguard configuration is manageable, use identical backing stores on both the primary node and alternate nodes. To use VMs as Serviceguard Nodes configurations, the backing storage units must be whole disks. Integrity VM does not support using other types of backing stores on primary and alternate nodes for applications that are configured as Serviceguard packages.
The VM Host system storage configurations must comply with both Integrity VM and Serviceguard product requirements. For information about the Integrity VM storage subsystem, see Chapter 7.
Network requirements
To make sure network communication with guests is always available, provide identical network devices on both the primary and alternate nodes. Physical NICs (pNICs) and vswitches must be the same on both the original and adoptive nodes for virtual NICs (vNICs) to function after the failover. For more information about the Integrity VM networking subsystem, see Chapter 8.
In the Serviceguard with Integrity VM environment, you can use the following network configurations:
- Heartbeat LANs
  Serviceguard nodes use heartbeat LANs to maintain communication with one another. Whether Serviceguard is installed on the VM Host system or on the guest, HP recommends that you configure every LAN as a heartbeat LAN.
- Primary and standby LANs
  For local LAN failover, a Serviceguard node must have both a primary and standby LAN. In both VMs as Serviceguard Nodes and VMs as Serviceguard Packages configurations, use vswitches or hubs to connect two pNICs to the same network broadcast domain.
  For VMs as Serviceguard Packages configurations, Serviceguard monitors the physical connections and the vswitch monitor moves the vswitch between pNICs automatically.
  In a VMs as Serviceguard Nodes configuration, the pNICs are connected to vswitches, which are configured as vNICs in the guest. In this configuration, Serviceguard running in the guest determines the primary and standby LANs and performs the failover in the guest.
- Autoport Aggregation (APA)
  You can use HP-UX APA in the Serviceguard configuration on the VM Host systems. Use APA in MANUAL or AUTO-FEC modes when running on the VM Host system. Do not use LACP_AUTO mode link aggregates. For more information about APA, see the HP Auto Port Aggregation (APA) Support Guide.
- Virtual LANs (VLANs)
  Virtual LANs can be configured on the vswitches or the physical switches. You can use VLANs on the VM Host system (as described in the Using HP-UX VLANS manual). You can configure the VLAN on vswitches used by guests (as described in Section ).

The following sections describe the configuration procedures and the specific requirements for each of the Serviceguard configurations.

Introduction to HP Serviceguard with Integrity VM

Technical documentation

» Table of Contents

» Glossary

» Index