Service manual

System Overview 1-35
Applying the rules in Table 1–4 to a GS320 with eight QBBs, a customer might
set up a system as shown in Table 1–5. Such a system has three hard partitions
each with the required resources to run an operating system. The configuration
shows that hard partitions are confined to QBB boundaries and that no
resources are shared across partitions.
Table 1– 5 Possible 32-P Hard Partitioned System
Partition 0 Partition 1 Partition 2
QBB0 & 1
(CPUs 0-7)
QBB2 & 3
(CPUs 8-15)
QBB4 – QBB7
(CPUs 16-31)
4 PCI boxes -2
with STD I/Os
4 PCI boxes -2
with STD I/Os
8 PCI boxes -
2 with STD I/Os
Memory in
QBB0 & 1
Memory in
QBB2 & 3
Memory in
QBB4 - 7
Results of Hard Partitioning
1. A hard partition is a subset of system resources capable of running an
operating system.
2. Partitions are isolated from each other and know nothing about another’s
existence.
3. Errors: See Section 3.11.
• All errors that are faults crash all partitions.
• Uncorrectable errors that are not faults affect only the hard partition
experiencing the error.
• Correctable errors affect only the hard partition experiencing the error.
4. From an SRM console/operating system point of view, partitions look alike –
QBBs, CPUs, memory, and IOPs are numbered starting with 0.
NOTE: Result 4 can lead to confusion. Say two partitions with two QBBs in
each have been created in a system with four QBBs (0-3). If you issue
the command $ stop/cpu/poweroff 7 in one partition, the command
may target CPU3 in QBB1. If you issue the same command in the other
partition, the command may target CPU3 in QBB3. To minimize this
effect, create a hardware drawing of the partitions to help translate
software IDs to physical locations.