HP-UX Virtual Partitions Administrator Guide (includes A.05.07) (5900-1229, September 2010)

Cab/
Cell
Slot/ # of L3 L4 Family/
CPU Logical Cache Cache Model Processor
Cell Module CPUs Speed Size Size (hex.) Rev State
---- ------ ------- -------- ------ ------ ------- --- -------------
1 0/1/0 4 1.4 GHz 6 MB None 20/00 C0 Active
CPU threads are turned off.
From here, you can boot the vPars Monitor:
Shell> fs0:
fs0:\> hpux vpmon
Rebooting and Reconfiguring Conceptual Points
• If there is a pending Reboot for Reconfiguration for the involved nPartition, no virtual
partitions will be rebooted until all the virtual partitions within the given nPartition are shut
down and the involved vPars Monitor is rebooted. This implies that the target virtual partition
of the vparload, vparboot, and vparreset commands will not boot until all virtual
partitions within the nPartition have been shut down and the vPars Monitor is rebooted.
• For more information on using the -R and -r options of the shutdown and reboot
commands used in a Reboot for Reconfiguration, see “shutdown and reboot commands”
(page 24).
• For more information, see “Shutting Down or Rebooting the nPartition (Or Rebooting the
vPars Monitor)” (page 160) and the vPars Monitor command “reboot [mode]” (page 137).
• If you make an nPartition change where a Reboot for Reconfiguration is required, all the
virtual partitions within the nPartition need to be shutdown and the vPars Monitor rebooted
in order for the reconfiguration to take effect.
Reconfiguring the nPartition
You must perform a Reboot for Reconfiguration on an nPartition in the following circumstances:
• whenever you add cells to the nPartition
• whenever you need to allow an inactive cell to join the nPartition (such as after changing a
cell use-on-next-boot value from “n” to “y”).
• whenever you remove active cells from the nPartition
When the nPartition reboots from a Reboot for Reconfiguration, variables are written by the
HP-UX kernel in nPar mode. Some of these variables contain the most recent information about
the cells.
The vPars Monitor reads these variables when it boots. If a Reboot for Reconfiguration of the
nPartition has not been performed, the vPars Monitor does not receive the most recent information
about the cells, and an error will occur.
For information on performing a Reboot for Reconfiguration, see “Rebooting and Reconfiguring
Conceptual Points” (page 272) as well as “Reconfiguring an nPartition (Integrity)” (page 273) for
Integrity systems, and “Reconfiguring an nPartition (PA-RISC)” (page 274) for PA-RISC systems.
272 nPartition Operations