HP Server rp7405 nPartition Administrator's Guide, Second Edition - Page 172

Creating a New nPartition, environment: either Boot Console Handler BCH

Get HP Server rp7405 PDF manuals and user guides View all HP Server rp7405 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 172 highlights

You can confirm that the Genesis Partition was successfully created if the CC command reports that the "complex profile will be modified". If the CC command reports "Sorry, command failed", then the Genesis Partition was not created, possibly because one or more nPartitions are not at the shutdown for reconfig state. If this is the case, go back to Step 3 and ensure all nPartitions are inactive at the shutdown for reconfig state. 7. Issue the BO command to boot the Genesis Partition past its shutdown for reconfig state and make it an active nPartition. When a Genesis Partition is created, it remains at boot-is-blocked (in an inactive, shutdown for reconfig state), so you must boot it manually. The Genesis Partition always is assigned partition number 0, because when it is created it is the first and only nPartition in the server complex. Using the BO command to boot partition 0 will boot the Genesis Partition to its system boot environment: either Boot Console Handler (BCH, on HP 9000 servers) or Extensible Firmware Interface (EFI, on HP Integrity servers). GSP:CM> BO This command boots the selected partition. # Name --- ---- 0) Partition 0 Select a partition number : 0 Do you want to boot partition number 0, named Partition 0 ? (Y/[N]) y -> The selected partition will be booted. GSP:CM> 8. Access the console for the Genesis Partition and configure the nPartition as appropriate and necessary. From the service processor Command menu, enter MA to return to the Main menu, then enter CO to access the Console menu. The Genesis Partition is partition 0 and by default is named "Partition 0". You will need to set the boot paths or options, any core cell choices, the nPartition name, and other settings as appropriate. You also may need to add cells to the Genesis Partition if you want it to have more than one cell. Creating a New nPartition You can create a new nPartition by using any one of the following procedures: • "Creating a New nPartition (nPartition Commands)" (page 173) • "Creating a New nPartition (Partition Manager)" (page 175) Creating a new nPartition involves specifying one or more cells in a server complex, setting various attributes for the cells, and optionally specifying other nPartition settings. The settings you specify then are used to create a new nPartition, which has assigned to it the cells you selected. At least one cell in each nPartition must be connected to an I/O chassis that has core I/O attached. To boot an operating system from disk, the nPartition also must have a boot device and associated PCI card. When creating an nPartition, follow the HP nPartition requirements and guidelines. HP recommends only specific sets of nPartition configurations. 172 Creating and Configuring 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
You can confirm that the Genesis Partition was successfully created if the
CC
command
reports that the "complex profile will be modified".
If the
CC
command reports "Sorry, command failed", then the Genesis Partition was not
created, possibly because one or more nPartitions are not at the shutdown for reconfig state.
If this is the case, go back to Step 3 and ensure all nPartitions are inactive at the shutdown
for reconfig state.
7.
Issue the
BO
command to boot the Genesis Partition past its shutdown for reconfig state and
make it an active nPartition.
When a Genesis Partition is created, it remains at boot-is-blocked (in an inactive, shutdown
for reconfig state), so you must boot it manually.
The Genesis Partition always is assigned partition number 0, because when it is created it
is the first and only nPartition in the server complex.
Using the
BO
command to boot partition 0 will boot the Genesis Partition to its system boot
environment: either Boot Console Handler (BCH, on HP 9000 servers) or Extensible Firmware
Interface (EFI, on HP Integrity servers).
GSP:CM>
BO
This command boots the selected partition.
#
Name
---
----
0)
Partition 0
Select a partition number :
0
Do you want to boot partition number 0,
named Partition 0 ? (Y/[N])
y
-> The selected partition will be booted.
GSP:CM>
8.
Access the console for the Genesis Partition and configure the nPartition as appropriate and
necessary.
From the service processor Command menu, enter
MA
to return to the Main menu, then
enter
CO
to access the Console menu. The Genesis Partition is partition 0 and by default is
named "Partition 0".
You will need to set the boot paths or options, any core cell choices, the nPartition name,
and other settings as appropriate. You also may need to add cells to the Genesis Partition if
you want it to have more than one cell.
Creating a New nPartition
You can create a new nPartition by using any one of the following procedures:
•
“Creating a New nPartition (nPartition Commands)” (page 173)
•
“Creating a New nPartition (Partition Manager)” (page 175)
Creating a new nPartition involves specifying one or more cells in a server complex, setting
various attributes for the cells, and optionally specifying other nPartition settings. The settings
you specify then are used to create a new nPartition, which has assigned to it the cells you selected.
At least one cell in each nPartition must be connected to an I/O chassis that has core I/O attached.
To boot an operating system from disk, the nPartition also must have a boot device and associated
PCI card.
When creating an nPartition, follow the HP nPartition requirements and guidelines. HP
recommends only specific sets of nPartition configurations.
172
Creating and Configuring nPartitions