| Installation GuideChapter 23. Installation Phase 3: Installing using anacondaThis chapter describes an installation using the graphical user interface of anaconda. 23.1. The Non-interactive Line-Mode Text Installation Program OutputIf the cmdline option was specified as boot option in your parameter file (Refer to Section 26.6, "Parameters for kickstart installations") or in your kickstart file (refer to Chapter 32, Kickstart Installations), anaconda starts with line-mode oriented text output. In this mode, all necessary information must be provided in the kickstart file. The installer will not allow user interaction and stops if there is unspecified installation information. 23.2. The Text Mode Installation Program User InterfaceWhile 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: Interactively activating FCP LUNs 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
23.3. 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. 23.4. Configure the Install TerminalIf you logged in with ssh and X11 forwarding, anaconda starts immediately with its graphical user interface. If you did not set the display= variable and do not use X11 forwarding, anaconda gives you the choice of starting VNC or text mode. If you choose VNC, you will be asked for a password or you can choose to use VNC without a password. If you use a password, make a note of the password for future reference. The VNC server then starts. Now open a connection to the IP address of your z/VM guest virtual machine using a VNC client. Authenticate to the VNC server with the previously entered password. 23.5. Welcome to Red Hat Enterprise LinuxThe Welcome screen does not prompt you for any input. Click on the Next button to continue. You can install Red Hat Enterprise Linux on a large variety of storage devices. For System z, select - Basic Storage Devices
This option does not apply to System z. - Specialized Storage Devices
Select to install Red Hat Enterprise Linux on the following storage devices: Direct access storage devices (DASDs) Multipath devices such as FCP-attachable SCSI LUN with multiple paths Storage area networks (SANs) such as FCP-attachable SCSI LUNs with a single path
Use the option to configure Internet Small Computer System Interface (iSCSI) connections. You cannot use the FCoE (Fiber Channel over Ethernet) option on System z; this option is grayed out.
23.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. On System z, this contains activated DASDs. - Firmware RAID
Storage devices attached to a firmware RAID controller. This does not apply to System z. - 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) such as FCP LUNs attached over one single path.
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. 23.6.1.1. DASD low-level formattingAny DASDs used must be low-level formatted. The installer detects this and lists the DASDs that need formatting. If any of the DASDs specified interactively in linuxrc or in a parameter or configuration file are not yet low-level formatted, the following confirmation dialog appears: 23.6.1.2. Advanced Storage Options From this screen you can configure an iSCSI (SCSI over TCP/IP) target or FCP LUNs. Refer to Appendix B, ISCSI disks for an introduction to iSCSI. 23.6.1.2.1. 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 23.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 23.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.
FCP devices enable IBM System z to use SCSI devices rather than, or in addition to, DASD devices. FCP devices provide a switched fabric topology that enables System z systems to use SCSI LUNs as disk devices in addition to traditional DASD devices. IBM System z requires that any FCP device be entered manually (either in the installation program interactively, or specified as unique parameter entries in the parameter or CMS configuration file) for the installation program to activate FCP LUNs. The values entered here are unique to each site in which they are set up. Notes Interactive creation of an FCP device is only possible in graphical mode. It is not possible to interactively configure an FCP device in a text-only install. Each value entered should be verified as correct, as any mistakes made may cause the system not to operate properly. Use only lower-case letters in hex values. For more information on these values, refer to the hardware documentation check with the system administrator who set up the network for this system.
To configure a Fiber Channel Protocol SCSI device, select Add ZFCP LUN and click Add Drive. In the Add FCP device dialog, fill in the details for the 16-bit device number, 64-bit World Wide Port Number (WWPN) and 64-bit FCP LUN. Click the Add button to connect to the FCP device using this information. The newly added device should then be present and usable in the storage device selection screen on the Multipath Devices tab, if you have activated more than one path to the same LUN, or on Other SAN Devices, if you have activated only one path to the LUN. The installer requires the definition of a DASD. For a SCSI-only installation, enter none as the parameter interactively during phase 1 of an interactive installation, or add DASD=none in the parameter or CMS configuration file. This satisfies the requirement for a defined DASD parameter, while resulting in a SCSI-only environment. 23.7. Setting the HostnameSetup 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 a short 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. You may give your system any name provided that the full hostname is unique. The hostname may include letters, numbers and hyphens. Change the default setting localhost.localdomain to a unique hostname for each of your Linux instances. 23.7.1. Edit Network ConnectionsTo change your network configuration after you have completed the installation, use the Network Administration Tool. Type the system-config-network command in a shell prompt to launch the Network Administration Tool. If you are not root, it prompts you for the root password to continue. The Network Administration Tool is now deprecated and will be replaced by NetworkManager during the lifetime of Red Hat Enterprise Linux 6. Usually, the network connection configured earlier in installation phase 1 does not need to be modified during the rest of the installation. You cannot add a new connection on System z because the network subchannels need to be grouped and set online beforehand, and this is currently only done in installation phase 1. To change the existing network connection, click the button Configure Network. The Network Connections dialog appears that allows you to configure network connections for the system, not all of which are relevant to System z. All network connections on System z are listed in the Wired tab. By default this contains the connection configured earlier in installation phase 1 and is either eth0 (OSA, LCS), or hsi0 (HiperSockets). Note that on System z you cannot add a new connection here. To modify an existing connection, select a row in the list and click the Edit button. A dialog box appears with a set of tabs appropriate to wired connections, as described below. The most important tabs on System z are Wired and IPv4 Settings. 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". 23.7.1.1. Options common to all types of connectionCertain configuration options are common to all connection types. Specify a name for the connection in the Connection name name field. Select Connect 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. 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. 23.7.1.3. The 802.1x Security tabUse 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: TLS for Transport Layer Security Tunneled TLS for Tunneled Transport Layer Security, otherwise known as TTLS, or EAP-TTLS 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.
23.7.1.4. The IPv4 Settings tabUse the IPv4 Settings tab tab to configure the IPv4 parameters for the previously selected network connection. The address, netmask, gateway, DNS servers and DNS search suffix for an IPv4 connection were configured during installation phase 1 or reflect the following parameters in the parameter file or configuration file: IPADDR, NETMASK, GATEWAY, DNS, SEARCHDNS (Refer to Section 26.3, "Installation network parameters"). 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 servers field, 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. 23.7.1.4.1. Editing IPv4 routesRed Hat Enterprise Linux configures a number of routes automatically based on the IP addresses of a device. To edit additional routes, click the Routes button. The Editing IPv4 routes dialog appears. 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. 23.7.1.5. The IPv6 Settings tabUse 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 servers field, 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. 23.7.1.5.1. Editing IPv6 routesRed Hat Enterprise Linux configures a number of routes automatically based on the IP addresses of a device. To edit additional routes, click the Routes button. The Editing IPv6 routes dialog appears. 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. 23.7.1.6. Restart a network deviceIf 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. Press Ctrl+Alt+F2 to switch to virtual terminal tty2. 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. Open the interface configuration file in the vi editor: vi /tmp/ifcfg-device_name 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. Exit the vi editor. 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. Press Ctrl+Alt+F6 to return to anaconda.
23.8. Time Zone ConfigurationSet your time zone by selecting the city closest to your computer's physical location. Click on the map to zoom in to a particular geographical region of the world. Specify a time zone even if you plan to use NTP (Network Time Protocol) to maintain the accuracy of the system clock. From here there are two ways for you to select your time zone: Using your mouse, click on the interactive map to select a specific city (represented by a yellow dot). A red X appears indicating your selection. You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection.
Select System clock uses UTC. The system clock is a piece of hardware on your computer system. Red Hat Enterprise Linux uses the timezone setting to determine the offset between the local time and UTC on the system clock. This behavior is standard for systems that use UNIX, Linux, and similar operating systems. Click Next to proceed. To change your time zone configuration after you have completed the installation, use the Time and Date Properties Tool. Type the system-config-date command in a shell prompt to launch the Time and Date Properties Tool. If you are not root, it prompts you for the root password to continue. To run the Time and Date Properties Tool as a text-based application, use the command timeconfig. 23.9. Set the Root PasswordSetting up a root account and password is one of the most important steps during your installation. The root account is used to install packages, upgrade RPMs, and perform most system maintenance. Logging in as root gives you complete control over your system. The root user (also known as the superuser) has complete access to the entire system; for this reason, logging in as the root user is best done only to perform system maintenance or administration. Use the root account only for system administration. Create a non-root account for your general use and use the su command to change to root only when you need to perform tasks that require superuser authorization. These basic rules minimize the chances of a typo or an incorrect command doing damage to your system. To become root, type su - at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter. The installation program prompts you to set a root password for your system. . You cannot proceed to the next stage of the installation process without entering a root password.The root password must be at least six characters long; the password you type is not echoed to the screen. You must enter the password twice; if the two passwords do not match, the installation program asks you to enter them again. You should make the root password something you can remember, but not something that is easy for someone else to guess. Your name, your phone number, qwerty, password, root, 123456, and anteater are all examples of bad passwords. Good passwords mix numerals with upper and lower case letters and do not contain dictionary words: Aard387vark or 420BMttNT, for example. Remember that the password is case-sensitive. If you write down your password, keep it in a secure place. However, it is recommended that you do not write down this or any password you create. Do not use one of the example passwords offered in this manual. Using one of these passwords could be considered a security risk. To change your root password after you have completed the installation, use the Root Password Tool. Type the system-config-users command in a shell prompt to launch the User Manager, a powerful user management and configuration tool. If you are not root, it prompts you for the root password to continue. Enter the root password into the Root Password field. Red Hat Enterprise Linux displays the characters as asterisks for security. Type the same password into the Confirm field to ensure it is set correctly. After you set the root password, select Next to proceed. 23.10. Assign Storage Devices If you selected more than one storage device on the storage devices selection screen (refer to Section 23.6, "Storage Devices"), anaconda asks you to select which of these devices should be available for installation of the operating system, and which should only be attached to the file system for data storage. During installation, the devices that you identify here as being for data storage only are mounted as part of the file system, but are not partitioned or formatted. The screen is split into two panes. The left pane contains a list of devices to be used for data storage only. The right pane contains a list of devices that are to be available for installation of the operating system. Each list contains information about the devices to help you to identify them. 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. Reducing or expanding the amount of information presented might help you to identify particular devices. Move a device from one list to the other by clicking on the device, then clicking either the button labeled with a left-pointing arrow to move it to the list of data storage devices or the button labeled with a right-pointing arrow to move it to the list of devices available for installation of the operating system. The list of devices available as installation targets also includes a radio button beside each device. On platforms other than System z, this radio button is used to specify the device to which you want to install the boot loader. On System z this choice does not have any effect. The zipl boot loader will be installed on the disk that contains the /boot directory, which is determined later on during partitioning. When you have finished identifying devices to be used for installation, click Next to continue. |
| |
