Glossary

See Link Level Address

An Ignite-UX command that constructs a client directory on an Ignite-UX server without requiring the client to be booted from the Ignite-UX server first. See add_new_client(1M).

The ability to address a LUN with the same DSF regardless of the physical location of the LUN or the number of paths leading to it. Agile addressing is introduced in HP-UX 11i v3.

The representation of LUNs using lunpath hardware paths, LUN hardware paths, and persistent DSFs, introduced in HP-UX 11i v3.

For HP-UX 11i v1 and 11i v2, the software and driver bundles required for HP-UX. They must be loaded as part of the operating system.

A client system that requests an IP address for booting when its MAC address is not associated with a specific IP address on the server. An anonymous client has its IP address allocated from a pool of IP addresses set aside for anonymous clients. See registered client.

See standard label tape.

1. A file made with make_sys_image that contains files for installation or recovery for a system. The file format may be tar, cpio, or with HP-UX 11i v3, pax, and can be compressed. An archive does not include file system or disk layout information. Archives can be either recovery archives or golden archives. Recovery archives retain host-specific customizations from the system; golden archives have customizable files reset to the newconfig state. An archive may include the core HP-UX operating system, and may include application software, patches, and global customizations. 2. A file containing the contents of other files, created and maintained by programs such as pax, tar and cpio.

An Ignite-UX command that calculates the disk space required for an archive on a per top level directory basis by default. The results are written in Ignite-UX configuration file syntax to standard output. See archive_impact(1M).

A file that defines default boot behavior. For PA-RISC systems, the AUTO file is in the LIF volume. For Itanium®-based systems, the AUTO file is located in the /opt/ignite/boot directory. See hpux(1M) and hpux.efi(1M).

An Ignite-UX command that allows you to manipulate AUTO file contents. See auto_adm(1M).

Any installation done automatically, without manual interaction. This can be done at the command line with a bootsys command, or it can be scheduled to run at a particular time using the cron daemon.

A security hardening/lockdown tool that can enhance the security of the HP-UX operating system. It provides customized lockdown on a system-by-system basis.

To load the kernel and start the operating system that is referenced by the kernel that was loaded. See boot(1M).

The firmware interface on a PA-RISC system. The Itanium-based equivalent is the extensible firmware interface.

[W|V|I]INSTALL, [W|V|I]INSTALLFS, INSTCMDS or INSTCMDSIA, config files, and other files to support boot and Ignite-UX functionality needed to switch to another install source.

Installation media with no archive. Meant for booting only. Installation is completed using an Ignite-UX server.

A system with minimal Ignite-UX core functionality on a local subnet that provides an Ignite install kernel to a client to assist it with booting from an Ignite-UX server on another subnet.

Boot content, including [W|V|I]INSTALL, [W|V|I]INSTALLFS, INSTCMDS or INSTCMDSIA, and other content needed to support boot, formatted for a specific media type such as CD, DVD, or tape.

An Ignite-UX command that allows you to reboot and install clients that are currently running HP-UX. See bootsys(1M).

A package of software available from Software Distributor. Bundles are distributed within depots and contain products and filesets. Ignite-UX typically references software at the bundle level, as opposed to product or product.fileset.

A boot image formatted for a CD.

See configuration clause.

An Ignite-UX command that compares the files on a currently running system with a network recovery archive created by make_net_recovery. A report is generated showing those files that have been added, deleted, or changed since the recovery archive was created. See check_net_recovery(1M).

An Ignite-UX command that compares the files on a currently running system with a tape recovery archive created by make_tape_recovery. A report is generated showing those files that have been added, deleted, or changed since the recovery archive was created. See check_tape_recovery(1M).

An INDEX file for individual clients, kept in the /var/opt/ignite/client directory on the Ignite-UX server. Used to install recovery images made with make_net_recovery.

A computer that uses an Ignite-UX server for installation, recovery services, or both.

To replicate one computer’s software and configuration onto another. This can be accomplished to varying degrees using make_sys_image and make_[tape|net]_recovery.

Booting, loading HP-UX onto, and then starting a system. This process loads a new copy of HP-UX onto a system.

Text formatted commands and options entered at an HP-UX command line prompt or executed by a script.

System software you want replicated onto other systems, such as: an operating system, patches, and application software.

A file made smaller with compression software such as gzip or compress without losing any information. See gzip(1) and compress(1).

A file in the LIF volume that typically contains all the software configuration information and the default file system layout information. It includes default configuration information for the operating system release, user-defined configuration information, and information regarding archives and depots.

