Chapter 13. Booting the installation media After you have created bootable media you are ready to boot the Red Hat Enterprise Linux installation. You can register RHEL using the Red Hat Content Delivery Network (CDN). CDN is a geographically distributed series of web servers. These servers provide, for example, packages and updates to RHEL hosts with a valid subscription. During the installation, registering and installing RHEL from the CDN offers following benefits: Utilizing the latest packages for an up-to-date system immediately after installation and Integrated support for connecting to Red Hat Insights and enabling System Purpose. 13.1. Booting the installation from a network using HTTP When installing Red Hat Enterprise Linux on a large number of systems simultaneously, the best approach is to boot and install from a server on the local network. Follow the steps in this procedure to boot the Red Hat Enterprise Linux installation from a network using HTTP. Important To boot the installation process from a network, you must use a physical network connection, for example, Ethernet. You cannot boot the installation process with a wireless connection. Prerequisites You have configured an HTTP boot server, and there is a network interface in your system. See Additional resources for more information. You have configured your system to boot from the network interface. This option is in the UEFI, and can be labeled Network Boot or Boot Services . You have verified that the UEFI is configured to boot from the specified network interface and supports the HTTP boot standard. For more information, see your hardware's documentation. Your platform is x86_64 or you install in KVM. Procedure Verify that the network cable is attached. The link indicator light on the network socket should be lit, even if the computer is not switched on. Turn on the system. Depending on your hardware, some network setup and diagnostic information can be displayed before your system connects to an HTTP boot server. When connected, a menu is displayed according to the HTTP boot server configuration. Press the number key that corresponds to the option that you require. Note In some instances, boot options are not displayed. If this occurs, press the Enter key on your keyboard or wait until the boot window opens. The Red Hat Enterprise Linux boot window opens and displays information about a variety of available boot options. Use the arrow keys on your keyboard to select the boot option that you require, and press Enter to select the boot option. The Welcome to Red Hat Enterprise Linux window opens and you can install Red Hat Enterprise Linux using the graphical user interface. The installation program automatically begins if no action is performed in the boot window within 60 seconds. Optional: Edit the available boot options. Press E to enter edit mode. Change the predefined command line to add or remove boot options. Press Enter to confirm your choice. Additional Resources Automatically installing RHEL Boot options reference 13.2. Booting the installation from a network using PXE When installing Red Hat Enterprise Linux on a large number of systems simultaneously, the best approach is to boot and install from a server on the local network. Follow the steps in this procedure to boot the Red Hat Enterprise Linux installation from a network using PXE. Important To boot the installation process from a network, you must use a physical network connection, for example, Ethernet. You cannot boot the installation process with a wireless connection. Prerequisites You have configured a TFTP server, and there is a network interface in your system that supports PXE. See Additional resources for more information. You have configured your system to boot from the network interface. This option is in the BIOS, and can be labeled Network Boot or Boot Services . You have verified that the BIOS is configured to boot from the specified network interface and supports the PXE standard. For more information, see your hardware's documentation. Your platform is x86_64 or you install in KVM. Note On the ARM platform on KVM, booting in the Preboot Execution Environment (PXE) is functional but not supported, Red Hat strongly discourages using it in the production environments. If you require PXE booting, it is only possible with the virtio-net-pci network interface controller (NIC). Procedure Verify that the network cable is attached. The link indicator light on the network socket should be lit, even if the computer is not switched on. Switch on the system. Depending on your hardware, some network setup and diagnostic information can be displayed before your system connects to a PXE server. When connected, a menu is displayed according to the PXE server configuration. Press the number key that corresponds to the option that you require. Note In some instances, boot options are not displayed. If this occurs, press the Enter key on your keyboard or wait until the boot window opens. The Red Hat Enterprise Linux boot window opens and displays information about a variety of available boot options. Use the arrow keys on your keyboard to select the boot option that you require, and press Enter to select the boot option. The Welcome to Red Hat Enterprise Linux window opens and you can install Red Hat Enterprise Linux using the graphical user interface. The installation program automatically begins if no action is performed in the boot window within 60 seconds. Optional: Edit the available boot options: UEFI-based systems Press E to enter edit mode. Change the predefined command line to add or remove boot options. Press Enter to confirm your choice. BIOS-based systems Press the Tab key on your keyboard to enter edit mode. Change the predefined command line to add or remove boot options. Press Enter to confirm your choice. Additional Resources * Automatically installing RHEL Boot options reference 13.3. Booting the installation on IBM Z to install RHEL in an LPAR 13.3.1. Booting the RHEL installation from an SFTP, FTPS, or FTP server to install in an IBM Z LPAR You can install RHEL into an LPAR by using an SFTP, FTPS, or FTP server. Procedure Log in on the IBM Z Hardware Management Console (HMC) or the Support Element (SE) as a user with sufficient privileges to install a new operating system to an LPAR. On the Systems tab, select the mainframe you want to work with, then on the Partitions tab select the LPAR to which you wish to install. At the bottom of the screen, under Daily , find Operating System Messages . Double-click Operating System Messages to show the text console on which Linux boot messages will appear. Double-click Load from Removable Media or Server . In the dialog box that follows, select SFTP/FTPS/FTP Server , and enter the following information: Host Computer - Host name or IP address of the FTP server you want to install from, for example ftp.redhat.com User ID - Your user name on the FTP server. Or, specify anonymous. Password - Your password. Use your email address if you are logging in as anonymous. File location (optional) - Directory on the FTP server holding the Red Hat Enterprise Linux for IBM Z, for example /rhel/s390x/ . Click Continue . In the dialog that follows, keep the default selection of generic.ins and click Continue . 13.3.2. Booting the RHEL installation from a prepared DASD to install in an IBM Z LPAR Use this procedure when installing Red Hat Enterprise Linux into an LPAR using an already prepared DASD. Procedure Log in on the IBM Z Hardware Management Console (HMC) or the Support Element (SE) as a user with sufficient privileges to install a new operating system to an LPAR. On the Systems tab, select the mainframe you want to work with, then on the Partitions tab select the LPAR to which you wish to install. At the bottom of the screen, under Daily , find Operating System Messages . Double-click Operating System Messages to show the text console on which Linux boot messages will appear. Double-click Load . In the dialog box that follows, select Normal as the Load type . As Load address , fill in the device number of the DASD. Click the OK button. 13.3.3. Booting the RHEL installation from an FCP-attached SCSI disk to install in an IBM Z LPAR Use this procedure when installing Red Hat Enterprise Linux into an LPAR using an already prepared FCP attached SCSI disk. Procedure Log in on the IBM Z Hardware Management Console (HMC) or the Support Element (SE) as a user with sufficient privileges to install a new operating system to an LPAR. On the Systems tab, select the mainframe you want to work with, then on the Partitions tab select the LPAR to which you wish to install. At the bottom of the screen, under Daily , find Operating System Messages . Double-click Operating System Messages to show the text console on which Linux boot messages will appear. Double-click Load . In the dialog box that follows, select SCSI as the Load type . As Load address , fill in the device number of the FCP channel connected with the SCSI disk. As World wide port name , fill in the WWPN of the storage system containing the disk as a 16-digit hexadecimal number. As Logical unit number , fill in the LUN of the disk as a 16-digit hexadecimal number. Leave the Boot record logical block address as 0 and the Operating system specific load parameters empty. Click the OK button. 13.4. Booting the installation on IBM Z to install RHEL in z/VM When installing under z/VM, you can boot from: The z/VM virtual reader A DASD or an FCP-attached SCSI disk prepared with the zipl boot loader 13.4.1. Booting the RHEL installation by using the z/VM Reader You can boot from the z/VM reader. Procedure If necessary, add the device containing the z/VM TCP/IP tools to your CMS disk list. For example: Replace fm with any FILEMODE letter. For a connection to an FTPS server, enter: Where host is the host name or IP address of the FTP server that hosts the boot images ( kernel.img and initrd.img ). Log in and execute the following commands. Use the (repl option if you are overwriting existing kernel.img , initrd.img , generic.prm , or redhat.exec files: Optional: Check whether the files were transferred correctly by using the CMS command filelist to show the received files and their format. It is important that kernel.img and initrd.img have a fixed record length format denoted by F in the Format column and a record length of 80 in the Lrecl column. For example: Press PF3 to quit filelist and return to the CMS prompt. Customize boot parameters in generic.prm as necessary. For details, see Customizing boot parameters . Another way to configure storage and network devices is by using a CMS configuration file. In such a case, add the CMSDASD= and CMSCONFFILE= parameters to generic.prm . Finally, execute the REXX script redhat.exec to boot the installation program: 13.4.2. Booting the RHEL installation by using a prepared DASD Perform the following steps to use a Prepared DASD: Procedure Boot from the prepared DASD and select the zipl boot menu entry referring to the Red Hat Enterprise Linux installation program. Use a command of the following form: Replace DASD_device_number with the device number of the boot device, and boot_entry_number with the zipl configuration menu for this device. For example: 13.4.3. Booting the RHEL installation by using a prepared FCP attached SCSI Disk Perform the following steps to boot from a prepared FCP-attached SCSI disk: Procedure Configure the SCSI boot loader of z/VM to access the prepared SCSI disk in the FCP Storage Area Network. Select the prepared zipl boot menu entry referring to the Red Hat Enterprise Linux installation program. Use a command of the following form: Replace WWPN with the World Wide Port Name of the storage system and LUN with the Logical Unit Number of the disk. The 16-digit hexadecimal numbers must be split into two pairs of eight digits each. For example: Optional: Confirm your settings with the command: Boot the FCP device connected with the storage system containing the disk with the following command: For example:

Commands:
cp link tcpmaint 592 592 acc 592 fm
ftp <host> (secure
cd / location/of/install-tree /images/ ascii get generic.prm (repl get redhat.exec (repl locsite fix 80 binary get kernel.img (repl get initrd.img (repl quit
VMUSER FILELIST A0 V 169 Trunc=169 Size=6 Line=1 Col=1 Alt=0 Cmd Filename Filetype Fm Format Lrecl Records Blocks Date Time REDHAT EXEC B1 V 22 1 1 4/15/10 9:30:40 GENERIC PRM B1 V 44 1 1 4/15/10 9:30:32 INITRD IMG B1 F 80 118545 2316 4/15/10 9:30:25 KERNEL IMG B1 F 80 74541 912 4/15/10 9:30:17
redhat
cp ipl DASD_device_number loadparm boot_entry_number
cp ipl eb1c loadparm 0
cp set loaddev portname WWPN lun LUN bootprog boot_entry_number
cp set loaddev portname 50050763 050b073d lun 40204011 00000000 bootprog 0
query loaddev
cp ipl FCP_device
cp ipl fc00