2-8 instant Capacity on Demand Notes for Installation and Use
start a replacement CPU each time the system is booted until the faulty CPU is
replaced.
5.3 Partitioning
You must reinstall the iCAP software after a system is repartitioned. If a iCAP
system is to be partitioned, uninstall the iCAP software, partition the system,
and then reinstall the iCAP software on all of the new partitions. It is up to the
person who partitions the system to ensure that only the CPUs that have been
purchased are used within the partitions. Once the iCAP software has been
uninstalled, you must delete the iCAP data file
(SYS$SYSTEM:iCAP$DATA.DAT) so that your environment will be correctly
configured.
For more information about partitioning, refer to the OpenVMS Alpha
Partitioning and Galaxy Guide.
5.4 Accidental iCAP CPU Activation
If someone accidentally activates a iCAP CPU, you can modify the number of
iCAP CPUs back to the original number by using the following command:
$ @SYS$SYSTEM:iCAP$SYSTEM MODIFY
This command should be used only to rectify accidental activations. If you wish
to START or STOP a CPU, use the DCL commands
START/CPU [n] or STOP/CPU [n]
6.0 Platform Caveats
6.1 GS80, GS160 and GS320
On a traditional symmetrical multiprocessor (SMP) system such as the
GS140E, all CPUs are numbered sequentially and access time to system
memory from any CPU is equivalent. Therefore, it does not matter in which
order CPUs are put online. When you enter a START/CPU command without
specifying a specific CPU, the first inactive CPU that is encountered is started
up.
However, on NUMA architecture systems, you must consider the NUMA
hardware characteristics and your Quad Building Block (QBB) and CPU
configuration before starting a new CPU. Memory access speeds can vary
depending on whether the memory being accessed resides on the same QBB as
the new CPU. There must be at least one CPU online in each QBB to handle
Kommentare zu diesen Handbüchern