HP Integrity Virtual Machines Installation, Configuration, and Administration

• Storage Requirements
To make sure the Serviceguard configuration is managable, use identical backing stores on
both the primary node and alternate nodes. To use Serviceguard in Guest 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: “Creating Virtual Storage Devices” (page 71).
• 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: “Creating Virtual Networks” (page 99).
In the Serviceguard with Integrity VM environment, you can use the following network
configurations:
— Heartbeat LAN
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 Serviceguard in Guest and Serviceguard in Host configurations, use
vswitches or hubs to connect two pNICs to the same network broadcast domain.
For Serviceguard in Host configurations, Serviceguard monitors the physical connections
and the vswitch monitor moves the vswitch between pNICs automatically.
In a Serviceguard in Guest 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)
VLANs 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 8.4:
“Configuring VLANs” (page 106)).
The following sections describe the configuration procedures and the specific requirements for
each of the Serviceguard configurations.
11.2 Serviceguard in Guest Configurations
You can install Serviceguard on an HP-UX guest to provide high availability for the applications
running on the guest. In this type of configuration, the guest is configured as a node in a
142 Using HP Serviceguard with Integrity VM