Counts Summary; Parspec Change Policy; A Note On Deconfiguration - HP Integrity Superdome 2 16-socket Administrator's Manual

Table 9 Resource syntax summary
Resource
CPU
I/O
Memory

Counts Summary

At all times, the rule of min<=total<=max is enforced.
The first field is always one of the (case-insensitive) strings: cpu, core, io, ioslot, mem, or socket.
num, min, and max are all positive integers. num can be 0 in the case of —m.

Parspec change policy

The "parspec change policy" is an attribute of an nPar that the user can enable or disable. By
default, it is enabled. The parspec change policy determines whether the OA can automatically
modify a parspec to enable a partition operation (such as booting). In some scenarios, the system
cannot meet the customer requested resource or attribute specifications in the parspec for an nPar
or vPar. This could be due to non-existent resources or degraded resources or other restrictions in
the hardware architecture. Under these circumstances, the partition configuration in the parspec
might need to be modified to make progress. The parspec change policy attribute of the nPar
enables you to choose the behavior in these cases. If the parspec change policy is enabled (default),
the affected partition operation is continued with the available or modified resources or attributes
after making the required changes in the parspec. If the parspec change policy is disabled, the
affected partition operation is failed and no changes are made to the parspec.
For example, consider a scenario where the memory granularity specified by the user cannot be
accommodated by the system and a new memory granularity value must be applied. This is likely
to affect the vPar memory sizes specified by the user and stored in the parspec because they will
have to be rounded up to be a multiple of the new memory granularity. Users might want to make
vPar memory size adjustments manually and not have the system make any changes in the vPar
memory sizes they have assigned. In such cases, they need to disable the parspec change policy
for the nPar before they configure and boot vPars.

A note on Deconfiguration

On a vPars system, when a virtual partition with parspec change policy disabled goes down and
contains a deconfigured or deactivated CPU, the partition controller on the OA will try to
decommission the CPU from use and replace it with another good CPU, if possible. If this is not
possible, the partition controller will not allow the partition to boot until the user modifies the vPar
Forms
cpu:cpu_path
cpu::num
cpu:::{min}:{max}
socket:socket_id:cpu::num
-- or --
core:core_path
core::num
core:::{min}:{max}
socket:socket_id:core::num
io:io_path
ioslot:ioslot_path
mem::ilm_size
socket:socket_id:mem::slm_size
Options
-a, -d
-a, -m, -d
-m
-a, -d, -m
-a, -d
-a, -d, -m
-m
-a, -d, -m
-a, -d, -m
-a, -d, -m
-a, -d, -m
-a, -d, -m
Planning Your Virtual Partitions
# times/command
Multiple
Once
Once
Once per socket_id
Multiple
Once
Once
Once per socket_id
Multiple
Multiple
Once
Once per socket_id
87