Installing HP-UX 11.0 and Updating HP-UX 10.x to 11.
Notices Information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind about this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or direct, indirect, special, incidental or consequential damages about the furnishing, performance, or use of this material.
Printing History The Version date and printing date show the current edition of this manual. Minor updates may be made between major releases. The current Version is indicated by the date on the title page. November 1997, Edition 1.
Contents 1. Updating and Installing: Task Information Chapter Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Updating and Installing: Why Do It? . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Task-Information Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 2. Updating an Existing Operating System and Software Chapter Contents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Installing from a Media Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Preparing for a Media Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Booting the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Booting HP 9000 Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Booting HP 9000 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Booting the V-Class . . . .
Contents Configuring the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Using the Ignite-UX Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 The Basic Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113 OS Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Replacing the Kernel Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 7. Troubleshooting Chapter Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Likely Problem Areas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Using Config Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 During Installation and Configuration of Ignite-UX Tools and Data .
Contents Appendix Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .230 Section 1: Installation of Ignite-UX Server Software . . . . . . . . . . . . . .231 Ignite-UX Server System Requirements: . . . . . . . . . . . . . . . . . . . . . .231 Load the Ignite-UX software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .232 Edit Default Search Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Step 1: IUX setup of HP-UX OS from media . . . . . . . . . . . . . . . . . . . Step 2: Loading critical patches onto the OS. . . . . . . . . . . . . . . . . . . Step 3: Load Optional Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 4: Customize the system. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5: The Golden System is Done . . . . . . . . . . . . . . . . . . . . . . . . . . 262 263 264 264 264 Section 8: Loading HP-UX Patches Using Ignite-UX. . .
Updating and Installing: Task Information 1 Updating and Installing: Task Information Chapter 1 11
Updating and Installing: Task Information Chapter Contents Chapter Contents • Updating and Installing: Why Do It? • Task-Information Roadmap.
Updating and Installing: Task Information Updating and Installing: Why Do It? Updating and Installing: Why Do It? One of the first questions needing to be answered when system hardware has to be changed is: should the system undergo an update of just the software concerned, or is it more effective and less error-prone to just re-install the entire disk. Where the change involves a new file system layout, as in the transition between HP-UX 9.x and 10.
Updating and Installing: Task Information Updating and Installing: Why Do It? Moreover, for a system being re-installed with Ignite-UX, the install process can be initiated from the server with no local intervention at the client system. The System Administrator can also set up configuration files ahead of time for existing systems. Ignite-UX will use these during install instead of the default configuration. This can ensure that specific existing systems get unique configurations.
Updating and Installing: Task Information Task-Information Roadmap. Task-Information Roadmap. This manual documents procedures for installing and updating your HP-UX operating system and software. For doing "cold installs" which completely overwrite the data on the specified disk(s), the Ignite-UX tool replaces the old Cold Install toolset. It can be used for installing previous 10.x versions, as well.
Updating and Installing: Task Information Task-Information Roadmap. Task Location of Information (Cold) Installing HP-UX from media Chapter 3, “Installing From Media.” (Cold) Installing HP-UX from the network Chapter 5, “Installing from the Ignite-UX Server.” Installing Extension Software or bundled applications from media (as part of an install session). Chapter 3, “Installing From Media.” Installing Extension Software or bundled applications from the network (as part of an update session).
Updating an Existing Operating System and Software 2 Updating an Existing Operating System and Software Chapter 2 17
Updating an Existing Operating System and Software Chapter Contents Chapter Contents • Overview. • HP-UX System Requirements. • Updating SD-UX Before Installing/Updating Software. • Updating HP-UX Software. • Updating to HP-UX 11.0. • Using HP-UX Extension Software. • Adding Additional Functionality.
Updating an Existing Operating System and Software Updating a System Updating a System Figure 2-1 Chapter 2 19
Updating an Existing Operating System and Software Updating a System Overview. NOTE As of the HP-UX 11.0 release, Multi-Stream support has been added which enables SD-UX to store products and filesets of more than one bit-type in a single SD-UX depot, manage these software collections, and install them to systems. For information on special procedures for 32-bit and 64-bit updates and supported hardware, see “Updating to HP-UX 11.0” in this chapter. Updating your system from the existing HP-UX 10.
Updating an Existing Operating System and Software HP-UX Update Requirements HP-UX Update Requirements Update and Upgrade Paths You can use the SD-UX tools to update your OS to a later version of HP-UX, from 10.01, 10.10, 10.20, or 10.30. For upgrades to 10.x from 9.0x, see the manual Upgrading from HP-UX 9.x to 10.01. You can also use SD-UX to install or update applications. Required Kernels • The 32-bit kernel can execute on any Server or Workstation supported on 11.0, except the V2200 Server.
Updating an Existing Operating System and Software HP-UX Update Requirements NFS Diskless Updating a cluster server to HP-UX 10.30 or later is not supported. NFS Diskless functionality is not supported in HP-UX 10.30 or later. Do not update your server to HP-UX 11.0 if you intend for that server to operate as an NFS Diskless server. For the latest information on system support, consult your HP sales engineer. Fiber Link and HPIB HP-UX 11.0 does not support HPIB, or Fiber Link disks or controller cards.
Updating an Existing Operating System and Software HP-UX Update Requirements NOTE In general, the Disk Space Analysis phase of swinstall will warn you if disk space is insufficient. However, Disk Space Analysis does not currently check /var/adm/sw, where the database is kept, for temporary space usage. If you are running your system as LVM and /var comprises a single volume, be sure you have configured adequate space in the /var volume to accommodate the update files.
Updating an Existing Operating System and Software HP-UX Update Requirements For More Information on Space Requirements Refer to the current System Administration Tasks manual and the Release Notes for HP-UX 10.x for additional information on peripherals and disk space. Source Media The general names applied to the HP-UX source media are as follows: CD-ROMs Used • CORE • Applications. • Support. • HP-UX Extension Software (Includes essential patches).
Updating an Existing Operating System and Software HP-UX Update Requirements mkdir /SD_CDROM Enter mount /dev/dsk/c1t2d0 /SD_CDROM Enter The device name "c1t2d0" should be replaced with whatever device name you found using ioscan in item 7 above.
Updating an Existing Operating System and Software Updating SD-UX Before Installing/Updating Software Updating SD-UX Before Installing/Updating Software CAUTION Before you can update to, for example, 11.0, you must extract the new version of SD-UX from the 11.0 CD or software depot from which you plan to update your system. Do not attempt to use your present version of swinstall to update the system to a newer version. The update will fail.
Updating an Existing Operating System and Software Updating SD-UX Before Installing/Updating Software For additional examples and discussion regarding loading swgettools refer to “SW-DIST Installation”, in this chapter. Action: Getting the New SD-UX Tools Now, use swgettools to update SD-UX. For example: /var/tmp/swgettools -s /SD_CDROM If you get a message indicating that the software is not compatible, you may disregard this message. This is because the tool is, in effect, “updating itself”.
Updating an Existing Operating System and Software Updating SD-UX Before Installing/Updating Software 1. Copy the swgettools script file and the swagent.Z file (both in the catalog/SW-GETTOOLS/pfiles directory) from the CD to a location that your users have FTP access to. 2. Tell the user to do the following: a. FTP the two files into the /var/tmp directory on the system to be updated. b. Use chmod +x to make the /var/tmp/swgettools script executable. c.
Updating an Existing Operating System and Software Updating SD-UX Before Installing/Updating Software Example: cp /tmp/depot/catalog/SW-GETTOOLS/pfiles/sw* /usr/tmp /usr/tmp/swgettools -s swperf:/SD_CDROM -t /usr/tmp For More Information Consult the swgettools(1M) and, swinstall(1M) man pages, on the new system, the readme document: /usr/sbin/swlist -a readme -l product SW-DIST Or see the manual Managing HP-UX Software with SD-UX for assistance with the following: • If you encounter an error during the
Updating an Existing Operating System and Software Updating HP-UX Software Updating HP-UX Software See the section, “Updating to HP-UX 11.0” in this chapter, for specific information about transitioning to HP-UX 11.0. You should have installed the new SW-DIST product first, as given in the previous sections in this chapter. On HP 9000 Workstations, you will see a Graphical User Interface (GUI), by default, for interactive invocation of swinstall.
Updating an Existing Operating System and Software Updating HP-UX Software The value can include the following: B.11.00 In addition to the size/version options, updating between 11.0 word-widths requires the following options to swinstall: -x reinstall=true -x reinstall_files=true Interactive Command-Line Example For example, for an interactive update from 10.x to B.11.00 (32-bit), you would enter the following: Non-interactive Command Line (match_target) Non-interactive updates to 11.
Updating an Existing Operating System and Software Updating HP-UX Software Note the following precautions If you are patching a 10.x system having previous patches, in order to remove all prior patch information from the IPD prior to updating to HP-UX 11.0, see the procedure toward the end of this manual: “Section 8: Loading HP-UX Patches Using Ignite-UX”, in Appendix C, “Ignite-UX System Administration.
Updating an Existing Operating System and Software Updating HP-UX Software HP-UX Version Supported Minimum PDC Revision Minimum Firmware Revision 9000/800/K380 32 and 64-bit 8 37.23 9000/804/K450 32 and 64-bit 36 37.40 9000/889/K460 32 and 64-bit 36 37.40 9000/889/K460-EG 32 and 64-bit 36 37.40 9000/889/K460-XP 32 and 64-bit 36 37.40 9000/899/K570 32 and 64-bit 8 37.23 9000/800/K580 32 and 64-bit 8 37.
Updating an Existing Operating System and Software Updating HP-UX Software You will see a string similar to the following: 9000/804/K450 Compare the model string to the listing in the table of supported 64-bit systems. CAUTION If the model number does not appear in the table of supported 64-bit systems, do not attempt to install or update to HP-UX 11.0 64-bit, because you risk rendering your system unusable. Instead, install or update to HP-UX 11.0 32-bit operation.
Updating an Existing Operating System and Software Updating HP-UX Software For details on SD-UX procedures, refer to Managing HP-UX Software with SD-UX. Execute the Support Tools Manager, to determine the firmware (PDC) revision loaded in your CPU. NOTE On a multiprocessor system, you need to determine the firmware revision for only one CPU. The firmware installed applies to all processors.
Updating an Existing Operating System and Software Updating HP-UX Software • If your HP 9000 Server does not have installed the necessary revision of firmware, you must contact your HP Support Representative to get your firmware updated before attempting to install or update to HP-UX 11.0 64-bit version. CAUTION If you try to update a system lacking the correct level of firmware, you risk putting the system into an unusable state. Step 3.
Updating an Existing Operating System and Software Updating HP-UX Software You will see a message similar to the following: FIRMWARE INFORMATION Firmware Version: 37.31 4. To display the chip revision, enter: Main menu: Enter command or menu > in cr You will see a message listing modules and revisions for the system. Look for the module named PDC. For example, PDC IMPORTANT 34 Check the firmware and PDC revision numbers against Table 2-1, “Supported Hardware and Firmware for 11.0 64-bit Operation.
Updating an Existing Operating System and Software Updating HP-UX Software You’ll see a display showing that the T-class has two PDC banks. For example, Active Firmware Versions: SP Bank 0: SP 2.02, PSCM 1.60, Compiled 06/24/97 19:08 UT PDC Bank 1: J537 PSCM Boot ROM: 2.2 Alternate Firmware Versions: SP Bank 1: SP 2.00, PSCM 1.60, Compiled 03/21/97 21:45 UT PDC Bank 0: J533 The critical piece of information is the PDC Bank of the active Firmware Version. (In this example, the information is J537.
Updating an Existing Operating System and Software Updating HP-UX Software Updating to HP-UX 11.0 32-bit Version If you are updating your system to HP-UX 11.0 32-bit version, no hardware or firmware updates are required, but note the caution below. When you update a system to 11.0 32-bit version, you have the following choices: • If you are updating a system running HP-UX 10.01, 10.10, or 10.20, you can update directly to HP-UX 11.0 32-bit version. • If you are upgrading a system running HP-UX 9.
Updating an Existing Operating System and Software Updating HP-UX Software Updating to HP-UX 11.0 64-bit Version When you update a system to 11.0 64-bit version, you have the following choices: • If you are updating a system running HP-UX 10.20, and it is 64-bit capable (PA8000 and 64-bit compatible firmware), you can update directly to the HP-UX 11.0 64-bit version. • If you are updating a system running HP-UX 10.01 or 10.10, you must first update to HP-UX 10.
Updating an Existing Operating System and Software Updating HP-UX Software Figure 2-3 Update Paths to HP-UX 11.0 64-bit Version HP-UX 9.04 HP-UX 10.01 HP-UX 10.10 HP-UX 10.20 32-bit version HP-UX 11.00 64-bit version HP-UX 11.00 Transitions within HP-UX 11.0, between 32-bit and 64-bit, are also possible. Example of Update Path to 11.0 64-bit (K220 System):. For example, suppose you are running HP-UX 10.
Updating an Existing Operating System and Software Updating HP-UX Software Example of Update Path 11.0 64-bit (K460 System). For example, suppose you are running HP-UX 10.20 on a K460 system (PA8000, which does support 64-bits), and you want to update to HP-UX 11.0 64-bit. You would perform the following steps: 1. Upgrade firmware on K460 (if not already compatible). 2. Update HP-UX 10.20 directly to HP-UX 11.0 64-bit version. Transitioning Between Versions Once HP-UX 11.
Updating an Existing Operating System and Software Updating HP-UX Software Updating Interactively from the GUI After invoking swinstall from the command line for an interactive update (for example: swinstall -x os_name=HP-UX:32 -x os_release=B.11.0), you will see the following screen: Specify Source Screen Figure 2-4 1. Clicking on the field beside Source Depot Type displays a choice of Local CDROM, Local Directory, Local Tape, or Network Directory/CDROM.
Updating an Existing Operating System and Software Updating HP-UX Software For More Information For information on the options for swinstall, and to change the degree of detail for its logging functions, see the manual Managing HP-UX Software with SD-UX and the man page for swinstall(1M). Software Selection Screen Figure 2-5 1. On the Software Selection screen, highlight an item and click on the Actions menu item Open Item to see a listing of the contents of that bundle or product.
Updating an Existing Operating System and Software Updating HP-UX Software If you want to match the general filesets and functionality you already have on your old system, choose Match What Target Has... from the action menu. A log file is available from the Analysis screen. AND/OR 2. To choose specific bundles/products to add to the Match What Target Has... selection, highlight the additional item, and then choose Mark for Install from the Actions menu.
Updating an Existing Operating System and Software Updating HP-UX Software • By clicking on the Logfile button, you can open the logfile to monitor the progress of the analysis. You will also see a listing of files already on the target system which will be reinstalled in new versions. The Disk space... button will become accessible after the analysis process is complete and you can view the results. • Click on OK to proceed. Time Note The analysis phase requires 5 to 10 minutes.
Updating an Existing Operating System and Software Updating HP-UX Software NOTE If you are updating from an HP-VUE bundle to a CDE bundle, the /usr file system will undergo significant expansion. This expansion may exceed the default file system size set by Cold Install for /usr. See Chapter 7, “Troubleshooting,” for information on resetting file system size. 2. Ensure that the /var "Available After" space is at least 20 MB. (The screen shown indicates only about 3.
Updating an Existing Operating System and Software Updating HP-UX Software • As the system reboots for the first time, the new filesets are being configured. You can, therefore, expect a first boot time of several minutes. Subsequent reboot processes will not take as long. After Logging In 1. The login screen appears after the system has rebooted. Log in at this time. 2. Check the following log files for any messages, including warnings, relating to the update: /var/adm/sw/swinstall.
Updating an Existing Operating System and Software Updating HP-UX Software Updating Non-Interactively from Media or Network For a generic, single-media update where no "customizing" is required, you will be using the swinstall tool non-interactively. You can use a general instruction to "match what the target has" in order to load the updated versions of the same filesets as you have on your current system. 1. If you are using an external CD-ROM, ensure that the drive is turned onand mounted.
Updating an Existing Operating System and Software Updating HP-UX Software -x reinstall=true \ -x reinstall_files=true NOTE You will also need to repeat the above steps with the appropriate bundle on the HP-UX Extension Software. (See “Using HP-UX Extension Software” and the patch descriptions on the disc). The system will automatically reboot after updating with this bundle. For the details of swinstall options, see Managing HP-UX Software with SD-UX.
Updating an Existing Operating System and Software Using HP-UX Extension Software Using HP-UX Extension Software In addition to the tapes or CDs holding the operating system, the 11.0 release includes a CD labelled "HP-UX Extension Software". This CD is included as a means of delivering fixes for any problems that may be discovered after the release has been packaged for shipment. Procedure After you have installed or updated your system, read the Extension Software Information Sheet.
Updating an Existing Operating System and Software Installing Applications Software Installing Applications Software If your applications software is already in a depot (SD packaged), it can be loaded with the Ignite-UX installation. If it is in a non-SD format, you can create a bundle by using the Ignite-UX tool make_bundle and install or update it on the target system. See Appendix C, “Ignite-UX System Administration,”for specific examples for doing this.
Updating an Existing Operating System and Software Installing Applications Software Since optional networking products are shipped on separate media from the CORE HP-UX, their drivers are removed from the kernel during the update process. This means that if you update using the CORE medium or a depot made from it, the optional networking will not be available after reboot.
Updating an Existing Operating System and Software Installing Applications Software During the install, swinstall will edit the /stand/system file, rebuild the kernel, and reboot the system to bring the new kernel libraries into memory. For more information about installing and using VxFS and HP OnlineJFS, see the manual HP-UX System Administration Tasks, Chapter 4.
Installing From Media 3 Installing From Media Chapter 3 55
Installing From Media Chapter Contents Chapter Contents • Installing from a Media Source. • Booting the Target System. • Guided Installation: Using the Task Wizard. • Advanced Installation: Using Ignite-UX (TUI).
Installing From Media Installing from a Media Source Installing from a Media Source Figure 3-1 Preparing for a Media Install Media Used in Installation: Only the "CORE" HP-UX media will be required for the OS installation. Other media may need to be installed using the SD-UX tools unless they are available on a depot (see Chapter 2, “Updating an Existing Operating System and Software.”) • Tape: HP-UX Runtime (the "CORE" tape). • Tape: HP Applications. (Includes Ignite-UX).
Installing From Media Installing from a Media Source • Tape: HP-UX Support (Includes diagnostics). • Tape: HP-UX Extension Software. (Includes essential patches). OR • CD-ROM: HP-UX 10.x CORE • CD-ROM: Applications. (Includes Ignite-UX). • CD-ROM: Support. (Includes diagnostics). • CD-ROM: HP-UX Extension Software (Includes essential patches). Note: Only CD-ROM media will be used after HP-UX 10.20. "Original" customers receive only CD-ROM media; "Update" customers may receive CD-ROM or DDS-format tape.
Installing From Media Booting the Target System Booting the Target System The details in the following section are provided for guidance in case you have a variety of HP systems with different boot-console interfacing. 1. Make sure any external devices connected to the target system are turned on. 2. Turn on the target computer or cycle power. 3. Insert the CORE media into the appropriate drive. • Workstations: At the message that says how to stop autoboot, press and hold ESC.
Installing From Media Booting the Target System Newer Workstation Boot Help Menu: Command Description Auto [boot|search] [on|off] Boot [pri|alt|scsi.addr] [isl] Boot lan[.lan_addr] [install] [isl] Chassis [on|off] Diagnostic [on|off] Fastboot [on|off] Help Information LanAddress Monitor [type] Path [pri|alt] [lan.id|SCSI.
Installing From Media Booting the Target System When the actions menu shown above appears, do the following: • Press s Enter, to start a search for bootable devices. Older Workstation Search Results ========================================================================= Searching for Devices with Bootable Media. To terminate search, press and hold the ESCAPE key. Device Selection Device Path Device Type and Utilities P0 scsi.6.0 HP 2213A IPL P1 scsi.3.0 P2 scsi.0.
Installing From Media Booting the Target System Booting HP 9000 Servers As noted previously, you can halt the server autoboot process and redirect the boot process to boot from the desired media device.
Installing From Media Booting the Target System Newer Server Search Results ================================================================ Searching for potential boot device. This may take several minutes. To discontinue, press any key. Path Number P0 P1 P2 P3 Device Path 56/52.0 (dec) 56/52.3 (dec) 56/52.4 (dec) 56/52.6 (dec) Device Type Seq. record access media Seq.
Installing From Media Booting the Target System 2. Press any key to stop the autoboot process, at the message to do so. 3. Insert the install media (tape or CD-ROM). 4. Determine the hardware path of the install device from your system administrator. (There is no search capability to determine this information on older HP 9000 Server models). • If the primary path shown on your screen is not the same as that for the install device, respond with "n" to the prompt "Boot from primary boot path".
Installing From Media Booting the Target System Booting the V-Class To boot the system from the CORE media, follow the initial instructions on powering up the system and external drive (if used), as in “Booting the Target System”, in this chapter. The V2200 System Boot Console Typically the V-Class boot console has the following display when powered up (this example is for a Model SPP2000).
Installing From Media Booting the Target System ----------------------------------------------------------------PDC Firmware Version Information PDC_ENTRY version 3.1.0.29 POST Revision: 3.1.4.0 OBP Fieldtest Release 3.1.0.29, compiled 97/06/19 16:33:50(2) SPP_PDC version 1.1.7.2 ----------------------------------------------------------------Proc type Proc# Proc Rev Speed State Dcache Icache ---------- ----- -------- ------- ------- ------- ------- HP,PA82000 0 4.
Installing From Media Booting the Target System Command Description ------- ----------- AUto [BOot|SEArch ON|OFF] Display or set the specified flag BOot [PRI|ALT| ] Boot from a specified path BootTimer [time] Display or set boot delay time CLEARPIM Clear PIM storage CPUconfig [] [ON|OFF] Configure/Deconfigure Processor DEfault Set the sytem to defined values DIsplay Display this menu ForthMode Switch to the Forth OBP interface IO List the I/O devices in the system LS
Installing From Media Booting the Target System Primary boot path = 1/0:0.4.
Installing From Media Booting the Target System Searching for Other Bootable Devices If your CD-ROM is mounted at other than the primary path, and you need to determine the path, enter “``sea’’” (search) at the command prompt to see a general listing of devices. The CD will be listed with its hardware path. For example: Command: sea Searching for Devices with Bootable Media. Device Selection Device Path Device Type ----------------------------------------------------------------P0 5/2:0.2.
Installing From Media Using the Ignite-UX Interface Using the Ignite-UX Interface The following sections will guide you in using the Ignite-UX graphical and terminal interfaces. Choosing a Language for Interaction After booting from media, you will first see the following screen on systems that have a PS2 keyboard: Figure 3-4 Selecting a Keyboard Language • Enter the number of the keyboard language you are using. Then press Enter. This selection determines the key layout of the console keyboard.
Installing From Media Using the Ignite-UX Interface Welcome Screen Figure 3-5 ======================================================================== Welcome to Ignite-UX! Use the key to navigate between fields, and the arrow keys within fields. Use the key to select an item. Use the or to pop-up a choices list. If the menus are not clear, select the "Help" item for more information.
Installing From Media Using the Ignite-UX Interface NOTE Shortcuts Tips for using the TUI (character) interface: • If you prefer to use the keyboard to manipulate the Install interface, you can do so by typing the underlined letter of an item (such as "I" for Install HP-UX). • For general screen help, choose the Help button at the bottom of each screen. For context-sensitive help, press f1 or CTRL-f. • Use CTRL-k to get navigation key help.
Installing From Media Using the Ignite-UX Interface =========================================================================== User Interface and Media Options This screen lets you pick from options that will determine if an Ignite-UX server is used, and your user interface preference.
Installing From Media Using the Ignite-UX Interface • For a full Ignite-UX interface install (TUI mode), select Advanced Installation. You will see the interface shown in Figure 3-12, with the same functionality as is described in “Using the Ignite-UX Interface.”, but with TUI navigation. If you need to make adjustments to LVM parameters, select the Advanced Installation. Network Information (You will not see this screen if you are doing a media-only installation).
Installing From Media Using the Ignite-UX Interface The Task Wizard Welcome Screen Figure 3-9 TUI Navigation and Shortcuts In TUI mode, you will be able to use the keyboard to navigate. Press CTRL-K for detailed keyboard help at any time. HP-family terminals display function key labels (also called softkey labels) at the bottom of the window.
Installing From Media Using the Ignite-UX Interface 4. Press Enter again to select the item. 5. Tab to the next field. • You may also have to take some action, such as select OK or Modify in order to activate your selection. You can use the local help for the screen (f1 or Help) to get specific information. • As a shortcut to specifying an action, you can type the underlined letter of an item (such as "C" for Cancel) to activate the item without highlighting it.
Installing From Media Using the Ignite-UX Interface The rest of the wizard screens let you do the following tasks: • Select a root disk. • Specify the amount of root swap space. • Select a file system type. • Specify root volume group disks. • Select a language(s). • Select a user license. • Select Additional Software. • Pre-install disk information. (To allow you to exclude disks from the install.) • Pre-install check information. (To allow you to review errors or warnings.) • System Summary.
Installing From Media Using the Ignite-UX Interface The Task Wizard: Exiting Figure 3-11 If you want to leave the Task Wizard mode at any time, select the Cancel button, or press C. You will have the choices illustrated in Figure 3-11. You may want to leave the Task Wizard in order to do more advanced disk configuration or to add hardware, for example, in which case you can restart Ignite-UX in advanced mode in this screen.
Installing From Media Using the Ignite-UX Interface Advanced Media Installation (TUI) If you choose to run an advanced interface for the media install, you will see the following on the system you are installing: Figure 3-12 If you had been doing the individual installation from an Ignite-UX server, you would see a similar screen in GUI format, with full mouse functionality. The configuration which you can do on each of the tabs, in TUI and in GUI, is the same.
Installing From Media Using the Ignite-UX Interface 80 Chapter 3
Configuring an Ignite-UX Server 4 Configuring an Ignite-UX Server Chapter 4 81
Configuring an Ignite-UX Server Chapter Contents Chapter Contents • Overview: the Ignite-UX Server. • Ignite-UX Distribution Media. • Hardware Requirements for the Ignite-UX Server. • Network Requirements. • Setting Up an Ignite-UX Server. • Using Configuration Files. NOTE For online information about the Ignite-UX server, please see the /opt/ignite/share/doc/ directory on your system, and the manpage ignite(5).
Configuring an Ignite-UX Server Installing Server Software Installing Server Software Figure 4-1 Overview: the Ignite-UX Server For multiple installations, you will generally be executing the installation from the server, although you can also choose to install from a client-target system, in TUI mode.
Configuring an Ignite-UX Server Installing Server Software The requirements for a server are outlined in “Hardware Requirements for the Ignite-UX Server and Clients”. The steps for installing the server are outlined in “Setting Up an Ignite-UX Server”, Installation of Ignite-UX will take care of most of the server configuration tasks. These include setting up IP addresses and hostnames, interface location, and client response behavior.
Configuring an Ignite-UX Server Installing Server Software Memory For any system installed using Ignite-UX, the required minimum is 32 MB. (Some older Series 800 models (PA1.0 processor), such as 8x5 are not supported.) Your HP sales engineer can assist in determining the proper amount of RAM. Information on RAM requirements is also available on the following web site: http://www.hp.com:80/computing/mvp/memory. html.
Configuring an Ignite-UX Server Installing Server Software For example, in the Korn Shell or Posix Shell, you would type the following, using your system_name: export DISPLAY=system_name:0.0 • Product media to load onto the server your Ignite-UX and any software depots you plan to distribute to target systems. • Network access to the clients to be installed. Client and Server must be on the same subnet if you plan to do the initial boot of the client over the network.
Configuring an Ignite-UX Server Installing Server Software The Logical Volume Manager is offered on all HP 9000 platforms. Because it helps to organize file space across multiple physical disks, you are encouraged to adopt this method of disk management, if you are using multiple disks. See the manual System Administration Tasks, or the lvm(7) man page for details. Series 700 Software Disk Striping is replaced by LVM disk striping for all HP-UX 10.x systems. LVM disk striping is supported by Ignite-UX.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server Setting Up an Ignite-UX Server Ignite-UX functions through a client-server system. Much of the server setup process will be performed for you in the Ignite-UX installation process, but there are also some separate steps you must take after installation. Tools are supplied to help you complete the server setup. The following steps outline setting up or updating the server: 1. Obtain access to a suitable system running HP-UX 10.x.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server Installing Ignite-UX Software Each software bundle contains the Ignite-UX tools plus the data files required for support of the particular HP-UX release indicated by the bundle name. The Ignite-UX product replaces the capability previously supplied by the NetInstall bundle that came with HP-UX releases 10.01, 10.10 and 10.20. (A system cannot be configured as a server for both NetInstall and Ignite-UX.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server To use a depot other than /dev/dsk/c0t2d0 to read the software, you can specify the depot with the -s option. For example, the following would apply if you already have an OS depot, or you have made modifications to it. Then you can use the make_config and manage_index commands to generate a configuration file. For example: # make_config -s server:/depot_700 \ -c /var/opt/ignite/data/Rel_B.10.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server HP-supplied software is packaged in this form. See the make_bundles(1M) manpage for information on making SD bundles in an SD depot.) For example, to make compiler depot bundles available type the following: /opt/ignite/bin/make_config -s hpfcxxx.hp.com:/depots/compiler -c \ /var/opt/ignite/data/Rel_B.10.20/compilers_cfg /opt/ignite/bin/manage_index -a -f /var/opt/ignite/data/Rel_B. 10.20/compilers_cfg 2.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server Starting the Ignite-UX Server • Run ignite to complete the configuration and to start the server process. Type the following: /opt/ignite/bin/ignite This will start the Ignite-UX server. Complete the Configuration: After you have Ignite-UX up and running, you will see the Welcome screen and then the Ignite-UX Server GUI. When you have booted the clients you will see client icons on the Server GUI.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server Figure 4-2 The Server Options Tab • Select on Default Configurations, highlight the one you want 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). • Click on the selection list to display the available (configured) printers. Select the one you want to use.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server • Use the Interface selection list to designate where you want to see the client UI for this installation. If you have a server configured, you can have the choice of running the client installation interface from either the target (as a Terminal User Interface) or the Ignite-UX server (as a Graphical User Interface). If the client installation is to be non-interactive (no interface), select "None".
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server This data can also be configured from a command line by using the tool setup_server(1M) for this procedure. Or you can directly edit the instl_boottab file; this is necessary in order to modify the listing of existing IP addresses. See the instl_bootd(1M) man page for further details. DHCP Address Range First ensure that these IP addresses are not assigned elsewhere. These IP addresses are used during the OS download and application loading.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server Server Session Options Tab Figure 4-4 The Session Options tab displays a number of check boxes to configure client response behavior. • Confirm New Clients: This check box, if set, results in the appearance of a dialog screen each time a new client is booted from the Ignite-UX server.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server Select this button to cause the client system to halt (rather than reboot) after installation. • Automatically move completed clients to history: Select this button to automatically add completed clients to the end of the history log, /var/opt/ignite/clients/history/history.log. It will also move their config and manifest files to history for future reference. The client icon will be removed from the Server screen.
Configuring an Ignite-UX Server Setting Up an Ignite-UX Server You can now proceed with using the Ignite-UX interface (“Installing from the Server”). For More Information See Appendix B, “Using Configuration Files,”for the details of setting up configuration files for Ignite-UX. For more details about server configuration and "golden disks", see the "Ignite-UX Startup Guide for System Administrators" and "Ignite-UX Cold Installations", both on your Ignite-UX server system in /opt/ignite/share/docs/.
Installing from the Ignite-UX Server 5 Installing from the Ignite-UX Server Chapter 5 99
Installing from the Ignite-UX Server Chapter Contents Chapter Contents • Booting Client Systems from the Network. • Installing from the Server. • Selecting Server or Client Console Interaction. • Displaying the Client Systems. • Configuring the Installation • Basic Tab. • Software Tab. • System Tab. • File System Tab. • Advanced Tab. • Doing a Non-Interactive Remote Installation (bootsys).
Installing from the Ignite-UX Server Network Source Installation Network Source Installation Figure 5-1 Booting Client Systems from the Network NOTE Network boot applies to HP 9000 Workstations and HP 9000 Servers (K/D Class) only.
Installing from the Ignite-UX Server Network Source Installation Supported Workstations: At Release 11.
Installing from the Ignite-UX Server Network Source Installation If the client system is already running an OS, you may use this procedure or use the bootsys command as described in “Non-Interactive Installation Using bootsys”. Procedure 1. Determine your network server address for the install. If necessary, see your system administrator for this information. 2. Turn on your target system. 3.
Installing from the Ignite-UX Server Network Source Installation search lan Note that it will typically take two or three searches before the Ignite-UX server will be found, due to a built-in delayed response from the server system. • Identify your LAN server from the listing. • If three attempts result in no response from the desired server, see Chapter 7, “Troubleshooting.” 3.
Installing from the Ignite-UX Server Network Source Installation Command Description ------Auto [boot|search] [on|off] Display or set auto flag Boot [pri|alt|scsi.addr] [isl] Boot from primary,alternate or SCSI Boot lan[.
Installing from the Ignite-UX Server Network Source Installation Time Note (Booting from LAN) This should take 3 to 5 minutes.
Installing from the Ignite-UX Server Installing from the Server Installing from the Server Figure 5-4 Selecting Server or Client Console Interaction. If you have not already done so, start Ignite-UX by typing /opt/ignite/bin/ignite.
Installing from the Ignite-UX Server Installing from the Server If you are using Ignite-UX from the server, you will see the GUI and graphical navigation, as in the following procedures. If you are using it from a client, you will see a Terminal User Interface (TUI), but with equivalent keyboard navigation. Displaying the Client Systems Figure 5-5 The Ignite-UX Server Client Display Before any new clients are represented as icons on the server display, they must first be booted from the Ignite-UX server.
Installing from the Ignite-UX Server Installing from the Server • Click the right mouse button (Mouse Button Three) on the selected client icon to get an Actions screen similar to the pulldown Actions menu. Displaying Client Actions Clicking the right mouse button on a client icon opens a client actions menu: Figure 5-6 • To install a client, click on Install Client → New Install. • To repeat the previous install configuration on another client, click on Install client → Repeat Installation.
Installing from the Ignite-UX Server Installing from the Server • Remove client will simply delete the icon for the selected client. Data for that client is also removed. • View Hardware allows you to see a display of the hardware associated with the selected client. • View/Print Manifest allows you to see or print the manifest and/or Software Certificate. The manifest is also available in saved form on the client and server systems after the installation as the manifest files.
Installing from the Ignite-UX Server Configuring the Installation Configuring the Installation Figure 5-7 To begin the installation, first select a client icon. Then, from the Actions menu, choose Install Client → New install, or Install Client → Repeat install. At the beginning of a new installation: if you have previously installed this client, you will be asked if you want to use the same install configuration data again.
Installing from the Ignite-UX Server Configuring the Installation • You can choose a pre-set configuration in the "Repeat Install" selection list to repeat a previously installed configuration and execute it within Ignite-UX, without further intervention. Using the Ignite-UX Interface. After you choose to install a system, you will see the following screen. The Basic Tab Figure 5-8 NOTE If you see the following message: Settings from a previous installation session were found at startup.
Installing from the Ignite-UX Server Configuring the Installation Respond Yes if you wish to re-use some or all of the configuration that you used in the previous session. Respond No if you want to use an entirely new configuration. This screen shows all the basic information for setting up the file system and for loading the Operating System (OS) environment. It also allows you to configure languages, locale, and keyboard requirements. A Save As...
Installing from the Ignite-UX Server Configuring the Installation Ignite-UX. "HFS" is the standard file system format. The File System tab will give you additional opportunities to configure the LVM volumes. In the File System tab, you can edit the sizes of LVM partitions, or use the values that Ignite-UX computes for you.
Installing from the Ignite-UX Server Configuring the Installation A locale describes the system management of a language for doing the following: • Messaging • Representing numbers • Displaying monetary values • Telling time • Generating characters • Sorting text HP-UX can have more than one installed language.
Installing from the Ignite-UX Server Configuring the Installation variables in your config file. When using LVM, you will see selections for easily setting up multiple disks, striping, and file system creation. For details on setting this up, see the instl_adm(4) man page. Functions Available on all Tabs Save As… In server mode, when you have finished your configuration for all tabs, you can save the configuration as a specific file.
Installing from the Ignite-UX Server Configuring the Installation The Software Tab Figure 5-9 This tab allows you to choose licensing level and additional applications that you configured when you set up your server. To access a specific depot, you can also change depot locations. NOTE This display does not dynamically update from a newly-selected depot. When choosing a new depot, it must be identical in content to the current one.
Installing from the Ignite-UX Server Configuring the Installation • Product List: Double-click on a product in the list to select (highlight) it and to toggle its "marked" status ("Yes" or "No"). You can also use the Mark/Unmark Selection(s) button to toggle the "marked" status for a selected item. NOTE If patches are kept in a separate depot, by default they will be loaded after CORE software.
Installing from the Ignite-UX Server Configuring the Installation System Parameter Screen Figure 5-10 Hostname Your system must have a unique system name (a "hostname"), which can be a simple name (such as cleo). A system name must fulfill the following conditions: • It must contain no more than 8 characters • It must contain only letters, numbers, underscore (_), or hyphen (-). • It must start with a letter. • Upper case letters are not recommended.
Installing from the Ignite-UX Server Configuring the Installation IP Address This field will be used to enter the IP address. IP addresses are of the form nn.n.nn.nnn. For example: 15.1.48.140 You can use the tool nslookup hostname to determine an existing IP address. Subnet Mask This field will be used to set the subnet mask. The subnet mask will typically be provided by your network administrator, and is of the form nnn.nnn.nnn.n or a corresponding hex number. For example: 255.255.248.
Installing from the Ignite-UX Server Configuring the Installation Set Time Zone Screen Figure 5-11 Select this button to bring up a display of time zone selections. You will see two selector lists: the first consists of general locations, and the second has corresponding time zones. Select an item and select OK to make a choice.
Installing from the Ignite-UX Server Configuring the Installation Set Root Password Screen Figure 5-12 The "root" account is used for system administration tasks. To insure the security of the system, the root account should have a password. You should observe the following requirements when setting a password: • The password must be at least six characters long. • Characters must be from the English alphabet.
Installing from the Ignite-UX Server Configuring the Installation • XNTP Static Routes Screen Figure 5-13 If your network is divided into subnets, you will probably need to specify a gateway system to reach other subnets: • Destination: The field has the word "default" or the IP address of the destination network. • Gateway: The IP address of the device connecting your network to the remote network, or your own IP, if wildcard routing is used.
Installing from the Ignite-UX Server Configuring the Installation DNS Screen Figure 5-14 On this screen, you can configure the Domain Name (an extension to the host name, such as fc.hp.com) and the IP address of the Domain Name Server. The listing of current Servers is displayed, if they are predefined in the Ignite-UX server. The IP address of the Domain Name Server is given in a form such as 15.13.115.168. Use the command nslookup on a running system to find this information.
Installing from the Ignite-UX Server Configuring the Installation NIS Screen Figure 5-15 Typically, the (non-server) hosts in a network are NIS clients. Whenever a process on an NIS client requests configuration information, it calls NIS instead of looking in its local configuration files. The set of maps shared by the servers and clients is called the NIS domain. For more information on NIS, see the domainname(1M) man page, or the manual Installing and Administering NIS Services.
Installing from the Ignite-UX Server Configuring the Installation XNTP Screen Figure 5-16 The xntpd daemon maintains system time, in agreement with Internet standard time servers. It does all computations in fixed point arithmetic and clock adjustment code is carried out with high precision. For more information on xntp, see the xntpd(1M) man page.
Installing from the Ignite-UX Server Configuring the Installation Figure 5-17 This screen enables you to configure different network interface card(s). You can enter or change IP and Subnet information, as needed, and designate the Primary Interface. NOTE If the target system has more than one interface, the LAN card designated as Primary will be the one that is associated with the host name of the system in /etc/hosts. • Select an interface card from the selection list.
Installing from the Ignite-UX Server Configuring the Installation File System Tab Figure 5-18 This tab enables you to do a variety of file-system and disk-configuration tasks and will differ in appearance, depending on whether you previously selected LVM or whole disk, on the Basic tab. This illustration is what you would see if you had picked LVM on the Basic tab. Adding and Changing File System Configuration To add or change any configurations on the display of file systems, 1.
Installing from the Ignite-UX Server Configuring the Installation For LVM: • One of the logical volumes must be root (/). • A swap volume is required. • Directory names must have valid HP-UX names (e.g., /usr, /database, etc.). The buttons which activate changes are: • Add • Modify • Remove Generally, changes are not put into effect until you select one of these. If you make a change and then leave the tab without using one of these buttons, your changes may not be applied.
Installing from the Ignite-UX Server Configuring the Installation NOTE Renaming or changing the FS structure of a disk causes the old file system on that disk to be lost (a warning message will remind you of this). • If you want to add a new/unused disk and give it a different volume group name or create a new volume group, select the Add/Remove field and follow the procedure.
Installing from the Ignite-UX Server Configuring the Installation Add/Remove Disks Fixed size: The selected (highlighted) file system is set to this size. All Remaining: The selected file system automatically takes over all remaining file system space on the disk or volume group. Free Size: Use this selection when you know how much free space you wish the volume to have after the system is installed. The size of the volume will be the specified amount plus the amount the selected software requires.
Installing from the Ignite-UX Server Configuring the Installation Additional Tasks This button enables you to configure advanced information in the following categories, as needed: Click on the field to see the following menu items: • Disk Parameters. • File System Parameters. • Logical Volume Parameters. • Volume Group Parameters. Clicking on one of these will open a screen which will enable you to change advanced parameters. The button will retain the label of the area you are currently working in.
Installing from the Ignite-UX Server Configuring the Installation 3. Indicate whether Media Init is required, by clicking on the selection box and selecting a choice, as needed. 4. Select Modify to configure changes. 5. Select OK, to leave Advanced Disk Parameters and return to the File System tab. Tracks per Cylinder • Select a disk by clicking on its entry in the list displayed. • Edit the Trks/Cyl field as needed, using the backspace and left/right arrow keys.
Installing from the Ignite-UX Server Configuring the Installation The interleave factor, “interleave”, refers to the relationship between sequential logical records and sequential physical records on the disk. It defines the number of physical records that lie between the beginning points of two consecutively numbered logical records. The choice of interleave factor can have a substantial impact on disk performance. For more information, consult the manual for your disk hardware.
Installing from the Ignite-UX Server Configuring the Installation • Minfree • Disk Density • Cylinder/Group Advanced Logical Volume Layout Screen Figure 5-21 Use this screen to do detailed configuring of LVM, as needed, in the following areas: Cont Alloc (Continuous Allocation): See the manpage lvcreate(1M), for more information. B-block Relo (Bad-Block Relocation): See the manpage lvcreate(1M), for more information.
Installing from the Ignite-UX Server Configuring the Installation For more details, see the manpage lvcreate(1M). LVol Name (Logical Volume Name): • Type in the name you want for the selected volume. For more details, see the manpage lvcreate(1M). Logical Volume to Disk This button displays a screen which allows you to restrict the disk drives Mapping on which the volume data will reside. Normally, the data will be allocated over these disks sequentially. See the manpage lvextend(1M), for more details.
Installing from the Ignite-UX Server Configuring the Installation • Physical Ext Size (MB) (Physical Extent Size in Megabytes). Advanced Tab Figure 5-23 Transfer Lists In this screen you can activate any HP or custom scripts which you might want to run as part of your installation. Note that the scripts listed are those with a "scripts" keyword in the INDEX file. The file /var/opt/ignite/config.local is a place holder for such files as you may want to generate for post-install, for example.
Installing from the Ignite-UX Server Configuring the Installation Removing a Script To remove an item from "Scripts to be Executed:" 1. Select the item in "Scripts to be Executed". 2. Select Remove to remove it. The item will be deactivated, but will continue to be available in the "Scripts Available" list.
Installing from the Ignite-UX Server Executing the Installation: Go! Executing the Installation: Go! Select Go! in any Ignite-UX tab to initiate the installation. You do not need to examine all tabs, if you simply want to do a generic installation. 1. You will then see a confirmation screen listing the disks that will be written on during the process of installation, and a log of any warnings or errors.
Installing from the Ignite-UX Server Executing the Installation: Go! Figure 5-24 The manifest screen provides customer order information for the selected target system. Ignite-UX can display and print the manifest of a newly-installed system from the Server screen, with the action View/Print Manifest. You can view or print the manifest when a target client is "Complete", as indicated by the Client Status screen. The online information is scrollable.
Installing from the Ignite-UX Server Executing the Installation: Go! • Swap Configuration • Kernel Configuration. • System Information. The manifest file is saved on the server as /var/opt/ignite/clients/LLA/manifest/manifest. It is on the target client system as /var/opt/ignite/local/manifest/manifest.
Installing from the Ignite-UX Server Executing the Installation: Go! See Appendix C, “Ignite-UX System Administration,”and the manpage entry for the bootsys(1m) command for more examples and information.
HP-UX System Recovery 6 HP-UX System Recovery Chapter 6 143
HP-UX System Recovery Chapter Contents Chapter Contents • Overview. • System Recovery: Creating a Bootable Recovery Tape: make_recovery. • Creating a Bootable Install Tape: make_medialif. • "Expert" Recovery Using Core Media Tools.
HP-UX System Recovery Overview Overview HP-UX provides two recovery methods as part of the standard product. Which method you use will depend on the situation. “Expert” Recovery The first method, “expert recovery” (formerly called Support Media Recovery), allows you to recover a slightly damaged root disk or root volume group. With this method, you boot a special recovery system from core HP media.
HP-UX System Recovery Overview 1. Replace the failed disk (if necessary) - boot from your customized recovery tape. 2. Wait for the recovery to complete. 3.
HP-UX System Recovery System Recovery: Creating a Bootable Recovery Tape System Recovery: Creating a Bootable Recovery Tape NOTE The copyutil tool is only supported as a diagnostic tool for HP-UX 10.x or later, and should not be used for recovery. Instead, you should use one of the tools described in this chapter. Note also that make_recovery (and booting from tape) is not yet supported on current HP V- class systems. The make_recovery command creates a system recovery tape.
HP-UX System Recovery System Recovery: Creating a Bootable Recovery Tape NOTE The system recovery tape is only as good as the last time it was created. The tape should be re-created if new software, hardware, or patches have been added. You can use the check_recovery to determine whether the system has changed enough that the tape needs to be re-created. Logging Progress and errors are logged to the file /var/opt/ignite/logs/mkrec.log*.
HP-UX System Recovery System Recovery: Creating a Bootable Recovery Tape To duplicate the recovered system disk or volume group, do the following: 1. Mount the system recovery tape on the tape drive. 2. Boot the system. 3. Interrupt the boot sequence to redirect it to the tape drive. 4. Cancel the non-interactive installation by hitting any key when given the opportunity. 5. Provide necessary configuration information such as disks, hostname, IP address, timezone, root password, and DNS server. 6.
HP-UX System Recovery System Recovery: Creating a Bootable Recovery Tape Note that the install will proceed according to how the variables run_ui and control_from_server are set in the INSTALLFS and in the config files. Creating a fully self-contained tape that does not require the use of an Ignite-UX server involves copying a depot or system archive to the tape and specifying a config file representing the archive or depot.
HP-UX System Recovery “Expert” Recovery Using the Core Media “Expert” Recovery Using the Core Media If your system should become so compromised or corrupt that it will not boot at the login prompt, or the system boots, but critical files are corrupted, adversely affecting overall system performance, it may be useful to restore system elements with core recovery media. Before you attempt to recover an HP-UX system, you should have the following information about your system disk available.
HP-UX System Recovery “Expert” Recovery Using the Core Media Automated Recovery Procedures There are four possible expert recovery situations, each of which has its associated recovery procedure: • If, after a system problem, you can't get the system to the ISL> prompt from the system disk, you will want to rebuild the bootlif on the system disk, and install all critical files required to boot on the root filesystem.
HP-UX System Recovery “Expert” Recovery Using the Core Media The console will then display the following: Boot from alternate boot path (Y or N)?> 5. If the alternate boot path specifies the address of the CD device where the Core CD is mounted, enter y at the prompt. If the alternate boot path does not specify the address of the CD device where the HP-UX Core media is mounted, enter n at the prompt.
HP-UX System Recovery “Expert” Recovery Using the Core Media * Loading in a shell... * Loading in the recovery system commands... ... HP-UX SYSTEM RECOVERY CORE MEDIA WARNING: YOU ARE SUPERUSER !! NOTE: Commands residing in the RAM-based file system are unsupported 'mini'comma nds. These commands are only intended for recovery purposes. Loading commands needed for recovery! Press to continue. 10.
HP-UX System Recovery “Expert” Recovery Using the Core Media 11. To load a file or files, enter l at the prompt; something similar to the following will be displayed: Filesystem kbytes used avail %cap iused ifree iused Mounted on / 2011 1459 552 73% 137 343 29% ? /duped_root 2011 1418 593 71% 49 431 10% ? Enter the filename(s) to load: 12. Enter the name(s) of the damaged/corrupted file(s) you wish to load.
HP-UX System Recovery “Expert” Recovery Using the Core Media 14. Press return and the Main Menu appears: HP-UX CORE MEDIA RECOVERY MAIN MENU s. b. l. r. x. c. Search for a file Reboot Load a file Recover an unbootable HP-UX system Exit to shell Instructions on chrooting to a lvm /(root). This menu is for listing and loading the tools contained on the core media. Once a tool is loaded, it may be run from the shell. Some tools require other files to be present in order to successfully execute.
HP-UX System Recovery “Expert” Recovery Using the Core Media 18. To begin the actual system recovery, select r. The HP-UX Recovery MENU is then displayed: HP-UX Recovery MENU Select one of the following: a. Rebuild the bootlif (ISL, HPUX, and the AUTO file) and install all files required to boot and recover HP-UX on a root file system. b. Do not rebuild the bootlif but install files required to boot and recover HP-UX on the root file system. c. Rebuild only the bootlif. d.
HP-UX System Recovery “Expert” Recovery Using the Core Media 20. Assuming the root device file is incorrect, select b. You will be prompted to enter the correct device filename: Enter the device file associated with the '/'(ROOT) file system.
HP-UX System Recovery “Expert” Recovery Using the Core Media 21. If you were to enter c1t1d0 as the root device filename, you would see the following display: DEVICE FILE VERIFICATION MENU This menu is used to specify the path of the root file system When the information is correct, select 'a'. INFORMATION to verify: Device file used for '/'(ROOT) is c1t1d0 The path to disk is 56/52.1.0 Select one of the following: a. The above information is correct. b.
HP-UX System Recovery “Expert” Recovery Using the Core Media 23. Assuming that the bootlif path is correct, enter a; the following menu is displayed: FILE SYSTEM CHECK MENU The file system check '/sbin/fs/hfs/fsck -y /dev/rdsk/c1t1d0' will now be run. Select one of the following: a. Run fsck -y . b. Prompt for the fsck run string on c1t1d0. m. Return to the 'HP-UX Recovery MENU.' Selection: 24.
HP-UX System Recovery “Expert” Recovery Using the Core Media downloading INSTALL to /stand/vmunix **** Creating device files on the target disk **** ******* Renaming the following files: ******* '/.profile' has been renamed '/.profileBK' *********** Installing bootlif mkboot -b /dev/rmt/1m mkboot -a NOTE *********** -i ISL -i HPUX /dev/rdsk/c1t1d0 hpux (56/52.1.
HP-UX System Recovery “Expert” Recovery Using the Core Media RECOVERY COMPLETION MENU Use this menu after the recovery process has installed all requested files on your system. Select one of the following: a. REBOOT the system and continue with recovery. b. Return to the Main Menu. Selection: 27. Once you find yourself at the Recovery Completion menu, complete the recovery process by selecting a. You will see messages similar to the following: NOTE: System rebooting ...
HP-UX System Recovery “Expert” Recovery Using the Core Media THIS SYSTEM HAS BEEN BOOTED USING A TEMPORARY KERNEL! DO NOT ATTEMPT TO INVOKE MULTI-USER RUN-LEVEL USING THIS KERNE L! Type the following command from the shell prompt for more information about completing the recovery process: cat /RECOVERY.DOC 30. To obtain more information on the recovery process, type the following at the prompt: # cat /RECOVERY.
HP-UX System Recovery “Expert” Recovery Using the Core Media INSTRUCTIONS to complete your LVM recovery: The system must now be up now in "maintenance mode". NOTE: In order for the following steps to lead to a successful lvm recovery the LVM label information must be valid. If the bootlif was updated from the RAM-based recovery system, then "mkboot -l" has already been run to repair this label. step 1.
HP-UX System Recovery “Expert” Recovery Using the Core Media /lvmrec.scrpt c0t6d0 In this example 'c0t6d0' is the device file used to access the bootlif. step 3. Once '/lvmrec.scrpt' completes, issue the command "reboot" and bringthe system fully up. The recovery of the root LVM is complete. If the '/lvmrec.scrpt' issued the following warning: "************ I M P O R T A N T ******************" " " "Root logical volume has been repaired, but.......
HP-UX System Recovery “Expert” Recovery Using the Core Media Installing Critical Root Files Only Following is an example of the detailed procedure for installing all the critical files necessary to boot on the target root filesystem: Boot the CORE media, following the steps in .
HP-UX System Recovery “Expert” Recovery Using the Core Media WARNING: YOU ARE SUPERUSER !! NOTE: Commands residing in the RAM-based file system are unsupported 'mini' comm ands. These commands are only intended for recovery purposes. Loading commands needed for recovery! WARNING: If ANYTHING is changed on a root (/) that is mirrored, ‘maintenance mode’ (HPUX -1m) boot MUST be done in order to force the mirrored disk to be updated! Press to continue. 3.
HP-UX System Recovery “Expert” Recovery Using the Core Media HP-UX Recovery MENU Select one of the following: a. Rebuild the bootlif (ISL, HPUX, and the AUTO file) and install all files required to boot and recover HP-UX on a target root file system. b. Do not rebuild the bootlif but install files required to boot and recover HP-UX on the root file system. c. Rebuild only the bootlif. d. Replace only the kernel on the root file system. m. x. Return to 'HP-UX Recovery Media Main Menu'. Exit to the shell.
HP-UX System Recovery “Expert” Recovery Using the Core Media Enter the device file associated with the '/'(ROOT) file system (example: c0t1d0s1lvm ) : c0t0d0s13 /dev/rdsk/c0t0d0s13 not a special file Enter the address associated with the '/'(ROOT) file system (example: 4.0.1) : 4.0.0 NOTE: if your '/'(ROOT) is not part of a sectioned disk layout enter a 'W' for whole disk layout or enter a 'l' for an LVM disk layout instead of a section number.
HP-UX System Recovery “Expert” Recovery Using the Core Media FILE SYSTEM CHECK MENU The file system check '/sbin/fs/hfs/fsck -y /dev/rdsk/c1t1d0' will now be run. Select one of the following: a. Run fsck -y . b. Prompt for the fsck run string on c1t1d0. m. Return to the 'HP-UX Recovery MENU.' Selection: 9. Select a to run fsck -y to check your file system for corruption.
HP-UX System Recovery “Expert” Recovery Using the Core Media downloading INSTALL to /stand/vmunix **** Creating device files on the target disk **** ******* Renaming the following files: ******* '/.profile' has been renamed '/.profileBK' RECOVERY COMPLETION MENU Use this menu after the recovery process has installed all requested files on your system. Select one of the following: a. REBOOT the target system and continue with recovery. b. Return to the CORE Media Main Menu. Selection: 12.
HP-UX System Recovery “Expert” Recovery Using the Core Media COnfiguration menu INformation menu SERvice menu MFG menu Displays Displays Displays Displays or sets boot values hardware information service commands manufacturing commands DIsplay HElp [
HP-UX System Recovery “Expert” Recovery Using the Core Media The file contains the following information: If a card has been added to, or removed from, your system since the original installation was completed, there is a chance that the device file for the root disk has changed. Consequently, before you run the LVM script ./lvmrec.scrpt (Step 2, below), you should first recover /stand/ioconfig from backup and reboot.
HP-UX System Recovery “Expert” Recovery Using the Core Media In this example 'c0t6d0' is the device file used to access the bootlif. step 3. Once '/lvmrec.scrpt' completes, issue the command "reboot" and bring the system fully up. The recovery of the root LVM is complete. issued the following warning: If the '/lvmrec.scrpt' "************ I M P O R T A N T ******************" " " "Root logical volume has been repaired, but.......
HP-UX System Recovery “Expert” Recovery Using the Core Media Welcome to the HP-UX installation process! Use the and/or arrow keys to navigate through the following menus, and use the key to select an item. If the menu items are not clear, select the "Help" item for more information. [ Install HP-UX ] [ Run a Recovery Shell ] [ Cancel and Reboot ] [ Advanced Options ] [ Help ] 1.
HP-UX System Recovery “Expert” Recovery Using the Core Media WARNING: If ANYTHING is changed on a root(/) that is mirrored a 'maintenance mode'(HPUX -lm) boot MUST be done in order to force the mirrored disk to be updated!! Press to continue. 3. Press Return and the following status message is displayed: Loading commands needed for recovery! After a similar boot steps to the previous, the following message appears HP-UX CORE MEDIA RECOVERY MAIN MENU s. b. l. r. x. c.
HP-UX System Recovery “Expert” Recovery Using the Core Media This menu must be used to determine the path to the bootl if (ISL, HPUX and the AUTO file). When the information is correct, select 'a'. INFORMATION to verify: Path to the bootlif is 56/52.1.0 Select one of the following: a. The above information is correct. b. WRONG!! The path to bootlif is incorrect. m. x. Return to the 'HP-UX Recovery MENU.' Exit to the shell. Selection: 6.
HP-UX System Recovery “Expert” Recovery Using the Core Media BOOT STRING VERIFICATION MENU This menu must be used to verify the system's boot string. When the information is correct, select 'a'. INFORMATION to verify: The system's boot string should be: 'hpux' Select one of the following: a. The above information is correct. b. WRONG!! Prompt the user for the system's boot string. m. x. Return to the 'HP-UX Recovery MENU.' Exit to the shell.
HP-UX System Recovery “Expert” Recovery Using the Core Media RECOVERY COMPLETION MENU Use this menu after the recovery process has installed all requested files on your system. Select one of the following: a. REBOOT the target system and continue with recovery. b. Return to the CORWE Media Main Menu. Selection: 10. Once you find yourself at the RECOVERY COMPLETION MENU, complete the recovery process by selecting a, rebooting your system. This completes the process for rebuilding the bootlif only.
HP-UX System Recovery “Expert” Recovery Using the Core Media * Loading in a shell... * Loading in the recovery system commands... ... HP-UX SYSTEM RECOVERY CORE MEDIA WARNING: YOU ARE SUPERUSER !! NOTE: Commands residing in the RAM-based file system are unsupported 'mini' commands. These commands are only intended for recovery purposes.
HP-UX System Recovery “Expert” Recovery Using the Core Media 5. To begin the actual system recovery, select r. You will see the HP-UX Recovery menu: HP-UX Recovery MENU Select one of the following: a. Rebuild the bootlif (ISL, HPUX, and the AUTO file) and install all files required to boot and recover HP-UX on a target root file system. b. Do not rebuild the bootlif but install files required to boot and recover HP-UX on the root file system. c. Rebuild only the bootlif. d.
HP-UX System Recovery “Expert” Recovery Using the Core Media Enter the device file associated with the '/'(ROOT) file system (For example: c0t1d0s1lvm ) : device_file /dev/rdsk/device_file not a special file Enter the address associated with the '/'(ROOT) file system (For example: 4.0.1) : address NOTE: if your '/'(ROOT) is not part of a sectioned disk layout enter a 'W' for whole disk layout or enter a 'l' for an LVM disk layout instead of a section number.
HP-UX System Recovery “Expert” Recovery Using the Core Media FILE SYSTEM CHECK MENU The file system check '/sbin/fs/hfs/fsck -y /dev/rdsk/c1t1d0' will now be run. Select one of the following: a. Run fsck -y . b. Prompt for the fsck run string on c1t1d0. m. Return to the 'HP-UX Recovery MENU.' Selection: 10.
HP-UX System Recovery “Expert” Recovery Using the Core Media 12. Once you find yourself at the RECOVERY COMPLETION MENU, complete the recovery process by selecting a, REBOOT the target system.... This completes the process for replacing the kernel only.
Troubleshooting 7 Troubleshooting Chapter 7 185
Troubleshooting Chapter Contents Chapter Contents • Likely Problem Areas • Running add_release • Running swinstall • Booting a Client • Setting Up the Ignite-UX Cluster • Running the make_depots command • Adjusting File System Size • Large Systems 186 Chapter 7
Troubleshooting Likely Problem Areas Likely Problem Areas As an install progresses, you will see messages relating to the progress being entered into the log file. Usually these messages are related to normal behavior. ERROR and WARNING messages have the following significance: ERROR This indicates a serious problem, usually requiring action from the user in order to proceed with an installation. WARNING This indicates something out of the ordinary, but not fatal. The warning may require action.
Troubleshooting Using Config Tools Using Config Tools Table 7-1 Running add_release Message(s) or Behavior Couldn't mount cdrom device at: device_file Possible Cause This error could occur if: • the user entered the wrong device file • the cdrom is not loaded and ready Fix Try to mount the cdrom manually by executing the following: mount -Fcdfs -oro \ cdrom_block_device_file \ mount_point_dir Verify that the device file is correct by running sam.
Troubleshooting Using Config Tools Message(s) or Behavior Possible Cause Fix Load command failed: load_command This error occurs if the command used to load software has failed during the load. Such failure can be due to a problem with the media or the source specification. Refer to the log file for the command used to load software. If make_depots is used its log file is under /var/opt/ignite/logs.
Troubleshooting Using Config Tools Table 7-2 Other Problems Related to add_release Message(s) or Behavior Possible Cause You do not see the releases you expect to see as available to load. This could happen if you specify the wrong -u parameter. Fix For -u the following parameters should be used: -u re This should be used by HP Authorized distributors to load DART software and OS releases provided to them by HP as part of the Instant Ignition program.
Troubleshooting During Installation and Configuration of Ignite-UX Tools and Data During Installation and Configuration of Ignite-UX Tools and Data Table 7-3 Running swinstall Message(s) or Behavior swinstall cannot read the tape. For example you may see the following: Possible Cause Wrong device file Use the Actions menu in the SAM Peripheral Devices/Tape Devices area to show the device files for the tape drive. No device file present for the tape.
Troubleshooting During Installation and Configuration of Ignite-UX Tools and Data Message(s) or Behavior Failure reading the contents of the tape (cont.). Possible Cause Bad/wrong tape. Fix Verify label on tape. Check the contents. SD tapes are in "tar" format.
Troubleshooting During Installation and Configuration of Ignite-UX Tools and Data Table 7-4 Booting a Client Message(s) or Behavior Using "boot lan.080009-xxxxxx" s700 won't boot from known good IUX server. Possible Cause • Not enough temporary IP addresses for booting. • rbootd is not running on the server. • server lan is something other than ethernet, e.g., FDDI,X.25,token-r ing, and s700 is older generation 715,735,755.
Troubleshooting During Installation and Configuration of Ignite-UX Tools and Data Table 7-5 Setting Up the Ignite-UX Cluster Message(s) or Behavior ERROR: This machine is not an NFS server (no nfsd running). The -n option will not be processed. 194 Possible Cause NFS is not set up. The IUX server must be an NFS server if you wish to control the installation process from the IUX server or if you wish to make sure that config files and manifest information end up on the server.
Troubleshooting During Installation and Configuration of Ignite-UX Tools and Data Message(s) or Behavior Bad IP addresses specified for either the temp IP or DHCP: ERROR: Illegal IP (IP address given) passed to -I. OR ERROR: Bad range passed to -I. 1st IP address given is greater than 2nd IP address given. Possible Cause Fix The checks done on this IP address are the following: Given a format like ###.###.###.### (for example, 151.12.54.205), ensure the following: Check the IP address syntax.
Troubleshooting During Installation and Configuration of Ignite-UX Tools and Data Message(s) or Behavior Possible Cause Fix make_depots: warning - -r option \ ignored with -d absolute path name Using either -r or -m option with -d absolute path name. Remove -r and/or -m option. make_depots: warning - -r and -o \ arguments that differ not recommended Arguments to -r and -o are different. Make arguments the same.
Troubleshooting During Installation and Configuration of Ignite-UX Tools and Data Message(s) or Behavior make_depots: error - \ unknown source depot type XXX Chapter 7 Possible Cause The -s argument is not identifiable as either a depot (local or remote) or a character or block special device file. Fix Specify a real source depot.
Troubleshooting During Installation and Configuration of Ignite-UX Tools and Data Message(s) or Behavior make_depots: \ malloc of XXX failed make_depots: \ strdup of XXX failed Possible Cause The make_depots command failed due to lack of resources. make_depots: \ tmpnam of XXX failed Fix Kill other applications running on the system to free up memory. Add more memory and/or swap space.
Troubleshooting Adjusting File System Size Adjusting File System Size The absolute minimum /usr file-system sizes needed to update to HP-UX 11.0 are: • For 32-bit: 300 MB. • For 64-bit: 324 MB. If the required file-system size for the bundle you copy to a depot exceeds that file system limit set by your disk installation, you will get an error condition during the copy process. You can use lvextend and extendfs in this situation to create a larger file system.
Troubleshooting Adjusting File System Size PE Size (Mbytes) Total PE Alloc PE Free PE Total PVG 4 249 170 79 0 The "Free PE" indicates the number of 4 MB extents available, in this case this is 79 (equivalent to 316 MB). 2. Enter the following: /sbin/shutdown Change to single user state. This will allow /var to be unmounted. 3.
Troubleshooting Large Systems Large Systems If you are running a system with a large number of file systems, note the following possible problem areas: 1. On a large system such as a T500 with a very large number of disk drives (such as 50 or more), you may see messages such as the following, during the system analysis phase of cold install. Out of inode- can't link or find disk or Write failed, file system is full. or File system full. 2.
Troubleshooting Large Systems • By raising maxusers to a large value, such as 200. • By selecting an appropriate bundle of SAM-tuned parameters from the SAM Kernel Configuration Actions menu. You should determine the correct configuration for your system. Note that this problem does not appear to affect the Upgrade process (updating from HP-UX 9.0x), since during Upgrade, the new kernel parameters are derived from the previous kernel.
Configuring for a DHCP Server A Configuring for a DHCP Server Appendix A 203
Configuring for a DHCP Server Appendix Contents Appendix Contents • Using DHCP Services: Overview. • Setting Up a DHCP Server. • Details on the DHCP Services. • Enabling DHCP on a System Not Initially Configured with DHCP. • Examples of DHCP Usage. • Using bootptab as an Alternative to DHCP. • Background Information on DHCP Design.
Configuring for a DHCP Server Introduction Introduction The HP-UX 10.20 version of HPUX and Ignite-UX supports retrieving network information via the Dynamic Host Configuration Protocol (DHCP). This appendix gives the details of setting up DHCP. The Ignite-UX GUI allows for setting up DHCP for use during system installation. This Appendix is for the user who wishes to use DHCP for ongoing IP address management, as well as for system installation.
Configuring for a DHCP Server Using DHCP Services: Overview Using DHCP Services: Overview DHCP provides the following features: • Allows for dynamically allocating IP addresses and hostnames. • Automatically supplies most of the networking defaults that are requested during a system installation or first time boot. • Provides for on-going IP address maintenance via a concept of an "IP address lease".
Configuring for a DHCP Server Using DHCP Services: Overview An alternative to using DHCP is to create /etc/bootptab entries for each specific client on the network. This allows for specific IP address mappings and greater control. For more detail, please see the section in this Appendix , “Using bootptab as an Alternative to DHCP,” at the end of this chapter.
Configuring for a DHCP Server Setting Up a DHCP Server Setting Up a DHCP Server Once you have decided that using DHCP will provide a benefit, you will need to follow the steps below to set up a DHCP server. Note that only one DHCP server per network subnet is required. On the server system: 1. Allocate a set of currently unused IP addresses (preferably a contiguous block of addresses). For example: 15.1.48.50 - 15.1.48.80 2. Pre-assign and register hostnames to the IP address allocated above.
Configuring for a DHCP Server Setting Up a DHCP Server f. Now you will need to fill in the information on this screen. Some information may require additional research if you are not familiar with the terms or with your network. Group Name: Subnet Address: Subnet Mask: Subnet Address Pool: Allow Any Device Class: Appendix A This can be any name that isn't already defined as a DHCP group. For example: group1 This is the portion of an IP address that is not masked off by the subnet mask (see below).
Configuring for a DHCP Server Setting Up a DHCP Server If you want this range of addresses to be used only by HP-UX systems, then unselect this button, and enter the text: "HewlettPackard.HP-UX" in the text field provided. When using Ignite-UX to set up DHCP, it will set a class specific to the server, and will set the dhcp_class_id string to match. For more detail, see the instl_adm(4) man page. Automatic Allocation to Bootp Clients: Accept New Clients: Address Lease Time: Leave this option disabled.
Configuring for a DHCP Server Setting Up a DHCP Server Callback Routines: None is necessary. g. Once the parameters are all filled in, then press OK on the Add DHCP Group screen. SAM will then make the modifications to the /etc/dhcptab file. h. You will now want to use the Action menu to Enable boot Server (if it is not already enabled). 5. Now, new systems that are installed with HP-UX 10.20 (or newer) or booted with a pre-installed 10.
Configuring for a DHCP Server Setting Up a DHCP Server • When a system boots for the first time (either after a Cold Install, or the first boot of a pre-loaded (Instant Ignition) system): The auto_parms tool, that lets you configure the system identity and basic configuration parameters, will invoke the dhcpclient, which will broadcast out to find a DHCP server. The server, in turn, provides a default set of networking parameters.
Configuring for a DHCP Server Setting Up a DHCP Server d. Highlight the card you wish to enable DHCP on, go to the Actions pull-down menu and select Configure. e. Single click the Enable DHCP button. NOTE If Enable DHCP appears grayed-out, you will need to use the alternate method for enabling DHCP described below. f. Single click OK and exit SAM. Your system will now begin using DHCP after the next reboot.
Configuring for a DHCP Server Setting Up a DHCP Server In this case, you will need to add the variable definition to a specific interface variable block. As an example, you would need to add DHCP_ENABLE[2]=1 to the following interface variable block in order to enable DHCP on the lan1 interface: INTERFACE_NAME[2]=lan1 IP_ADDRESS[2]=15.1.50.89 SUBNET_MASK[2]=255.255.248.0 BROADCAST_ADDRESS[2]="" The contents of /etc/rc.config.
Configuring for a DHCP Server Setting Up a DHCP Server b. Use a unique dhcp_class_id in both the dhcptab and the 8K config file. This dhpc_class_id could have the server's hostname init. In this case, enter the following in INSTALLFS: is_network_info_temporary=true c. And enter your class i.d. as the following in the dhcptab and INSTALLFS: dhcp_class_id 3.
Configuring for a DHCP Server Setting Up a DHCP Server If you also specify a boot-file (bf) of /opt/ignite/boot/boot_lif in the bootptab entries, then you do not need any additional entries in /etc/opt/ignite/inst_boottab. In this case, you would then boot the clients using boot lan instead of boot lan install. Only clients known in /etc/bootptab would be able to boot if you do not use instl_boottab.
Configuring for a DHCP Server Setting Up a DHCP Server More information on DHCP in general can be found in the following locations: • Man pages: bootpd(1m) dhcptools(1M) auto_parms(1M) dhcpdb2conf(1M) • Worldwide Web information site: http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.
Configuring for a DHCP Server Setting Up a DHCP Server 218 Appendix A
Using Configuration Files B Using Configuration Files Appendix B 219
Using Configuration Files Appendix Contents Appendix Contents • Types of Config Files. • Combining Config Files via INDEX Entries.
Using Configuration Files Introduction Introduction The Ignite-UX central data store is called a config file. A config file can be thought of as a recipe for how to construct a target system. The config file is expressed in a language designed for this purpose. The language is fully defined in the instl_adm(4) manual page. The syntax is human-readable; config files may be created directly by a user or via the Ignite-UX graphical user interface.
Using Configuration Files Types of Config Files Types of Config Files For maintenance convenience, the configuration information is split into several different config files. These config files fall into the following basic classes: • Default disk and file system layout. Because the capabilities of each operating system release differ somewhat, HP supplies a different set of defaults for each release.
Using Configuration Files Types of Config Files It is possible to specify defaults for attributes like the IP address of the Ignite-UX server and whether to run a UI to install a new target. These can be specified in the first 8 KB of the install file system (/opt/ignite/boot/INSTALLFS). This information is added or deleted with the instl_adm(1m) command. • Client-specific configuration files.
Using Configuration Files Combining Config Files Via INDEX Entries Combining Config Files Via INDEX Entries The grouping of config files into useful configurations is accomplished in the INDEX file (/var/opt/ignite/ INDEX). This file contains a list of valid configurations, each of which is made up of one or more config files. The list of these configurations is presented in the UI as the basic starting point. For example, the INDEX file might contain the following: cfg "HP-UX B.10.
Using Configuration Files Combining Config Files Via INDEX Entries in the first 8 KB of /opt/ignite/boot/INSTALLFS is implicitly appended to each configuration. The client-specific configuration file (/var/opt/ignite/clients/0x{LLA}/config) is implicitly added as the last config file for each configuration. A default cfg clause for each release is shipped as part of the Ignite-UX product.
Using Configuration Files Combining Config Files Via INDEX Entries physical_volume disk[2/0/1.4.0] { } logical_volume "apps1" { mount_point= "/apps1" usage=VxFS size=30%free minfree=5 stripes=2 } logical_volume "apps2" { mount_point= "/apps2" usage=VxFS size=remaining minfree=5 stripes=2 } } This example defines a few of the network parameters which will be assigned to the machine after it has been installed: final system_name = "acorn1" final ip_addr["lan0"] = "15.99.45.123" final netmask["lan0"] = "255.
Using Configuration Files Combining Config Files Via INDEX Entries sw_category = "Applications" sd_software_list = "EERoute,r=2.4,a=HP-UX_B.10.
Using Configuration Files Combining Config Files Via INDEX Entries 228 Appendix B
Ignite-UX System Administration C Ignite-UX System Administration Appendix C 229
Ignite-UX System Administration Appendix Contents Appendix Contents • Section 1: Installation of Ignite-UX Server Software. • Section 2: The Install Archive. • Section 3: Automatic Installation. • Section 4: Customization. • Section 5: Post-Install Scripts. • Section 6: Using Ignite-UX Across Gateways. • Section 7: Steps to Create A “Golden System”. • Section 8: Loading HP-UX Patches Using Ignite-UX. • Section 9: Setting Install Parameters Dynamically.
Ignite-UX System Administration Section 1: Installation of Ignite-UX Server Software Section 1: Installation of Ignite-UX Server Software NOTE Ignite-UX is a replacement for the Net-Install product.
Ignite-UX System Administration Section 1: Installation of Ignite-UX Server Software Load the Ignite-UX software You should load one or more Ignite-UX release versions. They are organized as bundles corresponding to the release that you wish to load on your target systems. For example, if you wish to load HP-UX 10.20 onto systems you should load the Ignite-UX-10-20 bundle. You can multiple releases if desired To load this software use the swinstall command. For example to load Ignite-UX to load HP-UX 10.
Ignite-UX System Administration Section 1: Installation of Ignite-UX Server Software If you get the following error message: ERROR: This machine is not an NFS server (no nfsd running). The -n option will not be processed. you did not follow the installation instructions properly. The Ignite-UX server must be an NFS server. Exit Ignite-UX, and make the Ignite-UX server an NFS server before continuing. You can do this by using “sam”, or by editing /etc/rc.config.
Ignite-UX System Administration Section 1: Installation of Ignite-UX Server Software 15.2.73.1 15.2.73.20 Step 2.2.2) Permanent IP addresses are distributed via DHCP Services. DHCP Address ranges to use for remainder of installation. Unless you are familiar with DHCP services, for this exercise, do not modify the DHCP Class ID, or the DHCP Addresses are temporary field. Provide a range of available “permanent” IP address. These can only be supplied once here in Ignite-UX.
Ignite-UX System Administration Section 1: Installation of Ignite-UX Server Software You may wish to de-select the “Ask for customer information” checkbox, as this installation information is more geared to HP and HP distributor-partner manufacturing. Step 3) Starting the Installation Process There is nothing that needs to be done to the target system to allow it to use Ignite-UX. If the target system is currently running any version of HP-UX 9.x, 10.
Ignite-UX System Administration Section 2: The Install Archive Section 2: The Install Archive This section will cover the following topics: • Creating an OS Archive (golden image). • Configuring Ignite-UX to recognize the OS archive. • Using Ignite-UX “ignite” tools to install to a target. In this test scenario, we will create a “golden image”, or OS archive, which is a snapshot of a known good installation which we want to copy to other systems.
Ignite-UX System Administration Section 2: The Install Archive Ignite-UX is capable of installing systems from SD depots as well as archives. You may want to use this capability when setting up your “golden system” since you will need to have a system installed somehow before you can get an image. See a later section for details. The make_sys_image command is provided to assist in creating the OS archive. Refer to the make_sys_image(1m) man page for details.
Ignite-UX System Administration Section 2: The Install Archive On the Ignite-UX server, create an archives directory to store the golden image. It is best to keep the naming conventions Rel_B.11.00 (or whatever your release is). This directory will need to be NFS exported if you’ll be using NFS to transfer the archive to the target. # mkdir /var/opt/ignite/archives # mkdir /var/opt/ignite/archives/Rel_B.11.00 Step 1.4: Move the OS archive to /var/opt/ignite/archives/Rel_B.11.00/hpfcnjm2.
Ignite-UX System Administration Section 2: The Install Archive (This points to directory where the archive lives, must be NFS exported) • In the “init sw_sel” clause, change the following: description = “Archive HP-UX 11.00 CDE” (This will now appear in the Environments section of the Ignite-UX user-interface as a menu choice). • archive_path = “hpfcnjm2.gz” (This points to the actual file in combination with the nfs_source line).
Ignite-UX System Administration Section 2: The Install Archive init sw_sel “golden image” { description = “Archive HP-UX 11.00 CDE” sw_source = “core archive” sw_category = “HPUXEnvironments” archive_type = gzip tar # For NFS, the path to the archive is relative to the mount # point specified in the sw_source: archive_path = “hpfcnjm2.gz” # ftp/remsh sources can use a full path: # archive_path = “/pub/IUXarchives/B.11.00_700_CDE.gz” impacts = “/” 23Kb impacts = “/.
Ignite-UX System Administration Section 2: The Install Archive Note that “/var/opt/ignite/config.local” should be last. The last config file has the highest priority to override values in prior config files. The file “/opt/ignite/data/Rel_B.11.00/config” supplies the disk and file-system layout defaults, plus other control information required by Ignite-UX. It must be first in every cfg clause. Each “cfg” clause appears as an available configuration to Ignite-UX. Therefore, the string “HP-UX B.11.
Ignite-UX System Administration Section 2: The Install Archive This will cause the target system to boot a copy of the Ignite-UX kernel and file system that bootsys copies to the target. An icon representing the system will appear in the Ignite-UX user interface on the server when the system has completed boot. (This may take several minutes.) Only booted clients will appear as icons.
Ignite-UX System Administration Section 2: The Install Archive Select “Actions->Install Client->New Install” You should now see the Ignite-UX screen with five tabs across the top. (If you see the “System Hardware Inventory” screen simply select OK to bypass this screen). Step 4.3: In the Basic tab (default): Under “Configurations:” select “HP-UX B.11.00 archive”. Ensure the Root Disk, Root Swap and other fields are correct for your installation.
Ignite-UX System Administration Section 2: The Install Archive When finished entering data, select “Go!” A configuration dialog will appear. Make sure the data is correct, and select “Go!” again. Step 4.9: Displaying target installation status If you double-click on the icon of the target system in the Ignite-UX server GUI during execution, a status screen will be displayed showing the install progress.
Ignite-UX System Administration Section 3: Automatic Installation Section 3: Automatic Installation Setting up your Ignite-UX server so that the default configuration is correct for any given system will save you time and allow you to easily automate installations. This section discusses setting up the defaults the way you like them, as well as setting up a configuration for a specific target system.
Ignite-UX System Administration Section 3: Automatic Installation Using a “Saved” configuration: When using the ignite GUI on the server, during an install session when you are finished with specifying the configuration for particular target, you may choose to save the result as a named configuration. This will save any changes that you made during the session. You can then either specify the configuration as the default, and/or just use the name you give it to the bootsys command using the -i option.
Ignite-UX System Administration Section 3: Automatic Installation Defaults that must be specified with instl_adm(1M): There are some network parameters that need to be known by the target clients when they first boot. The command bootsys (or DHCP/BOOTP) can supply the hostname and IP address; however, the netmask and gateway need to be supplied in the ram-filesystem (INSTALLFS). This can done by using the instl_adm(1m) command.
Ignite-UX System Administration Section 3: Automatic Installation The easiest way to create the “config” file is to use one already built by IUX. If you’ve previously installed a system (it’s best to use one from a similar system to your target,) you can find a config file in the /var/opt/ignite/clients/history/ directories. Use this as the basis for your new file. Copy it to the following: /var/opt/ignite/clients//config Edit its contents to correspond to your new system.
Ignite-UX System Administration Section 3: Automatic Installation final netmask[“lan0”]=”255.255.248.0” final dns_domain=”fc.hp.com” final dns_nameserver[0]=”15.2.72.254” TIMEZONE=”MST7MDT” is_net_info_temporary=TRUE } # end “Current System Parameters” Typically, you would want to change the networking parameters to the correct values. For example: final system_name=”system11” final ip_addr[“lan0”]=”15.2.75.
Ignite-UX System Administration Section 3: Automatic Installation The target system should boot into the IUX install process and complete the install automatically. Errors will be reported on the client screen and in the install.log file. NOTES If you are attempting to install 10.x onto a system running an HP-UX 9.
Ignite-UX System Administration Section 4: Customization Section 4: Customization This section will focus on ways to customize the default configuration, either by adding additional info to the default config (dynamic parameters) or by adding additional software selections to be loaded after the archive. We’ll be adding the following: • SD Bundles • Kernel parameters • Additional install parameters, e.g.
Ignite-UX System Administration Section 4: Customization This creates the patch_bundle_cfg file which IUX needs to manage the install from the depot. 2. Add the new config file name (the argument to -c above) to the /var/opt/ignite/INDEX file so that it appears in our “HP-UX B.11.00 archive” configuration. We created this configuration in Section 2. cfg “HP-UX B.11.00 archive” { description “The ARCHIVE B.11.00 release with patches.” “/opt/ignite/data/Rel_B.11.00/config” “/var/opt/ignite/data/Rel_B.11.
Ignite-UX System Administration Section 4: Customization 1. In the new file /var/opt/ignite/data/Rel_B.11.00/kernel_cfg add the following: (Note that, in lieu of “HPUXAdditions”, you could designate your own category). HARDWARE_MODEL ~ “9000/7.*” { sw_sel “My_Kernel_Mods” { description = “Kernel parameters only” sw_source = “cmds” sw_category = “HPUXAdditions” mod_kernel += “nproc 2000” mod_kernel += “maxuprc 127” load_with_any = “golden image” } } 2.
Ignite-UX System Administration Section 4: Customization In this example, there is a set of parameters we want all systems to have, “Basic_Kernel_Mods”. These are force loaded. There is also an optional set, “Advanced_Kernel_Mods”, which can be selected in the UI or in a config file at install time. The contents of the /var/opt/ignite/data/Rel_B.11.00/kernel_cfg file is now: HARDWARE_MODEL ~ “9000/7.
Ignite-UX System Administration Section 4: Customization Additional Install Parameters There are a large number of additional parameters which can be set when we install a system. These are listed in the instl_adm(4) man page. As a simple example, we may want to set the swap space of all machines we install using the “golden image” archive to 100 MB. The “golden image” is defined in the following file /var/opt/ignite/data/Rel_B.11.00/core_700_archive_cfg. 1.
Ignite-UX System Administration Section 5: Post Install Scripts Section 5: Post Install Scripts Any number of tasks may be performed on the target system after the OS is installed by providing a script to be run on the target system. This section touches on some common examples, but scripts can easily be written to mount additional disk drives, add additional software, modify configurations based on system use, etc.
Ignite-UX System Administration Section 5: Post Install Scripts It will then show up in the Advanced tab for all configurations. NOTE Scripts are accessed by Ignite-UX via tftp. Make sure the directory the script resides in is available to tftp by examining and/or changing the /etc/inetd.conf file. 2. Managing Network Printers One task an administrator generally needs to perform after a new OS installation is setting up printers. Here is one method you can use to automate this process.
Ignite-UX System Administration Section 6: Using Ignite-UX Across Gateways Section 6: Using Ignite-UX Across Gateways A system that is running 9.x or 10.x can use the Ignite-UX server across a gateway if the target system is booted via the bootsys command. If the system is booted manually, it will need a helper system to help it boot across a gateway, and enabling the target system to perform a “boot lan. install” to the local boot helper system.
Ignite-UX System Administration Section 6: Using Ignite-UX Across Gateways 15.1.53.180 15.1.53.181 15.1.53.182 Step 4: Reboot the target system, interrupt the boot sequence by pressing , and type the following: > boot lan. install How to Set Up a 9.0x System as a Boot Helper Essentially, the 9.05 helper machine, on the same subnet as the install target machine(s), hosts the files necessary for network boot of the target.
Ignite-UX System Administration Section 6: Using Ignite-UX Across Gateways On the install server (on one side of the gateway): 1. cd /opt/ignite/boot You can make the changes to the actual boot files in this directory, or copy INSTALLFS to another file and make changes to that file by adding a -F option spec to the instl_adm calls below. The rest of this section assumes you just use the “real” version. These changes aren’t very extensive, so this should be acceptable. 2. Run: instl_adm > fs_cfg 3.
Ignite-UX System Administration Section 6: Using Ignite-UX Across Gateways system_name will cause set_parms not to run, so all other needed system info (timezone, routes, etc.) should probably be set along with system_name. 5. Run: instl_adm -f fs_cfg This applies the changes to the INSTALLFS file. 6. Copy /opt/ignite/boot/* files to the 9.05 boot helper’s /opt/ignite/boot directory. NOTE Any further changes MUST be done on the server system and copied over to the helper system. The 9.
Ignite-UX System Administration Section 7: Steps to Create a “Golden System” Section 7: Steps to Create a “Golden System” Section 2 discusses creating an archive-image of your golden system. We’ll cover the steps for creating the golden system itself here. In general, the golden system is simply a system which has been configured with all the software and customizations which will need to be distributed to a group of target systems.
Ignite-UX System Administration Section 7: Steps to Create a “Golden System” On the IUX server, set up the core software to be distributed: # make_depots -r B.11.00 -a 700 -s \ hpfclc:/release/S700_11.00/B3782EA # /opt/ignite/bin/make_config -r B.11.00 The make_depots command will copy the release B.11.00 software at the SD depot pointed to by the “-s” option (this pathname will depend on the setup of the SD depot you are accessing) onto the local Ignite-UX server.
Ignite-UX System Administration Section 7: Steps to Create a “Golden System” Step 3: Load Optional Software Load any optional HP and third-party software you want to make available to ALL users. Keep in mind that we are creating a golden system, and anything put on this will be distributed to all systems installed using the golden image. You’ll need to keep in mind licensing restrictions, as well. HP software (such as compilers) are normally loaded using SD from media or a network SD depot.
Ignite-UX System Administration Section 8: Loading HP-UX Patches Using Ignite-UX Section 8: Loading HP-UX Patches Using Ignite-UX Ignite-UX can use an existing Software Distributor (SD) depot to distribute additional software. This depot can be managed separately from Ignite-UX. In this example we’ll create a patch depot containing HP-UX Patches, create a single patch bundle of the contents of the depot, and then add this bundle to an existing Ignite-UX configuration.
Ignite-UX System Administration Section 8: Loading HP-UX Patches Using Ignite-UX Creating a Patch Depot 1. Create a Patch Depot: Obtain the set of patches you want to place and manage in an SD depot. For example: PHCO_7891 PHCO_9348 PHKL_9361 PHSS_7726 PHSS_8966 PHSS_9400 PHCO_8353 PHKL_8376 PHKL_9569 PHSS_8667 PHSS_9201 HP patches as delivered by the Response Center or the HP Web site are shar files consisting of a product depot and README file. 2. Unshar the patches: # for i in PH* do sh $i done 3.
Ignite-UX System Administration Section 8: Loading HP-UX Patches Using Ignite-UX # PHCO_7891 B.10.00.00.AA allows mount to turnon hfs-specific opts PHCO_8353 B.10.00.00.AA cumulative awk(1) patch PHCO_9348 B.10.00.00.AA cron(1M) and at(1) patch PHKL_8376 B.10.00.00.AA Fix vmtrace bug. PHKL_9361 B.10.00.00.AA Fix panic caused by MP race PHKL_9569 B.10.00.00.AA NFS and VxFS (JFS) cumulative patch PHSS_7726 B.10.00.00.AA CDE Dtterm August 96 patch PHSS_8667 B.10.00.00.AA CDE Runtime Nov96 Patch PHSS_8966 B.10.
Ignite-UX System Administration Section 8: Loading HP-UX Patches Using Ignite-UX The default behavior of swlist is to now show only the higher level software bundles. Individual patches in the bundle can still be viewed by using swlist options.
Ignite-UX System Administration Section 8: Loading HP-UX Patches Using Ignite-UX We created this file with the make_config command file previously.
Ignite-UX System Administration Section 9: Setting Install Parameters Dynamically Section 9: Setting Install Parameters Dynamically Ignite-UX can make intelligent decisions about install parameters when it runs, based on information it reads from the target system. Instead of forcing static values for, say, swap size or kernel parameters, the best values for these can be determined based on the characteristics of the target machine.
Ignite-UX System Administration Section 9: Setting Install Parameters Dynamically This could also be added to the “config” file created for automatic installs (see Section 4). Note that if the “_hp_pri_swap” parameter is set later in the order of files searched in the “cfg” definition, this setting will be overwritten. The order the files are evaluated is documented in the instl_adm(4) man page. Also be aware that the config file used for automatic installs is overwritten as part of the install process.
Ignite-UX System Administration Section 9: Setting Install Parameters Dynamically { cfg “small system configuration” = true } To check the syntax of all configuration files that are listed in the /var/opt/ignite/INDEX file you can use the command: # instl_adm -T If you want to check the syntax of a file that is not yet in the INDEX file, you can use the command: # instl_adm -T -f 272 Appendix C
Ignite-UX System Administration Section 10: Installing NetScape as a Post-Configuration Step Section 10: Installing NetScape as a Post-Configuration Step Here is a little more complicated example of using Ignite-UX post installation scripts to load software on new installs. Netscape is one of those tools which seems to have a new navigator every six months. Due to the frequency of the changes, this tool may not make sense to include on the “golden system”.
Ignite-UX System Administration Section 10: Installing NetScape as a Post-Configuration Step * Attached below we have supplied a sample “run-netscape”. * You will also need to create a default configuration file. Merely take an existing one and remove all user and host specific information. Step 2) Write an install and customization script Attached below is a script we used for installing Netscape in our environment.
Ignite-UX System Administration Section 10: Installing NetScape as a Post-Configuration Step echo “* Loading Netscape” mkdir ${NETSCAPE_INSTALL_DIR} cd ${NETSCAPE_INSTALL_DIR} rcp ${IUX_SERVER}:${IUX_ARCHIVE_DIR}/${NETSCAPE_GZIP} ${NETSCAPE_GZIP} rcp ${IUX_SERVER}:${IUX_ARCHIVE_DIR}/run-netscape . rcp ${IUX_SERVER}:${IUX_ARCHIVE_DIR}/default-preferences .
Ignite-UX System Administration Section 10: Installing NetScape as a Post-Configuration Step 276 Appendix C
Index Numerics 11.0, updating to, 50 64-bit hardware support table, 32 updating to, 31 A add_release, 89 adding server software add_release, 89 additional network interfaces, 126 AdvJournalFS.VXFS-ADVKRN, 53 AdvJournalFS.
Index HP OnlineJFS features, 53 installing, 53 HP-UX selecting OS environment, 112 HP-UX Extension Software, 51 I Ignite-UX errors, 186, 202 hardware requirements, 84, 85 interface, 101, 141 products and filesets, 84 RAM requirement, 84, 85 install (pre-configured) Go!, 116, 139 CD names, 57 client, 74 default values, 75 Extension Software, 51 media list, 57 server,searching for, 103 single system, 74 stand-alone, 74 tape names, 57 time,install kernel load, 61 time,kernel load, 64, 106 using defaults, 116
Index order of loading, 118 patches, loading, 265 patches, removing prior patch inlo.
Index V V-class booting, 65 firmware revision, 38 versions for updates, 21 volume group name changing, 136 VUE-to-CDE migration, 48 VxFS adding functionality, 53 file systems, 86, 113 OnlineJFS, 53 X XNTP configuring, 126 280 Index