See configuration file.

Defines a collection of related configuration files used to install or recover a system. You will find configuration clauses in the /var/opt/ignite/INDEX file for installations, and in the /var/opt/ignite/clients/MAC_address/CINDEX file for recoveries, on an Ignite-UX server.

A file that contains information describing installation behavior, archive contents, or the contents of a depot. Configuration files are referenced by the INDEX and CINDEX files. See instl_adm(4).

An Ignite-UX command that replicates a PA-RISC recovery tape made with make_tape_recovery. See copy_boot_tape(1M).

See custom limited config.

An installation tailored to your specific requirements, including: kernel parameters, the running of user-supplied scripts, host information, and networking information.

A configuration file that informs Ignite there is no corresponding archive. Used with boot helper media. Also called a crippled config.

A process that runs in the background and is usually immune to termination instructions.

For HP-UX 11i v1 and 11i v2, software bundles that are installed as default with HP-UX. These bundles can be deselected before installation.

A repository of software products, organized so Software Distributor (SD-UX) commands can use it as a software source.

A user friendly, readable string, such as “LAB2CAB23LUN15”, that is stored on a device. It remains viewable even if the device is moved physically. See scsimgr(1M).

Stands for Dynamic Host Configuration Protocol, and is a way of dynamically allocating IP addresses and other network topology information to clients for a specified lease time.

A boot request that is directed to a particular Ignite-UX server or boot helper system. A directed boot allows boot and installation from an Ignite-UX server on a different subnet without requiring a boot helper.

The VxVM equivalent of an LVM volume group.

The way hard disks are formatted and information stored on them. There are two general methods of disk layout: physical-storage layout and logical-storage layout. VxVM and LVM use logical-storage layout, and use various layout techniques such as mirroring and striping.

The version of the VxFS private data that is used for its file system layout. This term can be abbreviated to DLVx, where x is the disk layout version number. See mkfs_vxfs(1M).

Stands for Domain Name Service, and provides mapping between hostnames and IP addresses.

Stands for Device Special File. A file associated with an I/O device. DSFs are read and written to as ordinary files are, resulting in activation of the associated device.

A use designation typically for an LVM logical volume or a VxVM volume for system crash dump storage. See crashconf(1M).

A boot image formatted for a DVD.

See Extensible Firmware Interface.

An extension to ISO9660 for creating bootable optical media.

The list of files and directories in /opt/ignite/recovery/mnr_essentials describing the default minimum contents of a recovery archive.

An Ignite-UX mode of operation allowing expert users to repair a system with software damage without reinstalling HP-UX.

The Intel® developed firmware environment on Itanium-based systems that acts as an interface between operating systems and platform firmware. The interface consists of platform related information, as well as boot and runtime service calls. The PA-RISC equivalent is the boot console handler.

A collection of files and supporting data structures residing directly on a mass storage device or on a virtual or logical disk. There are various file system implementations, such as HFS and VxFS.

For SD-UX, a collection of files within a product. The product may be part of a bundle. See sd(5).

The IP address of a system that routes forwarded traffic to a non-local network. A gateway IP address is usually associated with a router.

An archive with files set to the newconfig state. See archive.

A combination of a golden archive, and a configuration file describing a system’s disk layout and file system. Use as a common configuration to install systems.

A method of interacting with computers that employs metaphors such as windows and desktops and uses mouse-driven menus.

A command available with HP-UX that compresses and decompresses files in “.gz” format. See gzip(1).

Stands for Host Bus Adaptor. A physical I/O interface that provides I/O processing and connectivity between a server and a storage device.

A particular implementation of a file system. See mkfs_hfs(1M).

The HP-UX bootstrap loader. Loads the kernel and starts HP-UX. For Ignite-UX, the HP-UX bootstrap loader loads the install kernel (e.g. IINSTALL) and install file system (e.g. IINSTALLFS). The bootstrap loader may also load other LIF content it needs to operate. See hpux(1M).

See Ignite-UX.

The ignite command name. See ignite(5).

An HP-UX administration toolset that allows simultaneous installation of HP-UX on multiple PA-RISC and Itanium-based clients, the creation and use of custom installations, the remote recovery of clients, and the creation of recovery media.

A server from which Ignite-UX is used to install HP-UX on client systems.

The installation kernel for Itanium-based systems.

The associated file system for the IINSTALL kernel.

