vparboot(1M)

vparboot(1M)

NAME vparboot - boot a virtual partition SYNOPSIS

vparboot -p vp_name [-b kernel_path ] [-o boot_opts ] [-B boot_addr ]

PA-RISC platforms only vparboot -p vp_name -I ignite_kernel Itanium -based platforms only vparboot -p vp_name -I [ [-d name]| [-s server_ip [-c client_ip -m subnet_mask] -b boot_le [-o optional_data]]]

-g gateway_ip

Platform Support Remarks This vparboot describes functionality on systems not running Onboard Administrator (OA) based partition management. For vparboot on systems with OA based partition management, refer to vparboot2 (1M), by typing man vparboot2. DESCRIPTION The vparboot command causes the virtual partition monitor to boot the specied virtual partition. The monitor must be running. The virtual partition must exist in the monitor conguration and be in the Down state. For this reason, it is not possible to boot the local partition using this command. The partition in which the command is executing is called the local partition. On hard-partitionable systems, such as Superdome, if there is a pending reboot for reconguration, the specied virtual partition will not be booted until all the virtual partitions on that hard partition (nPartition) are shut down and the virtual partition monitor is rebooted. Refer to "Performing a Reboot for Recong for an nPartition" in the nPartition Administrators Guide for more information. Also if the system is up and running in vPars mode, and the next boot mode is set to nPars mode, the specied virtual partition will not be booted until the systems next boot mode is changed to vPars mode using vparenv -m vPars. Options

vparboot recognizes the following command line options and arguments: -p vp_name
Species the unique name of the virtual partition that is to be booted. The virtual partition must exist in the monitors database, must be in the Down state, and must have a congured boot device. Required. Species the absolute path to a bootable kernel for the virtual partition. For example, if a non-partitioned system start string at the ISL prompt is:

-b kernel_path

ISL> hpux -iS /stand/vmunix

the kernel-path is the /stand/vmunix portion of this string. If this option is omitted, the value is taken from any -b kernel_path specied during virtual partition creation or its most recent modication, or /stand/vmunix if -b kernel_path has never been specied.

-o boot_opts

Species the command-line options to be applied when the virtual partition is booted. For example, if a non-partitioned system start string at the ISL prompt is:

ISL> hpux -iS /stand/vmunix

the boot_opts string in this case will be -iS. Note that if there is a space included in the string, the string must be quoted. Refer to the virtual partitions administration guide Installing and Managing HPUX Virtual Partitions, and the chapter titled "Monitor and Shell Commands" for a full list of supported boot option strings. If the -o option is omitted, the value is taken from any -o boot_opts specied during virtual partition creation or its most recent modication, or the empty string if -o boot_opts has never been specied.

-B boot_addr

Species the device from which the virtual partition kernel image is read. It must be one of the following three forms: 1 Hewlett-Packard Company 1

HP-UX 11i Version 3: September 2010

vparboot(1M)

vparboot(1M)

bo[ot] | pri[mary] (case-insensitive). This is the default if the -B option is omitted. vparboot attempts to boot vp_name from the device previously congured with the BOOT attribute. It is an error if no device has been so congured.

alt[ernate|boot]
(case-insensitive). vparboot attempts to boot vp_name from the device previously congured with the ALTBOOT attribute. It is an error if no device has been so congured.

tape
(case-insensitive). On PA-RISC platforms vparboot attempts to boot vp_name from a device previously congured with the TAPE attribute. It is an error if no device has been so congured. On Itanium(R)-based platforms, lists all the tape devices assigned to the partition. The user will then be prompted to select the tape device from which to boot the partition. This will 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 to the desired boot device (for example, 10/6.0). vparboot does not check any part of such a specication. 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 command either fails with an error, or the boot attempt fails with no error indication. 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 the vparcreate (1M) or vparmodify (1M) manpage for details.

-I ignite_kernel

(PA-RISC platforms only)

Species a path to a cold-install kernel such as

