HP-UX Virtual Partitions Administrator's Guide (includes A.03.05 and A.04.05)

# setboot -a mirror_disk_hw_path
Execute the vparefiutil command on the new disk.
# vparefiutil -u [-H mirror_disk_hw_path]
Booting from a recently added boot disk.
Problem:
If you add a boot disk at a known hardware path, it may not be possible to immediately
boot from this new disk.
Solution:
If the EFI signature of the disk is known, the vparload -E command can be used to
boot from the disk.
Monitor: Booting the vPars Monitor
To boot the vPars Monitor, from ISL or EFI, specify /stand/vpmon:
PA-RISC:
ISL> hpux /stand/vpmon
Integrity:
Shell> fs0
fs0:\> hpux
HPUX> boot vpmon
NOTE: You must be in vPars mode to boot the Monitor. See “Modes: Switching between
nPars and vPars Modes (Integrity only)” (page 118). Also, backspace is sometimes not
parsed correctly; if the command fails, try again without backspacing.
With no arguments to vpmon, the Monitor will load and go into interactive mode with the
following prompt:
MON>
The following options are available when booting the Monitor:
boots all virtual partitions that have the autoboot attribute set. For more information,
see vparmodify(1M).
-a
boots the virtual partitions using an alternate partition database file. For more
information, see “Using an Alternate Partition Database File ” (page 167). The default
partition database file is /stand/vpdb.
-D database_filename
For more information on the vPars boot sequence, see “Boot Sequence” (page 32).
Monitor: Accessing the Monitor Prompt
You can reach the Monitor prompt in the following ways:
From the ISL or EFI prompt, you can boot the Monitor into interactive mode (see “Monitor:
Booting the vPars Monitor” (page 126)).
After shutting down all virtual partitions, you will arrive at the Monitor prompt on the
console (see “Shutting Down or Rebooting the nPartition (OR Rebooting the vPars Monitor)”
(page 152)).
A.03.xx and earlier: When the system monarch CPU is not owned by any virtual partition,
you will also see the Monitor prompt MON> while toggling among the virtual consoles.
A monarch CPU exists in both non-vPars and vPars servers. After a server is powered-on,
the monarch CPU determines what other CPUs are configured in the server and then launches
126 Monitor and Shell Commands