The current state of your computer, or portion of your computer. Often thought of as a “snapshot” of the state of the machine at any given moment.

A file on the Ignite-UX server and in LIF volumes that groups references to configuration files in configuration clauses in order to define installation behavior.

Implements the operating system independent portion of the bootstrap process on PA-RISC systems. It is loaded and executed after self-test and initialization have completed successfully. See isl(1M).

The installation kernel for 32-bit enabled PA-RISC systems.

Perform an installation.

Boot content and other files needed to support Ignite-UX functionality during install and recovery.

See IINSTALLFS, INSTALLFS, VINSTALLFS, and WINSTALLFS.

See IINSTALL, INSTALL, VINSTALL, and WINSTALL.

Loading the operating system, other software, and configuration information onto a system.

Removable media such as tape, CD, and DVD for stand alone installation of a client system.

The associated file system for the INSTALL kernel.

A compressed tar archive of commands in the LIF volume, or on an Ignite-UX server, required for specifying the system configuration to install on a PA-RISC system.

A compressed tar archive of commands in the LIF volume, or on an Ignite-UX server, required for disk layout on an Itanium-based system.

An Ignite-UX command that checks syntax on Ignite-UX configuration files and manages the configuration file in an installation file system on an Ignite-UX server. See instl_adm(1M).

A boot protocol daemon for Ignite-UX clients that responds to PA-RISC systems requesting boot services from the Ignite-UX server. See instl_bootd(1M).

An Ignite-UX command that combines a CD boot image or DVD boot image with install content. See instl_combine(1M).

An Ignite-UX command that will parse and debug an Ignite-UX client’s configuration files. See instl_dbg(1M).

See initial system loader.

An ISO9660 formatted file that is to be written to a CD or DVD. Used for a bit-for-bit burn of a CD or DVD.

The name of an internal IUX program that presents the Ignite-UX client installation configuration user interface. This interface has five tabs: Basic, Software, System, File System, and Advanced. It is used to customize all or part of the operating system installation on the client before an installation or recovery. This command is not invoked from the command line.

See Ignite-UX.

The HP-UX kernel is the executable code responsible for managing the computer’s resources, such as: allocating memory, creating processes, and scheduling programs for execution. The kernel resides in RAM (random access memory) whenever HP-UX is running.

See MAC address.

An option available on certain file systems that allows file sizes greater than 2 gigabytes.

A DSF with the hardware path information such as SCSI bus, target, and LUN embedded in the file’s minor number and file name, such as /dev/dsk/c#t#d#. These are the only DSFs available in releases prior to HP-UX 11i v3.

The representation of a hardware path as it exists in releases prior to HP-UX 11i v3. It is composed of a series of bus-nexus addresses separated by slashes (/) leading to the HBA. After the HBA, additional address elements, such as domain, area, port, tartet, and LUN, are separated by periods (.). The string /0/2/1/0.1.4.0.0.2.7 is an example of a legacy hardware path.

The representation of legacy hardware paths and legacy DSFs as in releases prior to HP-UX 11i v3.

See Logical Interchange Format.

Portions of content needed for boot and install combined into a LIF file. The LIF file is included in boot content and in install content.

See MAC address.

A simple file system implemented on HP computers able to run HP-UX to aid in media transportability. See lif(4).

A virtual subdivision of a volume group. See logical volume manager.

A specific volume manager type created and managed by the HP LVM product. See lvm(7).

An identifier of a SCSI device. This refers to an end storage device such as a disk, tape, floppy, or CD. This is the unit itself and does not represent the path to the unit.

A hardware path for a SCSI LUN that virtualizes all paths to the LUN. The first path element is 64000, followed by a virtual bus instance and a logical unit number. Multipathed LUNs have a single LUN hardware path. The string 64000/0xfa00.0x22 is an example of a LUN hardware path. LUN hardware paths are part of the agile view introduced in HP-UX 11i v3.

The representation of a hardware path for a mass storage device. It is identical in format to a legacy hardware path up to the HBA. After the HBA, additional addressing is represented in hexadecimal format. The string 0/2/1/0.0x50001fe1500170ac.0x4017000000000000 is an example of a lunpath hardware path. Lunpath hardware paths are part of the agile view introduced in HP-UX 11i v3.

Stands for Media Access Control. A network card’s unique hardware number. Used to uniquely identify a network interface connected to a local area network.

Collectively refers to the make_tape_recovery and make_net_recovery Ignite-UX commands.