/opt/ignite/boot/WINSTALL. This form of the command is used to coldinstall 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 local 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, there is no cold-install_kernel at the 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 the Server name or IP address , is not specied, vparboot loads the cold-install kernel from the le space of the local virtual partition. Otherwise the command loads it from the le space of the specied server. The comma is a required part of the server name syntax.

-I

(Itanium-based platforms only) Arguments are optional. Once the command exits, you must enter Control-A in a console window until you reach the virtual console for vp_name . There you are presented with one or more MAC addresses of I/O controllers assigned to vp_name . Select the appropriate address to load the cold-install kernel. If no MAC address can be identied, or if the selected MAC address fails to load the cold-install kernel, you must identify the source of the problem, then retry the vparboot command.

-d name
2

Species the DB-Prole name from which user specied Direct boot settings are read from the database 2 HP-UX 11i Version 3: September 2010

Hewlett-Packard Company

vparboot(1M)

vparboot(1M)

-s server_ip -c client_ip -g gateway_ip -m subnet_mask -b boot_file -o optional_data

Species the static IP address for the boot server Species the static IP address for the client. If client IP information is missing in the DB-Prole, DHCP will be used by default. Species the static IP address for the gateway Species the subnet mask for the local network Species the absolute path to a bootable le on the boot server. If empty then it will be assumed that the server controls the boot File for the client. Species the optional command line arguments to pass to the boot le

SECURITY RESTRICTIONS This command is restricted to processes owned by superuser. When virtual partition exible administrative capability is enabled, a virtual partition can only be booted from within a Designated-Admin vPar. RETURN VALUE The vparboot command exits with one of the following values:

0 1

Successful completion. 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 le on a remote PA server:

vparboot -p Trondheim -I mysys.myserver.mydomain.com,/mypath/myinst

Cold-install the virtual partition vparsd2 using DB-Prole settings on a remote Itanium server:

vpardbprofile -d profile1
Profile Name: profile1 Network Type: IPv4 Server IP address: 15.1.165.152 Client IP address: 15.1.163.92 Gateway IP address: 15.1.165.240 Subnet Mask: 255.255.248.0 Boot File: /opt/ignite/boot/nbp.efi Optional Data: IINSTALL

vparboot -p vparsd2 -I -d profile1

Cold-install the virtual partition vparsd2 passing network information on a remote Itanium server:

vparboot -p vparsd2 -I -s 15.1.165.152 -c 15.1.163.92 -g 15.1.165.240 -m 255.255.248.0 -b /opt/ignite/boot/nbp.efi -o IINSTALL

ERRORS

vparboot displays error messages on standard error for any of the following conditions:
vp_name does not exist in the monitor. vp_name is in some state other than Down, and so cannot be booted. Use the vparreset command instead. An error occurs while trying to access an Ignite server or cold-install le. You have specied the BOOT, TAPE, or ALTBOOT device, but the corresponding device has not been congured in vp_name . HP-UX 11i Version 3: September 2010 3 Hewlett-Packard Company 3

vparboot(1M)

vparboot(1M)

NOTE: If the boot device has not been congured properly, the vparboot command will complete without error, but the virtual partition will not boot. Possible reasons for this could be: The BOOT or ALTBOOT attribute was assigned to a device other than a disc or DVD. The TAPE attribute was assigned to a device other than tape. The le at the default or congured kernel path does not exist or is not a bootable image. The vparboot command and the virtual partition monitor are at different revision levels. This message is only a warning. The command continues. When the virtual partition exible administrative capability is enabled and the local virtual partition is not a Designated-Admin vPar.

AUTHOR

vparboot was developed by the Hewlett-Packard Company.

SEE ALSO vparadmin(1M), vparcreate(1M), vparcong(1M), vpardump(1M), vpareutil(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), vpardbprole(1M), vparresources(5), vpartition(5), vpmon(5).

Hewlett-Packard Company

HP-UX 11i Version 3: September 2010