HP Serviceguard Using Serviceguard in HP BladeSystem Configurations

Figure 11: Server Profile for BL860c installed in Device Bay 7

Primary site LAN and private heartbeat LAN assigned

to Interconnect Bays 1 & 2

Standby site LAN and private heartbeat LAN assigned

to Interconnect Bays 5 & 6

Fiber Channel Ports 1 and 2 assigned

to Interconnect Bays 3 & 4

In summary, this example uses the following Virtual Connect server profile configuration to minimize SPOFs with the components that were available to this BL860c server blade:

∙LAN on Motherboard (LOM):

–Port1: Site LAN

–Port 2: (unassigned)

–Port 3: (unassigned)

–Port 4: Serviceguard Heartbeat LAN

∙Mezzanine Card 1 (Fiber Channel HBA)

–Port 1: SAN (primary)

–Port 2: SAN (alternate)

∙Mezzanine Card 2 (Ethernet HBA):

–Port 5: Site LAN (standby)

–Port 6: Serviceguard Heartbeat LAN (secondary)

∙Mezzanine Card 3 (not installed – recommend using a 2nd Fibre Channel HBA for redundancy)

Using Serviceguard in HP BladeSystem Configurations

With the existing high availability features of the HP BladeSystem, adding Serviceguard for HP-UX on Integrity blades builds upon that foundation to provide improved availability for mission-critical applications. The complete Serviceguard Solution portfolio, including the Serviceguard Storage Management Suite, SGeRAC, SGeSAP, Enterprise Cluster Master Toolkit and all Serviceguard

17