nPartition Information

The vPars database is entirely separate from the nPartition complex profile data. Therefore, a change in the vPars partition database does not change any complex profile data. For an example on changing information in both the vPars partition database and the nPartition complex profile, see “Using Primary and Alternate Paths with nPartitions”.

For a given nPartition, the Virtual Front Panel (VFP) displays an OS heartbeat whenever at least one virtual partition within the nPartition is up.

All vPars within an nPartition share the same console device. For a given nPartition, this is the nPartition’s console. For more information on the console and console logs, see “Virtual Consoles” and “nPartition Logs”.

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.

Once the BIB (Boot-Is-Blocked) state is set in the nPartition, virtual partitions will not be able to boot up until all the virtual partitions have been shutdown and the vPars Monitor rebooted. In other words, once there is a pending Reboot for Reconfiguration within the given nPartition, no virtual partitions can 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.

If any of the following conditions occur, the OS must be booted in nPars mode:

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”.

For more information, see “Shutting Down or Rebooting the nPartition (Or Rebooting the vPars Monitor)” and the vPars Monitor command “reboot [mode]”.