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

Introduction

HP Product Interaction

Chapter 1

• SCSI Initiator ID (PA-RISC only)

For vPars A.03.xx and earlier: the SCSI Initiator ID is the ID of the SCSI controller. Although you can

display and set SCSI parameters for the SCSI controller at the BCH prompt, on a vPars server, you can

also set these values from the HP-UX shell of a virtual partition using the vPars command vparutil. For

more information, see the vparutil (1M) manpage.

For vPars A.04.xx and later: please use the mptutil command. For information on mptutil, see the

Ultra320 SCSI Support Guide or the support guide for your card.

• 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 “Boot||Shut: Setboot and System-wide Stable Storage” on page 137.

• mkboot and LIF files

The mkboot command allows you to write to files in the LIF area on both Integrity and PA-RISC servers;

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 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” on page 143.

• /stand filesystem size

Due to the vPars files that will exist in /stand, you should increase by 100 MB the size of the /stand file

system that you normally create.

• 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 (RFR) until all the virtual partitions within the

nPartition have been shutdown and the vPars Monitor has been rebooted. 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 “Boot||Shut: Shutting Down or Rebooting a Virtual Partition” on page 133 and

“Boot||Shut: Shutting Down or Rebooting the nPartition (OR Rebooting the vPars Monitor)” on page 135.

• 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. This is normal.