Ignite-UX Installation Booting

ManualsBrandsHP ManualsSoftwareHP Ignite-UX

Table of Contents

Abstract .............................................................................................................................................. 2

Executive summary ............................................................................................................................... 2

Section I: Installation and recovery booting processes .............................................................................. 3

HP9000 systems: ............................................................................................................................. 3

Booting from a CD or DVD ............................................................................................................ 3

Booting from a CD or DVD with HP-UX 11i v2 and greater ............................................................... 4

Booting from a tape ...................................................................................................................... 4

Booting from a LAN ...................................................................................................................... 4

Booting a HP9000 virtual partition ................................................................................................. 7

HP Integrity systems: ......................................................................................................................... 9

Booting from a CD/DVD ............................................................................................................... 9

Booting a vPars system ................................................................................................................ 10

Booting from a tape .................................................................................................................... 10

Booting from a LAN .................................................................................................................... 15

Section II: Troubleshooting the secondary loader ................................................................................... 17

Debugging HP9000 booting problems: ............................................................................................ 17

Errors booting HP9000 systems without virtual partitions ................................................................. 17

Debug level logging ................................................................................................................... 18

Setting debug level logging on HP Integrity systems ............................................................................ 19

Additional debug level logging for both HP9000 and HP Integrity systems ........................................... 19

Troubleshooting early install kernel boot problems on HP Integrity systems ............................................ 21

The “pre_reboot_cmd” command hook ............................................................................................. 22

Network recovery/installation without network boot helpers: ............................................................... 23

Booting from tape (HP9000 only) ................................................................................................. 24

Booting from CD/DVD (HP9000 and/or HP Integrity systems) ......................................................... 25

The bootsys(1m) command .......................................................................................................... 25

Customizing the media ............................................................................................................... 25

Section III: Network boot helpers ......................................................................................................... 26

Glossary ........................................................................................................................................... 27

For more Information .......................................................................................................................... 28

Summary of content (29 pages)

