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

Changing the Server Complex Profile, How the Complex Profile is Updated

Page 37 highlights

The Complex Profile consists of three parts, or groups of data, which are described in detail in Table 1-5 (page 40): • "Stable Complex Configuration Data" (page 40) - This group contains complex-wide settings, including the complex name, serial number, the nPartition assignment for each cell, and other details that apply to the entire server complex. The Complex Profile contains one Stable Complex Configuration Data entry. • "Dynamic Complex Configuration Data" (page 40) - Architecturally reserved data. • "Partition Configuration Data" (page 40) - This group contains individual nPartition settings, including the nPartition name, core cell choices, and other details that are specific to an nPartition. The Complex Profile contains a Partition Configuration Data entry for each possible nPartition. (A server complex may have a maximum of sixteen nPartitions, globally numbered from 0-15.) The master copy of all parts of the Complex Profile resides on the service processor (MP or GSP) for the complex. Each cell in the complex also has a copy of the Stable Complex Configuration Data and a copy of the Partition Configuration Data for the nPartition to which it is assigned. The service processor (MP or GSP) in the server manages all Complex Profile data and keeps all copies of the data coherent using a locking mechanism, as described in the next sections. Changing the Server Complex Profile To modify the Complex Profile and thus change the server complex configuration, you use an administration tool such as Partition Manager or one of the nPartition commands. See "Administration Tools for nPartitions" (page 18) for details. You cannot directly edit the Complex Profile data for a server. The service processor maintains a set of locks that are used to ensure that only one set of changes to the Complex Profile occurs at a time. When you configure nPartitions, the administration tools you use revise the Complex Profile for the server in coordination with the service processor. The tools acquire and release locks as needed when modifying Complex Profile entries. You do not directly manage Complex Profile locks under normal circumstances, but you can force an entry to be unlocked if required. How the Complex Profile is Updated A server Complex Profile is updated when you use one of the nPartition administration tools (such as Partition Manager or commands) to create, modify, or delete an nPartition or modify complex-wide data. The general process by which changes to the Complex Profile occur is as follows: 1. An administrator uses an nPartition administration tool to request that a specific configuration change occurs. This is a request to create, modify, or delete an nPartition or modify complex-wide data such as the complex name. 2. The tool acquires a lock from the service processor (MP or GSP) for the Complex Profile entry that will be revised. The lock ensures that no other changes to the Complex Profile entry will occur while the tool revises it. If the entry already is locked, that Complex Profile entry cannot be updated and the request will fail and the tool exits with an error message. 3. The tool reads the Complex Profile entry whose lock it has acquired. 4. The tool revises the Complex Profile entry according to the administrator request. Complex Profile 37

  • 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

The Complex Profile consists of three parts, or groups of data, which are described in detail in
Table 1-5 (page 40)
:
“Stable Complex Configuration Data” (page 40)
— This group contains complex-wide
settings, including the complex name, serial number, the nPartition assignment for each
cell, and other details that apply to the entire server complex.
The Complex Profile contains one Stable Complex Configuration Data entry.
“Dynamic Complex Configuration Data” (page 40)
— Architecturally reserved data.
“Partition Configuration Data” (page 40)
— This group contains individual nPartition
settings, including the nPartition name, core cell choices, and other details that are specific
to an nPartition.
The Complex Profile contains a Partition Configuration Data entry for each possible
nPartition. (A server complex may have a maximum of sixteen nPartitions, globally numbered
from 0-15.)
The master copy of all parts of the Complex Profile resides on the service processor (MP or GSP)
for the complex. Each cell in the complex also has a copy of the Stable Complex Configuration
Data and a copy of the Partition Configuration Data for the nPartition to which it is assigned.
The service processor (MP or GSP) in the server manages all Complex Profile data and keeps all
copies of the data coherent using a locking mechanism, as described in the next sections.
Changing the Server Complex Profile
To modify the Complex Profile and thus change the server complex configuration, you use an
administration tool such as Partition Manager or one of the nPartition commands. See
“Administration Tools for nPartitions” (page 18)
for details. You cannot directly edit the Complex
Profile data for a server.
The service processor maintains a set of locks that are used to ensure that only one set of changes
to the Complex Profile occurs at a time.
When you configure nPartitions, the administration tools you use revise the Complex Profile for
the server in coordination with the service processor. The tools acquire and release locks as
needed when modifying Complex Profile entries. You do not directly manage Complex Profile
locks under normal circumstances, but you can force an entry to be unlocked if required.
How the Complex Profile is Updated
A server Complex Profile is updated when you use one of the nPartition administration tools
(such as Partition Manager or commands) to create, modify, or delete an nPartition or modify
complex-wide data.
The general process by which changes to the Complex Profile occur is as follows:
1.
An administrator uses an nPartition administration tool to request that a specific configuration
change occurs.
This is a request to create, modify, or delete an nPartition or modify complex-wide data
such as the complex name.
2.
The tool acquires a lock from the service processor (MP or GSP) for the Complex Profile
entry that will be revised.
The lock ensures that no other changes to the Complex Profile entry will occur while the
tool revises it.
If the entry already is locked, that Complex Profile entry cannot be updated and the request
will fail and the tool exits with an error message.
3.
The tool reads the Complex Profile entry whose lock it has acquired.
4.
The tool revises the Complex Profile entry according to the administrator request.
Complex Profile
37