nPartition Administrator's Guide
Complex Profile Entry Locking and Unlocking
Each Complex Profile entry has its own lock which is used to restrict access to the entry. If
necessary you can manually unlock Complex Profile entries, however in nearly all situations
you instead should allow the administration tools to automatically acquire and release locks.
CAUTION: You should generally avoid manually unlocking Complex Profile entries because
doing so can can result in the loss of configuration changes.
The locks for Complex Profile entries are managed as described here.
• For the Stable Complex Configuration Data entry, there are slight differences in the locking
mechanisms on HP 9000 and HP Integrity servers.
— On cell-based HP 9000 servers, the Stable Complex Configuration Data has a single
lock.
— On cell-based HP Integrity servers, the Stable Complex Configuration Data has two
separate locks: a "read lock" for restricting read access to the current Stable Complex
Configuration Data entry, and a "write lock" for restricting access to a modifiable copy
of the Stable Complex Configuration Data.
• On both HP 9000 and HP Integrity cell-based servers there is one lock for each Partition
Configuration Data entry (each nPartition has its own Partition Configuration Data entry).
The parunlock command and the service processor RL command enable you to manually
unlock Complex Profile entries.
It can be necessary to manually unlock a Complex Profile entry in the situation where an nPartition
configuration tool such as Partition Manager has prematurely exited. If such a tool exits before
it sends revised Complex Profile entries and corresponding lock keys back to the service processor,
the entries that the tool locked will remain locked indefinitely (until they are manually unlocked).
Manually Unlocking a Complex Profile Entry You can manually unlock Complex Profile entries
after an nPartition configuration tool has exited before unlocking the entries it had locked. In
this situation an attempt to modify the nPartition or complex-wide setting will fail because the
Complex Profile entries still are locked. If you are certain no authorized users are changing
configurations, use the parunlock command or the service processor RL command to unlock
the entries. After they are unlocked you can perform the modifications you had previously
attempted. For details see “Unlocking Complex Profile Entries” (page 199).
Aborting a Complex Profile Change A pending update of the Complex Profile can be canceled
or prevented by clearing the lock for a Complex Profile entry before the service processor has
pushed out the revised data for the entry. This occurs, for example, when you have issued a
request to change the nPartition assignment of an active cell and then manually unlock the
effected Complex Profile entries before performing a reboot for reconfig of the nPartition to
which the cell is assigned. For details see “Canceling Pending Changes to the Complex Profile”
(page 201).
Complex Profile Group Details
Table 1-5 lists details of the three groups of data that comprise the Complex Profile.
Complex Profile 39