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

For information on using the vPars commands, see the following sections in the chapter vPars
Monitor and Shell Commands:
• “Managing: Creating a Virtual Partition” (page 155).
• “vPars Monitor: Booting the vPars Monitor” (page 134).
• “Booting a Virtual Partition” (page 158)
• “Shutting Down or Rebooting the nPartition (Or Rebooting the vPars Monitor)” (page 160)
Server Chipset Upgrade The process documented in many of the updates assumes you are not
performing a hardware upgrade that causes a change in hardware paths (for example, upgrading
from the sx1000 chipset to the sx2000 chipset). For information on upgrading vPars when the
upgrade includes a hardware path change, see “Upgrading Integrity Servers from the sx1000 to
sx2000 Chipset” (page 114).
Cautions
Hardware Paths on the vPars Command Line
— Hardware Path Differences Between Cellular (nPartitionable) and Non-cellular Systems
The hardware paths for some example system are formatted for non-cellular systems. For
cellular systems, their hardware paths contain the prefix of the cell number. Therefore, on
non-cellular systems, the path 0/0 refers to a SBA/LBA format. However, on cellular systems,
the path 0/0 refers to a cell/SBA format. Read the section “Planning, Installing, and Using
vPars with an nPartitionable Server” (page 49) if you are using a cellular system.
— Path Formats on the vPars Command Line
For vPars A.03.01 or earlier, you must explicitly specify the LBA for I/O allocation. Thus, for
cellular systems on A.03.01 or earlier, you must use the cell/SBA/LBA format on the
command line. If you use only the cell/SBA format the vPars commands will not assume
that all LBAs under the specified SBA are to be included in the allocation. Doing so may
cause the system to panic.
For vPars A.03.02 or later, you can use either the cell/SBA or cell/SBA/LBA format on
the command line. The vPars commands will assume the command applies to all LBAs under
the specified SBA.
— When OE is installed in vPar mode by excluding the vPars bundle from the OE, system
boot fails
Installing a vPar in vPar mode by selecting the HP-UX OE without selecting vPars bundle
is not supported. So, always install the OE along with the vPars bundle in the vPar mode.
If you try to boot a system that has the OE installed in vPar mode where the vPars bundle
was not selected, the system will fail to boot up.
Other Considerations
This section covers:
• “Installing Server Firmware on non-nPartitionable Servers” (page 72)
• “Setting the GSP Terminal Type” (page 73)
• “Increase in Size of /stand File System” (page 74)
• “VxFS (Veritas File System) (vPars A.03.xx)” (page 74)
Installing Server Firmware on non-nPartitionable Servers
Installing Firmware for the systems running vPars must be done in a standalone (PA-RISC) or
nPars (Integrity) mode. Once in standalone or nPars mode, the procedure for installing firmware
on a system with vPars installed is the same as a system without vPars installed. Additional
72 Installing, Updating, or Removing vPars and Upgrading Servers with vPars