HP 9000 rp7410 nPartition Administrator's Guide, Second Edition - Page 27

Active and Inactive nPartition Boot States, Overview of Managing nPartitions

Page 27 highlights

Active and Inactive nPartition Boot States Each nPartition has a boot state of either active or inactive. The boot state indicates whether the nPartition has booted so that it may be interactively accessed through its console (active nPartitions) or if it cannot be used interactively (inactive nPartitions) You can use the parstatus -P command or Partition Manager to list all nPartitions and their boot states (active or inactive status). # parstatus -P [Partition] Par # of # of I/O Num Status Cells Chassis Core cell Partition Name (first 30 chars) 0 inactive 2 1 ? feshd5a 1 active 2 1 cab1,cell2 feshd5b # Likewise, you can view nPartition boot states using the Virtual Front Panel, which is available from the service processor Main menu for the server complex. Active nPartition An nPartition that is active has at least one core-capable cell that is active (not in a boot-is-blocked state). When an nPartition is active, one or more of the cells assigned to the nPartition have completed partition rendezvous and the system boot interface (the BCH or EFI environment) has loaded and been displayed through the nPartition console. An operating system can be loaded and run from the system boot interface on an active nPartition. Inactive nPartition An inactive nPartition is considered to be in the shutdown for reconfig state, because all cells assigned to the nPartition either remain at a boot-is-blocked state or are powered off. To make an inactive nPartition active, use the BO command at the service processor (MP or GSP) Command menu. The BO command clears the boot-is-blocked flag for all cells assigned to the nPartition, thus allowing the cells to rendezvous and enabling the nPartition to run the system boot interface. (If all cells assigned to an nPartition are powered off, you must power on its cells to enable the nPartition to become active.) To make an nPartition inactive perform a shutdown for reconfig. You can issue commands from the operating system, the system boot interface (BCH or EFI), or the service processor (MP or GSP) Command menu. All three methods reboot an nPartition and hold all of its cells at boot-is-blocked; as a result the nPartition is shutdown for reconfig (placed in an inactive state). For details see Chapter 5 (page 87). Overview of Managing nPartitions This section provides overviews of common nPartition management tasks. The following task overviews are given here: • "Basics of Listing nPartition and Complex Status" • "Basics of nPartition Creation" • "Basics of nPartition Modification" • "Basics of nPartition Booting and Resetting" Basics of Listing nPartition and Complex Status You can list server complex hardware details and nPartition configuration details using the following tools and commands. Overview of Managing nPartitions 27

  • 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

Active and Inactive nPartition Boot States
Each nPartition has a boot state of either active or inactive.
The boot state indicates whether the nPartition has booted so that it may be interactively accessed
through its console (active nPartitions) or if it cannot be used interactively (inactive nPartitions)
You can use the
parstatus -P
command or Partition Manager to list all nPartitions and their
boot states (active or inactive status).
#
parstatus -P
[Partition]
Par
# of
# of I/O
Num Status
Cells Chassis
Core cell
Partition Name (first 30 chars)
=== ============ ===== ======== ========== ===============================
0
inactive
2
1
?
feshd5a
1
active
2
1
cab1,cell2 feshd5b
#
Likewise, you can view nPartition boot states using the Virtual Front Panel, which is available
from the service processor Main menu for the server complex.
Active nPartition
An nPartition that is active has at least one core-capable cell that is active (not
in a boot-is-blocked state). When an nPartition is active, one or more of the cells assigned to the
nPartition have completed partition rendezvous and the system boot interface (the BCH or EFI
environment) has loaded and been displayed through the nPartition console. An operating system
can be loaded and run from the system boot interface on an active nPartition.
Inactive nPartition
An inactive nPartition is considered to be in the shutdown for reconfig state,
because all cells assigned to the nPartition either remain at a boot-is-blocked state or are powered
off.
To make an inactive nPartition active, use the
BO
command at the service processor (MP or GSP)
Command menu. The
BO
command clears the boot-is-blocked flag for all cells assigned to the
nPartition, thus allowing the cells to rendezvous and enabling the nPartition to run the system
boot interface. (If all cells assigned to an nPartition are powered off, you must power on its cells
to enable the nPartition to become active.)
To make an nPartition inactive perform a shutdown for reconfig. You can issue commands from
the operating system, the system boot interface (BCH or EFI), or the service processor (MP or
GSP) Command menu. All three methods reboot an nPartition and hold all of its cells at
boot-is-blocked; as a result the nPartition is shutdown for reconfig (placed in an inactive state).
For details see
Chapter 5 (page 87)
.
Overview of Managing nPartitions
This section provides overviews of common nPartition management tasks.
The following task overviews are given here:
“Basics of Listing nPartition and Complex Status”
“Basics of nPartition Creation”
“Basics of nPartition Modification”
“Basics of nPartition Booting and Resetting”
Basics of Listing nPartition and Complex Status
You can list server complex hardware details and nPartition configuration details using the
following tools and commands.
Overview of Managing nPartitions
27