Information Technology Reference
In-Depth Information
the concept of a CPU is defined as a physical CPU socket, which is the primary
definition used for Dynamic Domains. This is not the definition used by Oracle
Solaris when it numbers and counts CPUs.
8.1.1 M9000 Configuration Example
Although the M9000 is the largest M-Series server in the series, it is actually easier
to configure than the M5000 due to the smaller number of memory configuration
permutations possible. This advantage is balanced by the less flexible memory
population rules, which dictate only 16 or 32 DIMMs per CMU. These trade-offs
will become more obvious while working through the example.
The desired outcome of this exercise is as follows:
Configure an M9000 with five domains.
Two domains should have 6 CPUs, 128 GB of memory, 4 Gigabit Ethernet
(GbE) ports, and 2 8 Gb Fiber Channel (FC) cards, and should use internal
boot disks. Call these Domains 1 and 2.
Two domains should have 4 CPUs, 256 GB of memory, 4 GbE ports, and
2 8 Gb FC cards, and should use internal boot disks. Call these Domains
3 and 4.
One domain should have 4 CPUs, 64 GB of memory, and 2 GbE ports, and
should use internal boot disks. Call this Domain 5. Some resources from
this domain must be available for the other domains on an as-needed basis.
The domains with 4 CPUs must be able to have CPUs removed without hav-
ing to shut down first.
Provide room for 25% growth.
Domains requiring 6 CPUs can be configured in two different ways:
A four-CPU CMU in Uni-XSB mode along with two XSBs from a four-CPU
CMU in Quad-XSB mode
A four-CPU CMU in Uni-XSB mode along with a two-CPU CMU in Uni-XSB
mode
There are trade-offs between these two options. Sharing a four-CPU CMU board
reduces the solution cost, but creates a single point of failure for two domains.
Combining the four-CPU and two-CPU CMU boards is more expensive, but does
provide for complete hardware isolation between the domains. Both options will
be discussed here.
 
 
Search WWH ::




Custom Search