PAGE 1
Ignite-UX Installation Booting Table of Contents Abstract .............................................................................................................................................. 2 Executive summary............................................................................................................................... 2 Section I: Installation and recovery booting processes .............................................................................. 3 HP9000 systems: .........
PAGE 2
Abstract Ignite-UX for HP-UX addresses the need for system administrators to perform operating system installations, deployment, and recovery, often on a large scale. It provides the means for creating and reusing standard operating system configurations. Additionally, Ignite-UX delivers the ability to archive operating system configurations, and to use these archives to replicate systems, with the added benefit of speeding up the process.
PAGE 3
Section I: Installation and recovery booting processes This section provides a high-level outline of the system booting process that occurs prior to installation or recovery of the HP-UX operating system using Ignite-UX. HP9000 systems: Booting from a CD or DVD System booting from a CD or DVD is as follows: 1. The command to boot from the CD or DVD is entered at the boot console. Please consult the documentation appropriate to the system for information on how to boot from CD/DVD. 2.
PAGE 4
The kernel loads the installation file system by executing calls to the secondary loader to load the file system. Since the kernel has not initialized the input/output (I/O) subsystem, it has no ability to access a disk device to read from the installation media. 8. The kernel starts init from the installation file system that was just loaded. 9. Lastly, init starts the installation or recovery process. Booting from a CD or DVD with HP-UX 11i v2 and greater The Ignite-UX C.6.0.
PAGE 5
4. The client retrieves the boot file from the Ignite-UX server using firmware implemented tftp, and then extracts the ISL. 5. The ISL on the client reads the AUTO file from the boot LIF. 6. The secondary loader reads from the boot LIF and is started with the information read from the AUTO file. At this point, both ISL and the secondary loader are set to read from the LAN device.
PAGE 6
Figure 1 illustrates the process of booting from the network by HP9000 systems: Figure 1 Client Server boot lan install – bootp query on boot lan – bootp query on port tftp response on 1068 from inetd response on 68 from tftp ISL tftp AUTO (hpux (;0)/boot/INSTALL) tftp HPUX 1067 – 67 – /opt/ignite/boot/INSTALL kernel runs – callback to PDC to get install filesystem tftp INSTALLFS into RAM filesystem Kernel completes initialization and then starts /sbin/init Note: The method that very old HP9
PAGE 7
Booting an HP9000 virtual partition This example is illustrated with an rp8400 system that has been split into three Virtual Partitions (vPars). The virtual partition, host1, has already been installed with the vPars software and the vPars monitor is running. The remaining two virtual partitions have been configured but not installed. The virtual partition host1 has Ignite-UX installed previously and has depots that contain the HP-UX B.11.11 OE, the vPars software, and enablement patches.
PAGE 8
The vPars boot process is as follows: host1 host2 1. The vparboot command locates the installation kernel and file system. 2. The vparboot command transfers the installation kernel and file system to the vPars monitor. 3. The monitor places them into the memory that is used by the host being started. 4. The kernel in the virtual partition is started. Once the vPar host2 has started and is running the kernel in the installation file system, it must be able to contact the IgniteUX server.
PAGE 9
HP Integrity systems: Booting from a CD/DVD System booting from a CD/DVD is as follows: 1. Enter the commands to boot from an appropriate DVD or use the boot manager menu (if configured). Please consult the documentation appropriate to the system for information on how to use the EFI or how to configure the boot manager menu. 2. The EFI reads the CD or DVD media to determine if it is an El Torito format CD or DVD (HP Integrity systems can only boot from El Torito format CD or DVD media). 3.
PAGE 10
Booting a vPars system When you boot HP Integrity servers running vPars you are using EFI to perform the boot. This is different from the way vPars works on HP9000 systems. Please consult the other areas in this white paper for information on how HP Integrity systems boot. Please consult the vPars release notes for the version you are running to see if there are any limitations on what boot methods are allowed.
PAGE 11
The following table shows the firmware requirements for various HP Integrity systems in order to support tape boot. All systems support two-step media recovery. Native Tape Boot by System Model Model 5 Native Tape Boot Minimum Firmware Revision rx1600, rx1620 Yes 04.05 or later rx2600, rx5670 No NA rx2660 Yes 01.03 or later rx2620, rx4640 Yes 04.05 or later rx3600, rx6600 Yes 6 Any – supports tape boot from first release rx7620, rx8620 Yes 5.
PAGE 12
The following table shows the HBAs that are supported for native tape boot along with the minimum EFI firmware driver revision. Native Tape Boot by SCSI Model Parallel SCSI Model Minimum Required EFI firmware Revision A6828A (Single port U160) 1.03.01.00 A6829A (Dual port U160) 1.03.01.00 A7173A (Dual port U320) 1.04.02.00 AB290A (U320 Gigabit 1.04.02.00 Ethernet combo) The following table illustrates the tape drive capabilities of HP systems according to protocol.
PAGE 13
Ignite-UX as of version C.6.8 creates tapes that conform to the UEFI 2.0 specification for bootable tapes; only tapes created by this version of Ignite-UX onwards are natively bootable. The following table shows the format of the tapes created by different versions of Ignite-UX and if they are bootable on HP Integrity servers: Native Tape Boot by Ignite-UX Version and Tape Format Ignite-UX Version Format Native Tape Boot Up to and including C.6.2 HP9000 format, LIF in first file followed by archive.
PAGE 14
Without going into detail about the new format for bootable tapes on HP Integrity servers, the tape contains the following files (this assumes the recovery tape does not span multiple tapes): Recovery Tape Contents File Number Contents File Number Contents 1 ANSI Label containing VOL1 13 header ANSI Label 2 EFIBOOTHPUX 14 IINSTALL 3 ANSI Label 15 ANSI Label 4 ANSI Label 16 ANSI Label 5 BOOTLOADER 17 IINSTALLFS 6 ANSI Label 18 ANSI Label 7 ANSI Label 19 ANSI Label 8 FPWSAEFI
PAGE 15
This program is responsible for loading everything else required from the tape to start the kernel (along with its install file system) and hence set the recovery going. The kernel completes its initialization. The installation continues with the kernel running init from the installation file system loaded by the bootloader. The Ignite-UX Administration Guide contains information on how to configure boot manager menu options for tape boot on HP Integrity servers that support it.
PAGE 16
kernel and the installation file system before passing control to the kernel. The bootloader tells the kernel where it loaded the installation file system. This is different from how booting works on HP9000 systems. 7. The kernel completes its initialization. The installation continues with the kernel running init from the installation file system loaded by the bootloader.
PAGE 17
Section II: Troubleshooting the secondary loader Debugging HP9000 booting problems: Errors booting HP9000 systems without virtual partitions It is likely that at some point errors will appear when booting a HP9000 system (without Virtual Partitions) that are similar to the following errors, though the actual errors vary across systems (the amount of information provided varies and you might or might not see a hex dump).
PAGE 18
Examples: • A value of –7 for the ENTRY_INIT error can mean different things for different devices. For a LAN device it could mean that nothing responded to its boot request. For a disk device, it could mean that the device does not exist (for example, the device path is incorrect).
PAGE 19
Setting debug level logging causes the system to print information about the instructions that the secondary loader is executing. Typically this information is useful only to HP Support. Enable these loader debug options only when requested to do so by HP Support.
PAGE 20
In addition to booting with the -i3 flag (how you do this depends on the type of system you are using), you can enable debug level logging during an installation or recovery before the Ignite-UX Graphical User Interface (GUI) 8 program starts. On the screen that provides the option to Install HP-UX, select Advanced Options. In the screen that appears, scroll down to debug level and press Enter to select level 3. The same amount of detail is provided for levels 3, 4 and 5.
PAGE 21
Troubleshooting early install kernel boot problems on HP Integrity systems When you encounter the rare occurrence of a kernel hang or delay during boot on HP Integrity systems, you can localize where the problem might be occurring. There is a boot loader option –v that directs the kernel to print out what is happening in the kernel during its initialization.
PAGE 22
When the function completes, the “In Progress ...” gets erased and replaced with: Init[ 11]:0xe0000000010599d0: io_memory_config - DONE (0x00001cbf9196 iticks) To enable this output, you should perform the following actions when booting the IINSTALL install kernel (these instructions assume that you are booting from a CD or DVD): 1. At the EFI shell, choose one of the following options: • If you have configured an option to boot from the CD or DVD drive, select that option.
PAGE 23
To enable this feature, the pre_reboot_cmd command hook must be specified in the install file system. The following is an example showing how to set it: 1. Save the default contents of the install file system to a temporary file # instl_adm -d > /var/tmp/myconfig 2.
PAGE 24
Booting from tape (HP9000 only) The make_boot_tape(1m) command can create a bootable tape containing just enough information to boot a HP9000 system. However, you must use a combination of an interface card and a tape drive that is bootable. Booting the tape will get the system to the point where it can contact an Ignite-UX server. Note the –f option to make_boot_tape which allows you to specify the configuration that will be placed into the LIF on the tape.
PAGE 25
Booting from CD/DVD (HP9000 and/or HP Integrity systems) This section no longer discusses how to create custom CD/DVD boot media for HP9000 or HP Integrity servers. Instead, please refer to the Ignite-UX Custom Configuration Files document in the section titled, “How do I create the CD equivalent of a tape created by make_boot_tape?” The bootsys(1m) command The bootsys command allows you reinstall or recover an existing HP-UX system on its next reboot.
PAGE 26
Section III: Network boot helpers The bootp protocol query UDP broadcast is not routable (cannot relay or forward). In view of this, Ignite-UX provides you the ability to configure a boot helper. A boot helper is the supported method for accessing an Ignite-UX server when it is located on a different subnet than the client.
PAGE 27
Glossary BCH Boot Console Handler is the firmware prompt that is available when the system first boots. At the BCH prompt, you can start a system boot and execute other BCH commands. DHCP Distributed Host Configuration Protocol allows systems to gain IP addresses and other configuration information dynamically. EFI Extensible Firmware Interface is the firmware interface for HP Integrity systems.
PAGE 28
For more Information The Ignite-UX Administration Guide, along with other documents and white papers, are available at http://www.docs.hp.com/en/IUX/infolib.html Product information regarding Ignite-UX is available at http://www.docs.hp.com/en/IUX/ The following relevant documents are available online at the HP Technical Documentation Web site at http://www.docs.hp.
PAGE 29
© Copyright 2004-2008 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.