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

Introduction

HP Product Interaction

Chapter 1

• Real-time clock (RTC)

Fixed in A.03.03 and later, A.04.01 and later:

The monitor keeps track of the OS time for each virtual partition relative to the real-time clock. The OS

time is the time that is changed via the set_parms or date commands.

However, you can change the real-time clock at the BCH prompt or at the monitor prompt (MON>). If you

change the real-time clock, you need to run the monitor command toddriftreset to reset the drifts

relative to the real-time clock. For information on the monitor commands, see “Using Monitor Commands”

on page 118.

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 enviroment and vice versa.

• 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 134.

• 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 140.

• /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.