| Installation GuideChapter 7. Booting the InstallerRed Hat Enterprise Linux 6 does not support UEFI for 32-bit x86 systems. Note that the boot configurations of UEFI and BIOS differ significantly from each other. Therefore, the installed system must boot using the same firmware that was used during installation. You cannot install the operating system on a system that uses BIOS and then boot this installation on a system that uses UEFI. Red Hat Enterprise Linux 6 supports version 2.2 of the UEFI specification. Hardware that supports version 2.3 of the UEFI specification or later should boot and operate with Red Hat Enterprise Linux 6, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from http://www.uefi.org/specs/agreement/To start the installation program from a Red Hat Enterprise Linux DVD or from minimal boot media, follow this procedure: Power on your computer system. Insert the media in your computer. Power off your computer with the boot media still inside. Power on your computer system. You might need to press a specific key or combination of keys to boot from the media. On most computers, a message appears briefly on the screen very soon after you turn on the computer. Typically, it is worded something like Press F10 to select boot device, although the specific wording and the key that you must press varies widely from computer to computer. Consult the documentation for your computer or motherboard, or seek support from the hardware manufacturer or vendor. If your computer does not allow you to select a boot device as it starts up, you might need to configure your system's Basic Input/Output System ( BIOS) to boot from the media. To change your BIOS settings on an x86, AMD64, or Intel 64 system, watch the instructions provided on your display when your computer first boots. A line of text appears, telling you which key to press to enter the BIOS settings. Once you have entered your BIOS setup program, find the section where you can alter your boot sequence. The default is often C, A or A, C (depending on whether you boot from your hard drive [C] or a diskette drive [A]). Change this sequence so that the DVD is first in your boot order and that C or A (whichever is your typical boot default) is second. This instructs the computer to first look at the DVD drive for bootable media; if it does not find bootable media on the DVD drive, it then checks your hard drive or diskette drive. Save your changes before exiting the BIOS. For more information, refer to the documentation that came with your system. To abort the installation, either press Ctrl +Alt+Del or power off your computer with the power switch. You may abort the installation process without consequence at any time prior to selecting Write changes to disk on the Write partitioning to disk screen. Red Hat Enterprise Linux makes no permanent changes to your computer until that point. Please be aware that stopping the installation after partitioning has begun can leave your computer unusable. 7.1. Starting the Installation ProgramRed Hat Enterprise Linux 6 does not support UEFI for 32-bit x86 systems. Note that the boot configurations of UEFI and BIOS differ significantly from each other. Therefore, the installed system must boot using the same firmware that was used during installation. You cannot install the operating system on a system that uses BIOS and then boot this installation on a system that uses UEFI. Red Hat Enterprise Linux 6 supports version 2.2 of the UEFI specification. Hardware that supports version 2.3 of the UEFI specification or later should boot and operate with Red Hat Enterprise Linux 6, but the additional functionality defined by these later specifications will not be available. The UEFI specifications are available from http://www.uefi.org/specs/agreement/To start, first make sure that you have all necessary resources for the installation. If you have already read through Chapter 3, Planning for Installation on the x86 Architecture, and followed the instructions, you should be ready to start the installation process. When you have verified that you are ready to begin, boot the installation program using the Red Hat Enterprise Linux DVD or any boot media that you have created. 7.1.1. Booting the Installation Program on x86, AMD64, and Intel 64 SystemsYou can boot the installation program using any one of the following media (depending upon what your system can support): Red Hat Enterprise Linux DVD - Your machine supports a bootable DVD drive and you have the Red Hat Enterprise Linux installation DVD. Boot CD-ROM - Your machine supports a bootable CD-ROM drive and you want to perform network or hard drive installation. USB flash drive - Your machine supports booting from a USB device.
Insert the boot media and reboot the system. You might need to press a specific key or combination of keys to boot from the media. On most computers, a message appears briefly on the screen very soon after you turn on the computer. Typically, it is worded something like Press F10 to select boot device, although the specific wording and the key that you must press varies widely from computer to computer. Consult the documentation for your computer or motherboard, or seek support from the hardware manufacturer or vendor. If your computer does not allow you to select a boot device as it starts up, you might need to configure your system's Basic Input/Output System ( BIOS) to boot from the media. To change your BIOS settings on an x86, AMD64, or Intel 64 system, watch the instructions provided on your display when your computer first boots. A line of text appears, telling you which key to press to enter the BIOS settings. Once you have entered your BIOS setup program, find the section where you can alter your boot sequence. The default is often C, A or A, C (depending on whether you boot from your hard drive [C] or a diskette drive [A]). Change this sequence so that the DVD is first in your boot order and that C or A (whichever is your typical boot default) is second. This instructs the computer to first look at the DVD drive for bootable media; if it does not find bootable media on the DVD drive, it then checks your hard drive or diskette drive. Save your changes before exiting the BIOS. For more information, refer to the documentation that came with your system. After a short delay, the graphical boot screen appears, which contains information on a variety of boot options. Installation program automatically begins if you take no action within the first minute. For a description of the options available on this screen, refer to Section 7.1.2, "The Boot Menu". The boot media displays a graphical boot menu with several options. If no key is hit within 60 seconds, the default boot option runs. To choose the default, either wait for the timer to run out or hit Enter on the keyboard. To select a different option than the default, use the arrow keys on your keyboard, and hit Enter when the correct option is highlighted. If you want to customize the boot options for a particular option, press the Tab key. To access the boot: prompt at which you can specify custom boot options, press the Esc key and refer to Section 7.1.3, "Additional Boot Options". The boot menu options are: - Install or upgrade an existing system
This option is the default. Choose this option to install Red Hat Enterprise Linux onto your computer system using the graphical installation program. - Install system with basic video driver
This option allows you to install Red Hat Enterprise Linux in graphical mode even if the installation program is unable to load the correct driver for your video card. If your screen appears distorted or goes blank when using the Install or upgrade an existing system option, restart your computer and try this option instead. - Rescue installed system
Choose this option to repair a problem with your installed Red Hat Enterprise Linux system that prevents you from booting normally. Although Red Hat Enterprise Linux is an exceptionally stable computing platform, it is still possible for occasional problems to occur that prevent booting. The rescue environment contains utility programs that allow you fix a wide variety of these problems. - Boot from local drive
This option boots the system from the first installed disk. If you booted this disc accidentally, use this option to boot from the hard disk immediately without starting the installer.
7.1.3. Additional Boot OptionsWhile it is easiest to boot using a DVD and perform a graphical installation, sometimes there are installation scenarios where booting in a different manner may be needed. This section discusses additional boot options available for Red Hat Enterprise Linux. To pass options to the boot loader on an x86, AMD64, or Intel 64 system, press the Esc key at boot time. The boot: prompt appears, at which you can use the boot loader options described below. To perform a text mode installation, at the installation boot prompt, type: linux text
To specify an installation source, use the linux repo= option. For example: linux repo=cdrom:device
linux repo=ftp://username:password@URL
linux repo=http://URL
linux repo=hd:device
linux repo=nfs:options:server:/path
linux repo=nfsiso:options:server:/path
In these examples, cdrom refers to a CD or DVD drive, ftp refers to a location accessible by FTP, http refers to a location accessible by HTTP, hd refers to an ISO image file accessible on a hard drive partition, nfs refers to an expanded tree of installation files accessible by NFS, and nfsiso refers to an ISO image file accessible by NFS. ISO images have an SHA256 checksum embedded in them. To test the checksum integrity of an ISO image, at the installation boot prompt, type: linux mediacheck
The installation program prompts you to insert a DVD or select an ISO image to test, and select OK to perform the checksum operation. This checksum operation can be performed on any Red Hat Enterprise Linux DVD. It is strongly recommended to perform this operation on any Red Hat Enterprise Linux DVD that was created from downloaded ISO images. This command works with the DVD, hard drive ISO, and NFS ISO installation methods. If you need to perform the installation in serial mode, type the following command: linux console=<device>
For text mode installations, use: linux text console=<device>
In the above command, <device> should be the device you are using (such as ttyS0 or ttyS1). For example, linux text console=ttyS0. Text mode installations using a serial terminal work best when the terminal supports UTF-8. Under UNIX and Linux, Kermit supports UTF-8. For Windows, Kermit '95 works well. Non-UTF-8 capable terminals works as long as only English is used during the installation process. An enhanced serial display can be used by passing the utf8 command as a boot-time option to the installation program. For example: linux console=ttyS0 utf8
Options can also be passed to the kernel. For example, to apply updates for the anaconda installation program from a USB storage device enter: linux updates
For text mode installations, use: linux text updates
This command results in a prompt for the path to the device that contains updates for anaconda. It is not needed if you are performing a network installation and have already placed the updates image contents in rhupdates/ on the server. After entering any options, press Enter to boot using those options. 7.2. Installing from a Different Source You can install Red Hat Enterprise Linux from the ISO images stored on hard disk, or from a network using NFS, FTP, HTTP, or HTTPS methods. Experienced users frequently use one of these methods because it is often faster to read data from a hard disk or network server than from a DVD. The following table summarizes the different boot methods and recommended installation methods to use with each: Table 7.1. Boot methods and installation sources | Boot method | Installation source |
|---|
| Installation DVD | DVD, network, or hard disk | | Installation USB flash drive | Installation DVD, network, or hard disk | | Minimal boot CD or USB, rescue CD | Network or hard disk |
7.3. Booting from the Network using PXE Configure the computer to boot from the network interface. This option is in the BIOS, and may be labeled Network Boot or Boot Services. Once you properly configure PXE booting, the computer can boot the Red Hat Enterprise Linux installation system without any other media. To boot a computer from a PXE server: Ensure 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 computer. A menu screen appears. Press the number key that corresponds to the desired option.
If your PC does not boot from the netboot server, ensure that the BIOS is configured to boot first from the correct network interface. Some BIOS systems specify the network interface as a possible boot device, but do not support the PXE standard. Refer to your hardware documentation for more information. Some servers with multiple network interfaces might not assign eth0 to the first network interface as the firmware interface knows it, which can cause the installer to try to use a different network interface from the one that was used by PXE. To change this behavior, use the following in pxelinux.cfg/* config files: IPAPPEND 2APPEND ksdevice=bootif These configuration options above cause the installer to use the same network interface the firmware interface and PXE use. You can also use the following option: ksdevice=link This option causes the installer to use the first network device it finds that is linked to a network switch. Chapter 8. Configuring Language and Installation SourceBefore the graphical installation program starts, you need to configure the language and installation source. 8.1. The Text Mode Installation Program User InterfaceWe recommend that you install Red Hat Enterprise Linux using the graphical interface. If you are installing Red Hat Enterprise Linux on a system that lacks a graphical display, consider performing the installation over a VNC connection - see Chapter 31, Installing Through VNC. If anaconda detects that you are installing in text mode on a system where installation over a VNC connection might be possible, anaconda asks you to verify your decision to install in text mode even though your options during installation are limited. If your system has a graphical display, but graphical installation fails, try booting with the xdriver=vesa option - refer to Chapter 28, Boot OptionsNot every language supported in graphical installation mode is also supported in text mode. Specifically, languages written with a character set other than the Latin or Cyrillic alphabets are not available in text mode. If you choose a language written with a character set that is not supported in text mode, the installation program will present you with the English versions of the screens. The widgets include: Window - Windows (usually referred to as dialogs in this manual) appear on your screen throughout the installation process. At times, one window may overlay another; in these cases, you can only interact with the window on top. When you are finished in that window, it disappears, allowing you to continue working in the window underneath. Checkbox - Checkboxes allow you to select or deselect a feature. The box displays either an asterisk (selected) or a space (unselected). When the cursor is within a checkbox, press Space to select or deselect a feature. Text Input - Text input lines are regions where you can enter information required by the installation program. When the cursor rests on a text input line, you may enter and/or edit information on that line. Text Widget - Text widgets are regions of the screen for the display of text. At times, text widgets may also contain other widgets, such as checkboxes. If a text widget contains more information than can be displayed in the space reserved for it, a scroll bar appears; if you position the cursor within the text widget, you can then use the Up and Down arrow keys to scroll through all the information available. Your current position is shown on the scroll bar by a # character, which moves up and down the scroll bar as you scroll. Scroll Bar - Scroll bars appear on the side or bottom of a window to control which part of a list or document is currently in the window's frame. The scroll bar makes it easy to move to any part of a file. Button Widget - Button widgets are the primary method of interacting with the installation program. You progress through the windows of the installation program by navigating these buttons, using the Tab and Enter keys. Buttons can be selected when they are highlighted.
8.1.1. Using the Keyboard to NavigateNavigation through the installation dialogs is performed through a simple set of keystrokes. To move the cursor, use the Left, Right, Up, and Down arrow keys. Use Tab, and Shift-Tab to cycle forward or backward through each widget on the screen. Along the bottom, most screens display a summary of available cursor positioning keys. To "press" a button, position the cursor over the button (using Tab, for example) and press Space or Enter. To select an item from a list of items, move the cursor to the item you wish to select and press Enter. To select an item with a checkbox, move the cursor to the checkbox and press Space to select an item. To deselect, press Space a second time. Pressing F12 accepts the current values and proceeds to the next dialog; it is equivalent to pressing the OK button. Unless a dialog box is waiting for your input, do not press any keys during the installation process (doing so may result in unpredictable behavior). Use the arrow keys on your keyboard to select a language to use during the installation process (refer to Figure 8.3, "Language Selection"). With your selected language highlighted, press the Tab key to move to the OK button and press the Enter key to confirm your choice. The language you select here will become the default language for the operating system once it is installed. Selecting the appropriate language also helps target your time zone configuration later in the installation. The installation program tries to define the appropriate time zone based on what you specify on this screen. Once you select the appropriate language, click Next to continue. If you booted the installation from minimal boot media or with the askmethod boot option, use the arrow keys on your keyboard to select an installation method (refer to Figure 8.4, "Installation Method"). With your selected method highlighted, press the Tab key to move to the OK button and press the Enter key to confirm your choice. 8.3.1. Installing from DVDTo install Red Hat Enterprise Linux from a DVD, place the DVD your DVD drive and boot your system from the DVD. Even if you booted from alternative media, you can still install Red Hat Enterprise Linux from DVD media. The installation program then probes your system and attempts to identify your DVD drive. It starts by looking for an IDE (also known as an ATAPI) DVD drive. To abort the installation process at this time, reboot your machine and then eject the boot media. You can safely cancel the installation at any point before the Write changes to disk screen. Refer to Section 9.16, "Write changes to disk" for more information. If your DVD drive is not detected, and it is a SCSI DVD, the installation program prompts you to choose a SCSI driver. Choose the driver that most closely resembles your adapter. You may specify options for the driver if necessary; however, most drivers detect your SCSI adapter automatically. If the DVD drive is found and the driver loaded, the installer will present you with the option to perform a media check on the DVD. This will take some time, and you may opt to skip over this step. However, if you later encounter problems with the installer, you should reboot and perform the media check before calling for support. From the media check dialog, continue to the next stage of the installation process (refer to Section 9.3, "Welcome to Red Hat Enterprise Linux"). 8.3.2. Installing from a Hard DriveThe Select Partition screen applies only if you are installing from a disk partition (that is, you selected in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd boot option, you already specified a partition. Select the partition containing the ISO files from the list of available partitions. Internal IDE, SATA, SCSI, and USB drive device names begin with /dev/sd. Each individual drive has its own letter, for example /dev/sda. Each partition on a drive is numbered, for example /dev/sda1. Also specify the Directory holding images. Enter the full directory path from the drive that contains the ISO image files. The following table shows some examples of how to enter this information: Table 8.1. Location of ISO images for different partition types | Partition type | Volume | Original path to files | Directory to use |
|---|
| VFAT | D:\ | D:\Downloads\RHEL6 | /Downloads/RHEL6 | | ext2, ext3, ext4 | /home | /home/user1/RHEL6 | /user1/RHEL6 |
If the ISO images are in the root (top-level) directory of a partition, enter a /. If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/, and the images are in /home/new/, you would enter /new/. An entry without a leading slash may cause the installation to fail. 8.3.3. Performing a Network InstallationWhen you start an installation with the askmethod or repo= options, you can install Red Hat Enterprise Linux from a network server using FTP, HTTP, HTTPS, or NFS protocols. Anaconda uses the same network connection to consult additional software repositories later in the installation process. If your system has more than one network device, anaconda presents you with a list of all available devices and prompts you to select one to use during installation. If your system only has a single network device, anaconda automatically selects it and does not present this dialog. If you are not sure which device in the list corresponds to which physical socket on the system, select a device in the list then press the Identify button. The Identify NIC dialog appears. The sockets of most network devices feature an activity light (also called a link light) - an LED that flashes to indicate that data is flowing through the socket. Anaconda can flash the activity light of the network device that you selected in the Networking Device dialog for up to 30 seconds. Enter the number of seconds that you require, then press OK. When anaconda finishes flashing the light, it returns you to the Networking Device dialog. When you select a network device, anaconda prompts you to choose how to configure TCP/IP: IPv4 options - Dynamic IP configuration (DHCP)
Anaconda uses DHCP running on the network to supply the network configuration automatically. - Manual configuration
Anaconda prompts you to enter the network configuration manually, including the IP address for this system, the netmask, the gateway address, and the DNS address.
IPv6 options - Automatic
Anaconda uses router advertisement (RA) and DHCP for automatic configuration, based on the network environment. (Equivalent to the Automatic option in NetworkManager) - Automatic, DHCP only
Anaconda does not use RA, but requests information from DHCPv6 directly to create a stateful configuration. (Equivalent to the Automatic, DHCP only option in NetworkManager) - Manual configuration
Anaconda prompts you to enter the network configuration manually, including the IP address for this system, the netmask, the gateway address, and the DNS address.
Anaconda supports the IPv4 and IPv6 protocols. However, if you configure an interface to use both IPv4 and IPv6, the IPv4 connection must succeed or the interface will not work, even if the IPv6 connection succeeds. By default, anaconda uses DHCP to provide network settings automatically for IPv4 and automatic configuration to provide network settings for IPv6. If you choose to configure TCP/IP manually, anaconda prompts you to provide the details in the Manual TCP/IP Configuration dialog: The dialog provides fields for IPv4 and IPv6 addresses and prefixes, depending on the protocols that you chose to configure manually, together with fields for the network gateway and name server. Enter the details for your network, then press OK. When the installation process completes, it will transfer these settings to your system. 8.3.4. Installing via NFSThe NFS dialog applies only if you selected in the Installation Method dialog. If you used the repo=nfs boot option, you already specified a server and path. Enter the domain name or IP address of your NFS server in the NFS server name field. For example, if you are installing from a host named eastcoast in the domain example.com, enter eastcoast.example.com. Enter the name of the exported directory in the Red Hat Enterprise Linux 6 directory field: If the NFS server is exporting a mirror of the Red Hat Enterprise Linux installation tree, enter the directory which contains the root of the installation tree. If everything was specified properly, a message appears indicating that the installation program for Red Hat Enterprise Linux is running. If the NFS server is exporting the ISO image of the Red Hat Enterprise Linux DVD, enter the directory which contains the ISO image.
Specify any NFS mount options that you require in the NFS mount options field. Refer to the man pages for mount and nfs for a comprehensive list of options. If you do not require any mount options, leave the field empty.
8.3.5. Installing via FTP, HTTP, or HTTPSWhen you provide a URL to an installation source, you must explicitly specify http:// or https:// or ftp:// as the protocol. The URL dialog applies only if you are installing from a FTP, HTTP, or HTTPS server (if you selected in the Installation Method dialog). This dialog prompts you for information about the FTP, HTTP, or HTTPS server from which you are installing Red Hat Enterprise Linux. If you used the repo=ftp or repo=http boot options, you already specified a server and path. Enter the name or IP address of the FTP, HTTP, or HTTPS site from which you are installing, and the name of the directory that contains the /images directory for your architecture. For example: /mirrors/redhat/rhel-6/Server/i386/
To install via a secure HTTPS connection, specify https:// as the protocol. Specify the address of a proxy server, and if necessary, provide a port number, username, and password. If everything was specified properly, a message box appears indicating that files are being retrieved from the server. If your FTP, HTTP, or HTTPS server requires user authentication, specify user and password as part of the URL as follows: {ftp|http|https}://<user>:<password>@<hostname>[:<port>]/<directory>/
For example: The DVD offers an option to verify the integrity of the media. Recording errors sometimes occur while producing DVD media. An error in the data for package chosen in the installation program can cause the installation to abort. To minimize the chances of data errors affecting the installation, verify the media before installing. If the verification succeeds, the installation process proceeds normally. If the process fails, create a new DVD using the ISO image you downloaded earlier. Chapter 9. Installing using anacondaThis chapter describes an installation using the graphical user interface of anaconda. 9.1. The Text Mode Installation Program User InterfaceInstalling in text mode does not prevent you from using a graphical interface on your system once it is installed. Apart from the graphical installer, anaconda also includes a text-based installer. If one of the following situations occurs, the installation program uses text mode: While text mode installations are not explicitly documented, those using the text mode installation program can easily follow the GUI installation instructions. However, because text mode presents you with a simpler, more streamlined installation process, certain options that are available in graphical mode are not also available in text mode. These differences are noted in the description of the installation process in this guide, and include: configuring advanced storage methods such as LVM, RAID, FCoE, zFCP, and iSCSI. customizing the partition layout customizing the bootloader layout selecting packages during installation configuring the installed system with firstboot
9.2. The Graphical Installation Program User InterfaceIf you have used a graphical user interface (GUI) before, you are already familiar with this process; use your mouse to navigate the screens, click buttons, or enter text fields. You can also navigate through the installation using the keyboard. The Tab key allows you to move around the screen, the Up and Down arrow keys to scroll through lists, + and - keys expand and collapse lists, while Space and Enter selects or removes from selection a highlighted item. You can also use the Alt+X key command combination as a way of clicking on buttons or making other screen selections, where X is replaced with any underlined letter appearing within that screen. If you are using an x86, AMD64, or Intel 64 system, and you do not wish to use the GUI installation program, the text mode installation program is also available. To start the text mode installation program, use the following command at the boot: prompt: linux text
It is highly recommended that installs be performed using the GUI installation program. The GUI installation program offers the full functionality of the Red Hat Enterprise Linux installation program, including LVM configuration which is not available during a text mode installation. Users who must use the text mode installation program can follow the GUI installation instructions and obtain all needed information. 9.2.1. Screenshots during installationAnaconda allows you to take screenshots during the installation process. At any time during installation, press Shift+Print Screen and anaconda will save a screenshot to /root/anaconda-screenshots. If you are performing a Kickstart installation, use the autostep --autoscreenshot option to generate a screenshot of each step of the installation automatically. Refer to Section 32.3, "Creating the Kickstart File" for details of configuring a Kickstart file. 9.2.2. A Note about Virtual ConsolesThe Red Hat Enterprise Linux installation program offers more than the dialog boxes of the installation process. Several kinds of diagnostic messages are available to you, as well as a way to enter commands from a shell prompt. The installation program displays these messages on five virtual consoles, among which you can switch using a single keystroke combination. A virtual console is a shell prompt in a non-graphical environment, accessed from the physical machine, not remotely. Multiple virtual consoles can be accessed simultaneously. These virtual consoles can be helpful if you encounter a problem while installing Red Hat Enterprise Linux. Messages displayed on the installation or system consoles can help pinpoint a problem. Refer to Table 9.1, "Console, Keystrokes, and Contents" for a listing of the virtual consoles, keystrokes used to switch to them, and their contents. Generally, there is no reason to leave the default console (virtual console #6) for graphical installations unless you are attempting to diagnose installation problems. Table 9.1. Console, Keystrokes, and Contents | console | keystrokes | contents |
|---|
| 1 | ctrl+alt+f1 | graphical display | | 2 | ctrl+alt+f2 | shell prompt | | 3 | ctrl+alt+f3 | install log (messages from installation program) | | 4 | ctrl+alt+f4 | system-related messages | | 5 | ctrl+alt+f5 | other messages |
9.3. Welcome to Red Hat Enterprise LinuxThe Welcome screen does not prompt you for any input. Click on the Next button to continue. Using your mouse, select the language (for example, U.S. English) you would prefer to use for the installation and as the system default (refer to the figure below). Once you have made your selection, click Next to continue. 9.5. Keyboard ConfigurationUsing your mouse, select the correct layout type (for example, U.S. English) for the keyboard you would prefer to use for the installation and as the system default (refer to the figure below). Once you have made your selection, click Next to continue. Red Hat Enterprise Linux includes support for more than one keyboard layout for many languages. In particular, most European languages include a latin1 option, which uses dead keys to access certain characters, such as those with diacritical marks. When you press a dead key, nothing will appear on your screen until you press another key to "complete" the character. For example, to type � on a latin1 keyboard layout, you would press (and release) the ' key, and then press the E key. By contrast, you access this character on some other keyboards by pressing and holding down a key (such as Alt-Gr) while you press the E key. Other keyboards might have a dedicated key for this character. To change your keyboard layout type after you have completed the installation, use the Keyboard Configuration Tool. Type the system-config-keyboard command in a shell prompt to launch the Keyboard Configuration Tool. If you are not root, it prompts you for the root password to continue. You can install Red Hat Enterprise Linux on a large variety of storage devices. This screen allows you to select either basic or specialized storage devices. - Basic Storage Devices
Select to install Red Hat Enterprise Linux on the following storage devices: - Specialized Storage Devices
Select to install Red Hat Enterprise Linux on the following storage devices: Use the option to configure Internet Small Computer System Interface (iSCSI) and FCoE (Fiber Channel over Ethernet) connections.
If you select , anaconda automatically detects the local storage attached to the system and does not require further input from you. Proceed to Section 9.7, "Setting the Hostname". 9.6.1. The Storage Devices Selection Screen The storage devices selection screen displays all storage devices to which anaconda has access. Devices are grouped under the following tabs: - Basic Devices
Basic storage devices directly connected to the local system, such as hard disk drives and solid-state drives. - Firmware RAID
Storage devices attached to a firmware RAID controller. - Multipath Devices
Storage devices accessible through more than one path, such as through multiple SCSI controllers or Fiber Channel ports on the same system. The installer only detects multipath storage devices with serial numbers that are 16 or 32 characters in length. - Other SAN Devices
Any other devices available on a storage area network (SAN).
The storage devices selection screen also contains a Search tab that allows you to filter storage devices either by their World Wide Identifier (WWID) or by the port, target, or logical unit number (LUN) at which they are accessed. The tab contains a drop-down menu to select searching by port, target, WWID, or LUN (with corresponding text boxes for these values). Searching by WWID or LUN requires additional values in the corresponding text box. Each tab presents a list of devices detected by anaconda, with information about the device to help you to identify it. A small drop-down menu marked with an icon is located to the right of the column headings. This menu allows you to select the types of data presented on each device. For example, the menu on the Multipath Devices tab allows you to specify any of , , , , and to include among the details presented for each device. Reducing or expanding the amount of information presented might help you to identify particular devices. Each device is presented on a separate row, with a checkbox to its left. Click the checkbox to make a device available during the installation process, or click the radio button at the left of the column headings to select or deselect all the devices listed in a particular screen. Later in the installation process, you can choose to install Red Hat Enterprise Linux onto any of the devices selected here, and can choose to automatically mount any of the other devices selected here as part of the installed system. Note that the devices that you select here are not automatically erased by the installation process. Selecting a device on this screen does not, in itself, place data stored on the device at risk. Note also that any devices that you do not select here to form part of the installed system can be added to the system after installation by modifying the /etc/fstab file. Any storage devices that you do not select on this screen are hidden from anaconda entirely. To chain load the Red Hat Enterprise Linux boot loader from a different boot loader, select all the devices presented in this screen. 9.6.1.1. Advanced Storage Options From this screen you can configure an iSCSI (SCSI over TCP/IP) target or FCoE (Fibre channel over ethernet) SAN (storage area network). Refer to Appendix B, ISCSI disks for an introduction to iSCSI. 9.6.1.1.1. Select and configure a network interfaceIf a network interface is not already active on the system, anaconda must activate one through which to connect to the storage devices. If your system has only a single network interface, anaconda automatically activates it. However, if your system has more than one network interface available, anaconda prompts you with the Select network interface dialog to choose one to use during installation. Select an interface from the drop-down menu. Click OK.
Anaconda activates the interface that you selected, then starts NetworkManager to allow you to configure the interface. 9.6.1.1.2. Configure iSCSI parametersTo use iSCSI storage devices for the installation, anaconda must be able to discover them as iSCSI targets and be able to create an iSCSI session to access them. Each of these steps might require a username and password for CHAP (Challenge Handshake Authentication Protocol) authentication. Additionally, you can configure an iSCSI target to authenticate the iSCSI initiator on the system to which the target is attached (reverse CHAP), both for discovery and for the session. Used together, CHAP and reverse CHAP are called mutual CHAP or two-way CHAP. Mutual CHAP provides the greatest level of security for iSCSI connections, particularly if the username and password are different for CHAP authentication and reverse CHAP authentication. Repeat the iSCSI discovery and iSCSI login steps as many times as necessary to add all required iSCSI storage. However, you cannot change the name of the iSCSI initiator after you attempt discovery for the first time. To change the iSCSI initiator name, you must restart the installation. Procedure 9.1. iSCSI discovery Use the iSCSI Discovery Details dialog to provide anaconda with the information that it needs to discover the iSCSI target. Enter the IP address of the iSCSI target in the Target IP Address field. Provide a name in the iSCSI Initiator Name field for the iSCSI initiator in iSCSI qualified name (IQN) format. A valid IQN contains: the string iqn. (note the period) a date code that specifies the year and month in which your organization's Internet domain or subdomain name was registered, represented as four digits for the year, a dash, and two digits for the month, followed by a period. For example, represent September 2010 as 2010-09. your organization's Internet domain or subdomain name, presented in reverse order with the top-level domain first. For example, represent the subdomain storage.example.com as com.example.storage a colon followed by a string that uniquely identifies this particular iSCSI initiator within your domain or subdomain. For example, :diskarrays-sn-a8675309.
A complete IQN therefore resembles: iqn.2010-09.storage.example.com:diskarrays-sn-a8675309, and anaconda pre-populates the iSCSI Initiator Name field with a name in this format to help you with the structure. Use the drop-down menu to specify the type of authentication to use for iSCSI discovery:
If you selected as the authentication type, provide the username and password for the iSCSI target in the CHAP Username and CHAP Password fields.
If you selected as the authentication type, provide the username and password for the iSCSI target in the CHAP Username and CHAP Password field and the username and password for the iSCSI initiator in the Reverse CHAP Username and Reverse CHAP Password fields.
Click Start Discovery. Anaconda attempts to discover an iSCSI target based on the information that you provided. If discovery succeeds, the iSCSI Discovered Nodes dialog presents you with a list of all the iSCSI nodes discovered on the target. Each node is presented with a checkbox beside it. Click the checkboxes to select the nodes to use for installation.
Click Login to initiate an iSCSI session.
Procedure 9.2. Starting an iSCSI session Use the iSCSI Nodes Login dialog to provide anaconda with the information that it needs to log into the nodes on the iSCSI target and start an iSCSI session. Use the drop-down menu to specify the type of authentication to use for the iSCSI session:
If your environment uses the same type of authentication and same username and password for iSCSI discovery and for the iSCSI session, select to reuse these credentials. If you selected as the authentication type, provide the username and password for the iSCSI target in the CHAP Username and CHAP Password fields.
If you selected as the authentication type, provide the username and password for the iSCSI target in the CHAP Username and CHAP Password fields and the username and password for the iSCSI initiator in the Reverse CHAP Username and Reverse CHAP Password fields.
Click Login. Anaconda attempts to log into the nodes on the iSCSI target based on the information that you provided. The iSCSI Login Results dialog presents you with the results.
Click OK to continue.
9.6.1.1.3. Configure FCoE Parameters To configure an FCoE SAN, select Add FCoE SAN and click Add Drive. On the menu that appears in the next dialog box, select the network interface that is connected to your FCoE switch and click Add FCoE Disk(s). Data Center Bridging (DCB) is a set of enhancements to the Ethernet protocols designed to increase the efficiency of Ethernet connections in storage networks and clusters. Enable or disable the installer's awareness of DCB with the checkbox in this dialog. This should only be set for networking interfaces that require a host-based DCBX client. Configurations on interfaces that implement a hardware DCBX client should leave this checkbox empty. Auto VLAN indicates whether VLAN discovery should be performed. If this box is checked, then the FIP VLAN discovery protocol will run on the Ethernet interface once the link configuration has been validated. If they are not already configured, network interfaces for any discovered FCoE VLANs will be automatically created and FCoE instances will be created on the VLAN interfaces. |
| |
