HP-UX Virtual Partitions Administrator Guide (includes A.05.07) (5900-1229, September 2010)

# 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.
vPars 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 vPars Monitor. See “Modes: Switching
between nPars and vPars Modes (Integrity Only)” (page 126). Also, backspace is sometimes
not parsed correctly; if the command fails, try again without backspacing.
With no arguments to vpmon, the vPars Monitor will load and go into interactive mode with the
following prompt:
MON>
The following options are available when booting the vPars 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 175). The default
partition database file is /stand/vpdb.
-D database_filename
For more information on the vPars boot sequence, see “Boot Sequence” (page 30).
vPars Monitor: Accessing the vPars Monitor Prompt
You can reach the vPars Monitor prompt in the following ways:
• From the ISL or EFI prompt, you can boot the vPars Monitor into interactive mode (see
“vPars Monitor: Booting the vPars Monitor” (page 134)).
• After shutting down all virtual partitions, you will arrive at the vPars Monitor prompt on
the console (see “Shutting Down or Rebooting the nPartition (Or Rebooting the vPars
Monitor)” (page 160)).
• A.03.xx and earlier: When the system monarch CPU is not owned by any virtual partition,
you will also see the vPars 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
134 vPars Monitor and Shell Commands