You can cancel a pending change to the Stable Complex Configuration
Data for a cell-based server by unlocking the the Stable Complex Configuration
Data before the service processor has pushed out the revised data for the
entry.
For example, you can abort a cell assignment change when
you have issued a request to unassign an active cell but manually unlock the
effected Complex Profile entries before performing a reboot for reconfig of
the nPartition to which the cell originally is assigned.
For background details see “Complex Profile”.
 |
| |
|
 | CAUTION: You should generally avoid manually unlocking Complex Profile
entries because doing so can can result in the loss of configuration changes. |
|
| |
|
Procedure 6-26 Aborting Cell Assignment Changes
You can cancel a pending change to an active cell by using
this procedure. Only changes involving the unassignment (deletion) of an active
cell from an nPartition can practically be canceled.
After issuing
a request to unassign an active cell from its nPartition, do not perform a
shutdown or reset of the nPartition.
When the cell
assignment of an active cell is pending, the Stable Complex Configuration
Data is not pushed out until the cell is at the boot is blocked (BIB) state,
which occurs during a reboot for reconfig or shutdown for reconfig of its
nPartition.
Issue a request
to unlock the Stable Complex Configuration Data for the server where the cell
assignment change is pending.
Use one of the the
procedures given in “Unlocking Complex Profile Entries”.
Printable version
