HP Integrity Superdome SX2000 HP-UX 11i v3 Dynamic nPartitions - Features and - Page 14

Command sequences for Dynamic nPartitions scenarios

Page 14 highlights

Command sequences for Dynamic nPartitions scenarios This section shows representative command sequences to perform common Dynamic nPartitions operations. Cell replacement The following command sequence could be used if it is desired to replace or perform hardware maintenance upon the cell whose global slot number is S. It is assumed that the target cell is a floating cell and it has an active I/O chassis connected to it. First, it is necessary to quiesce all activity associated with the I/O chassis connected to the target cell. If there are any active LAN cards, it is necessary to use the ifconfig command with the unplumb option to tear down the Streams plumbing. If there are filesystems mounted on devices connected through the I/O chassis, then it is necessary to unmount them. The olrad command will give a CRA report to indicate any I/O usages if the I/O chassis to be deactivated is not quiescent. Once the I/O is quiesced, the cell replacement sequence can be executed: olrad -D -s S parolrad -d S frupower -f -c S The cell with global slot number S can now be physically removed from the cabinet. The cell can be repaired and reinserted, or it can be replaced with a new compatible cell. frupower -o -c S It is necessary to wait until the cell has completed its power on sequence. The parstatus command will show the cell in the "Inactive" state when the cell is ready. parolrad -a S olrad -A -s S Now the cell in the I/O connected to it are activated. The LAN connections can be reestablished in the filesystems remounted. Note that it was not necessary to use the parmodify command to unassign the cell from its partition. NOTE: During the Cell replacement sequence as mentioned above, when the I/O chassis is activated (using the "olrad -A -s" command), the instance numbers that get assigned for the I/O devices in the Chassis may be different from the instance numbers that were assigned for the I/O devices before the Chassis was deactivated (using the "olrad -D -s" command). This may result in I/O devices having different device special files(dsf) after a Cell replacement operation (persistent device special files are not impacted). If the user needs to have the same instance numbers (and thereby same dsf) for the I/O devices after the Cell Replacement sequence is performed, the "-f -r " option of ioinit(1M) can be used to reassign the previous instance numbers. Note that the "-r" option must be specified with ioinit(1M) as some of the I/O devices of type ext_bus, lan do not support online instance number reassignment. Cell migration Here is the command sequence to migrate the cell in slot S from partition p to partition q. It is assumed that the target cell is a floating cell and it does not have an I/O chassis. (If it did have active I/O, the instructions above for quiesceing and reestablishing I/O would apply.) Further, it is assumed that security certificates are in place to enable remote invocation of the parolrad command. 14

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22

14
Command sequences for Dynamic nPartitions scenarios
This section shows representative command sequences to perform common Dynamic nPartitions
operations.
Cell replacement
The following command sequence could be used if it is desired to replace or perform hardware
maintenance upon the cell whose global slot number is
S
.
It is assumed that the target cell is a
floating cell and it has an active I/O chassis connected to it.
First, it is necessary to quiesce all activity associated with the I/O chassis connected to the target cell.
If there are any active LAN cards, it is necessary to use the ifconfig command with the unplumb option
to tear down the Streams plumbing.
If there are filesystems mounted on devices connected through
the I/O chassis, then it is necessary to unmount them.
The olrad command will give a CRA report to
indicate any I/O usages if the I/O chassis to be deactivated is not quiescent.
Once the I/O is quiesced, the cell replacement sequence can be executed:
olrad -D -s
S
parolrad -d
S
frupower -f -c
S
The cell with global slot number
S
can now be physically removed from the cabinet.
The cell can be repaired and reinserted, or it can be replaced with a new compatible
cell.
frupower -o -c
S
It is necessary to wait until the cell has completed its power on sequence.
The
parstatus command will show the cell in the "Inactive" state when the cell is ready.
parolrad -a
S
olrad -A -s
S
Now the cell in the I/O connected to it are activated.
The LAN connections can be reestablished in
the filesystems remounted.
Note that it was not necessary to use the parmodify command to unassign the cell from its partition.
NOTE: During the Cell replacement sequence as mentioned above, when the I/O chassis is activated
(using the "olrad -A -s" command), the instance numbers that get assigned for the I/O devices in the
Chassis may be different from the instance numbers that were assigned for the I/O devices before the
Chassis was deactivated (using the "olrad -D -s" command). This may result in I/O devices having
different device special files(dsf) after a Cell replacement operation (persistent device special files are
not impacted). If the user needs to have the same instance numbers (and thereby same dsf) for the
I/O devices after the Cell Replacement sequence is performed, the "-f <file> -r " option of ioinit(1M)
can be used to reassign the previous instance numbers. Note that the “–r” option must be specified
with ioinit(1M) as some of the I/O devices of type ext_bus, lan do not support online instance number
reassignment.
Cell migration
Here is the command sequence to migrate the cell in slot
S
from partition
p
to partition
q
.
It is
assumed that the target cell is a floating cell and it does not have an I/O chassis.
(If it did have
active I/O, the instructions above for quiesceing and reestablishing I/O would apply.)
Further, it is
assumed that security certificates are in place to enable remote invocation of the parolrad command.