Ignite-UX Quick Start Guide Create an Ignite-UX Server and Cold-Install Clients HP Part Number: 5992-5230 Published: September 2008 Edition: 4
© Copyright 2007, 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.........................................................................................................5 Intended Audience.................................................................................................................................5 Typographic Conventions......................................................................................................................5 Related Information..........................................................
About This Document This document describes the most common procedure for setting up an Ignite-UX server, adding a client to the Ignite-UX server, and cold-installing HP-UX on that client. Glossary terms are italicized when used for the first time in this manual. Intended Audience This document is intended for system and network administrators with minimal experience installing, configuring, and managing HP-UX.
• • • • • • • HP-UX System Administrator’s Guide Managing Systems and Workgroups: A Guide for HP-UX System Administrators Software Distributor Administration Guide HP-UX Patch Management nPartition Administrator's Guide Getting Started with Software Package Builder VERITAS File System 4.1 (HP OnlineJFS/JFS) and VERITAS Volume Manager 4.1 Installation Guide Some or all of these documents are available on the Instant Information media and in printed form.
1 Setting up an Ignite-UX Server This chapter describes setting up an Ignite-UX server to cold install HP-UX 11i v1, v2, and v3 on clients over the network. You must have superuser privileges to set up an Ignite-UX server. You can stop anywhere in this procedure and resume where you left off at a later time. This document assumes the network boot clients are on the same subnet as the Ignite-UX server. This document also assumes the network DHCP and DNS servers are already set up.
Detection: The number of kbytes free on /opt is less than 2000000. Diagnosis: Not enough space. Correction: Extend the size of the logical volume with the lvextend command, and then extend the size of the file system within the logical volume with the extendfs command. Detailed instructions for this procedure are found in the HP-UX administration guides listed below, depending on your version of HP-UX. For HP-UX 11i v3, see the HP-UX System Administrator's Guide (volume 3): Logical Volume Management.
Consider creating a new file system for /var/opt/ignite. This could keep Ignite-UX from impacting other applications using /var if it fills /var/opt/ignite with depots and archives. Detailed instructions for this procedure are found in the HP-UX administration guides listed below, depending on your version of HP-UX. If you do create a file system for /var/opt/ignite, then you will see it in the bdf listing and will be able to manage your disk space to a greater level of detail.
The ioscan command lists no devices. Diagnosis: If the system is running HP-UX 11i v3, the system might have legacy mode disabled. To find out, issue the following command. # insf -Lv Correction: If legacy mode is disabled, issue the following command to get the DVD-ROM device name (add an “N” to the ioscan command options). Do not enable legacy mode without talking to the system administrator responsible for the Ignite-UX server.
3. Install the Ignite-UX software using swinstall if the Ignite-UX version on the DVD is later than any currently installed version of Ignite-UX and the HP-UX version on the OE media matches the HP-UX version on the Ignite-UX server. Procedure # swinstall -s /dvdrom Ignite-UX Common Errors ERROR: Could not apply the software selection “Ignite-UX”; it is not available from depot or root “server_name:/dvdrom”. Diagnosis: The DVD in the drive does not have Ignite-UX on it.
(substitute your release directory if it's different from 11.23). If the make_depots command returns quickly with no errors, the depot already exists on the system. Procedure Run the make_depots command below for all DVDs in the OE set. Remember to substitute your device file name and the appropriate release directory (Rel_B.11.xx) for your version of HP-UX. # /opt/ignite/bin/make_depots -s /dev/dsk/c1t2d0 \ -d /var/opt/ignite/depots/Rel_B.11.
ERROR: Depot depot_name does not exist. Diagnosis: The depot name was mistyped. Correction: Check the make_config command line for typos. Explore List the /var/opt/ignite/data/Rel_B.11.23 directory to see the core_media_cfg file just created with the make_config command. Configuration files are typically named after the depot, with a _cfg appended.
Configure the System as an Ignite-UX Server 1. NFS export the directory /var/opt/ignite/clients so you can control the installation process from the server and store configuration files and manifest information on the server. On successful completion of the setup_server command, the message Program completed successfully. will be displayed. If you wish, you may safely complete this section before “Create the HP-UX OE Configuration Information on the Ignite-UX Server” (page 12).
2 Cold-installing a Client Across the Network This chapter describes adding a client to an Ignite-UX server, and then installing HP-UX on that client from the Ignite-UX server over the network. You must have superuser privileges to cold-install a client. You can stop anywhere in this procedure and resume where you left off at later time. This document assumes the network boot clients are on the same subnet as the Ignite-UX server. Glossary terms are italicized when used for the first time in this manual.
Explore To get the MAC address for an Itanium-based system, select EFI Shell from the boot menu and then use the lanaddress command. Use the exit command to return to the boot menu.
To get the MAC address for a PA-RISC system, interrupt the boot process at the To discontinue, press any key within 10 seconds prompt. Enter the Information menu by typing in. Then enter LanAddress. If your client system is already running HP-UX, you can get the MAC address of the client by using the lanscan command. You may use any MAC address that is physically connected to the network.
Boot the Client System from the Ignite-UX Server This process is machine-dependent; follow the procedure for Intel® Itanium®-based or PA-RISC-based, depending on your system type. Procedure for Itanium®-based machines 1. Reboot the client system with the reboot command or cycle the power on the client system. Interrupt the reboot process by pressing the down arrow when prompted. 2. Select Boot Option Maintenance Menu.
3. Select Add a Boot Option 4. Select the network interface with the MAC address you entered in the /etc/bootptab file.
5. Enter a description of this boot option, n for the No BootOption data type, and y to the Save changes to NVRAM prompt. 6. Exit the Add a Boot Option menu.
7. Exit the Main Menu. 8. Select your new boot option from the Please select a boot option menu.
9. When prompted, enter the version of HP-UX you would like to install. Choose the operating system that matches the OE you used when you set up the Ignite-UX server –“Create the HP-UX OE Configuration Information on the Ignite-UX Server” (page 12). Note that this is a timed response and will default to the first selection. Common Errors TFTP PXE-E12: Could not detect network connection. Check cable.
Explore It's possible your system's EFI Boot Manager interface looks different from the screens above. The Legacy interface style is shown in the procedure above. On most systems you can change the interface style with the Boot Menu selection System Configuration. From there, select Change Boot Manager User Interface or Set User Interface depending on the current interface style. If you are currently using the Legacy style interface, you will have to select Exit to return to the Boot Manager menu.
Procedure for PA-RISC-based machines 1. Reboot the client system with the reboot command or by cycling the power, and then interrupt the reboot process when prompted. # reboot 2. Interrupt the boot process by pressing any key at the prompt Processor is starting autoboot process. To discontinue, press any key within 10 seconds. 3. From the firmware prompt, boot using the server's IP address: Main Menu: Enter command or menu >boot lan.server_IP_address install 4.
Install HP-UX from the Server Using the Client Console You will use the Ignite-UX terminal user interface (TUI) to install HP-UX. It will be displayed on the client console after the client successfully reboots. Move between menu buttons with the tab key and select by pressing enter. Help is available from the majority of these screens. 1. Select Install HP-UX from the welcome screen by pressing enter. Common Errors NOTE: The console firmware terminal type is currently set to “hp”.
3. If there is more than one network interface on the client system, you will be prompted to select the correct one for connecting to the server system. Select the LAN interface you entered in the server's /etc/bootptab or /etc/opt/ignite/instl_boottab file. 4. Ignite-UX then looks for networking information.
5. If a DHCP server is found, the NETWORK CONFIGURATION screen will contain the client's hostname and IP address. If there is networking configuration available for the server, it will be filled-in as well. Make sure the NETWORK CONFIGURATION parameters are set so the client system can contact the server. Then select OK.
Common Errors Failed to read “INDEX” file from the install server. Check that the install server's IP address is correct and the server has the “Ignite-UX” product loaded and is available via the tftp(1) service. Press any key to return to the network configuration menu: Diagnosis: The client can't find the Ignite-UX server. Correction: One possibility is that the wrong LAN was selected from the “LAN Interface Selection” menu above.
Common Errors Note: The currently selected configuration does not contain any environments. You may want to select another configuration. Diagnosis: The default configuration does not have an OE depot in it. Correction: This does not affect the configuration you created. Select the cfg clause you created as described above. 7. Configure your client's installation using the Ignite-UX itool TUI. Modify the fields of the configuration interface at your discretion.
b. c. d. Define the root password by selecting the Set Root Password... button. Set the time zone by selecting the Set Time Zone button. Set the DNS configuration information by selecting the Network Services... button on the System screen. Then select the DNS tab from the Network Services screen. e. 30 Once you select OK on the DNS tab, you will be returned to the itool. From there, select Go! to begin the cold install of the client.
CAUTION: A cold-install overwrites all data on the client disks selected for inclusion into any LVM volume group or VxVM disk group. 8. Make sure you read all the preinstall analysis information on the itool Confirmation screen. If you feel the cold install may proceed, select Go!. 9. After selecting Go!, the cold install will proceed. Status information is displayed on the client console as the installation progresses. The cold install of the client system is now complete.
Glossary Glossary terms are italicized when used for the first time in this manual and when used anywhere in the glossary. This is a standard glossary for Ignite-UX documentation – not all terms defined here appear in this guide. A add_new_client An Ignite-UX command that constructs a client directory on an Ignite-UX server without requiring the client to be booted from the Ignite-UX server first. See add_new_client(1M).
boot image Boot content, including [W|V|I]INSTALL, [W|V|I]INSTALLFS, INSTCMDS or INSTCMDSIA, and other content needed to support boot, formatted for a specific media type such as CD, DVD, or tape. bootsys An Ignite-UX command that allows you to reboot and install clients that are currently running HP-UX. See bootsys(1M). bundle A package of software available from Software Distributor. Bundles are distributed within depots and contain products and filesets.
D daemon A process that runs in the background and is usually immune to termination instructions. default-installed For HP-UX 11i v1 and 11i v2, software bundles that are installed as default with HP-UX. These bundles can be deselected before installation. depot A repository of software products, organized so Software Distributor (SD-UX) commands can use it as a software source. device identifier A user friendly, readable string, such as “LAB2CAB23LUN15”, that is stored on a device.
graphical user interface (GUI) A method of interacting with computers that employs metaphors such as windows and desktops and uses mouse-driven menus. gzip A command available with HP-UX that compresses and decompresses files in “.gz” format. See gzip(1). H HBA Stands for Host Bus Adaptor. A physical I/O interface that provides I/O processing and connectivity between a server and a storage device. hierarchical file system (HFS) A particular implementation of a file system. See mkfs_hfs(1M).
instl_dbg An Ignite-UX command that will parse and debug an Ignite-UX client’s configuration files. See instl_dbg(1M). ISL See initial system loader. ISO image An ISO9660 formatted file that is to be written to a CD or DVD. Used for a bit-for-bit burn of a CD or DVD. itool The name of an internal IUX program that presents the Ignite-UX client installation configuration user interface. This interface has five tabs: Basic, Software, System, File System, and Advanced.
M MAC address Stands for Media Access Control. A network card’s unique hardware number. Used to uniquely identify a network interface connected to a local area network. make_[tape|net]_recovery Collectively refers to the make_tape_recovery and make_net_recovery Ignite-UX commands. make_boot_tape An Ignite-UX command that creates a bootable tape that contains just enough information for a system to boot and connect to an Ignite-UX server. See make_boot_tape(1M).
optional With 11i v3, software bundles that are not installed with HP-UX by default. You must select these bundles before installation. Ignite-UX is an example of an optional software bundle. P partition A portion of a disk device that appears to volume managers, file systems, and other OS software as a disk device. Partitions allow different portions of a disk to hold content needed for boot, OS file systems, diagnostic tools, and other information.
S save_config An Ignite-UX command that creates a hardware configuration file. It extracts disk and file system information along with certain system and networking parameters for the current system, and writes it to a configuration file. See save_config(1M). script hook Predefined mechanisms allowing user-defined scripts to run at specific points during the execution of the installation.
U Unique LUN ID A general term for a LUN identifier, which might specifically be a physical disk's WWID, a WWID assigned to a SAN virtual LUN, the uniq_name assigned to a LUN for which a WWID could not be obtained, or some other type of identifier unique to a LUN. V Veritas A set of products from Symantec that include VxVM and VxFS. VINSTALL The installation kernel for V-class PA-RISC systems. VINSTALLFS The associated file system for the VINSTALL kernel.
