pdc(1M) pdc(1M)
NAME
pdc - processor-dependent code (firmware)
DESCRIPTION
is the firmware that implements all processor-dependent functionality, including initialization and self-test of the processor. Upon com-
pletion, it loads and transfers control to the initial system loader (isl(1M)). Firmware behavior varies somewhat, depending on the hard-
ware as described below.
To load from an external medium, must know the particular device on which resides. Typically the device is identified by the Primary Boot
Path that is maintained by in Stable Storage. A path specification is an I/O subsystem mnemonic that varies according to hardware model.
When the processor is reset after initialization and self-test complete, reads the Console Path from Stable Storage, and attempts to ini-
tialize the console device. If the initialization fails, attempts to find and initialize a console device. Algorithms used to find a con-
sole device are model-dependent. then announces the Primary Boot, Alternate Boot, and Console Paths.
If (see isl(1M)) is enabled, provides a 10-second delay, during which time the operator can override the sequence by typing any character
on the console. If the operator does not interrupt this process, initializes and reads from the Primary Boot Path. On models that support
autosearch, if this path is not valid and (see isl(1M)) is enabled, then searches to find a bootable medium.
If allowed to complete, a list of potentially bootable devices is displayed, labeled with abbreviated path identifiers (P0, P1, etc). A
simple menu is then displayed where the user can:
o Boot a specific device, using the abbreviated path identifier, or the full mnemonic.
o Start a device search where the contents are searched for IPL images (note the first search only identified devices and did not
check the contents).
o Enter the boot administration level.
o Exit the menu and return to autobooting
o Get help on choices
If the sequence is unsuccessful, overridden by the operator, or not enabled in the first place, interactively prompts the operator for the
Boot Path to use. Any required path components that are not supplied default to zero.
The Primary Boot, Alternate Boot, and Console Paths as well as and enable can be modified via
SEE ALSO
boot(1M), isl(1M).
PA-RISC Systems Only pdc(1M)
Check Out this Related Man Page
vparboot(1M) vparboot(1M)
NAME
vparboot - boot a virtual partition
SYNOPSIS
kernel_path] boot_opts] boot_addr]
PA-RISC platforms only
Itanium(R)-based platforms only
name]| server_ip client_ip optional_data]]]
DESCRIPTION
The command causes the virtual partition monitor to boot the specified virtual partition. The monitor must be running. The virtual parti-
tion must exist in the monitor configuration and be in the 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 reconfiguration the specified 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 Reconfig for an nPartition" in the for more information.
Options
recognizes the following command line options and arguments:
Specifies the unique name of the virtual partition that
is to be booted. The virtual partition must exist in the monitor's database, must be in the state, and must have a
configured boot device. Required.
Specifies 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:
the kernel-path is the portion of this string.
If this option is omitted, the value is taken from any specified during virtual partition creation or its most recent
modification, or if has never been specified.
Specifies 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:
the boot_opts string in this case will be Note that if there is a space included in the string, the string must be
quoted.
Refer to the virtual partitions administration guide and the chapter titled "Monitor and Shell Commands" for a full
list of supported boot option strings.
If the option is omitted, the value is taken from any specified during virtual partition creation or its most recent
modification, or the empty string if has never been specified.
Specifies the device from which the virtual partition kernel image is
read. It must be one of the following three forms:
bo[ot] | pri[mary]
(case-insensitive). This is the default if the option is omitted. attempts to boot vp_name from the device
previously configured with the attribute. It is an error if no device has been so configured.
(case-insensitive).
attempts to boot vp_name from the device previously configured with the attribute. It is an error if no device
has been so configured.
(case-insensitive). On PA-RISC platforms
attempts to boot from a device previously configured with the attribute. It is an error if no device has been so
configured. 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 from 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). does not
check any part of such a specification. If it is not a proper path, the path does not exist, the virtual parti-
tion 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 and attributes decides the boot action to
be taken. Refer to the vparcreate(1M) or vparmodify(1M) manpage for details.
(PA-RISC platforms only) Specifies a path to a cold-install kernel such as
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 local virtual partition (the one on which is run) or on any other networked sys-
tem or virtual partition accessible from that partition. The syntax for ignite_kernel is:
If cold-install_kernel begins with a slash, "/", you are specifying an absolute path and 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 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 Hence it is required to
specify an absolute path, such as
If the Server name or IP address, is not specified, loads the cold-install kernel from the file space of the local vir-
tual 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.
(Itanium-based platforms only) Arguments are optional.
Once the command exits, you must enter 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 identified, or if the selected MAC address fails to load the cold-install kernel, you must
identify the source of the problem, then retry the command.
Specifies the DB-Profile name from which user specified Direct boot
settings are read from the database
Specifies the static IP address for the boot server
Specifies the static IP address for the client. If client IP
information is missing in the DB-Profile, DHCP will be used by default.
Specifies the static IP address for the gateway
Specifies the subnet mask for the local network
Specifies the absolute path to a bootable file on the boot server. If empty
then it will be assumed that the server controls the boot File for the client.
Specifies the optional command line arguments to pass to the boot file
SECURITY RESTRICTIONS
This command is restricted to processes owned by superuser.
When virtual partition flexible administrative capability is enabled, a virtual partition can only be booted from within a Designated-Admin
vPar.
RETURN VALUE
The command exits with one of the following values:
Successful completion.
One or more error conditions occurred.
EXAMPLES
Boot the virtual partition called
Boot the virtual partition specifying an alternate kernel:
Cold-install the virtual partition from a file on a remote PA server:
Cold-install the virtual partition using DB-Profile settings on a remote Itanium server:
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
Cold-install the virtual partition passing network information on a remote Itanium server:
ERRORS
displays error messages on standard error for any of the following conditions:
o vp_name does not exist in the monitor.
o vp_name is in some state other than and so cannot be booted. Use the command instead.
o An error occurs while trying to access an Ignite server or cold-install file.
You have specified the or device, but the corresponding device has not been configured in vp_name.
NOTE: If the boot device has not been configured properly, the command will complete without error, but the virtual partition will not
boot. Possible reasons for this could be:
-- The or attribute was assigned to a device other than a disc or DVD.
-- The attribute was assigned to a device other than tape.
-- The file at the default or configured kernel path does not exist or is not a bootable image.
o The command and the virtual partition monitor are at different revision levels. This message is only a warning. The command continues.
o When the virtual partition flexible administrative capability is enabled and the local virtual partition is not a Designated-Admin vPar.
AUTHOR
was developed by the Hewlett-Packard Company.
SEE ALSO
vparadmin(1M), vparcreate(1M), vparconfig(1M), vpardump(1M), vparefiutil(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M),
vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), vpardbprofile(1M), vparresources(5), vpartition(5), vpmon(5).
vparboot(1M)