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

11
Table 2: HP Integrity Blade Comparison
BL860c BL870c
Processor
Intel
®
Itanium
®
9100 Processors
2 Sockets
1.66 GHz/18MB FSB667
1.42GHz/12MB FSB533
1.6GHz/12MB FSB533, single-core
Note: 9000 series processor (Montecito)
also supported
Intel
®
Itanium
®
9100 Processors
4 Sockets
1.6 GHz/24MB FSB533
1.6 GHz/18MB FSB533
1.42 GHz/12MB FSB533
Chipset hp zx2
Memory
PC2-4200 DDR-SDRAM (533 MHz)
12 Sockets
48GB max (using 4GB DIMMs)
PC2-4200 DDR-SDRAM (533 MHz)
24 Sockets
192GB max (using 8GB DIMMs)
HDD and
Controller
2 SFF Hot-Plug SAS HDDs
HW RAID 1 support
4 SFF Hot-Plug SAS HDDs
HW RAID 1 support
Networking 4 Integrated Gigabit NICs
Management Integrity iLO 2 Advanced Pack
OS Support HP-UX 11i v3 and v2; OpenVMS; Linux (Red Hat and SUSE); and Windows
Enclosure
8 Server Blades in c7000
4 Server Blades in c3000
4 Server Blades in c7000
2 Server Blades in c3000
Mezzanine
Support
3 mezzanine cards
Choices: 4Gb FC; IB; PCI-e pass-thru; 4-
port NIC expansion
3 mezzanine cards
Choices: 4Gb FC, IB, 4-port NIC
expansion
Eliminating Single Points of Failure in HP BladeSystem
Configurations
Designing a system architecture that eliminates all hardware-related single points of failure is the first
step in achieving high availability for business and mission-critical applications. While there are many
components of the HP BladeSystem that are redundant, it is still possible to configure HP BladeSystem
solutions that have single points of failure (SPOFs). It is up to the system architect to carefully design
HP BladeSystem solutions that will mitigate these SPOFs before using Serviceguard to achieve the
highest levels of availability. This section will describe where SPOFs can occur in HP BladeSystem
configurations and how to avoid them. Once these SPOFs have been addressed from a hardware-