HP-UX Virtual Partitions Administrator's Guide (includes A.04.06 and A.05.04)

vPars partition database is read. (Note that the files in the LIF area are still read when the
system or nPartition boots).
To simulate the effect of an AUTO file for a virtual partition, use the vPars commands so
that the information is saved in the vPars partition database. For more information, see “The
AUTO File on a Virtual Partition” (page 163).
• shutdown and reboot commands In a virtual partition, the shutdown and reboot
commands shutdown and reboot a virtual partition and not the entire nPartition.
Also, if a virtual partition is not set for autoboot using the autoboot attribute (see the
vparmodify(1M) manpage), the -r and -R options of the shutdown or reboot commands
will only shut down the virtual partition; the virtual partition will not reboot. In other words,
the virtual partition will halt when the autoboot attribute is not set. For more information,
see the vparmodify(1M) manpage.
For the -R and -r options of the shutdown and reboot commands, the virtual partition
will not reboot when there is a pending Reboot for Reconfiguration until all the virtual
partitions within the nPartition have been shutdown and the vPars Monitor has been
rebooted; note that -R sets a pending Reboot for Reconfiguration. Also, the requested
reconfiguration will not take place until all the virtual partitions within the involved
nPartition have been shutdown and the vPars Monitor has been rebooted.
For more information, see “Shutting Down or Rebooting a Virtual Partition” (page 154) and
“Shutting Down or Rebooting the nPartition (Or Rebooting the vPars Monitor)” (page 156).
• ioscan output On a PA-RISC system, the ioscan output for vcn and vcs drivers show
a value of NO_HW in the S/W State column. On an Integrity server, these drivers do not
appear in the ioscan output. This is normal.
• intctl Command The intctl command is an HP-UX tool that enables management of
I/O interrupts among the active CPUs. It can be installed from the HP-UX Software Pack
but should be used only by advanced administrators for performance tuning. If you are
managing interrupts on vPars systems, see the section “Managing I/O Interrupts” (page 237).
• kernel crash dump analyzer You cannot use a kernel crash dump analyzer on vPars Monitor
dumps because vPars Monitor dumps are structured differently than kernel dumps. For
more information on vPars Monitor dumps, see “vPars Monitor Dump Analysis Tool”
(page 278).
• top and other applications that show CPU ID The CPU ID displayed by the top command
and other applications may not be indicative of the actual CPU index in standalone or nPars
mode, nor of the actual hardware path. Within a virtual partition, top sees only the CPUs
assigned to it. Possible top output is shown below; the CPU index is the left-most column.
CPU LOAD USER NICE SYS IDLE BLOCK SWAIT INTR SSYS
0 0.01 0.0% 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%
1 0.00 0.0% 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%
2 0.01 0.0% 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%
4 0.01 0.0% 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%
7 0.01 0.0% 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%
8 0.06 0.0% 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%
--- ---- ----- ----- ----- ----- ----- ----- ----- -----
avg 0.02 0.0% 0.0% 0.0% 100.0% 0.0% 0.0% 0.0% 0.0%
• Agile view of Mass Storage The agile view of mass storage introduced in HP-UX 11i v3
(11.31) is supported with vPars.
Support for agile addressing vPars configurations and operations is provided starting with
vPars A.05.03. In the vPars A.05.01 and vPars A.05.02 releases, only the legacy hardware
path format is supported.
— The vPars A.05.03 release includes support for the next-generation mass storage
subsystem in HP-UX 11i v3 (including agile addressing). In the next-generation mass
24 Introduction