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

On cell-based HP Integrity, Installing and Managing HP-UX Virtual Partitions, vPars

Page 94 highlights

powered off when the OS issues a shutdown for reconfig command (for example, shutdown -h or shutdown /s). This is the normal behavior on HP rx7620, rx7640, rx8620, and rx8640 servers with a windows ACPI configuration setting. When softpowerdown is enabled on HP rx7620, rx7640, rx8620, and rx8640 servers, if one nPartition is defined in the server, then halting the OS powers off the server cabinet including all cells and I/O chassis. On HP rx7620, rx7640, rx8620, and rx8640 servers with multiple nPartitions, halting the OS from an nPartition with softpowerdown enabled causes only the resources on the local nPartition to be powered off. To power on hardware that has been powered off, use the PE command at the management processor Command menu. - acpiconfig disable softpowerdown When set on HP rx7620, rx7640, rx8620, and rx8640 servers, acpiconfig disable softpowerdown causes nPartition cells to remain at a boot-is-blocked state when the OS issues a shutdown for reconfig command (for example, shutdown -h or shutdown /s). In this case an OS shutdown for reconfig makes the nPartition inactive. This is the normal behavior on HP rx7620, rx7640, rx8620, and rx8640 servers with an ACPI configuration setting of default or single-pci-domain. To make an inactive nPartition active, use the management processor BO command to boot the nPartition past the boot-is-blocked state. • Boot Modes on HP Integrity nPartitions: nPars and vPars Modes On cell-based HP Integrity servers, each nPartition can be configured in either of two boot modes: - nPars Boot Mode In nPars boot mode, an nPartition is configured to boot any single operating system in the standard environment. When an nPartition is in nPars boot mode, it cannot boot the vPars monitor and therefore does not support HP-UX virtual partitions. - vPars Boot Mode In vPars boot mode, an nPartition is configured to boot into the vPars environment. When an nPartition is in vPars boot mode, it can only boot the vPars monitor and therefore it only supports HP-UX virtual partitions and it does not support booting HP OpenVMS I64, Microsoft Windows, or other operating systems. On an nPartition in vPars boot mode, HP-UX can boot only within a virtual partition (from the vPars monitor) and cannot boot as a standalone, single operating system in the nPartition. CAUTION: An nPartition on an HP Integrity server cannot boot HP-UX virtual partitions when in nPars boot mode. Likewise, an nPartition on an HP Integrity server cannot boot an operating system outside of a virtual partition when in vPars boot mode. To check or set the boot mode for an nPartition on a cell-based HP Integrity server, use any of the following tools as appropriate. Refer to Installing and Managing HP-UX Virtual Partitions (vPars), Sixth Edition, for details, examples, and restrictions. 94 Booting and Resetting nPartitions

  • 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

powered off when the OS issues a shutdown for reconfig command (for example,
shutdown -h
or
shutdown /s
).
This is the normal behavior on HP rx7620, rx7640, rx8620, and rx8640 servers with a
windows
ACPI configuration setting.
When softpowerdown is enabled on HP rx7620, rx7640, rx8620, and rx8640 servers, if
one nPartition is defined in the server, then halting the OS powers off the server cabinet
including all cells and I/O chassis. On HP rx7620, rx7640, rx8620, and rx8640 servers
with multiple nPartitions, halting the OS from an nPartition with softpowerdown
enabled causes only the resources on the local nPartition to be powered off.
To power on hardware that has been powered off, use the
PE
command at the
management processor Command menu.
acpiconfig disable softpowerdown
When set on HP rx7620, rx7640, rx8620, and rx8640
servers,
acpiconfig disable softpowerdown
causes nPartition cells to remain
at a boot-is-blocked state when the OS issues a shutdown for reconfig command (for
example,
shutdown -h
or
shutdown /s
). In this case an OS shutdown for reconfig
makes the nPartition inactive.
This is the normal behavior on HP rx7620, rx7640, rx8620, and rx8640 servers with an
ACPI configuration setting of
default
or
single-pci-domain
.
To make an inactive nPartition active, use the management processor
BO
command to
boot the nPartition past the boot-is-blocked state.
Boot Modes on HP Integrity nPartitions: nPars and vPars Modes
On cell-based HP Integrity
servers, each nPartition can be configured in either of two boot modes:
nPars
Boot Mode
In
nPars
boot mode, an nPartition is configured to boot any single operating system
in the standard environment. When an nPartition is in
nPars
boot mode, it cannot boot
the vPars monitor and therefore does not support HP-UX virtual partitions.
vPars
Boot Mode
In
vPars
boot mode, an nPartition is configured to boot into the vPars environment.
When an nPartition is in
vPars
boot mode, it can only boot the vPars monitor and
therefore it only supports HP-UX virtual partitions and it does not support booting HP
OpenVMS I64, Microsoft Windows, or other operating systems. On an nPartition in
vPars
boot mode, HP-UX can boot only within a virtual partition (from the vPars
monitor) and cannot boot as a standalone, single operating system in the nPartition.
CAUTION:
An nPartition on an HP Integrity server cannot boot HP-UX virtual partitions
when in
nPars
boot mode. Likewise, an nPartition on an HP Integrity server cannot boot
an operating system outside of a virtual partition when in
vPars
boot mode.
To check or set the boot mode for an nPartition on a cell-based HP Integrity server, use any
of the following tools as appropriate. Refer to
Installing and Managing HP-UX Virtual Partitions
(vPars)
, Sixth Edition, for details, examples, and restrictions.
94
Booting and Resetting nPartitions