Single System
Single System
Single System
Single System
High Availability
High Availability
High Availability
High Availability
36
Each cell should have at least two active CPUs.
37
Each cell should have at least 4 GB (8 DIMMs) of memory using 512-MB DIMMs and at least
8 GB of memory using 1-GB DIMMs.
38
I/O chassis ownership must be localized as much as possible. One way is to assign I/O chassis
to partitions in sequential order starting from INSIDE the single cabinet, then out to the I/O
expansion cabinet 'owned' by the single cabinet.
39
I/O expansion cabinets can be used only when the main system cabinet holds maximum
number of I/O card cages. Thus, the cabinet must first be filled with I/O card cages before
using an I/O expansion cabinet.
40
Single cabinets connected to form a dual cabinet (using flex cables) should use a single I/O
expansion cabinet if possible.
41
Spread enough connections across as many I/O chassis as it takes to become 'redundant' in
I/O chassis'. In other words, if an I/O chassis fails, the remaining chassis have enough
connections to keep the system up and running, or in the worst case, have the ability to reboot
with the connections to peripherals and networking intact.
42
All SCSI cards are configured in the factory as unterminated. Any auto termination is defeated.
If auto termination is not defeatable by hardware, the card is not used at first release.
Terminated cable would be used for connection to the first external device. In the factory and
for shipment, no cables are connected to the SCSI cards. In place of the terminated cable, a
terminator is placed on the cable port to provide termination until the cable is attached. This is
needed to allow HP-UX to boot. The customer does not need to order the terminators for these
factory integrated SCSI cards, since the customer will probably discard them. The terminators
are provided in the factory by use of constraint net logic.
43
Partitions whose I/O chassis are contained within a single cabinet have higher availability than
those partitions that have their I/O chassis spread across cabinets.
44
A partition's core I/O chassis should go in a system cabinet, not an I/O expansion cabinet
45
A partition should be connected to at least two I/O chassis containing Core I/O cards. This
implies that all partitions should be at least 2 cells in size. The lowest number cell or I/O
chassis is the 'root' cell; the second lowest number cell or I/O chassis combo in the partition is
the 'backup root' cell.
46
A partition should consist of at least two cells.
47
Not more than one partition should span a cabinet or a crossbar link. When crossbar links are
shared, the partition is more at risk relative to a crossbar failure that may bring down all the
cells connected to it.
Multi-System
Multi-System
Multi-System
Multi-System
High Availability
High Availability
High Availability
High Availability
(Please also refer
to Multi-System
High Availability
section following
this table)
48
Multi-initiator support is required for Serviceguard.
QuickSpecs
HP Integrity Superdome Servers 16-socket, 32-socket,
HP Integrity Superdome Servers 16-socket, 32-socket,
HP Integrity Superdome Servers 16-socket, 32-socket,
HP Integrity Superdome Servers 16-socket, 32-socket,
and 64-socket
and 64-socket
and 64-socket
and 64-socket
Configuration
DA - 11717 Worldwide — Version 20 — May 3, 2005
Page 36