Installing and Managing HP-UX Virtual Partitions (A.02.01)

Introduction
Supported Environments
Chapter 1 29
• System-wide stable storage and the setboot command
On a non-vPars server, the setboot command allows you to read
from and write to the system-wide stable storage of non-volatile
memory. However, on a vPars server, the setboot command does not
affect the stable storage. Instead, it reads from and writes to only the
partition database.
For more information see “System-wide Stable Storage and Setboot”
on page 58.
• mkboot and LIF files
The mkboot command allows you to write to files in the LIF area, for
example, the AUTO file. While on a vPars server, mkboot can still be
used to write to files in the LIF area, the LIF area is not read during
the boot of the OS of a virtual partition. Instead, only the
information stored in the vPars partition database is read. (Note: the
files in the LIF area are still read when the entire server 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 “Simulating the AUTO
File on a Virtual Partition” on page 138.
• /stand file system size
Due to the vPars files that will exist in /stand, you should increase
by 50 MB the size of the /stand file system that you normally create.
• SCSI Initiator ID
Although you can set the SCSI Initiator ID (the ID of the SCSI
controller) and rate at the BCH prompt, on a vPars server, you can
also set these values from the UNIX shell of a virtual partition.
For more information, see the vparutil (1M) manpage.
• ioscan output
The ioscan output for vcn and vcs drivers show a value of NO_HW in
the S/W State column. This is normal.
• intctl command
The inctl command is a HP-UX tool that allows you to manage I/O
interrupts among the active processors. However, in a vPars
environment you can manage the I/O interrupts only among the