9.3.

Welcome to Red Hat Enterprise Linux

The Welcome screen does not prompt you for any input.

Click on the Next button to continue.

Language Selection
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.

Figure 9.1. Language Configuration

9.5. Keyboard Configuration

Using 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.

Figure 9.2. Keyboard Configuration

Red Hat Enterprise Linux includes support for more than one keyboard layout for many languages. In particular, most European languages include a latin1option, 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.

9.6. Storage Devices

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.

Figure 9.3. Storage devices

Basic Storage Devices Select Basic Storage Devices to install Red Hat Enterprise Linux on the following storage devices: o hard drives or solid-state drives connected directly to the local system. Specialized Storage Devices Select Specialized Storage Devices to install Red Hat Enterprise Linux on the following storage devices: o Storage area networks (SANs) o Direct access storage devices (DASDs) o Firmware RAID devices

o Multipath devices Use the Specialized Storage Devices option to configure Internet Small Computer System Interface (iSCSI) and FCoE (Fiber Channel over Ethernet) connections. If you select Basic Storage Devices, 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.

Figure 9.4. Select storage devices Basic devices

Figure 9.5. Select storage devices Multipath Devices

Figure 9.6. Select storage devices Other SAN Devices

Devices are grouped under the following tabs: Basic Devices Basic storage devices directly connected to the local system, such as hard disk drives and solidstate 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.

Important device serial numbers must be 16 or 32 characters

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). If you do need to configure iSCSI or FCoE storage, click Add Advanced Target and refer to Section 9.6.1.1, Advanced Storage Options .

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.

Figure 9.7. The Storage Devices Search Tab

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 WWID, Capacity, Vendor, Interconnect, and Paths to include among the details presented for each device. Reducing or expanding the amount of information presented might help you to identify particular devices.

Figure 9.8. Selecting Columns

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.

Important chain loading

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.

when you have selected the storage devices to make available during installation, click Next and proceed to Section 9.11, Initializing the Hard Disk

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 toAppendix B, ISCSI disks for an introduction to iSCSI.

Figure 9.9. Advanced Storage Options

9.6.1.1.1. Select and configure a network interface

If 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, anacondaprompts you with the Select network interface dialog to choose one to use during installation.

Figure 9.10. Select network interface

1. Select an interface from the drop-down menu. 2. Click OK. Anaconda activates the interface that you selected, then starts NetworkManager to allow you to configure the interface.

Figure 9.11. Network Connections

For details of how to use NetworkManager, refer to Section 9.7, Setting the Hostname

9.6.1.1.2. Configure iSCSI parameters

To 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.

Figure 9.12. The iSCSI Discovery Details dialog

1. Enter the IP address of the iSCSI target in the Target IP Address field. 2. 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. o 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 o 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-sna8675309, and anaconda pre-populates theiSCSI Initiator Name field with a name in this format to help you with the structure. o o For more information on IQNs, refer to 3.2.6. iSCSI Names in RFC 3720 - Internet Small Computer Systems Interface (iSCSI) available fromhttp://tools.ietf.org/html/rfc3720#section-3.2.6 and 1. iSCSI Names and Addresses in RFC 3721 - Internet Small Computer Systems Interface (iSCSI) Naming and Discovery available from http://tools.ietf.org/html/rfc3721#section-1. 3. Use the drop-down menu to specify the type of authentication to use for iSCSI discovery:

Figure 9.13. iSCSI discovery authentication

o no credentials o CHAP pair o CHAP pair and a reverse pair 4. A. If you selected CHAP pair as the authentication type, provide the username and password for the iSCSI target in the CHAP Username andCHAP Password fields.

Figure 9.14. CHAP pair

B. If you selected CHAP pair and a reverse pair as the authentication type, provide the username and password for the iSCSI target in theCHAP Username and CHAP Password field and the username and password for the iSCSI initiator in the Reverse CHAP Username andReverse CHAP Password fields.

Figure 9.15. CHAP pair and a reverse pair

5. Click Start Discovery. Anaconda attempts to discover an iSCSI target based on the information that you provided. If discovery succeeds, theiSCSI Discovered Nodes dialog presents you with a list of all the iSCSI nodes discovered on the target. 6. Each node is presented with a checkbox beside it. Click the checkboxes to select the nodes to use for installation.

Figure 9.16. The iSCSI Discovered Nodes dialog

7. 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.

Figure 9.17. The iSCSI Nodes Login dialog

1. Use the drop-down menu to specify the type of authentication to use for the iSCSI session:

Figure 9.18. iSCSI session authentication

o o o o

no credentials CHAP pair CHAP pair and a reverse pair Use the credentials from the discovery step
If your environment uses the same type of authentication and same username and password for iSCSI discovery and for the iSCSI session, select Use the credentials from the discovery step to reuse these credentials.