An Ignite-UX command that creates a bootable tape that contains just enough information for a system to boot and connect to an Ignite-UX server. See make_boot_tape(1M).

An Ignite-UX command that creates a bundle container for products in a depot. See make_bundles(1M).

An Ignite-UX command that constructs Ignite-UX configuration files for Software Distributor depots. See make_config(1M).

An Ignite-UX command that builds a Software Distributor depot for use by other Ignite-UX tools by copying bundles from a Software Distributor source. See make_depots(1M).

An Ignite-UX command that creates a bootable tape for an Itanium-based system. The tape will contain boot and installation components, but not a recovery archive. See make_ipf_tape(1M).

An Ignite-UX command that creates a file containing a LIF volume that is used to boot PA-RISC systems. This file may then be copied to tape, CD, or DVD to create installation media. See make_medialif(1M).

An Ignite-UX command that creates a recovery archive and system config file, and stores the resultant recovery image on a system on the network. See make_net_recovery(1M).

An Ignite-UX command that creates an archive of a system. See make_sys_image(1M).

An Ignite-UX command that creates a recovery archive and system config file, and stores the resultant recovery image on a local tape. See make_tape_recovery(1M).

An Ignite-UX command that is used to manipulate an Ignite-UX INDEX or CINDEX file. See manage_index(1M).

Details of a client’s installation. It is available in a file on the client and the Ignite-UX server after successful installation, and it may be displayed or regenerated with the print_manifest command. See print_manifest(1M).

The combined software source, config files, and boot information to be written to CD or DVD, used when preparing installation media. It is a single large file in the HP-UX operating system that is written to the medium and used for installation or recovery.

The detection, correlation, and coordinated usage of multiple hardware paths leading to the same LUN.

When a system boots the HP-UX install kernel over the network from an Ignite-UX server.

The state of a file as it is stored in /usr/newconfig before it is moved into place and modified to be system specific. Files in a newconfig state contain no information about the personality of the system.

Stands for Network File System. Allows a client to perform transparent file access over the network.

See MAC address.

Stands for Network Information Service. It allows access from any system to any system with a single user identification and password.

The group of systems sharing NIS configuration information.

Diagnostic utilities stored in the boot area or service partition able to run without the operating system.

With 11i v3, software bundles that are not installed with HP-UX by default. You must select these bundles before installation. Ignite-UX is an example of an optional software bundle.

A portion of a disk device that appears to volume managers, file systems, and other OS software as a disk device. Partitions allow different portions of a disk to hold content needed for boot, OS file systems, diagnostic tools, and other information.

An HP-UX file archiving command that extracts, lists, and writes member files to an archive. Ignite-UX uses pax to produce tar, cpio, and pax formatted archives. See pax(1),tar(1), and cpio(1).

See Processor Dependent Code.

A DSF conforming to the naming model introduced in HP-UX 11i v3 to support agile addressing. The device file name contains an instance number, such as /dev/disk/disk#, and the minor number has no hardware path information.

Device identifier that uses information such as cabinet, bay, and LUN ID to indicate where the device is actually located. Used to indicate a specific device independent of I/O path changes.

An Ignite-UX command that repackages the Ignite-UX product into a depot on an Ignite-UX server in order to distribute Ignite-UX software to client systems that use the Ignite-UX server for network recovery. See pkg_rec_depot(1M).

An Ignite-UX command that displays a manifest of the system it is run on. It can either display the original manifest, or gather information about the current system when it runs. See print_manifest(1M).

The firmware that implements all processor-dependent functionality including initialization and self-test of the processor. Upon completion, it loads and transfers control to the initial system loader. Firmware behavior varies depending on the hardware series. See pdc(1M).

In SD-UX, a collection of filesets, individual filesets, or both.

Stands for preboot execution environment. A protocol built on top of DHCP on HP-UX Itanium-based systems used to request boot services from a server in order to load the operating system.

To stop all running code including the kernel, restart a computer, and boot the system. See shutdown(1M) and reboot(1M).

A compressed tar archive of commands required for expert recovery on PA-RISC systems.

A compressed tar archive of commands required for expert recovery on Itanium-based systems.

With 11i v3, software bundles that are recommended and should be installed with HP-UX because they fulfill required software dependencies, if any exist. You can deselect the bundles before installation.

See system recovery.

An archive that retains host specific customizations from the system. See archive.

A system-specific snapshot of a system that contains hostname, IP address, networking information, all files and directories essential to bringing up a functional system, as well as optionally including specified data on a disk, volume group, file, or directory basis. It is created with make_[tape|net]_recovery.

