Autobooting the Monitor and All Virtual Partitions

You can setup the monitor and all virtual partitions to boot automatically at power up. To do this, make sure the following four conditions are met:

The hard partition's primary and alternate boot paths point to the boot disks of different virtual partitions.
For example, to set the primary and alternate boot paths:
BCH> pa pri 0/0/2/0.6.0
BCH> pa alt 0/8/0/0.5.0
The autoboot flag in stable storage is set to ON.
To set the autoboot flag to ON:
BCH> au on
The contents of the AUTO files of the primary and alternate boot disks contain "hpux /stand/vpmon -a". (The -aoption of /stand/vpmon boots all the virtual partitions that have the autoboot flag set.)
To set the contents of the AUTO file on the LIF, log into the virtual partitions that own the primary and alternate boot disks, respectively, and execute the mkboot -a command:
For example, after logging into winona1 which owns the primary boot disk at 0/0/2/0.6.0, execute:
winona1# mkboot -a "hpux /stand/vpmon -a" /dev/rdsk/c2t6d0
and after logging into winona2 which owns the alternate boot disk at 0/8/0/0.5.0, execute:
winona2# mkboot -a "hpux /stand/vpmon -a" /dev/rdsk/c1t5d0
The autoboot flag of all the virtual partitions is set to AUTO.
AUTO is the default. However, if you need to reset the autoboot flag to AUTO:
winona1# vparmodify -p winona1 -B auto
winona1# vparmodify -p winona2 -B auto
winona1# vparmodify -p winona3 -B auto




	NOTE: For Superdome and other nPartition-able servers, you must use the boot device path "path flags" to set automatic booting past the BCH for a nPartition. See the manual HP System Partitions Guide for more information, including the proper configuration of paths for a nPartition. When booting multiple virtual partitions automatically, the sequence for booting is not deterministic, and booting a sequence of virtual partitions automatically is not supported. If booting a sequence is required, the sequence of virtual partitions needs to be booted manually (one by one). For more information on booting a virtual partition, see “Booting a Virtual Partition”. When booting multiple virtual partitions automatically, there is no way to tell which virtual partition will be active with the console after the partitions have booted. All changes to stable storage can only be performed at the `BCH`> prompt. See “System-wide stable storage and the setboot command”. If you need to reboot the hard partition as part of the process to access the `BCH`>, see “Shutting Down or Rebooting the Hard Partition (rebooting the vPars monitor)”. For information on accessing and using the BCH commands, please see your hardware manual.

Technical documentation