2. A. If you selected CHAP pair as the authentication type, provide the username and password for the iSCSI target in the CHAP Username andCHAP Password fields.

Figure 9.19. CHAP pair

B. If you selected CHAP pair and a reverse pair as the authentication type, provide the username and password for the iSCSI target in theCHAP Username and CHAP Password fields and the username and password for the iSCSI initiator in the Reverse CHAP Username andReverse CHAP Password fields.

Figure 9.20. CHAP pair and a reverse pair

3. 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.

Figure 9.21. The iSCSI Login Results dialog

4. 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).

Figure 9.22. Configure FCoE Parameters

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.

9.7. Setting the Hostname

Setup prompts you to supply a host name for this computer, either as a fully-qualified domain name (FQDN) in the format hostname. domainname or as ashort host name in the format hostname. Many networks have a Dynamic Host Configuration Protocol (DHCP) service that automatically supplies connected systems with a domain name. To allow the DHCP service to assign the domain name to this machine, specify the short host name only.

Figure 9.23. Setting the hostname

If your Red Hat Enterprise Linux system is connected directly to the Internet, you must pay attention to additional considerations to avoid service interruptions or risk action by your upstream service provider. A full discussion of these issues is beyond the scope of this document.

9.7.1. Edit Network Connections

To configure a network connection manually, click the button Configure Network. The Network Connections dialog appears that allows you to configure wired, wireless, mobile broadband, VPN, and DSL connections for the system using the NetworkManager tool. A full description of all configurations possible with NetworkManager is beyond the scope of this guide. This section only details the most typical scenario of how to configure wired connections during installation. Configuration of other types of network is broadly similar, although the specific parameters that you must configure are necessarily different.

Figure 9.24. Network Connections

To add a new connection or to modify or remove a connection configured earlier in the installation process, click the tab that corresponds to the type of connection. To add a new connection of that type, click Add. To modify an existing connection, select it in the list and click Edit. In either case, a dialog box appears with a set of tabs that is appropriate to the particular connection type, as described below. To remove a connection, select it in the list and click Delete. When you have finished editing network settings, click Apply to save the new configuration. If you reconfigured a device that was already active during installation, you must restart the device to use the new configuration refer to Section 9.7.1.6, Restart a network device.

9.7.1.1. Options common to all types of connection

Certain configuration options are common to all connection types. Specify a name for the connection in the Connection name name field. Select Start automatically to start the connection automatically when the system boots. When NetworkManager runs on an installed system, the Available to all users option controls whether a network configuration is available system-wide or not. During installation, ensure that Available to all users remains selected for any network interface that you configure.

9.7.1.2. The Wired tab

Use the Wired tab to specify or change the media access control (MAC) address for the network adapter, and either set the maximum transmission unit(MTU, in bytes) that can pass through the interface.

Figure 9.25. The Wired tab

9.7.1.3. The 802.1x Security tab

Use the 802.1x Security tab to configure 802.1X port-based network access control (PNAC). Select Use 802.1X security for this connection to enable access control, then specify details of your network. The configuration options include: Authentication Choose one of the following methods of authentication: o TLS for Transport Layer Security o Tunneled TLS for Tunneled Transport Layer Security, otherwise known as TTLS, or EAP-TTLS o Protected EAP (PEAP) for Protected Extensible Authentication Protocol Identity Provide the identity of this server. User certificate Browse to a personal X.509 certificate file encoded with Distinguished Encoding Rules (DER) or Privacy Enhanced Mail (PEM).