See expert recovery.

A client system that has its MAC address registered with the server in order to always boot to the same assigned IP address. For PA-RISC systems, the client’s MAC address is assigned to an IP address in the /etc/opt/ignite/instl_boottab or /etc/bootptab file. For Itanium-based systems, the default is to use the /etc/bootptab file.

With 11i v3, software and network driver bundles that are required and always installed with HP-UX. Software in this category cannot be deselected.

An Ignite-UX command that creates a hardware configuration file. It extracts disk and file system information along with certain system and networking parameters for the current system, and writes it to a configuration file. See save_config(1M).

Predefined mechanisms allowing user-defined scripts to run at specific points during the execution of the installation. Within the Ignite-UX installation procedure there are various script hooks: pre-config, pre-load, post-load, post-config, and final. See instl_adm(4) under “Command and Script Execution Hooks.”

A configuration clause of commands in the LIF volume containing scripts that can be selected in the itool under the Advanced tab.

See Software Distributor.

For 11i v1 and 11i v2, software bundles that are not installed by default with HP-UX. You must select these bundles to install them. Ignite-UX is an example of a selectable software bundle.

A computer that provides software and services to clients.

An Ignite-UX command that performs administration tasks for an Ignite-UX server from a command line interface. The same functionality is available with the Ignite-UX GUI. See setup_server(1M).

See depot.

An HP-UX product that provides a set of tools for centralized HP-UX software management. SD-UX commands are included with the installation of the HP-UX operating system. SD-UX commands typically use the prefix “sw”, such as in swinstall and swverify.

In terms of Ignite-UX (as opposed to any other usage) a client system that is not network booted, but may still use an Ignite-UX server for installation or recovery.

A tape containing ANSI standard labeling. Ignite-UX uses ansitape(1) to create a standard label tape.

A separate part of larger a network connected via network gateways.

A use designation typically for an LVM logical volume or a VxVM volume for paging. See swapon(1M).

A use designation typically for an LVM logical volume or a VxVM volume that can be used for DUMP or SWAP.

A compressed tar archive of commands in the LIF volume or on an Ignite-UX server, required for installation of PA-RISC systems.

A compressed tar archive of commands in the LIF volume or on an Ignite-UX server, required for installation of Itanium-based systems.

See image.

The use of a recovery image to reestablish a system.

A method of interacting with computers that employs a character-based display that works on non-graphical terminals. The TUI uses a keyboard for navigation, not a mouse.

A method of using the Ignite-UX tape recovery tool when a system or I/O interface does not support firmware tape boot. The method involves step 1: booting from installation media such as DVD or CD, and then step 2: recovering from tape.

A general term for a LUN identifier, which might specifically be a physical disk's WWID, a WWID assigned to a SAN virtual LUN, the uniq_name assigned to a LUN for which a WWID could not be obtained, or some other type of identifier unique to a LUN.

A set of products from Symantec that include VxVM and VxFS.

The installation kernel for V-class PA-RISC systems.

The associated file system for the VINSTALL kernel.

The default kernel filename, used during normal system operation. vmunix is built by the mk_kernelcommand, which Ignite calls during system installation. The AUTO file typically contains the entry “boot vmunix”, which references /stand/vmunix on the selected boot device.

1. A pool of data storage made up of one or more physical disks. These volumes are created and managed using tools from one of the volume managers, VxVM or LVM. See volume manager. 2. A tape, especially when ANSI labeled.

An arbitrary grouping of disks for use by LVM. See volume manager.

A subsystem for managing disk space that allows one or more disks to be combined. It can provide increased size, improved reliability via data and path redundancy, greater configuration flexibility, and other features for managing file system space.

A Veritas product from Symantec that is a file system implementation.

A specific volume manager type that is a Veritas product from Symantec. See volume manager.

Refers to the WINSTALL, VINSTALL, IINSTALL, or INSTALL installation kernel depending on your system.

Refers to the WINSTALLFS, VINSTALLFS, IINSTALLFS, or INSTALLFS file system depending on your system.

A volume management selection that treats the entire disk as one volume. This selection does not use a volume manager product. For bootable disks, it is a practical selection only for Itanium-based systems.

The installation kernel for 64-bit PA-RISC systems.

The associated file system for the WINSTALL kernel.

Stands in part for network time protocol. The xntpd daemon maintains system time in agreement with Internet standard time servers. This can be configured from the itool System tab under Network Services->XNTP.