HP-UX Reference (11i v1 05/09) - 1M System Administration Commands N-Z (vol 4)

v
vparboot(1M) vparboot(1M)
restore the contents archived using make_tape_recovery
from
tape. All
the contents on the target disk will be lost.
Boot From Hardware Path:
Any other string is assumed to be the hardware path (for example, 10/6.0) to the
desired boot device.
vparboot does not check any part of such a specification.
If it is not a proper path, the path does not exist, the virtual partition does not
own the device at that path, or there is no bootable device at that path, the com-
mand either fails with an error, or the boot attempt fails with no error indica-
tion.
Boot actions:
If the boot from primary path fails then the combination of
autoboot and
autosearch attributes decides the boot action to be taken. Refer to
vparcreate(1M) or vparmodify(1M) for details.
-I ignite_kernel Specifies a path to a cold-install kernel such as
/opt/ignite/boot/WINSTALL
.
This form of the command is used to cold-install an instance of HP-UX on a virtual
partition. Most often, this is done on a newly-created virtual partition, one that has a
completely unwritten disk. However, it can be used to cold-install HP-UX over an
existing instance.
ignite_kernel can reside either on the current virtual partition (the one on which
vparboot is run) or on any other networked system or virtual partition accessible
from that partition. The syntax for ignite_kernel is:
[server-name-or-IP-addr
,]cold-install-kernel
If cold-install-kernel begins with a slash, (
/), you are specifying an absolute path and
vparboot looks for it at that location. With Ignite-UX revisions prior to C.6.0, if
cold-install-kernel does not begin with
/, the default path /opt/ignite/boot/ is
prepended to cold-install-kernel.
With Ignite-UX revision C.6.0 or later, the cold-install-kernel is not present under
default path
/opt/ignite/boot
. Hence it is required to specify an absolute path,
such as
/opt/ignite/boot/Rel_B.11.11/WINSTALL
.
If server-name-or-IP-addr, is not specified,
vparboot loads the cold-install kernel
from the file space of the current virtual partition. Otherwise the command loads it
from the file space of the specified server. The comma is a required part of the server
name syntax.
RETURN VALUE
The
vparboot command exits with one of the following values:
0 Successful completion.
1 One or more error conditions occurred.
EXAMPLES
Boot the virtual partition called Oslo:
vparboot -p Oslo
Boot the virtual partition Bergen specifying an alternate kernel:
vparboot -p Bergen -b /stand/vmunix_debug
Cold-install the virtual partition Trondheim from a file on a remote server:
vparboot -p Trondheim -I mysys.myserver.mydomain.com,/mypath/myinst
Cold-install the virtual partition Sandefjord from a file at the default path /opt/ignite/boot on the
current virtual partition:
vparboot -p Sandefjord -I WINSTALL
DIAGNOSTICS
vparboot displays error messages on standard error for any of the following conditions:
• vp_name does not exist in the monitor.
HP-UX 11i Version 1: September 2005 − 2 − Hewlett-Packard Company Section 1M−−1097