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

Genesis Partition, Basics of nPartition Modification

Page 30 highlights

example, by the -u... -h... set of options). For remote administration using IPMI over LAN the tool remotely accesses the service processor of the target complex (for example, by the -g... -h... set of options). For remote administration details see "Remote and Local Management of nPartitions" (page 41). For detailed procedures for creating and managing nPartitions see Chapter 6 (page 165). Genesis Partition The Genesis Partition is the initial, one-cell nPartition created within a server complex by the service processor (MP or GSP) CC command. The Genesis Partition is just like any other nPartition except for how it is created and the fact that its creation wipes out any previous nPartition configuration data. For a detailed procedure see "Creating a Genesis Partition" (page 170). If your server complex has its nPartitions pre-configured by HP, you do not need to create a Genesis Partition. NOTE: For servers based on the HP sx1000 or sx2000 chipset, you can instead use nPartition tools running on a remote system to remotely create and configure new nPartitions (including the first nPartition in the complex). See "Remote and Local Management of nPartitions" (page 41) for details. You can use nPartition management tools running on the Genesis Partition as the method for configuring all nPartitions in the complex. The Genesis Partition always is partition number 0. When it is first created, the Genesis Partition consists of one cell that is connected to an I/O chassis that has core I/O installed. The Genesis Partition also should have a bootable disk (or a disk onto which you can install an operating system). If an operating system is not installed on any disks in the Genesis Partition, you can boot the Genesis partition to the system boot interface (either BCH or EFI) and from that point install an operating system. This installation requires either having access to an installation server, or to a CD drive (or DVD drive) attached to an I/O chassis belonging to the nPartition. After you boot an operating system on the Genesis Partition, you can modify the nPartition to include additional cells. You also can create other, new nPartitions and can modify them from the Genesis Partition or from any other nPartition that has an operating system with the nPartition tools installed. Basics of nPartition Modification Modifying an nPartition involves using an nPartition administration tool to revise one or more parts of the server Complex Profile data, which determines how hardware is assigned to and used by nPartitions. The Complex Profile is discussed in "Complex Profile" (page 36). For detailed procedures see Chapter 6 (page 165). You can modify an nPartition either locally or remotely. • For local administration, use nPartition Commands or Partition Manager from an nPartition in the same complex as the nPartition to be modified. Some nPartition details also can be modified locally from an nPartition console by using EFI Shell commands or BCH menu commands. • For remote administration, use remote administration features of the Enhanced nPartition Commands or Partition Manager Version 2.0. You can use either of two methods for remote administration: WBEM and IPMI over LAN. 30 Getting Started with 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

example, by the
-u... -h...
set of options). For remote administration using IPMI
over LAN the tool remotely accesses the service processor of the target complex (for
example, by the
-g... -h...
set of options).
For remote administration details see
“Remote and Local Management of nPartitions”
(page 41)
.
For detailed procedures for creating and managing nPartitions see
Chapter 6 (page 165)
.
Genesis Partition
The Genesis Partition is the initial, one-cell nPartition created within a server complex by the
service processor (MP or GSP)
CC
command. The Genesis Partition is just like any other nPartition
except for how it is created and the fact that its creation wipes out any previous nPartition
configuration data.
For a detailed procedure see
“Creating a Genesis Partition” (page 170)
.
If your server complex has its nPartitions pre-configured by HP, you do not need to create a
Genesis Partition.
NOTE:
For servers based on the HP sx1000 or sx2000 chipset, you can instead use nPartition
tools running on a remote system to remotely create and configure new nPartitions (including
the first nPartition in the complex).
See
“Remote and Local Management of nPartitions” (page 41)
for details.
You can use nPartition management tools running on the Genesis Partition as the method for
configuring all nPartitions in the complex. The Genesis Partition always is partition number 0.
When it is first created, the Genesis Partition consists of one cell that is connected to an I/O chassis
that has core I/O installed. The Genesis Partition also should have a bootable disk (or a disk onto
which you can install an operating system).
If an operating system is not installed on any disks in the Genesis Partition, you can boot the
Genesis partition to the system boot interface (either BCH or EFI) and from that point install an
operating system. This installation requires either having access to an installation server, or to a
CD drive (or DVD drive) attached to an I/O chassis belonging to the nPartition.
After you boot an operating system on the Genesis Partition, you can modify the nPartition to
include additional cells. You also can create other, new nPartitions and can modify them from
the Genesis Partition or from any other nPartition that has an operating system with the nPartition
tools installed.
Basics of nPartition Modification
Modifying an nPartition involves using an nPartition administration tool to revise one or more
parts of the server Complex Profile data, which determines how hardware is assigned to and
used by nPartitions. The Complex Profile is discussed in
“Complex Profile” (page 36)
.
For detailed procedures see
Chapter 6 (page 165)
.
You can modify an nPartition either locally or remotely.
For local administration, use nPartition Commands or Partition Manager from an nPartition
in the same complex as the nPartition to be modified. Some nPartition details also can be
modified locally from an nPartition console by using EFI Shell commands or BCH menu
commands.
For remote administration, use remote administration features of the Enhanced nPartition
Commands or Partition Manager Version 2.0.
You can use either of two methods for remote administration: WBEM and IPMI over LAN.
30
Getting Started with nPartitions