Best Practices for HP BladeSystem Deployments using HP Serviceguard Solutions for HP-UX 11i (May 2010)

19
– HP BLc 4Gb Fibre Channel Pass-thru Module (P/N 403626-B21)
– Brocade 4/12 SAN Switch (P/N AE370A - Note P/N AE373A to upgrade the AE370 12 port
switch to 24 ports is also supported)
– Brocade 4/24 SAN Switch for c-Class BladeSystem (P/N AE372A)
– Cisco MDS 9124e 12-port Fabric Switch (P/N AG641A)
– Cisco MDS 9124e 24-port Fabric Switch (P/N AG642A)
– HP B-series 8/12c SAN Switch (P/N AJ820A)
– HP B-series 8/24c SAN Switch (P/N AJ821A or AJ822A)
– HP BLc 4Gb Virtual Connect Fibre Channel Module (P/N 409513-B21 or 409513-B22)
– HP Virtual Connect 8Gb 24-Port Fibre Channel Module (P/N 466482-B21)
– HP Virtual Connect 8Gb 20-Port Fibre Channel Module (P/N 572018-B21)
• SAS Interconnects:
– HP 3Gb SAS BL Switch (P/Ns AJ864A or AJ865A; note this interconnect module is supported
only with the P700m SAS Controller mezzanine HBA)
• InfiniBand Interconnects:
– HP BLc 4X DDR InfiniBand Switch Module (P/N 410398-B21)
– HP BLc 4X DDR InfiniBand Gen 2 Switch Module (P/N 489183-B21)
Serviceguard Clustering within a Single Blade Enclosure
With the ability of HP BladeSystem enclosures to contain multiple HP Integrity server blades, it is
possible to run a Serviceguard cluster completely self-contained within an enclosure. Figure 12 shows
an example of this type of configuration, also known as a “cluster in a box”.
Figure 12: Example of a Serviceguard “cluster in a box” Configuration using a c7000 Enclosure
HP Systems Insight Manager (SIM)
Central Management Server (CMS)
Serviceguard
cluster
Quorum Service
(Linux OS)
c7000 BladeSystem
Enclosure
EVA Disk Array
Redundant
Network
Links
Redundant
Fibre
Channel
Links