HP Integrity Superdome 2 8/16 HP Superdome 2 Partitioning Administrator Guide - Page 80

Counts Summary, Parspec change policy, A note on Deconfiguration

Get HP Integrity Superdome 2 8/16 PDF manuals and user guides View all HP Integrity Superdome 2 8/16 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 80 highlights

Table 7-3 Resource syntax summary Resource CPU I/O Memory Forms Options cpu:cpu_path -a, -d cpu::num -a, -m, -d cpu:::{min}:{max} -m socket:socket_id:cpu::num -a, -d, -m -- or -- core:core_path -a, -d core::num -a, -d, -m core:::{min}:{max} -m socket:socket_id:core::num -a, -d, -m io:io_path -a, -d, -m ioslot:ioslot_path -a, -d, -m mem::ilm_size -a, -d, -m socket:socket_id:mem::slm_size -a, -d, -m # times/command Multiple Once Once Once per socket_id Multiple Once Once Once per socket_id Multiple Multiple Once Once per socket_id Counts Summary • At all times, the rule of min

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
Table 7-3 Resource syntax summary
# times/command
Options
Forms
Resource
Multiple
-a, -d
cpu:
cpu_path
CPU
Once
-a, -m, -d
cpu::
num
Once
-m
cpu:::
{min}:{max}
Once per socket_id
-a, -d, -m
socket:
socket_id
:cpu::
num
-- or --
Multiple
-a, -d
core:
core_path
Once
-a, -d, -m
core::
num
Once
-m
core:::
{min}:{max}
Once per socket_id
-a, -d, -m
socket:
socket_id
:core::
num
Multiple
-a, -d, -m
io:
io_path
I/O
Multiple
-a, -d, -m
ioslot:
ioslot_path
Once
-a, -d, -m
mem::
ilm_size
Memory
Once per socket_id
-a, -d, -m
socket:
socket_id:mem::slm_size
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.
Parspec change policy
The “parspec change policy” is an attribute of an nPar which the user can enable or disable. By
default, it is enabled. The parspec change policy determines whether the OA can automatically
modify a parspec in order to enable a partition operation (such as booting). In some scenarios,
it is possible that 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 hardware architecture. Under these circumstances,
the partition configuration in the parspec may need to be modified to make forward progress.
The parspec change policy attribute of the nPar gives the customer the ability to choose the
behavior in these cases. If the parspec change policy is enabled (default), the affected partition
operation is continued with 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 the scenario where the memory granularity specified by the user cannot
be accommodated by the system and a new memory granularity value has to be applied. This
is likely to affect the vPar memory sizes specified by the user and stored in the parspec since
they will have to be rounded up to be a multiple of the new memory granularity. Users may
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 that case, they would have 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
80
Planning Your System for Virtual Partitions