HP-UX Virtual Partitions Administrator's Guide (includes A.05.02)

Introduction

HP Product Interaction

Chapter 1

Booting the machine into standalone mode from a boot disk which had its OS time ahead of the RTC will

advance the RTC. If the machine is then booted into a vPars environment, the OS time of all the virtual

partitions will be advanced. Administrators should ensure that the RTC is adjusted accordingly before

booting the machine from standalone mode into a vPars environment and vice versa.

• SCSI Initiator ID

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, you can also set these values

on a vPars server 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: use the mptconfig command to view or set the SCSI parameters for

Ultra320 host bus adapters (HBAs). For information on the mptconfig command, see the Ultra320 SCSI

Host Bus Adapter Support Guide. For Ultra2/Ultra160 SCSI HBAs, the SCSI parameters can only be set

from the BCH prompt (on PA-RISC) or from the EFI Shell prompt using EFI applications (on Integrity).

For information on setting and conﬁrming SCSI parameters for Ultra2/Ultra160 HBAs, see the Ultra160

SCSI Host Bus Adapter Service and User Guide.

• 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

stable storage. Instead, it only reads from and writes to the vPars partition database.

For more information see “Setboot and System-wide Stable Storage” on page 164.

• mkboot and LIF ﬁles

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

for example, the AUTO ﬁle. While on a vPars server, mkboot can still be used to write to ﬁles in the LIF

area. However, the LIF area is not read during the boot of an OS on a virtual partition. Instead, only the

information stored in the vPars partition database is read. (Note that the ﬁles in the LIF area are still

read when the system or nPartition boots).

To simulate the effect of an AUTO ﬁle 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 171.

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

nPartition have been shutdown and the vPars Monitor has been rebooted; note that -R sets a pending

RFR. Also, the requested reconﬁguration 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” on page 160 and “Shutting

Down or Rebooting the nPartition (OR Rebooting the vPars Monitor)” on page 162.