Chapter 06 Ignite-UX HP-UX Handbook Revision 13.
Chapter 06 Ignite-UX October 29, 2013 TERMS OF USE AND LEGAL RESTRICTIONS FOR THE HP-UX RECOVERY HANDBOOK ATTENTION: PLEASE READ THESE TERMS CAREFULLY BEFORE USING THE HP-UX HANDBOOK. USING THESE MATERIALS INDICATES THAT YOU ACCEPT THESE TERMS. IF YOU DO NOT ACCEPT THESE TERMS, DO NOT USE THE HP-UX HANDBOOK. THE HP-UX HANDBOOK HAS BEEN COMPILED FROM THE NOTES OF HP ENGINEERS AND CONTAINS HP CONFIDENTIAL INFORMATION.
Chapter 06 Ignite-UX October 29, 2013 TABLE OF CONTENTS Overview ________________________________________________________________________ 5 Obtaining Ignite-UX ________________________________________________________________ 5 Application CD-ROM/DVD__________________________________________________________________6 HP-UX 11i Core OS CD/DVD 1 _______________________________________________________________ 6 WWW to HP’s Software Depot ______________________________________________________________ 6 Ignite-
Chapter 06 Ignite-UX October 29, 2013 Ignite-UX and SAS Devices __________________________________________________________ 37 Creating SD-UX and non-SD-UX Software Depots _______________________________________ 38 Creating an HP-UX Core-OS Depot __________________________________________________________ 38 Creating an Individual Patch Depot__________________________________________________________ 39 Special Handling of Patches _______________________________________________________________ 40 Creating a
Chapter 06 Ignite-UX October 29, 2013 Overview Ignite-UX is an installation tool for HP-UX systems. The Ignite-UX clients can be installed from software depots containing the Core OS, patches and applications, or from archived “images”. These depots do not necessarily need to be placed onto the Ignite-UX server; any NFS-capable system can be used as the depot server; can be used for cloning systems. A so-called Golden System Image will be created from pre-configured source systems.
Chapter 06 Ignite-UX October 29, 2013 Ignite-UX added support for HP-UX 11.31 with the C.7.0, February 2007, release. With IgniteUX version C.7.0, the product bundle that installs on all supported versions of HP-UX has changed from B5725AA to IGNITE. When IGNITE is installed, B5725AA is automatically removed. If scripts reference the old bundle name, they must be updated to reference the new bundle name. The HP-UX version-specific bundles, such as Ignite-UX-11-23, will not change names.
Chapter 06 Ignite-UX October 29, 2013 Ignite-UX Mailing Lists / Updates To receive a email when a new version of Ignite-UX is available, write an email to: majordomo@hpfcdn.fc.hp.com with following content: subscribe ignite-ux-notify End Ignite-UX FAQs Write an empty email to: iux_faq@igniteux.fc.hp.com Changes in the C.7.13 release The C.7.
Chapter 06 Ignite-UX October 29, 2013 The IMM size is the size of the initial memory module on HP 9000 (PA-RISC) systems. The first memory module must be large enough to hold the install kernel and install file system. If installing HP-UX 11i v3, the boot disk must be at least 9 GB. HP-UX 11i v3 requires more space on the HP-UX boot disk than prior HP-UX releases. Ignite-UX version C.7.
Chapter 06 Ignite-UX October 29, 2013 loading Ignite-UX, in which case loading Ignite-UX will automatically remove the NetInstall software. Otherwise loading any of the Ignite-UX software bundles will give an error. Installing Ignite-UX from Application DVD Look for the required device file for your DVD drive. If the mount point does not exist, create it with mkdir. Then mount the Applications DVD to /SD_CDROM.
Chapter 06 Ignite-UX October 29, 2013 # /usr/sbin/swinstall -s /SD_CDROM Ignite-UX-11-00 # /usr/sbin/swinstall -s /SD_CDROM Ignite-UX-11-11 Installing Ignite-UX from HP-UX 11i CoreOS DVD1 To install Ignite-UX, mark one of the Ignite-UX filesets or the complete bundle B5725AA for installation in the software tab after choosing the Advanced Installation screen. Ignite-UX servers must have at least 800 MB of free disk space available in /opt/ignite to install support for all HP-UX releases (B.11.11, B.11.
Chapter 06 Ignite-UX October 29, 2013 Configuring the Ignite-UX Server Starting Ignite-UX The search path /opt/ignite/bin has been added to /etc/PATH during the installation. To update your current PATH variable source /etc/PATH use: # . ./etc/PATH or simply login again. To startup Ignite-UX: # /opt/ignite/bin/ignite If the error message occurs stating the Ignite-UX server not being set up as an NFS server, start NFS with: # /usr/bin/vi /etc/rc.config.d/nfsconf NFS_SERVER=1 NFS_CLIENT=1 # /sbin/init.
Chapter 06 Ignite-UX October 29, 2013 from the Ignite-UX screen. The following describes the quick setup. Server options: Select the box and highlight the Operating System to use from the list. When doing a client installation, this configuration will be installed on targets if no other is specified. The default setting can be overridden on a per-client basis by Ignite-UX.
Chapter 06 Ignite-UX October 29, 2013 bootptab entry for an Ignite-UX client: sysname:\ hn:\ vm=rfc1048:\ ht=ether:\ ha=080009352575:\ ip=15.1.51.82:\ sm=255.255.248.0:\ bf=/opt/ignite/boot/boot_lif Session options: controls the appearance of a dialog screen each time a new client is booted from the Ignite-UX server.
Chapter 06 Ignite-UX October 29, 2013 The Ignite instl_bootd server has been modified so that it will respond to anonymous Itanium clients (not successful on all network environments). Use bootpd method, if: Ignite-UX server is running HP-UX 11.23 or greater Any release of Ignite-UX is installed bootpd is being used, e.g.
Chapter 06 Ignite-UX October 29, 2013 Restart the bootpd daemon. Using the instl_bootd method: instl_bootd daemon is used by Ignite-UX to boot PA-RISC clients configure instl_bootd using the Options:Server Configuration screen configuration file is /etc/opt/ignite/instl_bootptab instl_bootd daemon normally runs on ports 1067/1068 (unique) used only for booting PA-RISC clients Ignite 4.
Chapter 06 Ignite-UX ht=ether October 29, 2013 hardware type is Ethernet. For consistency if it was required that PA-RISC systems boot using bootp as well the boot file would be given as: bf=boot_lif:\ hd=/opt/ignite/boot:\ or bf=/opt/ignite/boot/boot_lif:\ This would allow a PA-RISC system to boot using bootp as well (note that this would preclude the use of the install option to boot lan from the boot console handler). A /etc/bootptab entry is required for each MAC address.
Chapter 06 Ignite-UX October 29, 2013 • To display settings in the direct boot profile: Shell> dbprofile or Shell> dbprofile -dn test • To create and modify settings in a direct boot profile: Shell>dbprofile -dn test -dhcp -sip 192.168.0.1 \ -m 255.255.255.0 Shell>dbprofile -dn test -b "tmp/nparsys1/loader.efi" \ -od "optional data " Where optional data is the actual data you want to pass to the boot file.
Chapter 06 Ignite-UX October 29, 2013 Check /etc/inetd.conf for “bootps” and “tftp” entries being uncommented. The "tftp" line must contain /opt/ignite and /var/opt/ignite paths. Was inetd restarted or given an option to re-read the configuration files (inetd -c), after they were edited? Is the inetd process running? Check for entries in /var/adm/inetd.sec that may cause inetd to deny service to certain clients. Check /var/adm/syslog/syslog.
Chapter 06 Ignite-UX October 29, 2013 Received n bytes in s seconds tftp> quit Caveats: Because the Itanium client sends a broadcast no other DHCP servers should be in the same subnet as the Ignite-UX server and the client. Other DHCP servers my answers faster than the Ignite-UX client, leading to failed installation attempts. Alternatively use a dbprofile.
Chapter 06 Ignite-UX October 29, 2013 ux.html?jumpid=reg_R1002_USEN, chapter "Required Patches" in the latest Release Notes at http://www.software.hp.com/products/IUX/docs.html. The most problematic when installing from network is permission and network protocol errors. Before installing the client, you should check tftp, inet, NFS, etc. The /var/adm/syslog/syslog.log can be very useful troubleshooting this issue. Check the /etc/dfs/dfstab or /etc/exportfs and /etc/inetd.conf for correct settings.
Chapter 06 Ignite-UX October 29, 2013 On the server to see if maybe there isn't any unassigned IP available for the client. To make a portable low revision DDS backup for recovery, it is suggested to use a DDS1 device file for creating a tape. Using the DDS1 device file makes the tape compatible with other DDS tape drives.
Chapter 06 Ignite-UX October 29, 2013 Note: The maximum physical extents of a boot disk is 5628. If desired, increase the PE size for larger hard disks. A golden system image can be written onto tape if desired: # /opt/ignite/data/scripts/make_sys_image -d /dev/rmt/0m -s local When using make_sys_image, important system files are temporarily replaced which leads to intensive disruptions on a productive system, among other things, the name resolution, login, etc.
Chapter 06 Ignite-UX October 29, 2013 Ignite-UX System Recovery Tools - make_recovery The make_recovery command has been obsolete for some time, but was shipped with IgniteUX along with its replacements command make_tape_recovery. Executing make_recovery prompted a note saying: NOTE: make_recovery(103): The make_recovery command will be replaced by make_tape_recovery. Both commands are supported in this release (Ignite-UX Revision 3.2).
Chapter 06 Ignite-UX October 29, 2013 for example # xhost +host1 Export the display if necessary: # export DISPLAY=:0 for example # export DISPLAY=host1:0 On the Ignite-UX server start Ignite-UX as root: # /opt/ignite/bin/ignite In case of a new client, add the new client first: Choose Start the Tape Recovery Archive Creation: Click on the client icon and select
Chapter 06 Ignite-UX October 29, 2013 Note: make_tape_recovery will check if there are configuration files from previously saved archives. If no configuration files exist that have different settings, only a core OS (essential files) will be archived. /opt/ignite/recovery/mnr_essentials lists the files and directories that are considered essential.
Chapter 06 Ignite-UX October 29, 2013 device file of the format /dev/dsk/ when specifying a whole-disk (non-LVM) file system. Further -x arguments: -x include=file|dir: Includes the file or directory in the recovery archive but does not cross any mount points. -x inc_cross=file|dir: 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.
Chapter 06 Ignite-UX October 29, 2013 -p: If the tape was created without stating an Ignite-UX server , the files will be located at /var/opt/ignite/recovery/latest. If an IUX server was stated, the files are at /var/opt/ignite/clients//recovery/. Only following files will be created which can be edited before presuming the tape creation: archive_cfg, control_cfg, system_cfg.
Chapter 06 Ignite-UX October 29, 2013 # /usr/bin/mt -t /dev/rmt/0mn rew # /usr/bin/mt -t /dev/rmt/0mn fsf 1 # /usr/bin/tar tvf /dev/rmt/0m Note: 0m not 0mn Extracting single files from the tar archive (Integrity) # /usr/bin/mt -t /dev/rmt/0mn rew # /usr/bin/mt -t /dev/rmt/0mn fsf 22 # /usr/bin/tar xvf /dev/rmt/0m filename1 tmp/filename2 Note there is no leading ‘/‘ when specifying a directory path.
Chapter 06 Ignite-UX October 29, 2013 7. Make any desired changes to the file systems, hostname, IP address, timezone, root password, DNS server, and gateway information. 8. Select [ GO ] to proceed with the installation. Restoring from a make_tape_recovery Tape on Integrity systems With the latest firmware, for most systems simply boot from the tape device from the EFI Shell.
Chapter 06 Ignite-UX October 29, 2013 * IF NEEDED: Dual Boot process: Insert the Core-OS DVD-ROM into the DVD-ROM drive. 1. Boot the system. 2. Interrupt the boot sequence to redirect it to the DVD-ROM drive. 3. Cancel the non-interactive installation by hitting the key when the following messages are displayed: 4. WARNING: The configuration information calls for a non- interactive installation.
Chapter 06 Ignite-UX October 29, 2013 Without Online-JFS, a new file system must be created to change the file system to support largefiles. Check if the file system supports large files with: # /usr/sbin/fstyp -v /dev/vgxx/lvolx|grep f_flag f_flag: 16 large files are activated f_flag: 0 large files are inactive With Online-JFS # /usr/sbin/fsadm -F vxfs /file_system_path If the output shows largefiles, then large files are activated. If it shows nolargefiles large files are inactive.
Chapter 06 Ignite-UX October 29, 2013 In case of conflicting entries in the selections, Exclusions take precedence over inclusions. Exporting the archive directory The default archive location on the Ignite-UX server is /var/opt/ignite/recovery/archives/. The hostname is the name of the system being archived.
Chapter 06 Ignite-UX October 29, 2013 for example # export DISPLAY=host1:0 On the Ignite-UX server start Ignite-UX as root: # /opt/ignite/bin/ignite In case of a new client, add the new client first: Choose Start the Tape Recovery Archive Creation: Click on the client icon and select . You will now be guided through some screens for additional configuration.
Chapter 06 Ignite-UX October 29, 2013 for example # /opt/ignite/bin/make_net_recovery -Av -a host2:/my_archives -s host1 -a: Specifies the NFS server and location to store the archive. The archive directory must be NFS exported and sufficient disk space is required.
Chapter 06 recovery.log flist Ignite-UX October 29, 2013 progress and error log file tar archive content Reviewing the zipped tar archive # /usr/contrib/bin/gzcat \ /var/opt/ignite/recovery/archives// \ | tar -tvf - > /tmp/archive_content or # /usr/contrib/bin/gzcat \ /var/opt/ignite/recovery/archives// \ | tar -tvf - | more Restoring from the Network Recovery Archive Please see chapter "Booting and installing an HP-UX client”.
Chapter 06 Ignite-UX October 29, 2013 control_from_server=FALSE run_ui=FALSE env_vars += "INST_ALLOW_WARNINGS=10" Then, issue the following command: # /opt/ignite/bin/instl_adm -F /var/tmp/my_lif -f /var/tmp/cfg Writing the LIF Header and the network recovery archive onto tape Create a DDS1 device file if you do not have one already.
Chapter 06 Ignite-UX October 29, 2013 Mapping between device special files and devices cannot be restored during recovery – known issue C.7.0. During recovery on a system that has more than seven disk and tape devices, Ignite-UX may not successfully remap the device special file names so that they refer to the original devices. Because of this problem, the make_net_recovery and make_tape_recovery commands on HP-UX 11i v3 print a WARNING message and prompt the user to confirm that they wish to continue.
Chapter 06 Ignite-UX October 29, 2013 Ignite-UX fully supports a configuration where only RAID LUNs are presented to a system. (This includes having a hot spare configured.) Note that the HP PCI/PCI-X SAS MPT Adapter supports a maximum of two RAID LUNs and a hot spare. These restrictions do not apply to the P400 Core I/O card. The P400 Core I/O card presents only RAID LUNs to the system; it is not possible to present individual SAS drives to a system.
Chapter 06 Ignite-UX October 29, 2013 # /opt/ignite/bin/ make_depots -s /dev/dsk/c1t2d0 \ -d /var/opt/ignite/depots/Rel_B.11.31/core Example 3: A disk depot for an HP-UX 11iv3 DCOE installation will be created. Please insert the first of the two HP-UX 11iV3 Core-OS DVD-ROMs in the DVD-ROM drive. The depot will be named dcoe_core and will be created at: /var/opt/ignite/depots/Rel_B.11.31. # /opt/ignite/bin/make_depots -s /dev/dsk/c2t3d0 \ -d /var/opt/ignite/depots/Rel_B.11.
Chapter 06 Ignite-UX October 29, 2013 Running swlist again to verify the creation of the bundle. # /usr/sbin/swlist -d @ /var/opt/ignite/depots/Rel_B.11.23/my_patches To display the patches of this bundle, use # /usr/sbin/swlist -l product \ -d @ /var/opt/ignite/depots/Rel_B.11.23/my_patches Changing individual patch depots. If you need to add additional patches to the depot in the future, simply unshar the patches as described above, swcopy them into the patch depot, and rerun make_bundles.
Chapter 06 Ignite-UX October 29, 2013 Creating non-SD-UX Depots If the source is a non-SD-UX depot, the make_depots command is not applicable. Do not attempt to use non-core-OS archives (such as layered applications) that contain files that are loaded in /var/adm/sw/* . Delivering files in this directory in this method may corrupt the software distributor database. Please proceed with the next step "Creating Ignite-UX Config Files for SD-UX and non-SD-UX Depots".
Chapter 06 Ignite-UX October 29, 2013 # /opt/ignite/bin/instl_adm -T –f \ /var/opt/ignite/data/Rel_B.11.23/non_SD_config.cfg Managing the INDEX File The order of the INDEX file determines in which order the depots will be loaded. There must always be a HP-UX release specific config file such as /opt/ignite/data/Rel_B.11.23/config as the first line. If you are using the /var/opt/ignite/config.local file, it should always be the last entry for the cfg clause.
Chapter 06 disk 1 Ignite-UX 8/16/5.5.0 /dev/dsk/c1t1d0 sdisk CLAIMED /dev/dsk/c1t5d0 October 29, 2013 /dev/rdsk/c1t1d0 DEVICE QUANTUM FIREBALL1050S /dev/rdsk/c1t5d0 2) Insert the HP-UX 11.23 Core-OS DVD, but do not mount it. Then create the Core OS depot. # /opt/ignite/bin/make_depots -s /dev/dsk/c1t1d0 -r B.11.23 # /opt/ignite/bin/make_depots -s -d /var/opt/ignite/depots/Rel_B.11.23/core /dev/dsk/c1t1d0 \ Note for HP-UX 11i: For the second DVD, repeat make_depots with the same syntax.
Chapter 06 Ignite-UX October 29, 2013 "/var/opt/ignite/data/Rel_B.11.23/core.cfg" "/var/opt/ignite/data/Rel_B.11.23/QPK1123.cfg" "/var/opt/ignite/config.local" } 7) Verify the INDEX file for errors with: # /opt/ignite/bin/instl_adm –T 8) Please see Handbook chapter "Booting and installing an HP-UX client" to install the client. Example 2 - Creating a DVD-ROM SD-UX Depot Note: You can only create a DVD-ROM depot for installations containing one Core-OS DVD.
Chapter 06 Ignite-UX October 29, 2013 "/var/opt/ignite/config.local" } 6) Check the INDEX file with: # /opt/ignite/bin/instl_adm –T 7) Please see chapter "Booting and installing an HP-UX client" to install the client. Booting and Installing an HP-UX Client over the network If the client system is running HP-UX 11.X or later, the bootsys(1M) command can be used or a local network boot to install the client. It can be invoked either from a command shell, or from the Ignite-UX screen.
Chapter 06 Ignite-UX October 29, 2013 Configuring the client installation: Select one of the previously created cfg selections from the /var/opt/ignite/INDEX file or a make_net_recovery archive. For this, click on from the Basic Tab. Adjust any other parameters such as selecting the boot disk, etc. For adding/removing Software to be installed, please go to the tab. At the tab, adjust system settings such as the hostname, IP adress, etc.
Chapter 06 Ignite-UX October 29, 2013 Booting Integrity and PA-RISC Clients from the Network Note: For booting older workstations please see the Ignite-UX Admin Guide at www.hp.com/go/ignite-ux-docs 1) Switch the client on and interrupt the boot sequence pressing any key.
Chapter 06 Ignite-UX October 29, 2013 BOOT ADMIN> boot lan.15.10.18.156 install where 15.10.18.156 is the IP of the Ignite-UX boot helper. The client will be booted from the boot helper and then redirected to the Ignite-UX server to complete the installation. c) PA-RISC: Otherwise make the system search for servers and pick one or explicitly tell the system where to boot, as follows BOOT ADMIN> search lan install The list of servers will be displayed with IP addresses.
Chapter 06 Ignite-UX October 29, 2013 The system will be booted from the Ignite-UX kernel on the tape and then the Ignite-Ux server will be contacted to proceed with the installation. Typically the tape is created on the Ignite-UX server, because it contains Ignite-UX server specific information from the INSTALLFS file (edited with instl_adm). The tape can also be used if you have several lan cards and you want to use another than the built-in lan card for installation.
Chapter 06 Ignite-UX October 29, 2013 2) Edit the defaults file adding following lines: run_ui=false control_from_server=false env_vars+="INST_ALLOW_WARNINGS=1" With this step the interactive user interface has been switched off and the client will be installed automatically when booting from the network. 3) It is recommended to make further settings, because during the installation, no parameters can be adjusted like system name and IP address.
Chapter 06 Ignite-UX October 29, 2013 Note: Because files like /etc/hosts and devices files are temporarily removed from the clients system during the execution of make_sys_image, the system should not be in use !!! 1) Install the required operating system, patches and applications at the source system and configure it to your needs. 2) Create the archive directory on the Ignite-UX server: # /usr/bin/mkdir –p /var/opt/ignite/archives/Rel_B.xx.
Chapter 06 Ignite-UX October 29, 2013 5) Copy the config files and edited them correspondingly. If the –s local option was used first copy the archive to the Ignite-UX server, if Ignite-UX is not installed on the local system. HP-UX 11.x copy /opt/ignite/data/examples/core11.cfg /var/opt/ignite/data/Rel_B.11.##/core_archive.cfg For to Edit the copied config files changing following in the section sw_source: nfs_source = ":/var/opt/ignite/archives/Rel_B.11.
Chapter 06 Ignite-UX October 29, 2013 # /usr/bin/vi /etc/exports /var/opt/ignite/clients -anon=2 /var/opt/ignite/archives/Rel_B.11.23 –ro,anon=2 # /usr/sbin/exportfs –av For HP-UX 11.31: # vi /etc/dfs/dfstab share -F nfs -o anon=2 /var/opt/ignite/clients share -F nfs -o anon=2 /var/opt/ignite/archives/Rel_B.11.23 # shareall -F nfs 11) Please see chapter "Booting and installing an HP-UX client" to install the client. HP-UX Handbook – Rev 13.
Chapter 06 Ignite-UX October 29, 2013 Creating a Bootable Golden System Image Tape Note: Because files like /etc/hosts and devices files are temporarily removed from the clients system during the execution of make_sys_image, the system should not be in use! Please repeat step 1) to 4) of chapter "Creating a Golden System image". 5) Copy the config files and edited them correspondingly: For HP-UX 11.x copy /opt/ignite/data/examples/core11.cfg to /var/opt/ignite/data/Rel_B.11.##/golden_image_cd.
Chapter 06 Ignite-UX October 29, 2013 # /usr/sbin/newfs -F hfs -f 2048 /dev/vg00/rgoldenimage respectively for an Image > 2GB # /usr/sbin/newfs -F hfs -f 2048 -o largefiles /dev/vg00/rgoldenimage # /usr/bin/mkdir /bootcd # /usr/sbin/mount /dev/vg00/goldenimage /bootcd # /usr/bin/cp /tmp/.gz /bootcd # /usr/sbin/umount /bootcd 9) Then create the boot (LIF) header for the tape. For example, create a LIF image based on /var/opt/ignite/data/Rel_B.11.23/core_archive.cfg .
Chapter 06 Ignite-UX October 29, 2013 Detailed usage information is available via # make_opticaldisc_recovery -? Additional information is located at the start of the script. Customized Creation of Bootable CD/DVD Media The make_media_install script greatly simplifies the creation of custom bootable CD/DVD media. With one simple command line a CD/DVD can be created. Additionally, make_media_install can write golden archives to a bootable DVD.
Chapter 06 Ignite-UX October 29, 2013 Two-step media recovery requires the version of Ignite-UX on the tape, on the bootable CD/DVD, and on the system creating the CD/DVD media to be identical. If you do not have a matching Operating Environment DVD, the make_media_install script can be used to easily create a bootable CD/DVD with the correct Ignite-UX version.
Chapter 06 Ignite-UX October 29, 2013 On a system with a DVD writer, execute the following commands. (The iso_directory is the target directory for the .iso media file. The –r option specifies the release, such as B.11.11, B.11.23, or B.11.31. The –o option specifies the hardware architecture – valid choices on a PARISC system are: 32, 64v, or 64w.) # mkdir /var/opt/ignite/media/pseudo_root/archive # cp goldenarchive.gz /var/opt/ignite/media/pseudo_root/archive # make_media_install –r B.11.
