| Installation GuideChapter 19. Preparing for Installation19.1. Preparing for a Network InstallationMake sure no installation DVD (or any other type of DVD or CD) is in your hosting partition's drive if you are performing a network-based installation. Having a DVD or CD in the drive might cause unexpected errors. The Red Hat Enterprise Linux installation medium must be available for either a network installation (via NFS, FTP, HTTP, or HTTPS) or installation via local storage. Use the following steps if you are performing an NFS, FTP, HTTP, or HTTPS installation. The NFS, FTP, HTTP, or HTTPS server to be used for installation over the network must be a separate, network-accessible server. The separate server can be a virtual machine, LPAR, or any other system (such as a Linux on Power Systems or x86 system). It must provide the complete contents of the installation DVD-ROM. The public directory used to access the installation files over FTP, NFS, HTTP, or HTTPS is mapped to local storage on the network server. For example, the local directory /var/www/inst/rhel6 on the network server can be accessed as http://network.server.com/inst/rhel6. In the following examples, the directory on the installation staging server that will contain the installation files will be specified as /location/of/disk/space/publicly_available_directory. For example, /location/of/disk/space/var/isos. /publicly_available_directory/var/www/html/rhel6, for an HTTP install. In the following, you will require an ISO image. An ISO image is a file containing an exact copy of the content of a DVD. To create an ISO image from a DVD use the following command: dd if=/dev/dvd of=/path_to_image/name_of_image.iso
where dvd is your DVD drive device, name_of_image is the name you give to the resulting ISO image file, and path_to_image is the path to the location on your system where the resulting ISO image will be stored. 19.1.1. Preparing for FTP, HTTP, and HTTPS installationExtract the files from the ISO image of the installation DVD and place them in a directory that is shared over FTP, HTTP, or HTTPS. Next, make sure that the directory is shared via FTP, HTTP, or HTTPS, and verify client access. Test to see whether the directory is accessible from the server itself, and then from another machine on the same subnet to which you will be installing. 19.1.2. Preparing for an NFS installationFor NFS installation it is not necessary to extract all the files from the ISO image. It is sufficient to make the ISO image itself, the install.img file, and optionally the product.img file available on the network server via NFS. Transfer the ISO image to the NFS exported directory. On a Linux system, run: mv /path_to_image/name_of_image.iso /publicly_available_directory/
where path_to_image is the path to the ISO image file, name_of_image is the name of the ISO image file, and publicly_available_directory is a directory that is available over NFS or that you intend to make available over NFS. Use a SHA256 checksum program to verify that the ISO image that you copied is intact. Many SHA256 checksum programs are available for various operating systems. On a Linux system, run: $ sha256sum name_of_image.iso
where name_of_image is the name of the ISO image file. The SHA256 checksum program displays a string of 64 characters called a hash. Compare this hash to the hash displayed for this particular image on the Download Software page on the Red Hat Network (refer to Chapter 1, Obtaining Red Hat Enterprise Linux). The two hashes should be identical. Copy the images/ directory from inside the ISO image to the same directory in which you stored the ISO image file itself. Enter the following commands: mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o loop,rocp -pr /mount_point/images /publicly_available_directory/umount /mount_point
where path_to_imagename_of_imagemount_point mount -t iso9660 /var/isos/RHEL6.iso /mnt/tmp -o loop,rocp -pr /mnt/tmp/images /var/isos/umount /mnt/tmp
The ISO image file and an images/ directory are now present, side-by-side, in the same directory. Verify that the images/ directory contains at least the install.img file, without which installation cannot proceed. Optionally, the images/ directory should contain the product.img file, without which only the packages for a Minimal installation will be available during the package group selection stage (refer to Section 23.17, "Package Group Selection"). Ensure that an entry for the publicly available directory exists in the /etc/exports file on the network server so that the directory is available via NFS. To export a directory read-only to a specific system, use: /publicly_available_directory client.ip.address (ro)
To export a directory read-only to all systems, use: /publicly_available_directory * (ro)
On the network server, start the NFS daemon (on a Red Hat Enterprise Linux system, use /sbin/service nfs start). If NFS is already running, reload the configuration file (on a Red Hat Enterprise Linux system use /sbin/service nfs reload). Be sure to test the NFS share following the directions in the Red Hat Enterprise Linux Deployment Guide. Refer to your NFS documentation for details on starting and stopping the NFS server.
anaconda has the ability to test the integrity of the installation media. It works with the DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned DVDs). To use this test, type the following command at the boot: prompt: linux mediacheck
19.2. Preparing for a Hard Drive InstallationUse this option to install Red Hat Enterprise Linux on hardware systems without a DVD drive and if you do not want to access installation phase 3 and the package repository over a network. 19.2.1. Accessing Installation Phase 3 and the Package Repository on a Hard DriveHard drive installations using DASD or FCP-attached SCSI storage only work from native ext2, ext3, or ext4 partitions. If you have a file system based on devices other than native ext2, ext3, or ext4 (particularly a file system based on RAID or LVM partitions) you will not be able to use it as a source to perform a hard drive installation. Hard drive installations use an ISO image of the installation DVD (a file that contains an exact copy of the content of the DVD), and an install.img file extracted from the ISO image. With these files present on a hard drive, you can choose as the installation source when you boot the installation program. Hard drive installations use the following files: an ISO image of the installation DVD. An ISO image is a file that contains an exact copy of the content of a DVD. an install.img file extracted from the ISO image. optionally, a product.img file extracted from the ISO image.
To prepare a DASD or FCP-attached device as an installation source, follow these steps: Obtain an ISO image of the Red Hat Enterprise Linux installation DVD (refer to Chapter 1, Obtaining Red Hat Enterprise Linux). Alternatively, if you have the DVD on physical media, you can create an image of it with the following command on a Linux system: dd if=/dev/dvd of=/path_to_image/name_of_image.iso
where dvd is your DVD drive device, name_of_image is the name you give to the resulting ISO image file, and path_to_image is the path to the location on your system where the resulting ISO image will be stored. Transfer the ISO images to the DASD or SCSI device. Use a SHA256 checksum program to verify that the ISO image that you copied is intact. Many SHA256 checksum programs are available for various operating systems. On a Linux system, run: $ sha256sum name_of_image.iso
where name_of_image is the name of the ISO image file. The SHA256 checksum program displays a string of 64 characters called a hash. Compare this hash to the hash displayed for this particular image on the Download Software page on the Red Hat Network (refer to Chapter 1, Obtaining Red Hat Enterprise Linux). The two hashes should be identical. Copy the images/ directory from inside the ISO image to the same directory in which you stored the ISO image file itself. Enter the following commands: mount -t iso9660 /path_to_image/name_of_image.iso /mount_point -o loop,rocp -pr /mount_point/images /publicly_available_directory/umount /mount_point
where path_to_imagename_of_imagemount_point mount -t iso9660 /var/isos/RHEL6.iso /mnt/tmp -o loop,rocp -pr /mnt/tmp/images /var/isos/umount /mnt/tmp
The ISO image file and an images/ directory are now present, side-by-side, in the same directory. Verify that the images/ directory contains at least the install.img file, without which installation cannot proceed. Optionally, the images/ directory should contain the product.img file, without which only the packages for a Minimal installation will be available during the package group selection stage (refer to Section 23.17, "Package Group Selection"). install.img and product.img must be the only files in the images/ directory.
The Red Hat Enterprise Linux installation program can test the integrity of the installation medium. It works with the DVD, hard drive ISO, and NFS ISO installation methods. We recommend that you test all installation media before starting the installation process, and before reporting any installation-related bugs. To use this test, add the mediacheck parameter to your parameter file (refer to Section 26.7, "Miscellaneous parameters"). 19.2.1.1. Preparing for Booting the Installer from a Hard DriveIf you would like to boot (IPL) the installer from a hard drive, in addition to accessing installation phase 3 and the package repository, you can optionally install the zipl boot loader on the same (or a different) disk. Be aware that zipl only supports one boot record per disk. If you have multiple partitions on a disk, they all "share" the disk's one boot record. To prepare a hard drive to boot the installer, install the zipl boot loader on the hard drive by entering the following command: zipl -V -t /mnt/ -i /mnt/images/kernel.img -r /mnt/images/initrd.img -p /mnt/images/generic.prm
For more details on zipl.conf, refer to the chapter on zipl in Linux on System z Device Drivers, Features, and Commands on Red Hat Enterprise Linux 6. If you have an operating system installed on the disk, and you still plan to access it later on, refer the chapter on zipl in Linux on System z Device Drivers, Features, and Commands on Red Hat Enterprise Linux 6 for how to add a new entry in the zipl boot loader (that is, in zipl.conf). Chapter 20. Booting (IPL) the InstallerThe steps to perform the initial boot (IPL) of the installer depend on the environment (either z/VM or LPAR) in which Red Hat Enterprise Linux will run. For more information on booting, see the Booting Linux chapter in Linux on System z Device Drivers, Features, and Commands on Red Hat Enterprise Linux 6. 20.1. Installing under z/VMWhen installing under z/VM, you can boot from: Log on to the z/VM guest virtual machine chosen for the Linux installation. You can use x3270 or c3270 (from the x3270-text package in Red Hat Enterprise Linux) to log in to z/VM from other Linux systems. Alternatively, use the 3270 terminal emulator on the IBM System z Hardware Management Console (HMC). If you are working from a machine with a Windows operating system, Jolly Giant ( http://www.jollygiant.com/) offers an SSL-enabled 3270 emulator. A free native Windows port of c3270 called wc3270 also exists. If your 3270 connection is interrupted and you cannot log in again because the previous session is still active, you can replace the old session with a new one by entering the following command on the z/VM logon screen: logon user here
Replace user with the name of the z/VM guest virtual machine. Depending on whether an external security manager, for example RACF, is used, the logon command might vary. If you are not already running CMS (single user operating system shipped with z/VM) in your guest, boot it now by entering the command: #cp ipl cms
Be sure not to use CMS disks such as your A disk (often device number 0191) as installation targets. To find out which disks are in use by CMS use the following query: query disk
You can use the following CP (z/VM Control Program, which is the z/VM hypervisor) query commands to find out about the device configuration of your z/VM guest virtual machine: Query the available main memory, which is called storage in System z terminology. Your guest should have at least 512 megabytes of main memory. cp query virtual storage
Query available network devices of type: osaOSA (CHPID type OSD, real or virtual (VSWITCH or GuestLAN type QDIO), both in QDIO mode) hsiHiperSockets (CHPID type IQD, real or virtual (GuestLAN type Hipers)) lcsLCS (CHPID type OSE)
For example, to query all of the network device types mentioned above: cp query virtual osa
Query available DASDs. Only those that are flagged RW for read-write mode can be used as installation targets: cp query virtual dasd
Query available FCP channels: cp query virtual fcp
20.1.1. Using the z/VM ReaderPerform the following steps to boot from the z/VM reader: If necessary, add the device containing the z/VM TCP/IP tools to your CMS disk list. For example: cp link tcpmaint 592 592acc 592 fm Replace fm with any FILEMODE letter. Execute the command: ftp host
Where host is the hostname or IP address of the FTP server that hosts the boot images (kernel.img and initrd.img). Log in and execute the following commands. Use the (repl option if you are overwriting existing kernel.img, initrd.img, generic.prm, or redhat.exec files: cd /location/of/install-tree/images/ ascii get generic.prm (repl get redhat.exec (repl locsite fix 80 binary get kernel.img (repl get initrd.img (repl quit
Optionally check whether the files were transferred correctly by using the CMS command filelist to show the received files and their format. It is important that kernel.img and initrd.img have a fixed record length format denoted by F in the Format column and a record length of 80 in the Lrecl column. For example: VMUSER FILELIST A0 V 169 Trunc=169 Size=6 Line=1 Col=1 Alt=0 Cmd Filename Filetype Fm Format Lrecl Records Blocks Date Time REDHAT EXEC B1 V 22 1 1 4/15/10 9:30:40 GENERIC PRM B1 V 44 1 1 4/15/10 9:30:32 INITRD IMG B1 F 80 118545 2316 4/15/10 9:30:25 KERNEL IMG B1 F 80 74541 912 4/15/10 9:30:17
Press PF3 to quit filelist and return to the CMS prompt. Finally execute the REXX script redhat.exec to boot (IPL) the installer: redhat
20.1.2. Using a prepared DASDBoot from the prepared DASD and select the zipl boot menu entry referring to the Red Hat Enterprise Linux installer. Use a command of the following form: cp ipl DASD device number loadparm boot_entry_number
Replace DASD device number with the device number of the boot device, and boot_entry_number with the zipl configuration menu for this device. For example: cp ipl eb1c loadparm 0
20.1.3. Using a prepared FCP-attached SCSI DiskPerform the following steps to boot from a prepared FCP-attached SCSI disk: Configure the SCSI boot loader of z/VM to access the prepared SCSI disk in the FCP storage area network. Select the prepared zipl boot menu entry referring to the Red Hat Enterprise Linux installer. Use a command of the following form: cp set loaddev portname WWPN lun LUN bootprog boot_entry_number
Replace WWPN with the WWPN of the storage system and LUN with the LUN of the disk. The 16-digit hexadecimal numbers must be split into two pairs of eight digits each. For example: cp set loaddev portname 50050763 050b073d lun 40204011 00000000 bootprog 0
Optionally, confirm your settings with the command: query loaddev
IPL the FCP device connected with the storage system containing the disk with the command: cp ipl FCP_device
For example: cp ipl fc00
20.1.4. Using an FCP-attached SCSI DVD DriveThis requires a SCSI DVD drive attached to an FCP-to-SCSI bridge which is in turn connected to an FCP adapter in your System z. The FCP adapter must be configured and available under z/VM. Insert your Red Hat Enterprise Linux for System z DVD into the DVD drive. Configure the SCSI boot loader of z/VM to access the DVD drive in the FCP storage area network and specify 1 for the boot entry on the Red Hat Enterprise Linux for System z DVD. Use a command of the following form: cp set loaddev portname WWPN lun FCP_LUN bootprog 1
Replace WWPN with the WWPN of the FCP-to-SCSI bridge and FCP_LUN with the LUN of the DVD drive. The 16-digit hexadecimal numbers must be split into two pairs of eight characters each. For example: cp set loaddev portname 20010060 eb1c0103 lun 00010000 00000000 bootprog 1
Optionally, confirm your settings with the command: cp query loaddev
IPL on the FCP device connected with the FCP-to-SCSI bridge. cp ipl FCP_device
For example: cp ipl fc00
20.2. Installing in an LPARWhen installing in a logical partition (LPAR), you can boot from: an FTP server the DVD drive of the HMC or SE a DASD or an FCP-attached SCSI drive prepared with the zipl boot loader an FCP-attached SCSI DVD drive
Perform these common steps first: Log in on the IBM System z Hardware Management Console (HMC) or the Support Element (SE) as a user with sufficient privileges to install a new operating system to an LPAR. The SYSPROG user is recommended. Select Images, then select the LPAR to which you wish to install. Use the arrows in the frame on the right side to navigate to the menu. Double-click Operating System Messages to show the text console on which Linux boot messages will appear and potentially user input will be required. Refer to the chapter on booting Linux in Linux on System z Device Drivers, Features, and Commands on Red Hat Enterprise Linux 6 and the Hardware Management Console Operations Guide, order number [SC28-6857], for details.
Continue with the procedure for your installation source. 20.2.1. Using an FTP ServerDouble-click Load from CD-ROM, DVD, or Server. In the dialog box that follows, select FTP Source, and enter the following information: Host Computer: Hostname or IP address of the FTP server you wish to install from (for example, ftp.redhat.com) User ID: Your user name on the FTP server (or anonymous) Password: Your password (use your email address if you are logging in as anonymous) Account (optional): Leave this field empty File location (optional): Directory on the FTP server holding Red Hat Enterprise Linux for System z (for example, /rhel/s390x/) Click Continue. In the dialog that follows, keep the default selection of generic.ins and click Continue.
20.2.2. Using the HMC or SE DVD DriveDouble-click Load from CD-ROM, DVD, or Server. In the dialog box that follows, select Local CD-ROM / DVD then click Continue. In the dialog that follows, keep the default selection of generic.ins then click Continue.
20.2.3. Using a prepared DASDDouble-click Load. In the dialog box that follows, select Normal as the Load type. As Load address fill in the device number of the DASD. As Load parameter fill in the number corresponding the zipl boot menu entry that you prepared for booting the Red Hat Enterprise Linux installer. Click the OK button.
20.2.4. Using a prepared FCP-attached SCSI DiskDouble-click Load. In the dialog box that follows, select SCSI as the Load type. As Load address fill in the device number of the FCP channel connected with the SCSI disk. As World wide port name fill in the WWPN of the storage system containing the disk as a 16-digit hexadecimal number. As Logical unit number fill in the LUN of the disk as a 16-digit hexadecimal number. As Boot program selector fill in the number corresponding the zipl boot menu entry that you prepared for booting the Red Hat Enterprise Linux installer. Leave the Boot record logical block address as 0 and the Operating system specific load parameters empty. Click the OK button.
20.2.5. Using an FCP-attached SCSI DVD DriveThis requires to have a SCSI DVD drive attached to an FCP-to-SCSI bridge which is in turn connected to an FCP adapter in your System z machine. The FCP adapter has to be configured and available in your LPAR. Insert your Red Hat Enterprise Linux for System z DVD into the DVD drive. Double-click Load. In the dialog box that follows, select SCSI as the Load type. As Load address fill in the device number of the FCP channel connected with the FCP-to-SCSI bridge. As World wide port name fill in the WWPN of the FCP-to-SCSI bridge as a 16-digit hexadecimal number. As Logical unit number fill in the LUN of the DVD drive as a 16-digit hexadecimal number. As Boot program selector fill in the number 1 to select the boot entry on the Red Hat Enterprise Linux for System z DVD. Leave the Boot record logical block address as 0 and the Operating system specific load parameters empty. Click the OK button.
Chapter 21. Installation Phase 1: Configuring a Network DeviceAfter the kernel boot, you will configure one network device using the linuxrc program. This network device is needed to complete the installation. If you are installing interactively (with the default parameter file generic.prm), you will be asked questions about your network. It is a good idea to have your data ready in the form of a datasheet or similar. If you want to automate this step, supply the information for each option in your parameter file or CMS configuration file. As an example, let us look at how to configure an OSA network adapter under z/VM. When linuxrc starts, you see the following message: Starting the zSeries initrd to configure networking. Version is 1.2 Starting udev...
Network devices are sensed and listed. The list of devices depends on the cio_ignore kernel parameter used. If no devices are found because of cio_ignore, as in the example below, you can clear the list of ignored devices. Note that this might take some time and result in a long list when there are many devices, such as on an LPAR. Scanning for available network devices... Autodetection found 0 devices. Note: There is a device blacklist active! (Clearing might take long) c) clear blacklist, m) manual config, r) rescan, s) shell: c Clearing device blacklist... Scanning for available network devices... Autodetection found 14 devices. NUM CARD CU CHPID TYPE DRIVER IF DEVICES 1 OSA (QDIO) 1731/01 00 OSD qeth eth 0.0.f500,0.0.f501,0.0.f502 2 OSA (QDIO) 1731/01 01 OSD qeth eth 0.0.f503,0.0.f504,0.0.f505 3 OSA (QDIO) 1731/01 02 OSD qeth eth 0.0.1010,0.0.1011,0.0.1012 4 HiperSockets 1731/05 03 IQD qeth hsi 0.0.1013,0.0.1014,0.0.1015 5 OSA (QDIO) 1731/01 04 OSD qeth eth 0.0.1017,0.0.1018,0.0.1019 6 CTC adapter 3088/08 12 ? ctcm ctc 0.0.1000,0.0.1001 7 escon channel 3088/1f 12 ? ctcm ctc 0.0.1002,0.0.1003 8 ficon channel 3088/1e 12 ? ctcm ctc 0.0.1004,0.0.1005 9 OSA (QDIO) 1731/01 76 OSD qeth eth 0.0.f5f0,0.0.f5f1,0.0.f5f2 10 LCS OSA 3088/60 8a OSE lcs eth 0.0.1240,0.0.1241 11 HiperSockets 1731/05 fb IQD qeth hsi 0.0.8024,0.0.8025,0.0.8026 12 HiperSockets 1731/05 fc IQD qeth hsi 0.0.8124,0.0.8125,0.0.8126 13 HiperSockets 1731/05 fd IQD qeth hsi 0.0.8224,0.0.8225,0.0.8226 14 HiperSockets 1731/05 fe IQD qeth hsi 0.0.8324,0.0.8325,0.0.8326 <num>) use config, m) manual config, r) rescan, s) shell:
Enter the number of the configuration you want to use, for example 9. Selecting from the table provides the installer with information for the type of network device and the device addresses for its subchannels. Alternatively, you can enter m and proceed to enter the network type (qeth), the read, write, data channels, and the OSA port. Accept defaults by pressing Enter; under z/VM you might need to press Enter twice. m * NOTE: To enter default or empty values press enter twice. * Network type (qeth, lcs, ctc, ? for help). Default is qeth: qeth Read,write,data channel (e.g. 0.0.0300,0.0.0301,0.0.0302 or ? for help). 0.0.f5f0,0.0.f5f1,0.0.f5f2 Portname (1..8 characters, or ? for help). Default is no portname: Relative port number for OSA (0, 1, or ? for help). Default is 0: Activating network device... Detected: OSA card in OSD mode, Gigabit Ethernet
Then questions pertaining to your Linux instance are displayed: Hostname of your new Linux guest (FQDN e.g. s390.redhat.com or ? for help): host.subdomain.domain IPv4 address / IPv6 addr. (e.g. 10.0.0.2 / 2001:0DB8:: or ? for help) 10.0.0.42 IPv4 netmask or CIDR prefix (e.g. 255.255.255.0 or 1..32 or ? for help). Default is 255.0.0.0: 24 IPv4 address of your default gateway or ? for help: 10.0.0.1 Trying to reach gateway 10.0.0.1... IPv4 addresses of DNS servers (separated by colons ':' or ? for help): 10.1.2.3:10.3.2.1 Trying to reach DNS servers... DNS search domains (separated by colons ':' or ? for help): subdomain.domain:domain DASD range (e.g. 200-203,205 or ? for help). Default is autoprobing: eb1c Activated DASDs: 0.0.eb1c(ECKD) dasda : active, blocksize: 4096, 1803060 blocks, 7043 MB The installer requires the definition of a DASD. For a SCSI-only installation, enter none. This satisfies the requirement for a defined DASD parameter, while resulting in a SCSI-only environment. If you make a mistake, the dialog either notices the error and asks you to re-enter the parameter, or you can go back later to restart the dialog: Incorrect ... (<OPTION-NAME>): 0) redo this parameter, 1) continue, 2) restart dialog, 3) halt, 4) shell When you restart the dialog, it remembers what you entered before: Network type 0) default is previous "qeth", 1) new value, ?) help At the end of the configuration, you see the message Initial configuration completed: Initial configuration completed. c) continue, p) parm file/configuration, n) network state, r) restart, s) shell You can now check your network configuration by entering n: n eth0 Link encap:Ethernet HWaddr 02:00:00:AB:C9:81 inet addr:10.0.0.42 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:64 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3334 (3.2 KiB) TX bytes:336 (336.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo 10.0.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 eth0 c) continue, p) parm file/configuration, n) network state, r) restart, s) shell If you want to change something, enter r to restart the dialog. To show the parameters as specified in a parameter or configuration file or interactively enter p. You can then copy the output from your terminal and paste it into an editor to save it to disk on your local workstation. You can use the copy as a template for a parameter or configuration file for future installations: p NETTYPE=qeth IPADDR=10.0.0.42 NETMASK=255.255.255.0 GATEWAY=10.0.0.1 HOSTNAME=host.subdomain.domain SUBCHANNELS=0.0.f5f0,0.0.f5f1,0.0.f5f2 LAYER2=1 MACADDR=02:00:00:AB:C9:81 PORTNAME=OSAPORT DNS=10.1.2.3:10.3.2.1 SEARCHDNS=subdomain.domain:domain DASD=eb1c c) continue, p) parm file/configuration, n) network state, r) restart, s) shell Again, to change something, restart the dialog with r. Finally, if all is in order, enter c to continue: c Starting sshd to allow login over the network. Connect now to 10.0.0.42 and log in as user 'install' to start the installation. E.g. using: ssh -x [email protected] For VNC or text mode, disable X11 forwarding (recommended) with 'ssh -x'. For X11, enable X11 forwarding with 'ssh -X'. You may log in as the root user to start an interactive shell. The preliminary network setup is now complete and the installer starts an SSH daemon. You can log into your Linux instance over SSH. If you are using RUNKS=1 with kickstart and cmdline mode, linuxrc automatically starts the loader. 21.1. A Note on TerminalsDuring the installation, the installation program displays messages on a line-mode terminal. This is the HMC Operating System Messages applet if you install under LPAR, or a 3270 terminal if you install under z/VM. Linuxrc provides a rescue shell on the line-mode terminal. Press the Enter key (twice under z/VM) to start the shell. You cannot use full-screen applications such as the vi editor on the line-mode terminal. Switch to line-mode based editors such as ed, ex, or sed to edit text files if necessary. Be aware that long-running commands might not be interruptible with the escape sequence Ctrl+C. Call commands with options that make them return in time voluntarily. The shell on the 3270 terminal is available throughout the whole installation process until the point where the system needs to reboot. Once the shell has been provided, you may exit with an error level of zero to get a new shell instance replacing the old one, or you may exit with an error level different from zero to force a shutdown of the installation system. Connect to the installed system using user root to get a root shell without automatically starting the installer. For problem determination, you might connect with many ssh sessions. Chapter 22. Installation Phase 2: Configuring Language and Installation SourceBefore the graphical installation program starts, you need to configure the language and installation source. By default, if you are installing interactively (with the default parameter file generic.prm) the loader program to select language and installation source starts in text mode. In your new ssh session, the following message is displayed: Welcome to the anaconda install environment 1.2 for zSeries
22.1. Non-interactive Line-Mode Installation22.2. The Text Mode Installation Program User InterfaceWindow - 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.
22.2.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). 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. 22.4. Installation MethodUse the arrow keys on your keyboard to select an installation method (refer to Figure 22.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. 22.4.1. Installing from DVDThe installation program then probes your system and attempts to identify your DVD-ROM drive. It starts by looking for a SCSI DVD-ROM 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 23.16, "Write changes to disk" for more information. If the DVD drive is found and the driver loaded, the installer presents you with the option to perform a media check on the DVD. This takes 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 23.5, "Welcome to Red Hat Enterprise Linux"). 22.4.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. DASD names begin with /dev/dasd. Each individual drive has its own letter, for example /dev/dasda or /dev/sda. Each partition on a drive is numbered, for example /dev/dasda1 or /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 22.1. Location of ISO images for different partition types | File system | Mount point | Original path to files | Directory to use |
|---|
| 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. 22.4.3. Performing a Network InstallationThe installation program is network-aware and can use network settings for a number of functions. On System z, installation phases 2 and 3 take over the network configuration values specified previously either interactively or by means of a parameter or configuration file in installation phase 1. You can also instruct the installation program to consult additional software repositories later in the process. 22.4.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.
22.4.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/s390x/
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. 22.6. Retrieving Phase 3 of the Installation ProgramThe loader then retrieves phase 3 of the installation program from the network into its RAM disk. This may take some time. |
| |
