HP rp7440 nPartition Administrator's Guide, Second Edition - Page 25

Active and Inactive Cells, Cell Local Memory, Cell Property Details, system that does not support it. - quick

Page 25 highlights

as the active core cell, or if no core cell choices are specified, the nPartition attempts to select an eligible cell using a default process. Active and Inactive Cells Cells that are assigned to an nPartition and have booted to form an nPartition are active cells whose resources (processors, memory, and any attached I/O) can be actively used by software running in the nPartition. Cells that are inactive either are not assigned to an nPartition, or they have not participated in partition rendezvous to form an nPartition with any other cells assigned to the nPartition. (Partition rendezvous is the point during the nPartition boot process when all available cells in an nPartition join together to establish which cells are active for the current boot of the nPartition.) For example, a cell is inactive when it is powered off, has booted with a "n" use-on-next-boot value, or is assigned to an nPartition that has been reset to the shutdown for reconfig state. The resources belonging to inactive cells are not actively used by an nPartition. For a cell and its resources to be actively used the cell must boot and participate in partition rendezvous. Cell Local Memory On cell-based servers that are based on the HP sx1000 or sx2000 chipset, a portion of the memory in each cell can be configured as cell local memory (CLM), which is non-interleaved memory that can be quickly accessed by processors residing on the same cell as the memory. CAUTION: Memory configured as cell local memory only can be used by operating systems that support it. Any memory configured as cell local memory is unusable when an nPartition runs an operating system that does not support it. The nPartition management tools enable you to configure CLM for each cell either as a percentage of the total memory in the cell, or as an absolute number of gigabytes of memory. For details about configuring CLM see Chapter 3 (page 61). Cell Property Details Each cell has various properties that determine how the cell can be used and managed. To list the properties of cells in a server complex, you can use the parstatus -C command, parstatus -V -c# command, or Partition Manager. The parstatus -C command output includes cell property summaries such as the current assignments, usage, and I/O details for all cells in the complex. # parstatus -C [Cell] CPU Memory Use OK/ (GB) Core On Hardware Actual Deconf/ OK/ Cell Next Par Location Usage Max Deconf Connected To Capable Boot Num cab0,cell0 active core 4/0/4 8.0/ 0.0 cab 0,bay0,chassis1 yes yes 0 cab0,cell1 active base 4/0/4 8.0/ 0.0 - no yes 0 cab0,cell2 active base 4/0/4 8.0/ 0.0 cab 0,bay1,chassis3 yes yes 0 cab0,cell3 absent - - - - - - cab0,cell4 active core 2/0/4 4.0/ 0.0 cab 0,bay0,chassis3 yes yes 1 cab0,cell5 active base 2/0/4 4.0/ 0.0 - no yes 1 cab0,cell6 active base 2/0/4 4.0/ 0.0 cab 0,bay1,chassis1 yes yes 1 cab0,cell7 absent - - - - - - # nPartition Properties 25

  • 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
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266

as the active core cell, or if no core cell choices are specified, the nPartition attempts to select an
eligible cell using a default process.
Active and Inactive Cells
Cells that are assigned to an nPartition and have booted to form an nPartition are active cells
whose resources (processors, memory, and any attached I/O) can be actively used by software
running in the nPartition.
Cells that are inactive either are not assigned to an nPartition, or they have not participated in
partition rendezvous to form an nPartition with any other cells assigned to the nPartition.
(Partition rendezvous is the point during the nPartition boot process when all available cells in
an nPartition join together to establish which cells are active for the current boot of the nPartition.)
For example, a cell is inactive when it is powered off, has booted with a "n" use-on-next-boot
value, or is assigned to an nPartition that has been reset to the shutdown for reconfig state.
The resources belonging to inactive cells are not actively used by an nPartition. For a cell and its
resources to be actively used the cell must boot and participate in partition rendezvous.
Cell Local Memory
On cell-based servers that are based on the HP sx1000 or sx2000 chipset, a portion of the memory
in each cell can be configured as cell local memory (CLM), which is non-interleaved memory
that can be quickly accessed by processors residing on the same cell as the memory.
CAUTION:
Memory configured as cell local memory only can be used by operating systems
that support it.
Any memory configured as cell local memory is unusable when an nPartition runs an operating
system that does not support it.
The nPartition management tools enable you to configure CLM for each cell either as a percentage
of the total memory in the cell, or as an absolute number of gigabytes of memory.
For details about configuring CLM see
Chapter 3 (page 61)
.
Cell Property Details
Each cell has various properties that determine how the cell can be used and managed.
To list the properties of cells in a server complex, you can use the
parstatus -C
command,
parstatus -V -c
#
command, or Partition Manager.
The
parstatus -C
command output includes cell property summaries such as the current
assignments, usage, and I/O details for all cells in the complex.
#
parstatus -C
[Cell]
CPU
Memory
Use
OK/
(GB)
Core
On
Hardware
Actual
Deconf/ OK/
Cell
Next Par
Location
Usage
Max
Deconf
Connected To
Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 active core
4/0/4
8.0/ 0.0 cab 0,bay0,chassis1 yes
yes
0
cab0,cell1 active base
4/0/4
8.0/ 0.0 -
no
yes
0
cab0,cell2 active base
4/0/4
8.0/ 0.0 cab 0,bay1,chassis3 yes
yes
0
cab0,cell3 absent
-
-
-
-
-
-
cab0,cell4 active core
2/0/4
4.0/ 0.0 cab 0,bay0,chassis3 yes
yes
1
cab0,cell5 active base
2/0/4
4.0/ 0.0 -
no
yes
1
cab0,cell6 active base
2/0/4
4.0/ 0.0 cab 0,bay1,chassis1 yes
yes
1
cab0,cell7 absent
-
-
-
-
-
-
#
nPartition Properties
25