CA certificate Browse to a X.509 certificate authority certificate file encoded with Distinguished Encoding Rules (DER) or Privacy Enhanced Mail (PEM). Private key Browse to a private key file encoded with Distinguished Encoding Rules (DER), Privacy Enhanced Mail (PEM), or the Personal Information Exchange Syntax Standard (PKCS#12). Private key password The password for the private key specified in the Private key field. Select Show password to make the password visible as you type it.

Figure 9.26. The 802.1x Security tab

9.7.1.4. The IPv4 Settings tab

Use the IPv4 Settings tab tab to configure the IPv4 parameters for the previously selected network connection.

Use the Method drop-down menu to specify which settings the system should attempt to obtain from a Dynamic Host Configuration Protocol (DHCP) service running on the network. Choose from the following options: Automatic (DHCP) IPv4 parameters are configured by the DHCP service on the network. Automatic (DHCP) addresses only The IPv4 address, netmask, and gateway address are configured by the DHCP service on the network, but DNS servers and search domains must be configured manually. Manual IPv4 parameters are configured manually for a static configuration. Link-Local Only A link-local address in the 169.254/16 range is assigned to the interface. Shared to other computers The system is configured to provide network access to other computers. The interface is assigned an address in the 10.42.x.1/24 range, a DHCP server and DNS server are started, and the interface is connected to the default network connection on the system with network address translation (NAT). Disabled IPv4 is disabled for this connection. If you selected a method that requires you to supply manual parameters, enter details of the IP address for this interface, the netmask, and the gateway in the Addresses field. Use the Add and Delete buttons to add or remove addresses. Enter a comma-separated list of DNS servers in the DNS serversfield, and a comma-separated list of domains in the Search domains field for any domains that you want to include in name server lookups. Optionally, enter a name for this network connection in the DHCP client ID field. This name must be unique on the subnet. When you assign a meaningful DHCP client ID to a connection, it is easy to identify this connection when troubleshooting network problems. Deselect the Require IPv4 addressing for this connection to complete check box to allow the system to make this connection on an IPv6-enabled network if IPv4 configuration fails but IPv6 configuration succeeds.

Figure 9.27. The IPv4 Settings tab

9.7.1.4.1. Editing IPv4 routes

Red Hat Enterprise Linux configures a number of routes automatically based on the IP addresses of a device. To edit additional routes, click the Routesbutton. The Editing IPv4 routes dialog appears.

Figure 9.28. The Editing IPv4 Routes dialog

Click Add to add the IP address, netmask, gateway address, and metric for a new static route. Select Ignore automatically obtained routes to make the interface use only the routes specified for it here. Select Use this connection only for resources on its network to restrict connections only to the local network.

9.7.1.5. The IPv6 Settings tab

Use the IPv6 Settings tab tab to configure the IPv6 parameters for the previously selected network connection. Use the Method drop-down menu to specify which settings the system should attempt to obtain from a Dynamic Host Configuration Protocol (DHCP) service running on the network. Choose from the following options: Ignore IPv6 is ignored for this connection.

Automatic NetworkManager uses router advertisement (RA) to create an automatic, stateless configuration. Automatic, addresses only NetworkManager uses RA to create an automatic, stateless configuration, but DNS servers and search domains are ignored and must be configured manually. Automatic, DHCP only NetworkManager does not use RA, but requests information from DHCPv6 directly to create a stateful configuration. Manual IPv6 parameters are configured manually for a static configuration. Link-Local Only A link-local address with the fe80::/10 prefix is assigned to the interface. If you selected a method that requires you to supply manual parameters, enter details of the IP address for this interface, the netmask, and the gateway in the Addresses field. Use the Add and Delete buttons to add or remove addresses. Enter a comma-separated list of DNS servers in the DNS serversfield, and a comma-separated list of domains in the Search domains field for any domains that you want to include in name server lookups. Optionally, enter a name for this network connection in the DHCP client ID field. This name must be unique on the subnet. When you assign a meaningful DHCP client ID to a connection, it is easy to identify this connection when troubleshooting network problems. Deselect the Require IPv6 addressing for this connection to complete check box to allow the system to make this connection on an IPv4-enabled network if IPv6 configuration fails but IPv4 configuration succeeds.

Figure 9.29. The IPv6 Settings tab

9.7.1.5.1. Editing IPv6 routes

Red Hat Enterprise Linux configures a number of routes automatically based on the IP addresses of a device. To edit additional routes, click the Routesbutton. The Editing IPv6 routes dialog appears.

Figure 9.30. The Editing IPv6 Routes dialog

Click Add to add the IP address, netmask, gateway address, and metric for a new static route. Select Use this connection only for resources on its network to restrict connections only to the local network.

9.7.1.6. Restart a network device

If you reconfigured a network that was already in use during installation, you must disconnect and reconnect the device in anaconda for the changes to take effect. Anaconda uses interface configuration (ifcfg) files to communicate with NetworkManager. A device becomes disconnected when its ifcfg file is removed, and becomes reconnected when its ifcfg file is restored, as long as ONBOOT=yes is set. Refer to the Red Hat Enterprise Linux 6 Deployment Guide available from https://access.redhat.com/knowledge/docs/ for more information about interface configuration files. 1. Press Ctrl+ Alt+ F2 to switch to virtual terminal tty2. 2. Move the interface configuration file to a temporary location:
mv /etc/sysconfig/network-scripts/ifcfg-device_name /tmp

where device_name is the device that you just reconfigured. For example, ifcfg-eth0 is the ifcfg file for eth0.

The device is now disconnected in anaconda. 3. Open the interface configuration file in the vi editor:
vi /tmp/ifcfg-device_name

4. Verify that the interface configuration file contains the line ONBOOT=yes. If the file does not already contain the line, add it now and save the file. 5. Exit the vi editor. 6. Move the interface configuration file back to the /etc/sysconfig/network-scripts/ directory:
mv /tmp/ifcfg-device_name /etc/sysconfig/network-scripts/

The device is now reconnected in anaconda. 7. Press Ctrl+ Alt+ F6 to return to anaconda.