Ignite-UX Reference for HP-UX 11i HP Part Number: B3921-90005 Published: March 2010 Edition: 18
© Copyright 2009, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
1 Related information 1.1 Documents The following documents are available on the HP Business Support Center (BSC) www.hp.com/bizsupport/ and most are available on the HP-UX core documents page on the BSC www.hp.com/go/hpux-core-docs. The Ignite-UX documents page on the BSC is www.hp.com/go/ignite-ux-docs and the HP-UX Software Deployment documents page is www.hp.com/go/sw-deployment-docs.
— Product announcements — Access to downloads of the latest version of Ignite-UX • • • • • • • • • • • • 4 Ignite-UX Software Depot webpage http://www.hp.com/go/ignite-ux-download Links to documentation can be found on the Business Support Center http:// www.hp.com/go/ignite-ux-docs HP_UX_Docs Twitter account http://www.twitter.com/HP_UX_Docs HP-UX 11i Knowledge-on-Demand: Best practices from our lab to yours http:// h71028.www7.hp.com/enterprise/us/en/os/ hpux11i-kod-overview.
add_new_client(1M) add_new_client(1M) NAME add_new_client − add a client to an Ignite-UX server SYNOPSIS /opt/ignite/bin/add_new_client [ -? ] -s Ignite-UX_Server [-R release_name] [ -f ] [ -d ] DESCRIPTION add_new_client is used to construct a client directory on an Ignite-UX server without requiring the client to be booted from the Ignite-UX server first. The add_new_client command must be executed on the client and requires privileged user permission.
add_new_client(1M) add_new_client(1M) For 11.31 or later, run the shareall command to have the edits to the exports file take effect: /usr/sbin/shareall -F nfs For other releases, run the exportfs command to have the edits to the exports file take effect: /usr/sbin/exportfs -av International Code Set Support Ignite-UX uses a variety of system commands to accomplish its functionality.
add_new_client(1M) add_new_client(1M) /opt/ignite/lbin/loadfile /opt/ignite/lbin/rescan_hw_host SEE ALSO exportfs(1M), exports(4), ignite(5), nfs(7).
ANSITAPE(1M) Merlin ANSITAPE(1M) NAME ansitape − ANSI-standard magtape label program SYNOPSIS ansitape txrcpuA[vqfaei3] [mt=device] [vo=volume-name] [wo=output_file] [r|recordsize]] [bs=blocksize] [rf=[v|f]] [cc=[i|f|e]] filename1 filename2... [rs= DESCRIPTION Ansitape reads, writes, and creates magtapes conforming to the ANSI standard for magtape labelling. Primarily, this is useful to exchange tapes with VAX/VMS, which makes this kind of tape by default.
ANSITAPE(1M) A Merlin ANSITAPE(1M) This option is used to create an Ignite-UX recovery tape archive label. MODIFIER KEY LETTERS These key letters are part of the first argument to ansitape. v Normally ansitape does its work silently; the v (verbose) option displays the name of each file ansitape treats, preceded by the function letter. It also displays the volume name of each tape as it is mounted.
ANSITAPE(1M) Merlin ANSITAPE(1M) have variable record sizes with a smaller maximum, you must specify: rs=recordsize rf=v When the recordsize is manually given, ansitape does not read disk files to determine the maximum record length. rs=r This is a variant of the rs= option. This causes ansitape to read all disk files for recordsize, regardless of their size. Normally, files larger than 100K bytes are not scanned for recordsize. Using this option also implies variable-length records.
ANSITAPE(1M) Merlin ANSITAPE(1M) Note to Systems Programmers ansitape uses a boolean function (eot) to determine when the tape drive has hit the end of file. It is called every time a block of data is written to the tape. If this function ever returns TRUE (a defined constant), an automatic volume switch occurs. The pertinent device registers are obtained by a MTIOCGET ioctl system call. The registers are described in /sys/sundev/tmreg.h (Sun system with TapeMaster controller).
archive_impact(1M) archive_impact(1M) NAME archive_impact − calculate file system impacts for tar, cpio, and pax archives SYNOPSIS /opt/ignite/lbin/archive_impact fragment_size ] tar_archive [ -? ] -t [ -g | -z ] [ -l level ] [ -b block_size ] [ -f /opt/ignite/lbin/archive_impact fragment_size ] cpio_archive [ -? ] -c [ -g | -z ] [ -l level ] [ -b block_size ] [ -f /opt/ignite/lbin/archive_impact fragment_size ] pax_archive [ -? ] -p [ -g | -z ] [ -l level ] [ -b block_size ] [ -f DESC
archive_impact(1M) archive_impact(1M) EXAMPLES Generate file system impacts for the gzip compressed tar archive named mysys.tar.gz: archive_impact -t -g mysys.tar.gz Generate file system impacts for the compressed cpio archive named othersys.cpio.Z : archive_impact -c -z othersys.cpio.Z SEE ALSO pax(1), make_sys_image(1M), instl_adm(4), ignite(5).
auto_adm(1M) auto_adm(1M) NAME auto_adm − manage LIF AUTO configuration files SYNOPSIS /opt/ignite/bin/auto_adm [ -p platform] [ -f infile] [ -o outfile] [ -O output_format] [ -? ] /opt/ignite/bin/auto_adm [ -p platform] -n -T timeout -M message -l label -c command -b device -i image [ -o outfile] [ -O output_format] [ -? ] /opt/ignite/bin/auto_adm [ -p platform] -a -l label -c command -b device -i image [ -f infile] [ -o outfile] [ -O output_format] [ -? ] /opt/ignite/bin/auto_adm [ -p platform] -A app
auto_adm(1M) auto_adm(1M) -n Create a new AUTO or auto_conf file, and initialize it with data specified by the -T, -M, -l, -c, -b and -i options. -T timeout Specifies the timeout in seconds before the default action is taken. Zero (0) means wait indefinitely. -M message Specifies the kernel boot prompt message. -l label Specifies the label to write into new or modified records. -c command Indicates the ISL command to run when a record is executed.
auto_adm(1M) auto_adm(1M) auto_adm -f conf1 -O ISL This produces the following output: hpux KernelPrompt "Choose version to install" 0 1 reset "B.11.11 32bit install" boot (;0)boot/Rel_B.11.
auto_adm(1M) auto_adm(1M) 7 Could not open output file. 8 Requested record not found. 9 Internal Error. 10 File locked. AUTHOR auto_adm was written by Hewlett-Packard Company. SEE ALSO auto_adm(4), lif(4).
bootsys(1M) bootsys(1M) NAME bootsys − reboot and install clients using Ignite-UX SYNOPSIS /opt/ignite/bin/bootsys [ -a|-w ] [ -dvhrfS ] [ -i configuration |-R target_operating_system_release] [[ -l sw-sel=true|false]...] [-V var[=value]...] [ -s grace ] [ -t Ignite-UX_server ] [ -g gateway ] [ -m netmask ] [client1[:IP_address]] [client2[:IP_address]...] [-?] /opt/ignite/bin/bootsys -c Ignite-UX_Server [-a|-w] [-dvhrfS] [-i configuration | -R target_operating_system_release] [-l sw-sel=true|false]...
bootsys(1M) bootsys(1M) -w Causes the client system to boot Ignite-UX and then wait for the ignite user interface running on the Ignite-UX server to instruct the client on how to proceed with the installation. If neither the -a nor the -w option is given, the client will boot using the default mode stored in the /opt/ignite/boot/Rel_release/*INSTALLFS file. The keywords that control executing the user interface are control_from_server and run_ui.
bootsys(1M) bootsys(1M) -l sw-sel=true| false One or more -l options may be supplied to modify the default software that is selected for loading by the set of clients being installed. This is useful when automating installations where using just the -i option to select the configuration does not give enough control.
bootsys(1M) bootsys(1M) Blocking bootsys Attempts For computing environments in which the server has .rhosts permission to all systems, it is sometimes desirable to block the bootsys command from being able to execute on critical systems. This helps to prevent users from accidentally targeting the wrong system or a system that is actively in use and not yet ready to be installed. bootsys may be blocked by creating the file /.bootsys_block on the clients that you do not want to be reinstalled.
bootsys(1M) bootsys(1M) The host key prompt above is only issued once. Upon answering "yes", that host’s public key is stored in the user’s ˜/.ssh/known_hosts file and is validated for each new ssh session.
bootsys(1M) bootsys(1M) when its -u option is used. Note that the AUTO file is automatically restored if you installed to a different disk from the original boot disk. The bootsys_prep -u command is executed automatically the first time you boot from a disk on which bootsys has previously been executed: boot primary isl ISL> hpux /stand/vmunix Automatically install B.11.23 on the systems listed, and ignore clients that cannot be accessed: bootsys -a -R B.11.
check_net_recovery(1M) check_net_recovery(1M) NAME check_net_recovery − compare contents of network recovery image to a running system SYNOPSIS /opt/ignite/bin/check_net_recovery -s Ignite-UX_server [-?] DESCRIPTION check_net_recovery compares the files on a currently running system with a network recovery archive created by make_net_recovery.
check_net_recovery(1M) check_net_recovery(1M) International Code Set Support Ignite-UX uses a variety of system commands to accomplish its functionality. Because the output of many of these commands is parsed, Ignite-UX ensures that the POSIX locale is normally used by modifying environment variables. Help text and some command output not parsed by Ignite-UX will be left in the user’s specified locale.
check_tape_recovery(1M) check_tape_recovery(1M) NAME check_tape_recovery − compare contents of a tape recovery image to a running system SYNOPSIS /opt/ignite/bin/check_tape_recovery [-?] DESCRIPTION check_tape_recovery compares the files on a currently running system with a tape recovery archive created by make_tape_recovery.
check_tape_recovery(1M) check_tape_recovery(1M) specified locale. EXAMPLES check_tape_recovery may produce the following output: Generating new list of files Comparing file lists Added: /etc/opt/resmon/log/client.log.old Added: /etc/opt/resmon/log/registrar.log.
copy_boot_tape(1M) copy_boot_tape(1M) NAME copy_boot_tape − replicate a PA-RISC or HP Integrity boot tape SYNOPSIS /opt/ignite/bin/copy_boot_tape −u no_rewind_tape_device −p no_rewind_tape_device [ -M ] [ -v ] [ -? ] /opt/ignite/bin/copy_boot_tape −u no_rewind_tape_device −d directory [ -M ] [ -v ] [ -? ] /opt/ignite/bin/copy_boot_tape −p no_rewind_tape_device −d directory [ -M ] [ -v ] [ -? ] DESCRIPTION copy_boot_tape may be used to make a copy of a boot tape created with either make_tape_recovery, m
copy_boot_tape(1M) copy_boot_tape(1M) required if the tape contains variable size records, however if the records within a file in the tape are fixed or are in decreasing order, then the option may be safely ignored to take advantage of the improved performance. This option is not required to copy tapes created by Ignite-UX.
createMediaCatalogs(1m) createMediaCatalogs(1m) NAME createMediaCatalogs − create multi-media catalog for B.11.31 media SYNOPSIS /opt/ignite/data/scripts/createMediaCatalogs [... ] DESCRIPTION The createMediaCatalogs command is to used to create the multi-media catalog required for custom depot-based B.11.31 install media spanning multiple DVDs or other removable/mountable media (e.g. USB memory).
ignite(1M) ignite(1M) NAME ignite - manage an Ignite-UX server SYNOPSIS /opt/ignite/bin/ignite [config|version|client] [options] DESCRIPTION The ignite command is used to manage Ignite-UX server operation and control HP-UX client systems managed by the Ignite-UX server. The ignite command may be used to start a user interface for interactive management of the server and client systems. Normal interactive use of the ignite command is documented in the ignite−ui(1M) manual page.
ignite(1M) ignite(1M) AUTHOR Ignite-UX was developed by the Hewlett-Packard Company. FILES /var/opt/ignite/logs/ignite Modifications made to the system using the ignite command will be logged to this file. Read-only queries are not logged. SEE ALSO ignite−client(1M), ignite−config(1M), ignite−ui(1M), ignite−version(1M), ignite(5).
ignite-client(1M) ignite-client(1M) NAME ignite client - report Ignite-UX client information and manage client activities SYNOPSIS ignite client [-?] ignite client list [-?] -m xml [-l summary|status|details] [-a tag[.attr][=value]] [-x option=value] [client ...] ignite client modify [-?] [-m flat|xml] [-a attribute=value] client ignite client install [-?] [-m flat|xml] [-x option=value] [-c cfg] client ...
ignite-client(1M) ignite-client(1M) Options ignite client recognizes the following options: -a attribute=value Used to specify attributes for operation. The modify minor mode supports setting one attribute, client_name. Setting this value allows you to change the display name of an Ignite-UX client. The add minor mode supports several attributes for specifying information about the client to add. mac_addr MAC (LLA) hardware lan address. This attribute is required. uuid Universal Unique ID.
ignite-client(1M) ignite-client(1M) progress Percent complete of step. status Current status of the step. Can be one of the values: Waiting, Active, Complete, Error, Warning, Stopped, or WaitBoot. -a tag[[.attr]=value] When used with the list minor mode, the -a option allows filtering of the output to only content that matches the filter. Any XML elements that match the filter, and their ancestor elements will be included in the output. • -a tag will match any xml nodes whose name is tag. • -a tag.
ignite-client(1M) ignite-client(1M) Other extended options: clear_status Controls whether client_status file should be cleared. This option may be specified with the add or set_status minor modes. Allowed values are true or false (default). action A required option for control minor mode, specifying the word to place in client’s instruction file. Allowed values are: start_install, halt_install, reboot_client, and recovery_shell.
ignite-client(1M) ignite-client(1M) Example output: PAGE 38ignite-client(1M) ignite-client(1M)
List clients that have cfg attribute set to "HP-UX B.11.11 Default": ignite client list -m xml -l details -a attr.cfg=’HP-UX B.11.11 Default’ Add IPF client using DHCP to determine networking information: ignite client add -a mac_addr=0x0123456789AB client Add IPF client, setting up bootptab to automatically boot client into 11iv3 install environment: ignite client add -a mac_addr=0x0123456789AB -a release=B.11.
ignite-client(1M) ignite-client(1M) /var/opt/ignite/clients//server.instr File written to by the control minor mode to instruct the client on what action to perform. SEE ALSO ignite(1M), ignite−config(1M), ignite−ui(1M), ignite−version(1M), ignite(5).
ignite-config(1M) ignite-config(1M) NAME ignite config - list Ignite-UX configuration clause information. SYNOPSIS ignite config [-?] ignite config list [-?] -m xml [-x option=value] DESCRIPTION Reports configuration clauses available on Ignite-UX server in XML-format. Only configuration clauses defined in /var/opt/ignite/data/INDEX are listed. (See instl_adm(4) and manage_index(1M) for details on how to define configuration clauses.
ignite-config(1M) ignite-config(1M) } cfg "HP-UX B.11.31" { description "Default B.11.31" "/opt/ignite/data/Rel_B.11.31/config" "/opt/ignite/data/Rel_B.11.31/hw_patches_cfg" "/var/opt/ignite/data/config.local" } AUTHOR Ignite-UX was developed by the Hewlett-Packard Company. FILES /var/opt/ignite/data/INDEX SEE ALSO ignite(1M), ignite−client(1M), ignite−ui(1M), ignite−version(1M), manage_index(1M), instl_adm(4), ignite(5).
ignite-ui(1M) ignite-ui(1M) NAME ignite − Interactive HP-UX configuration, installation, and recovery manager SYNOPSIS /opt/ignite/bin/ignite [-recovery] [-install] [-S] [XToolkit-Options] [client1,client2,client3,...] DESCRIPTION The default mode of operation of the ignite command is to start the interactive user interface. If display is specified using the DISPLAY environment variable or the -display option, an interactive X-Windows graphical user interface (GUI) will be started.
ignite-ui(1M) ignite-ui(1M) SEE ALSO ignite(1M), ignite−client(1M), ignite−config(1M), ignite−version(1M), ignite(5).
ignite-version(1M) ignite-version(1M) NAME ignite version - list Ignite-UX server version information SYNOPSIS ignite version [-?] -m xml DESCRIPTION Writes XML-formatted version information of Ignite-UX server to standard output. This version information is important for programs to correctly handle future enhancements of the ignite command (see ignite(1M)). XML Attributes ignite_rev Indicates Ignite-UX product revision installed on server.
instl_adm(1M) instl_adm(1M) NAME instl_adm − maintain Ignite-UX configuration files SYNOPSIS /opt/ignite/bin/instl_adm [ -d ] [ -F filesystem|LIF_volume ] [ -h hostname ] [ -s SD_server[:depot_directory]] [ -g gateway ] [ -m netmask ] [ -t install_tftp_server ] [ -S dhcp_server ] [ -a message_file|- ] [-?] /opt/ignite/bin/instl_adm [ -d ] [ -c ] [ -f configuration_file ] [ -F filesystem|LIF_volume ] [-?] /opt/ignite/bin/instl_adm -T [ -i index_file | -D client_directory | -f configuration_file ] [-?] /o
instl_adm(1M) instl_adm(1M) assigned its own unique IP address. Supplying this default is not recommended if multiple installs are to execute simultaneously, because only one active host may occupy a given IP address at any given time. The use of a Dynamic Host Configuration Protocol (DHCP) server is the recommended method of supplying a default host name and IP address to installation clients. See the bootpd(1M) manpage for details on DHCP.
instl_adm(1M) instl_adm(1M) default file system and software configuration that is selectable during an install. This file is referenced by the INDEX file on the media. On an IgniteUX server, there may be numerous configuration files referenced by the INDEX file. −T Tests for proper syntax of all the configuration files listed in the INDEX file, as well as the configuration file data in the first 8K of the *INSTALLFS file (when no -f or -D option is given).
instl_adm(1M) instl_adm(1M) vi /tmp/cfg instl_adm -f /tmp/cfg Create a customized cold-install tape that gives a message to the user. This uses dd to extract the tape data, instl_adm to modify it, and dd to write a new tape. mt -t /dev/rmt/0m rew dd if=/dev/rmt/0m of=/tmp/tape.image bs=2k instl_adm -F /tmp/tape.image -a message_file mt -t /dev/rmt/0m rew dd if=/tmp/tape.image of=/dev/rmt/0m bs=2k AUTHOR Ignite-UX was developed by Hewlett-Packard Company.
instl_bootd(1M) instl_bootd(1M) NAME instl_bootd − boot protocol server for Ignite-UX clients SYNOPSIS /opt/ignite/lbin/instl_bootd [-s] [-r reuse_time ] [-t timeout ] [-d debug_level ] [-c command ] [-C command ] [-P port ] [-b boot_file ] [ instl_boottab ] [-?] DESCRIPTION instl_bootd is a boot protocol daemon that responds to boot requests from clients wishing to install an operating system using the Internet Boot Protocol (BOOTP) as defined in RFC951 and RFC1048.
instl_bootd(1M) instl_bootd(1M) option causes instl_bootd to execute command every time it responds to a boot request. -P port Override the default User Datagram Protocol (UDP) port numbers defined by services(4) for instl_boots and instl_bootc. Default values are 1067 and 1068 respectively. This causes instl_bootd to listen and respond to boot requests on port and port+1. port becomes the server port (instl_boots) and port+1 becomes the client port (instl_bootc).
instl_bootd(1M) instl_bootd(1M) client to which it is allocated. Once field 2 is set, the entry cannot be allocated to any other client. When instl_bootd receives a boot request, it searches instl_boottab for an IP address issued to the client during a prior boot request. If the search is unsuccessful, instl_bootd searches for the IP address with the oldest time stamp. An IP address may be marked with a reserve keyword, which causes instl_bootd to allocate the address to the client specified in field 2.
instl_bootd(1M) instl_bootd(1M) In addition to the services provided by instl_bootd, the tftp service must also be configured on the server system, and boot_file must be accessible through the tftp service (see tftp(1) and tftpd(1M)). AUTHOR bootpd was developed by Carnegie Mellon University and Stanford University. instl_bootd was derived from bootpd by Hewlett-Packard Company.
instl_combine(1M) instl_combine(1M) NAME instl_combine − combine a LIF file and file system for use on CD/DVD SYNOPSIS /opt/ignite/lbin/instl_combine [ -F LIF_volume ] -C file_system_image [-?] DESCRIPTION instl_combine is used when making an installation CD (or DVD) that contains a boot LIF volume and a mountable file system (either ISO9660/CDFS or HFS).
instl_combine(1M) instl_combine(1M) International Code Set Support Ignite-UX uses a variety of system commands to accomplish its functionality. Because the output of many of these commands is parsed, Ignite-UX ensures that the POSIX locale is normally used by modifying environment variables. Help text and some command output not parsed by Ignite-UX will be left in the user’s specified locale.
instl_combine(1M) instl_combine(1M) created in El-Torito format. Example 4 Create an Ignite-UX LIF image suitable for use on Itanium®-based architecture systems. Note that make_medialif by default creates a LIF_volume that matches the system on which the command is run. This example works even when run on a PA-RISC system to create media for an B.11.23 Itanium®-based system, but requires specifying the -o ipf -r B.11.23 options. make_medialif -c "B.11.23 CD cfg" -o ipf -r B.11.23 \ -l /var/tmp/IPF.
instl_dbg(1M) instl_dbg(1M) NAME instl_dbg − parse and debug an Ignite-UX client’s configuration files SYNOPSIS /opt/ignite/bin/instl_dbg -D client_directory [-f file] [-v] [-a {l|r}] [-cdlsh|-A] [-V var[=value]] [-S swsel[=TRUE|=FALSE]] [-U use_model[=TRUE|=FALSE]] [-n] [-?] DESCRIPTION instl_dbg is used to parse a client’s configuration files for syntax errors, place all relevant configuration information into one file, display/set variables, software selections, and use models, and detect any other
instl_dbg(1M) instl_dbg(1M) -l Instructs instl_dbg to perform a lint-type checks on the configuration files. These checks look for possible errors such as not initializing a variable with the init keyword, redefining disk layout structures (volume groups, physical disks, etc.), and overwriting instead of appending lists. -s Instructs instl_dbg to display all sw_sel, variables, and use model attributes to stdout.
instl_dbg(1M) instl_dbg(1M) 12 (twelve) will occur when there are warnings from the lint-type checks and any software access checks failed. EXAMPLES Debug iux_client’s configuration files and print the final configuration file to stdout: instl_dbg -D /var/opt/ignite/clients/iux_client -f Debug iux_client’s configuration files, print the disk and file system information to stdout, and save the final configuration file to my_cfg.out: instl_dbg -D /var/opt/ignite/clients/iux_client -d -f my_cfg.
make_boot_tape(1M) make_boot_tape(1M) NAME make_boot_tape − make a bootable tape to connect to an Ignite-UX server SYNOPSIS /opt/ignite/bin/make_boot_tape [ -d device_file_for_tape] [ -f configuration_file] [ -t tmp_directory] [ -v ] [ -? ] /opt/ignite/bin/make_boot_tape [ -d device_file_for_tape] [ -g gateway ] [ -m netmask ] [ -t tmp_directory] [ -v ] [ -? ] DESCRIPTION The tape created by make_boot_tape is a bootable tape that contains just enough information to boot a PA-RISC system and connect to
make_boot_tape(1M) make_boot_tape(1M) starting point for what is written to the tape. −g gateway Specifies the default Internet address for the gateway system through which the target system may reach the Ignite-UX server. This is useful when the target systems are not on the same subnet as the Ignite-UX server. The configuration already in /opt/ignite/boot/Rel_release/*INSTALLFS is used as a starting point in this case. The gateway specified is added to this data.
make_boot_tape(1M) make_boot_tape(1M) make_boot_tape -f tmp_configuration_file -t /tmp Create a boot tape and specify a different gateway IP address. Set the netmask value as well. All other configuration information is from what is already in the /opt/ignite/boot/Rel_release/INSTALLFS file. make_boot_tape -g 15.23.34.123 -m 255.255.248.0 NOTES make_boot_tape is currently limited to PA-RISC systems only. AUTHOR Ignite-UX was developed by Hewlett-Packard Company.
make_bundles(1M) make_bundles(1M) NAME make_bundles − create SD bundles in a depot SYNOPSIS /opt/ignite/bin/make_bundles { -b| -B} [ -i ] [ -n name ] [ -t title ] [ -c category ] [ -o psf ] [ -r revision ] depot_path [ -? ] /opt/ignite/bin/make_bundles [ -b ] [ -p| -f] [ -i ] [ -c category ] [ -o psf ] depot_path [ -? ] /opt/ignite/bin/make_bundles { -p| -f| -B } [ -i ] [ -c category ] [ -o psf ] [ -l file | product/fileset...
make_bundles(1M) make_bundles(1M) -c category Supplies the category for the bundle(s) that will be created. The default is to leave the bundles uncategorized. -o psf Causes make_bundles to create a product specification file and write it to the given psf without actually modifying the target depot. This may be useful in editing the bundle names or descriptions before running swpackage to create the bundles in the depot.
make_bundles(1M) make_bundles(1M) FILES /opt/ignite/lib/sd_opts Contains the list of SD options used by the swlist and swpackage commands run by make_bundles (as well as many other Ignite-UX commands). These options take precedence over the /var/adm/sw/defaults file in order to ensure the SD commands behave in an expected manner. Modifications to this file may cause make_bundles to not work as expected. SEE ALSO make_config(1M), sd(4), ignite(5).
make_config(1M) make_config(1M) NAME make_config − build Ignite-UX configuration files for SD depots SYNOPSIS /opt/ignite/bin/make_config -r release [ -o os_release] [ -l release_relative_source_depot] [ -v ] [ -x option] [ -d percent] [ -? ] level] [ -p ] [ -s /opt/ignite/bin/make_config -s source_depot -c configuration_file [ -a 700|800|both ] [ -f software_file] [ -o os_release] [ -l level] [ -p ] [ -d percent] [ -v ] [ -x option] [ -? ] DESCRIPTION make_config constructs Ignite-UX configuration
make_config(1M) make_config(1M) −s source_depot Specify a single source depot to process. The depot is specified just as in the SD commands. If the depot is on the local machine, specify the depot’s path name. If the depot is on a remote machine, specify remote_host_name:remote_depot_path. −c configuration_file Specify the name of the resulting configuration file. −a 700|800|both Specify the architecture of the bundles which should be processed (matches the bundle.architecture attribute).
make_config(1M) make_config(1M) −x option Specify particular optional behaviors. The options available via -x are: allow_missing_content By default, an error is given if any bundles that an B.11.31 or later operating environment calls out as "required" are missing from the depot. If -x allow_missing_content is provided, then only a warning message will be given in this case and the config file will be produced excluding any missing bundles.
make_config(1M) make_config(1M) /var/opt/ignite/data/Rel_B.11.23/depot1_cfg: make_config -r B.11.23 -s depot1 To process the depot found in /var/mydepot and create a configuration file for it at /home/me/my_cfg_file. (Do not modify /var/opt/ignite/data/INDEX.) make_config -s /var/mydepot -c /home/me/my_cfg_file SEE ALSO instl_bootd(1M), make_depots(1M), manage_index(1M), print_manifest(1M). instl_adm(4), ignite(5).
make_depots(1M) make_depots(1M) NAME make_depots − build Ignite-UX SD depots SYNOPSIS make_depots −d target_depot [ -r release ] [ option ] [ -? ] make_depots −r release [ option ] [ -? ] DESCRIPTION make_depots copies bundles from a Software Distributor (SD) source into a depot which may be used by other Ignite-UX tools. While it may be invoked directly by a user, it is provided mainly for use by other Ignite-UX commands.
make_depots(1M) make_depots(1M) −x swcopy_option Specifies an option that is passed onto the swcopy command invoked by make_depots (see swcopy(1M)). −i Specifies that only bundles that are marked as "ignitable" should be processed. Ignitable bundles are those that have the hp_ii.factory_integrate attribute set to TRUE, and may be included on factory-installed HP-UX systems. −v Specifies verbose mode. −p Specifies preview mode. Commands are displayed to stdout instead of actually being executed.
make_depots(1M) make_depots(1M) make_depots -r B.11.23 -a 700 -s /dev/dsk/c0t3d0 -o B.11.23 \ −x codeword="jona than alli sonk" −x customer_ID="Mykids Company" Process only Series 800 ignitable B.11.23 bundles found on a remote depot on client molly under a directory entitled peaches: make_depots -r B.11.23 -d peaches -s molly:/var/depot/Source \ −i -o B.11.23 -a 800 WARNINGS Some HP media contains protected software.
make_ipf_tape(1M) make_ipf_tape(1M) NAME make_ipf_tape − create an ANSI labeled bootable tape for an Integrity system SYNOPSIS /opt/ignite/bin/make_ipf_tape −f config_file [ -f config_file ...] | −F config_file [ -F config_file ... −C cfg_clause ...] | −c cfg_clause [ -C cfg_clause] [ -d tape_device_file] [ -n vol_name] [ -l LIF_file] [ -r release] [ -s script_file ...] [ -V] [ -w output_file] [ -?] DESCRIPTION make_ipf_tape creates an ANSI labeled bootable tape for an Integrity system.
make_ipf_tape(1M) make_ipf_tape(1M) −n volume_name Specifies the name of tape volume. Normally, this defaults to the first six characters of "HP" plus month and date the tape created. −l LIF_file Specifies where the resulting LIF volume (boot image) file is to be written. The default is /var/tmp/HPUXIUXLIF. −r release Specifies the OS release for this ANSI bootable tape. The default release is the output of uname -r, that is, matching the release of the HP-UX system on which the command is run.
make_ipf_tape(1M) AUTO make_ipf_tape(1M) A file indicates the BOOTLOADER command arguments controlling boot. IINSTALL Integrity kernel booted by Integrity install clients. IINSTALLFS This file is a install file system matching the install kernel. HPUXIUXLIF A LIF volume supplies following files needed by Ignite-UX. INDEX Not normally used in tape recovery, may have custom user recovery configuration to point to network depot.
make_medialif(1M) make_medialif(1M) NAME make_medialif − create bootable Ignite-UX LIF media image file SYNOPSIS /opt/ignite/bin/make_medialif −f config_file [ -f config_file ...] | −F config_file [ -F config_file ... −C cfg_clause ...] | −c cfg_clause [ -C cfg_clause ] [ -r release ] [ -o 32|64v|64w|IA | -a] [ -s script_file ...
make_medialif(1M) make_medialif(1M) -o 32|64v|64w|IA Specifies whether the LIF volume (boot image) should support hardware (install kernel) type 32-bit (PA-RISC), 64-bit (V-class PA-RISC), wide 64-bit (PARISC), or Itanium®-based. The default is to match the system on which the command is run. For convenience, 64 may be used as a synonym for 64v, and any of ia, ipf, or IPF may be used as a synonym for IA. This option cannot be combined with the -a option.
make_medialif(1M) make_medialif(1M) INSTALLFS is a symbolic link to INSTALLFS, this is preserved in the LIF volume. This option cannot be combined with any of −f, −c, −C, −a, −s, or −S. -? Displays the usage text. International Code Set Support Ignite-UX uses a variety of system commands to accomplish its functionality. Because the output of many of these commands is parsed, Ignite-UX ensures that the POSIX locale is normally used by modifying environment variables.
make_medialif(1M) make_medialif(1M) cp /opt/ignite/data/examples/core.cfg /home/root/config_cd" chmod u+w /home/root/config_cd In /home/root/config_cd comment out the nfs_source, ftp_source and remsh_source lines and change or uncomment the following objects: software object sw_source sw_sel field source_type source_format load_order change_media sw_source archive_path archive_type impacts value "DSK" ARCHIVE 0 FALSE label of above sw_source "myimage.
make_medialif(1M) make_medialif(1M) may be helpful to test the image before writing it to CD. Example 4 To create a boot LIF image (as in Example 2) with an archive on a B.11.23 client for a B.11.11 client, you would execute the following command: make_medialif -f /opt/ignite/data/Rel_B.11.11/config -f /home/root/config_cd -r B.11.11 -l /home/root/uxinstlf_cd All subsequent commands in Example 2 should be executed.
make_medialif(1M) make_medialif(1M) env_vars += "INST_ALLOW_WARNINGS=10" env_vars += "INST_BATCH_MODE_TIMEOUT=10" Place these variables in the WINSTALLFS before writing the image to medium using the same tape drive as before: instl_adm -F /home/root/uxinstlf -d > /tmp/cfg vi /tmp/cfg # add the above lines instl_adm -F /home/root/uxinstlf -f /tmp/cfg mt -t /dev/rmt/c0t3d0DDS1n rew dd if=/home/root/uxinstlf of=/dev/rmt/c0t3d0DDS1n obs=2k mt -t /dev/rmt/c0t3d0DDS1n rew Example 7 Unlike DDS tape in which only
make_medialif(1M) make_medialif(1M) Example 8 Suppose there is no archive, but instead an entire core operating system depot to install from DDS tape. Assume that the core depot is in /var/depots/core. To create a configuration file for this depot, you would: make_config -s /var/depots/core -c /home/root/core_cfg In the sw_source section of /home/root/core_cfg, remove the sd_server and sd_depot_dir lines, and then change the source_type from "NET" to "MT".
make_medialif(1M) make_medialif(1M) volume ISL10 data size 960926 directory size 3 04/06/30 13:59:56 filename type start size implement created ===================================================== ISL -12800 16 242 0 04/06/30 13:59:56 AUTO -12289 264 1 0 04/06/30 13:59:56 HPUX -12928 272 1024 0 04/06/30 13:59:56 WINSTALL -12290 1296 83837 0 04/06/30 14:00:03 WINSTALLFS -12290 85136 49152 0 04/06/30 14:00:06 PAD BIN 134288 256 0 04/06/30 14:00:06 Example 11 On a B.11.
make_medialif(1M) AUTO INDEX CONFIG HPUX IINSTALL IINSTALLFS INSTCMDSIA RECCMDSIA SYSCMDSIA SCRIPTS PAD make_medialif(1M) -12289 BIN BIN -12928 -12290 -12290 BIN BIN BIN BIN BIN 264 272 280 376 1400 206568 322792 382904 384720 544968 545016 1 1 92 1024 205161 116224 60112 1815 160242 45 256 0 0 0 0 0 0 0 0 0 0 0 04/06/30 04/06/30 04/06/30 04/06/30 04/06/30 04/06/30 04/06/30 04/06/30 04/06/30 04/06/30 04/06/30 14:52:46 14:52:46 14:52:46 14:52:46 14:52:56 14:52:56 14:52:56 14:52:56 14:53:07 14:53:07 1
make_medialif(1M) make_medialif(1M) /opt/ignite/data/Rel_release/RECCMDSIA gzip-compressed tar archive of recovery commands used in the recovery shell on Itanium®-based systems. /opt/ignite/data/Rel_release/SYSCMDS gzip-compressed tar archive of commands needed to load the rest of the software on PA-RISC systems. Each release has its own version. /opt/ignite/data/Rel_release/SYSCMDSIA gzip-compressed tar archive of commands needed to load the rest of the software on Itanium®-based systems.
make_net_recovery(1M) make_net_recovery(1M) NAME make_net_recovery − network based system recovery archive creation SYNOPSIS /opt/ignite/bin/make_net_recovery -s Ignite-UX_server [ -a archive_server:archive_directory] [ -A] [ -b] [ -d tag_string] [ -f content_file] [ -i|-ib] [ -l LLA] [ -n number_archives] [ -p] [ -P s|w|e] [ -m tar|cpio|pax] [ -r] [ -u] [ -v] [ -x content-options] [ XToolkit_Options] [ -?] DESCRIPTION make_net_recovery creates a system recovery archive and stores the archive on the ne
make_net_recovery(1M) make_net_recovery(1M) -f content_file Location of the file which identifies keywords to specify inclusions and exclusions for the archive. The default is /var/opt/ignite/clients/0xLLA/recovery/archive_content. This default file is located on the Ignite-UX server and accessed by the client through an NFS mount. The absolute path name to the archive_content file must be supplied as an argument to the -f option.
make_net_recovery(1M) make_net_recovery(1M) have possibly been edited. If the -A and -r options are both used, the -A option will be ignored, since the file list, flist, and other configuration files, *_cfg, have been created and possibly modified. -u Updates the Ignite-UX software from the Ignite server specified by the -s option. This is done only when the version of software on the server is newer than the client.
make_net_recovery(1M) make_net_recovery(1M) identifiers: include filename | directory Includes the specified filename or directory and all subdirectories and associated files. Mount points are not crossed and symbolic links are not followed. Note, file names may NOT end with a space. inc_cross filename | directory Include the specified filename or directory and all subdirectories and files contained underneath subdirectories. Local mount points are crossed but symbolic links are not followed.
make_net_recovery(1M) make_net_recovery(1M) Using the Recovery Archive To recover a failed system using the network recovery archive: • If the client system is being replaced, or the LAN card has changed since make_net_recovery was last used, you should manually rename the old client directory prior to starting the recovery. Not doing so will cause a new directory to be created and you will not see the recovery archives created under the old client directory.
make_net_recovery(1M) make_net_recovery(1M) /usr/sbin/exportfs -av Networking Features Two NFS mount points are established on the client by make_net_recovery. The /var/opt/ignite/clients directory on the Ignite-UX server is mounted to the client system to store configuration files which describe the client configuration and location of the recovery archive.
make_net_recovery(1M) make_net_recovery(1M) Create a system recovery archive that includes files from all file systems in the vg00 volume group: make_net_recovery -s myserver -x inc_entire=vg00 Create a system recovery archive that includes all of the vg00 and vg01 volume groups, but that excludes the /depots directory: make_net_recovery -s myserver -x inc_entire=vg00 -x inc_entire=vg01 -x exclude=/depots Preview the creation of the System Recovery Archive: make_net_recovery -p Use the -u option to have t
make_net_recovery(1M) make_net_recovery(1M) • ustar format archives may contain raw uids and gids up to 2097152. Because the text user and group name are stored, it may be possible to recover uids and gids larger than 2097152. • cpio format archives are strictly limited to uids and gids up to 262144. • ustar format archives cannot contain a file name pointed to by a link that is more than 100 bytes long (required by POSIX.1).
make_net_recovery(1M) make_net_recovery(1M) Warning: Setting _hp_ignite_sw_impact to 1 may cause recoveries to fail if any file system sizes are reduced below the minimum required. Note that changes to the system_cfg file must be done after a preview has been created (-p). After making the above changes, resume the creation of the tape recovery archive (-r).
make_net_recovery(1M) make_net_recovery(1M) system: Ignite-UX.MGMT-TOOLS Ignite-UX.RECOVERY AUTHOR Ignite-UX and make_net_recovery were developed by the Hewlett-Packard Company. DIAGNOSTICS All major steps within network recovery are logged on the server and displayed via the Ignite-UX Server GUI. FILES /opt/ignite/recovery/mnr_essentials Lists the files and directories that are considered essential and are always included in the archive if they exist on the system.
make_net_recovery(1M) make_net_recovery(1M) /var/opt/ignite/clients/0xLLA/recovery/config.local An optional configuration file that the user may create to add configuration information to be used during the recovery of the client. For example, you may want to add to this file to a post_config_cmd to remirror disks that the recovery process unmirrored. See the document /opt/ignite/share/doc/diskmirror.pdf for an example.
make_sys_image(1M) make_sys_image(1M) NAME make_sys_image − create compressed file archive of a running system SYNOPSIS /opt/ignite/data/scripts/make_sys_image -s IP | hostname | local [ -d directory | device ] [ -f file] [ -l 1 | 2 ] [ -n filename ] [ -r remsh_user ] [ -m c | t | p] [ -c z | g | n ] [ -a archive_size ] [ -R ] [ -g file_list ] [ -t y|n|o|p] [ -i ] [ -p ] [ -u ] [ -v ] [ -w log_file ] [ -x ] [ -L ] [ -? ] DESCRIPTION make_sys_image is used to create a system archive of a running single-
make_sys_image(1M) −l 1 | 2 make_sys_image(1M) Level of system identity clean-up: 1 None (overridden to 2 if the −f option is used). 2 Reset network and login information. Exclude device files, log files, and contents of /stand except /stand/system and /stand/kernrel. Remove hardware specific drivers from the /stand/system that gets archived. Files reset to newconfig state: /.profile /etc/rc.config.d/hpetherconf /etc/rc.config.d/hpfcgsc_lanconf /etc/rc.config.d/hpfcmsconf /etc/rc.config.
make_sys_image(1M) make_sys_image(1M) y Yes, run the tests along with make_sys_image (this is the default). n No, do not run the tests. This may be used on clients that the user knows contain the patch. o Run the tests only; that is, do not make a system image. It always exits and returns a 4 if a patch exists that fixes a pax defect; a 3 if it is an enablement patch (for example PAX-Enh on B.11.
make_sys_image(1M) make_sys_image(1M) SERVER=IP|local Equivalent to the -s option. DEST_DIR=directory|device Equivalent to the -d option. ARCHIVE_NAME=archive_filename Equivalent to the -n option. METHOD=c|t Equivalent to the -m option. COMPRESS=z|g Equivalent to the -c option. CLEAN_LEVEL=1|2 Equivalent to the -l option. International Code Set Support Ignite-UX uses a variety of system commands to accomplish its functionality.
make_sys_image(1M) make_sys_image(1M) remove the host identity and general network information: post_config_script+="make_sys_image -s 15.15.15.99 -l 2 -c z -m c" Create an Ignite-UX configuration file that specifies a cpio archive and compress it to the Ignite-UX server, default destination directory, and default file name: # instl_adm defaults: server="15.1.50.74" netmask[]="0xfffff800" route_gateway[0]="15.1.48.1" route_destination[0]="default" # end instl_adm defaults.
make_tape_recovery(1M) make_tape_recovery(1M) NAME make_tape_recovery − tape based system recovery archive creation SYNOPSIS /opt/ignite/bin/make_tape_recovery [ -s Ignite-UX_server ] [ -a tape_drive] [ -A] [ -b] [ -B boot_destination_file] [ -D tape_volume_name] [ -d tag_string] [ -f content_file] [ -i|-ib] [ -I] [ -l LLA] [ -n number_cfg_directories] [ -p] [ -P s|w|e] [ -m tar|cpio|pax] [ -r] [ -t tape_title_string] [ -u] [ -v] [ -x content-options] [ XToolkit_Options] [ -?] DESCRIPTION make_tape_rec
make_tape_recovery(1M) make_tape_recovery(1M) -B boot_destination_file Specifies the temporary location where the LIF volume will be assembled before it is written to tape. The default file is /var/tmp/uxinstlf.recovery for HP9000 systems and /var/tmp/HPUXIUXLIF for HP Integrity systems. At least 500 MB is required in /var/tmp directory where the LIF volume will be assembled.
make_tape_recovery(1M) -p make_tape_recovery(1M) Previews the processing that would take place without actually creating the tape. This is a way of verifying the directory /var/opt/ignite/recovery/latest (which is linked to the latest archive directory of the form /var/opt/ignite/recovery/date,time) on the local (client) system. To access this directory on a specified Ignite-UX server, the directory is located at /var/opt/ignite/clients/0xLLA/recovery/date,time.
make_tape_recovery(1M) make_tape_recovery(1M) -x inc_cross=file|directory Includes the file or directory in the recovery archive and crosses mount points to access any directories that are mounted or files contained in directories that are mounted. This option is for crossing local files system mounts only; not remote file system mounts. Note, file names may NOT end with a space. -x inc_entire=disk|vg_name Includes all file systems contained on the specified disk or volume group.
make_tape_recovery(1M) make_tape_recovery(1M) exclude filename | directory Exclude the specified filename or directory and all subdirectories and files contained under the subdirectories. Note, file names may NOT end with a space. make_tape_recovery reads the contents file to generate the list of files that will be used to create the system recovery archive. The contents file may be modified by hand or by running make_tape_recovery in interactive mode.
make_tape_recovery(1M) make_tape_recovery(1M) SYSCMDS RECCMDS SCRIPTS VERSION PAD Archive of commands needed for final install Archive of commands needed for expert recovery Scripts used during install post_load Ignite-UX version used to create tape Additional data to create full tape block The second tape file holds the recovery archive. The archive format depends on the options used to create the Recovery Tape.
make_tape_recovery(1M) make_tape_recovery(1M) • interrupt the boot sequence to redirect it to the tape drive, • choose no interaction with ISL, and • allow the install process to complete automatically. Using the Recovery Tape to Clone a System When creating a recovery tape for the purpose of cloning one system to another, it is best to run make_tape_recovery using the -i option.
make_tape_recovery(1M) make_tape_recovery(1M) A rewind mode device special file may be used in this case to simplify repeated attempts to list and extract archive content. Extracting files from tape may take a long time, especially when archives are large. Extracting Files from an Integrity Recovery Tape After the Integrity System Recovery Tape has been created, a single file or files may be extracted from tape by use of the ansitape command.
make_tape_recovery(1M) make_tape_recovery(1M) make_tape_recovery -A make_tape_recovery -s myserver -A Create a system recovery tape that includes files from all file systems in the vg00 volume group: make_tape_recovery -x inc_entire=vg00 make_tape_recovery -s myserver -x inc_entire=vg00 Create a system recovery tape that includes all of the vg00 and vg01 volume groups, but that excludes the /depots directory: make_tape_recovery -x inc_entire=vg00 -x inc_entire=vg01 -x exclude=/depots make_tape_recovery -s
make_tape_recovery(1M) make_tape_recovery(1M) system that was installed. It was not possible to run it in order to correctly set the permissions of the "transition" symlinks. You may consider running: "/opt/upgrade/bin/tlinstall -vf" after the system is completely restored. If software has not yet been installed using SD, the tlinstall command may need to be executed at this time as described above.
make_tape_recovery(1M) make_tape_recovery(1M) volumes will no longer be mirrored. They may be manually remirrored after the system is up. Using the config.local file in the clients directory, you may specify the LVM commands to restore mirrored disks to be executed automatically after the system has been restored. For more details, see the /opt/ignite/share/doc/diskmirror.pdf white paper.
make_tape_recovery(1M) make_tape_recovery(1M) volume groups as input to make_tape_recovery command or migrate all those unsupported volume group version to 2.2 or higher (using LVM’s Volume Group Version migration tool, vgversion) and rerun the command. DEPENDENCIES The Ignite-UX GUI must be run from the Ignite-UX Server, see ignite(5). make_tape_recovery depends on several other Ignite-UX tools.
make_tape_recovery(1M) make_tape_recovery(1M) /var/opt/ignite/clients/0xLLA/recovery/date,time Directory containing files pertaining to the make_tape_recovery command that was run with the -s option at the date and time indicated in the directory name.
manage_index(1M) manage_index(1M) NAME manage_index − manage Ignite-UX INDEX files SYNOPSIS /opt/ignite/bin/manage_index -a -f cfg_filename [-c cfg_clause_name | -r release] [ -p ] [ -v ] [-i index_filename ] [ -? ] /opt/ignite/bin/manage_index -a -s script_filename [ -p ] [ -v ] [-i index_filename ] [ -? ] /opt/ignite/bin/manage_index -d -c cfg_clause_name | -r release [ -p ] [ -v ] [-i index_filename ] [ -? ] /opt/ignite/bin/manage_index -e -c cfg_clause_name [ -p ] [ -v ] [-i index_filename ] [ -? ]
manage_index(1M) −d manage_index(1M) Delete an entire cfg clause or clauses. Which cfg clause(s) gets deleted depends on the other options: With −c: delete a particular cfg clause. With −r: delete all cfg clauses for that release. −e Establish the default cfg clause to be whatever clause is specified in the −c option. If any other cfg clause in /var/opt/ignite/data/INDEX is already the default, the old default is turned off.
manage_index(1M) manage_index(1M) −r release Only process cfg clauses from a given release. An example release is B.11.23. A cfg clause is said to belong to a particular release if any of the configuration files specified in it are located in the release-specific directory for that release. For example, if a cfg clause contains the /opt/ignite/data/Rel_B.11.23/core_cfg file, this cfg clause belongs to the B.11.23 release. −s script_filename Use the specified script.
manage_index(1M) manage_index(1M) Remove the script called /var/opt/ignite/scripts/setup_server from the scripts clause. manage_index -t -s /var/opt/ignite/scripts/setup_server Make the cfg clause called "HP-UX B.11.23 Default" the default: manage_index -e -c "HP-UX B.11.23 Default" Copy the existing cfg clause called "HP-UX B.11.23 Default" to a new clause called "HP-UX B.11.23 Default, DART75". manage_index -n "HP-UX B.11.23 Default" -c "HP-UX B.11.
pkg_rec_depot(1M) pkg_rec_depot(1M) NAME pkg_rec_depot − create a depot containing Ignite-UX recovery filesets SYNOPSIS /opt/ignite/lbin/pkg_rec_depot [ -f ] [ -? ] DESCRIPTION pkg_rec_depot is used to create a software depot on an Ignite-UX server for use in distributing IgniteUX software to client systems that use the server for network system recovery (see make_net_recovery(1M)) and tape system recovery (see make_tape_recovery(1M)).
print_manifest(1M) print_manifest(1M) NAME print_manifest − print a system manifest SYNOPSIS /opt/ignite/bin/print_manifest [ -s ] [ -o ] [ -e ] [ -i hw_path ] [ -d ] [ -? ] DESCRIPTION This utility prints a formatted ASCII system manifest to stdout. The manifest includes information on hardware and software installed and configured on the system. It gathers information about the system every time it is run. A manifest is included with each Instant Ignition system shipped from HP.
save_config(1M) save_config(1M) NAME save_config − create hardware configuration file SYNOPSIS /opt/ignite/bin/save_config [ -f file ] [ vg ...] [ disk ...] [ -? ] DESCRIPTION save_config extracts disk and file system structure information and certain system and networking parameters for the currently running system and writes them into a configuration file. When used in conjunction with an archive, it provides a quick means for restoring a system with Ignite-UX (see ignite(5)).
save_config(1M) save_config(1M) save_config vg00 To display the configuration information to stdout: save_config -f SEE ALSO make_medialif(1M), vgversion(1M), instl_adm(4), ignite(5), lvm(7).
setup_server(1M) setup_server(1M) NAME setup_server − perform some administration tasks for an Ignite-UX server SYNOPSIS /opt/ignite/lbin/setup_server [ -g gateway_ip_address ] ip_address | ip_address_1-ip_address_n | ip_address:MAC_address ] [ -I ip_address | ip_address_1-ip_address_n ] [ -l lan_interface ] [ -c class_id ] [ -t true | false ] [ -h true | false ] [ -n ] [ -u none | target | server | show ] [ -? ] [ -i DESCRIPTION There are several tasks which need to be performed to administer an Ign
setup_server(1M) setup_server(1M) −n Sets NFS mounts to allow client/server communication. This is an optional step. By default, no NFS exports from the server are required. However, if you wish to control the installation process from the server or if you wish to make sure that configuration files and manifest information are placed on the server, you must specify the −n option. This means that /var/opt/ignite/clients will be exported read/write.
setup_server(1M) setup_server(1M) 6 setup_server encountered 1 or more errors. SEE ALSO instl_adm(1M), instl_bootd(1M), make_config(1M), make_depots(1M), manage_index(1M), swinstall(1M), instl_adm(4), ignite(5).
auto_adm(4) auto_adm(4) NAME auto_adm − manage LIF AUTO configuration files DESCRIPTION auto_adm files occur in two different formats, auto_conf (CONF) and Initial System Loader (ISL) format. The auto_adm(1m) utility is used to manipulate these files, and to convert between formats. Information contained in an auto_adm file is used during the boot up process to offer the user a set of boot options, and to direct the ISL and Secondary System Loader (SSL) to execute the desired boot sequence.
auto_adm(4) auto_adm(4) ISL Format The ISL format is the file format actually written into the boot LIF by auto_adm, assembled from one or more CONF-formatted files. Like the CONF format, ISL formatted files consist of a global section and an image-specific section. The global section consists of a single line: hpux KernelPrompt message timeout default reset where the first two words are literally hpux KernelPrompt, and message, timeout, and default are as defined above under the CONF format section.
instl_adm(4) instl_adm(4) NAME instl_adm − Ignite-UX configuration file syntax DESCRIPTION The Ignite-UX configuration files determine the default system configurations available during the process of installing the HP-UX operating system. The Ignite-UX process uses configuration files to bring in default parameters, as well as, determine how the system will be configured.
instl_adm(4) instl_adm(4) The ability to save a modified system configuration through the UI makes use of the INDEX file. When the UI is used to make modifications to the system configuration, Ignite-UX produces a "delta" configuration file that represents the changes. When this delta configuration file is appended to the list of default configuration files, it overrides the defaults with the values you specified.
instl_adm(4) instl_adm(4) performs addition, whereas using it on string variables/keywords performs concatenation. There are several constructs in the configuration-file syntax where a set of parameters are associated with a specific object. For example, the file-system parameters associated with a given file system. If the object being defined has already been defined, the new parameters are merged with any parameters previously assigned to the object.
instl_adm(4) instl_adm(4) value. For example: Swap size in bytes: +${_hp_pri_swap+0}. Variables that the UI does not recognize as special are represented in the Additional button available in the UI on the Basic tab. From the Additional dialog, you may modify the values of any visible variables. Variables do not need to be declared as their type (integer or string) is determined the first time they are assigned and cannot be assigned a different type later.
instl_adm(4) instl_adm(4) The Ignite-UX process uses this information should it need to rewrite the configuration file. The configuration file is rewritten both by the UI and by the client installation process. In these cases, the process uses _hp_cfg_detail_level to determine how much information is represented by the configuration file and so may write the minimal amount of information, and then allow the rest be supplied by the other configuration files in the INDEX file set.
instl_adm(4) instl_adm(4) added. Setting this variable to "true" will cause only the paths explicitly specified for the volume group in the configuration file to be added. This variable has no effect when installing B.11.31 and later. Starting at B.11.31, Ignite-UX uses the agile device files to configure LVM, which takes advantage of all paths to a disk.
instl_adm(4) instl_adm(4) _hp_ht_enable Boolean-string variable that indicates whether to enable HyperThreading on HyperThread-capable systems, as reported by the is_ht_capable variable. Available on HP-UX B.11.31 or later. _hp_ignore_prior_config Boolean-string variable that can be used to prevent the use of the config file in the client’s /var/opt/ignite/clients/ directory. When set to "true" any pre-existing config file will be renamed to config.ignore and then be ignored.
instl_adm(4) instl_adm(4) sw_sels which contain locale keywords, the _hp_locale variable is set to the first value of the locale of the first selected sw_sel. _hp_min_swap Integer variable used as the minimum size the primary swap volume may be reduced to if there is not enough disk space for all other volumes. This value defaults to an amount that should allow the system to boot and run HP-UX.
instl_adm(4) instl_adm(4) _hp_saved_detail_level Internal string variable used in configuration files that have been created by a "Save-As" operation. Like _hp_cfg_detail_level, it contains a list of option characters that represent which aspects of the configuration file have been modified. The format is identical to the _hp_cfg_detail_level variable. _hp_sec_swap Integer variable that may be set in the UI to indicate how much secondary swap the user desires to have allocated in the root volume-group.
instl_adm(4) | instl_adm(4) Logical or operator. Variables in logic expressions must use one of the comparison operators to result in a boolean value. Use model names may appear in logic expressions and are treated as a single boolean value. Following the set of statements surrounded by { } you may supply an else clause followed by a set of statements enclosed in { } brackets. You may also specify conditional statements within conditional statements. For example: (num_disks > 1 & disk[_hp_root_disk].
instl_adm(4) instl_adm(4) disk drives do. See the I/O Configuration section for more information. disk[hw_path|index|dev_spec].device_id Evaluates to the device identifier of the disk specified by the hardware address path, index value or device specifier. Note that this is an attribute set by system administrators and is not guaranteed to be unique. See the I/O Configuration section for more information. disk[hw_path|index|dev_spec].
instl_adm(4) instl_adm(4) uname -m command is used instead. model Evaluates to a string containing the equivalent of the model command, which is typically more descriptive than hardware_model. is_hppa is_ia64 Boolean values that indicate if a system is PA-RISC or Itanium®-based architecture, respectively. is_ht_capable Boolean value that indicates if a system supports HyperThreading. Available on HP-UX B.11.31 or later. num_cpus Evaluates to the number of active processors discovered on the system.
instl_adm(4) instl_adm(4) release A string corresponding to the HP-UX release for which the configuration file contains the system defaults (for example, "B.11.11", "B.11.23", etc.). is_net_info_temporary A boolean value that reflects the choice made by you in the network information screen or as set using the keyword of the same name in the configuration file. (sw_sel string) A boolean value that reflects whether the software selection tag given as string has been selected for loading.
instl_adm(4) instl_adm(4) tools like save_config will not supply it. Use of this attribute is therefore discouraged. Device Specifier (dev_spec): A method that combines the above four types into a single prioritized list of attributes that refer to a disk. The format is a String, which means the entire method is surrounded by double quotes. Tools that create this method determine the order of attributes, based upon which I/O Protocol applies and what release is involved.
instl_adm(4) instl_adm(4) This section contains variables related to advanced features used to control the behavior of I/O configuration during installation and recovery. allow_disk_remap = boolean Setting this to true allows Ignite-UX to substitute a disk that was specified in the configuration files but that does not exist on the system with a disk that does exist and that was not specified to be used, hidden or blocked.
instl_adm(4) instl_adm(4) Because Ignite-UX does not control kernel boot inventory, some inventory information for blocked devices may be collected. All blocked devices will be hidden and not available for selection during install. To take effect, this variable must be set in the *INSTALLFS file using instl_adm. inventory_block_protocols = { "protocol" [ , "protocol" ]... } This keyword is used to control Ignite-UX inventory functionality.
instl_adm(4) instl_adm(4) } ... } ... physical_volume disk[hw_path|index|dev_spec] { physical_volume-attributes... } ... logical_volume { file-system/swap-attributes... } logical_volume "lvname" { file-system/swap-attributes... } ... } The keywords and attributes used for disk configuration are described below: partitioned_disk Begins the specification of a disk that may be partitioned into one or two simple partitions. The disk may be used for file system, swap, or file system and swap.
instl_adm(4) instl_adm(4) consists of file system attributes. File system attributes are described in the following sections. swap_partition In a partitioned_disk configuration, this keyword starts the specification for the swap partition of the disk. The block following this keyword is surrounded by { } brackets and consists of subset of the file system attributes, namely the size, usage, and optionally the mount_point. These attributes are described in the following sections.
instl_adm(4) instl_adm(4) size = minsize | remaining size = minsize | remaining | maxsize Specifies the size of the volume/file system to be number. In the case the size is set to remaining, the volume is assigned the disk space that is left after allocating all other volumes. If maxsize is specified in conjunction with remaining, the remaining disk space, up to maxsize, is assigned to the volume.
instl_adm(4) instl_adm(4) 4096, and 8192; the default is 1024. fragsize = number Sets the file system fragment size to number. ncpg = number Sets the number of cylinders per group to number. nbpi = number Sets the number of bytes per inode (inode density) to number. rotational_delay = number Sets the rotational delay factor for the file system to number. (See tunefs(1M).) largefiles = boolean Specifies that largefiles are to be enabled or disabled for this volume.
instl_adm(4) instl_adm(4) minor_number = number Determines the logical volume number that is assigned to the associated logical volume which in turn determines the minor number value for the device file. number may range from 0 to 255. If the minor_number is not specified and the logical volume name is specified and is the form lvolX, then the value X is used to determine the minor number. Otherwise, the value is assigned in the order the volumes are created.
instl_adm(4) instl_adm(4) is_net_info_temporary keyword. If the final keyword is specified, the information is applied to the final system, and overrides any temporary information that was used during the installation. Note that instl_adm may be used to set some of these temporary values with command line options. The keywords recognized for this are: [final] system_name = cplx_string Sets the client’s hostname and uname value to cplx_string.
instl_adm(4) instl_adm(4) later bootpd. The -l option may be used to specify debug output from the dhcpclient command. Other options are documented in the dhcpclient(1M) man page on HP-UX releases B.11.23 and later. For example, to set the debug output level: dhcp_misc_opts = "-l 6" [final] route_gateway [index] = cplx_string [final] route_destination [index] = cplx_string [final] route_count [index] = number These keywords are use to configure the client’s network routing information.
instl_adm(4) instl_adm(4) server = cplx_string Used to specify the default IP address of the install server, when the installation source is the network. This is an Ignite-UX server from which the installation process reads the configuration files. sd_server = cplx_string Specifies the IP address of the system to use as the source for the Software Distributor (SD) swinstall, or swm utilities. See swinstall(1M), or swm(1M) (for HP-UX B.11.31 or later).
instl_adm(4) instl_adm(4) When used in combination with the run_ui=false keyword, the client may enter a mode to wait for server instructions immediately after booting, assuming that it may obtain all necessary network information. halt_when_done = boolean Setting this value to true halts the client installation when it is complete instead of rebooting from the disk that was just installed; the default is false.
instl_adm(4) instl_adm(4) all clients that have access to that server must have an identical secrets file. The sd_secrets keyword allows you to specify the contents of the secrets file that are used by the Ignite-UX server performing the installation. sysadm_message = cplx_string Sets the message displayed when the client first boots the cold install process. This message is only recognized when stored in the configuration that exists in the first 8KB of the *INSTALLFS file.
instl_adm(4) instl_adm(4) mod_kernel += "tunable name value" mod_kernel += "module name [state]" The first performs the same as it did previously with the addition of the keyword tunable. The second describes how kernel modules are added to the client. The optional state argument has one of four values: static, auto, loaded and best. No syntax checking is performed for this value. See kcmodule(1M) for more information.
instl_adm(4) instl_adm(4) env_vars = cplx_string env_vars += cplx_string Sets a string of variables of the form variable=value that is sourced into the environment for the duration of the installation process. The format of cplx_string should be one variable assignment per line. The value of the assignment does not need to be quoted (unless quotes need to be part of the value). These variable assignments are stored in the file /tmp/install.vars and is left on the client after the installation.
instl_adm(4) instl_adm(4) sw_source src-tag-string { source-attributes... } sw_category cat-tag-string { description = string } sw_sel sel-tag-string { sw_source = src-tag-string sw_category = cat-tag-string selection-attributes... } init sw_sel sel-tag-string=boolean sw_source src-tag-string { source-attributes } The software source specifies an SD depot or an access method to an archive. The src-tag-string is used by sw_sel to identify which sw_source is applicable.
instl_adm(4) instl_adm(4) source_path = cplx_string Sets this keyword to the default device file path to access the tape or CD for non-network sources. If not specified, it will default to the device from which it was booted. change_media = boolean Setting this keyword indicates whether Ignite-UX should prompt you to change media before loading this source for non-network sources. The description information is used in the prompt so you know which media to insert.
instl_adm(4) instl_adm(4) load_order must be set to 0 (zero) to ensure it is loaded first, to invoke special handling within Ignite-UX. pre_load_cmd = cplx_string post_load_cmd = cplx_string post_config_cmd = cplx_string final_cmd = cplx_string Use to specify a shell command string that should be executed at the prescribed points during the installation. See the Command and Script Execution Hooks section for details.
instl_adm(4) instl_adm(4) sw_source = src-tag-string Specifies the sw_source from which this software selection is to be installed. The src-tag-string must match the tag string used when defining the source. This is a required attribute of a sw_sel. sw_category [+]= cat-tag-string Specifies the software category with which this software selection is to be grouped. Using the "+=" operator allows for placing the sw_sel into multiple categories.
instl_adm(4) instl_adm(4) This information is critical to the way Ignite-UX performs volume size calculations that are based relative on the amount of disk space used by each software selection. The make_config command automatically generates sw_sel statements with this information. The archive_impact command may be used to generate the impacts attributes when manually creating sw_sel statements that represent a tar/cpio/pax archive.
instl_adm(4) instl_adm(4) load_with_any ˜ tag-regexp [[ | tag-regexp ]...] load_with_any ˜ category.tag-regexp ... Specifies that when the ˜ operator is used rather than =, the sw_sel tags listed are treated as fnmatch(3C) regular expressions that may be used to match any selection fitting the given pattern. Note this operator uses fnmatch(3C) pattern matching expressions. Other uses of the ˜ operator in the configuration file are with extended regular expressions.
instl_adm(4) instl_adm(4) • Within a sw_source definition. • Within a sw_sel definition. • At the global level. Although only the = assignment operator is shown with these keywords, the += operator can also be used to add a script or command fragment to any existing assignments made to the same keyword in the same context. The = operator overwrites any prior assignments made for that keyword. A separate context for each keyword is kept for the global level, each unique sw_source and each unique sw_sel.
instl_adm(4) instl_adm(4) execute commands in this environment that may have dependencies on the version or modifications of the kernel that was put into place prior to rebooting. The final commands and scripts associated with a sw_source or sw_sel are executed first and the global versions last. Note that if a temporary host name/IP address is used during the installation, all the commands and scripts, including the final_cmd/script, are executed while that temporary information is in effect.
instl_adm(4) instl_adm(4) Configuration files that are parsed later have precedence over any earlier files and may override values set in earlier files. Thus, the client-specific configuration file has highest precedence. Tape and CD media are in lif (4) format and contain an INDEX file. Typically the only file referenced by the INDEX file is entitled CONFIG. It is this CONFIG file, in addition to the first 8KB of the *INSTALLFS file, that make up the configuration information for these media types.
instl_adm(4) instl_adm(4) } init sw_sel "EE pack" = (disk[_hp_root_disk].size > 1800Mb) #### The contents above would be stored in a file such as /var/opt/ignite/data/Rel_B.11.11/ee_apps_cfg, and then added to the INDEX file using the command: /opt/ignite/bin/manage_index -a \ -f /var/opt/ignite/data/Rel_B.11.11/ee_apps_cfg Scheduling a post_config_script To Be Run The /var/opt/ignite/data/config.
instl_adm(4) instl_adm(4) /opt/ignite/data/examples Contains example configuration files. See the comments in the files for details. SEE ALSO lifinit(1), lifls(1), archive_impact(1M), bootpd(1M), instl_adm(1M), instl_bootd(1M), lvmmigrate(1M), make_config(1M), manage_index(1M). swcopy(1M), swinstall(1M), swm(1M) (HP-UX B.11.31 or later), lif(4), ignite(5).
ANSITAPE(5) ANSITAPE(5) NAME ansitape - ANSI standard magtape labels DESCRIPTION An ANSI-labelled tape starts with a volume header. This header specifies the volume name and protection, the owner of the volume, and the ANSI label standard level that the tape conforms to. Every file on the tape has a header, some data blocks, and a trailer. A tape mark follows each of these elements. At the end of the tape, two tape marks follow the trailer, to indicate logical end-of-tape.
ANSITAPE(5) ANSITAPE(5) FILE HEADERS Field HDR1 Width 4 Example HDR1 17 FILE.DAT Set 6 VAX1 Vol Num 4 0001 File Num 4 0001 Generation 4 0001 Gen Version 2 00 Created 6 b86001 Expires Access 6 1 b86365 space Blockcount 6 000000 13 OS360 Name System IGN 7 Use Identifies first file header. Leftmost 17 characters of filename. Name of volume set this file is part of. Number of this volume within volume set. Number of file on this tape. Like a major release number.
ANSITAPE(5) ANSITAPE(5) Field HDR2 Rec Format Blk Length Rec Length Density Vol Switch Width 4 1 5 5 1 1 Example HDR2 D 02048 00080 3 0 Job Recording Car Control Blocking IGN Offset 17 2 1 1 11 2 user/program space space B 00 Use Second file header. Record format. Tape block size. Record size. Recording density code. 1 if this is a continuation of a file from a previous reel. See following notes. Unused in 9-track tapes. See following notes. See following notes.
ANSITAPE(5) ANSITAPE(5) The HDR3 and HDR4 labels are not written on IBM tapes. ANSI allows, but does not require, these labels. Field HDR3 OS OS Width 4 76 Example HDR3 Use Third file header. Operating-system dependent. This field is reserved for the use of the operating system that created the file. Other operating systems are supposed to disregard HDR3 records. On VAX/VMS, this record contains the RMS file description.
ignite(5) ignite(5) NAME ignite − HP-UX configuration, installation, and recovery manager SYNOPSIS /opt/ignite/bin/ignite [-recovery] [-install] [-S] [XToolkit-Options] [client1, client2, client3, ... ] DESCRIPTION Introduction The Ignite-UX product supports HP-UX install and recovery. The Ignite-UX product supports a very rich set of functionality and customization beyond the scope of what can be presented here.
ignite(5) ignite(5) • Sufficient disk space to load Ignite-UX and any software depots and/or archives to be used during the install. • Access to the Ignite-UX tool set. The tool set may be loaded onto any of the above clients. • Tape/CD-ROM to load Ignite-UX and any software depots planned for distribution on the server. • Network access to any clients to be installed. Client and server must be on the same subnet if the initial boot of the client is planned to be over the network.
ignite(5) ignite(5) Enabling (or updating) an existing depot If you already have an SD depot available, or if you have made changes to a depot about which Ignite-UX knows, you may use the make_config and manage_index commands to generate a configuration file that Ignite-UX will use to access the depot. For example: make_config -s server:/depot_1123 \ -c /var/opt/ignite/data/Rel_B.11.23/core_cfg manage_index -a -f \ /var/opt/ignite/data/Rel_B.11.
ignite(5) ignite(5) make_config -s server:/depots/compiler \ -c /opt/ignite/data/Rel_B.11.23/compilers_cfg manage_index -a -f /opt/ignite/data/Rel_B.11.23/compilers_cfg The depot server (in this example ) should be replaced with the server on which you have the SD software. The make_bundles command must be run on the same client the depot exists. If the depot is not on the Ignite-UX server, you may need to copy the make_bundles command to the depot server and run it there.
ignite(5) ignite(5) Do not apply the class ID unless you are configuring the install server to be a DHCP server. DHCP Addresses are Temporary If these DHCP Addresses are used only for performing installs, and the clients will get reassigned new addresses when deployed, keep this field set. If you want to set up the Ignite-UX server as a departmental DHCP server, in which case the IP address leases are permanent and isolated to the department’s DHCP server, set this field to false.
ignite(5) ignite(5) Itanium-Based Clients: 1) Cycle the power (perform a cold reset) on the client to bring it to a known state. During the boot sequence, status messages are displayed on the client console. Depending on what type of machine, server or workstation model, the EFI Boot Manager menu appears and looks similar to: EFI Boot Manager ver 1.10 [14.60] Please select a boot option HP-UX Primary Boot: 0/2/2/0.0.0.
ignite(5) ignite(5) link-level address (LLA) followed by the MAC/LLA address of the LAN card. Device Path Acpi(HWP0002,0)/Pci(3|0)/Mac(00306E4A134B) Boot0001: Acpi(HWP0002,0)/Pci(3|0)/Mac(00306E4A134B) Edit Existing Boot Option or make a new entry [E-Edit N-New]: 5) Enter N to add the new boot option. 6) Enter a brief, descriptive boot option name at the message prompt. In this example, the new boot option is named LAN1. Enter New Description: 7) Enter a brief description for this boot option.
ignite(5) ignite(5) Starting: LAN1 @(#) HP-UX IA64 Network Bootstrap Program Revision 1.0 Downloading HPUX bootloader Starting HPUX bootloader Downloading file fpswa.efi (371200 bytes) (c) Copyright 1990-2001, Hewlett Packard Company. All rights reserved HP-UX Boot Loader for IA64 Revision 1.671 Booting from Lan Downloading file AUTO (528 bytes) Press Any Key to interrupt Autoboot AUTO ==> boot IINSTALL Seconds left till autoboot 0 AUTOBOOTING...
ignite(5) ignite(5) If you want to reuse this configuration, save the file. Once installation is proceeding, check the client’s status on the server. When the installation completes, you may print a manifest and either save the client’s data in a history directory or remove the client and its data from the server. Refer to the online "Tutorial and Demo" for more information.
ignite(5) ignite(5) • Replace or repair the failed hardware. • Go to the client console and perform a network boot from the server on which the archive resides, or perform a boot from the tape. • If the client cannot boot over the network or is on a different subnet than the Ignite-UX server, see make_boot_tape(1M). • After the client is booted, select your recovery archive from the list of configuration choices displayed for installation on your client.
ignite(5) ignite(5) someone, other than the installer, to remove locks. For COMPLETE clients, it is possible for someone other than the installer to either remove locks or move them to history. RETURN VALUES ignite returns the following values: 0 ignite completed successfully. 1 ignite failed. DIAGNOSTICS Logging All major events are logged to the server log file located at /var/opt/ignite/logs/server. FILES /opt/ignite/bin Contains Ignite-UX commands.
