Page 1 Red Hat Enterprise Linux 4 Installation Guide for the IBM®S/390® and IBM®eServer™zSeries® Architectures ISBN: N/A Publication date:...
Page 2 Red Hat Enterprise Linux 4...
Page 3 All other trademarks referenced herein are the property of their respective owners. The GPG fingerprint of the security@redhat.com key is: CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E...
Page 4 Red Hat Enterprise Linux 4...
Page 5: Table Of Contents
Introduction ......................vii 1. Document Conventions ................. vii 2. How to Use This Manual ................viii 2.1. We Need Feedback! ................ix 3. Accessibility Solutions ..................ix 1. Steps to Get You Started ..................1 1. Additional S/390 Hardware Preparation for Installation Notes ......1 2.
Page 6 Red Hat Enterprise Linux 4 16. Preparing to Install ..................43 17. Installing Packages ..................44 18. Installation Complete ...................44 A. Removing Red Hat Enterprise Linux ..............45 B. Sample Parameter Files ..................47 C. Upgrading Your Current System ................51 1. Determining Whether to Upgrade or Re-Install ..........51 2.
Page 7: Introduction
Introduction Welcome to the Red Hat Enterprise Linux Installation Guide. This guide contains useful information to assist you during the installation of Red Hat Enterprise Linux 5.0.0. From fundamental concepts such as installation preparation to the step-by-step installation procedure, this book will be a valuable resource as you install Red Hat Enterprise Linux. 1.
Page 8: How To Use This Manual
Introduction Note A note is typically information that you need to understand the behavior of the system. A tip is typically an alternative way of performing a task. Important Important information is necessary, but possibly unexpected, such as a configuration change that will not persist after a reboot. Caution A caution indicates an act that would violate your support agreement, such as recompiling the kernel.
Page 9: We Need Feedback
Submit a bug report against the component Installation Guide in Bugzilla at: http://bugzilla.redhat.com/bugzilla/ When submitting a bug report, be sure to mention the manual's identifier: Installation Guide If you have a suggestion for improving the documentation, try to be as specific as possible when describing it.
Page 10 Introduction • The file provides more information and instructions for using some of README-Accessibility the tools available for users with special needs. This file can be found in , where is the release number of your installed /usr/share/doc/redhat-release-X/ subscription.
Page 11: Steps To Get You Started
Chapter 1. Steps to Get You Started The installation process assumes a basic familiarity with the IBM S/390 and IBM eServer zSeries platforms. For additional information on these platforms, refer to the IBM Redbooks available online at: http://www.redbooks.ibm.com/ [http://www.redbooks.ibm.com] This manual assumes you are familiar with the related Redbooks and can set up logical partitions (LPARs) and virtual machines (VMs) on an S/390 or IBM eServer zSeries system.
Page 12: Basic Overview Of The Boot Method
The NFS, FTP, or HTTP server to be used for installation over the network must be a separate machine which can provide the complete directory. Both the RedHat/ RedHat/base/ directories must be available and populated with all files from all installation RedHat/RPMS/ CD-ROMs.
Page 13 Hat Enterprise Linux. The Release Notes are formatted in HTML files located at the root of the disc. Copy the files to your installation directory. For example: cp /mnt/cdrom/RELEASE-NOTES*.html /location/of/disk/space/ The Release Notes are also available online from http://www.redhat.com/docs/. • Next, make available for network installation via NFS, FTP, or /location/of/disk/space/ HTTP and verify access from a client system.
Page 14: Using Iso Images For Nfs Installs
Chapter 1. Steps to Get You Started If the directory does not appear in the NFS shared directory, the wrong path may RedHat/ have been mounted and/or exported. • FTP and HTTP installations also support a second type of tree structure. To make it easier to...
Page 15: Installing Under Z/Vm
Make the correct DASDs accessible to the new VM or LPAR, and then proceed with installation. Additionally, if a file called exists in the directory from which you RedHat/base/updates.img install, it is used for installation program updates. Refer to the file in the install-methods.txt...
Page 16 80 • • get kernel.img (repl • get initrd.img (repl • ascii • get redhat.parm (repl • quit You may now create the parameter file (for example, ). Refer to Appendix B, redhat.parm Sample Parameter Files for sample files.
Page 17 Example file: redhat.exec /* */ 'cl rdr' 'purge rdr all' 'spool punch * rdr' 'PUNCH KERNEL IMG A (NOH' 'PUNCH REDHAT PARM A (NOH' 'PUNCH INITRD IMG A (NOH' 'ch rdr all keep nohold' 'i 00c' Example file: redhat.conf HOSTNAME="foobar.zSeries.example.com"...
Page 18 Chapter 1. Steps to Get You Started • DASD=<dasd-list> Where represents the list of DASD devices to be used by Red Hat Enterprise <dasd-list> Linux. Although autoprobing for DASDs is done if this parameter is omitted, it is highly recommended to include the parameter, as the device numbers (and therefore the DASD= device names) can vary when a new DASD is added to the Red Hat Enterprise Linux guest.
Page 19 Installing under z/VM • PEERID=<userid> Where represents the ID of the guest machines you want to connect to. Note that <userid> the ID must be written in capital letters. For example, a PEERID connection to a z/VM TCP/IP service machine should be written as: PEERID=TCPIP Note that the PEERID parameter replaces the IUCV parameter used with the Linux kernel version 2.4.
Page 20 Chapter 1. Steps to Get You Started DNS=10.0.0.1:10.0.0.2 • SEARCHDNS=<domain1>:<domain2>:…:<domainN> Where is a list of the search domains, separated by <domain1>:<domain2>:…:<domainN> colons. For example: SEARCHDNS=example.com:example.org • PORTNAME=<osa_portname> <lcs_portnumber> This variable supports OSA devices operating in qdio mode or non-qdio mode. When using qdio mode: is the portname specified on the OSA device <qeth_portname>...
Page 21: Installing On A Zseries Lpar: Preparation
The following sample script is a typical initial start-up script: /* */ 'CL RDR' 'PURGE RDR ALL' 'SPOOL PUNCH * RDR' 'PUNCH KERNEL IMG A (NOH' 'PUNCH REDHAT PARM A (NOH' 'PUNCH INITRD IMG A (NOH' 'CH RDR ALL KEEP NOHOLD' 'IPL 00C CLEAR'...
Page 22: Interactive Setup
Chapter 1. Steps to Get You Started When Red Hat Enterprise Linux runs in in LPAR, it attempts to acquire information about all devices granted to the LPAR. This could result in an out-of-memory condition on installations with a large number of devices. However, this can be avoided with the use of the cio_ignore kernel parameter.
Page 23: Installing In An Lpar Without The Red Hat Enterprise Linux For S/390 Cd-Roms
• 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)
Page 24: Do You Have Enough Disk Space
Chapter 1. Steps to Get You Started LPAR icon is disappearing, the installation program has begun), select the LPAR and double-click on Operating System Messages. The initial installation start-up script asks you questions about your networking and DASD configurations. Red Hat Enterprise Linux 5.0.0 has changed the limit for parameter file definitions and now accepts thirty-two (32) parameters.
Page 25: Installing Red Hat Enterprise Linux
Chapter 2. Installing Red Hat Enterprise Linux This chapter explains how to perform a Red Hat Enterprise Linux installation using the graphical, mouse-based installation program. The following topics are discussed: • Becoming familiar with the installation program's user interface • Starting the installation program •...
Page 26 Chapter 2. Installing Red Hat Enterprise Linux Figure 2.1. Installation Program Widgets as seen in Boot Loader Configuration...
Page 27: Using The Keyboard To Navigate
Using the Keyboard to Navigate Figure 2.2. Installation Program Widgets as seen in Disk Druid Here is a list of the most important widgets shown in Figure 2.1, “Installation Program Widgets as seen in Boot Loader Configuration” Figure 2.2, “Installation Program Widgets as seen in Disk Druid”: •...
Page 28: Running The Installation Program
Chapter 2. Installing Red Hat Enterprise Linux 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.
Page 29: Installation Using Vnc
Installation using VNC ssh -X linuxvm.example.com option enables X11 forwarding. The graphical installation program cannot be started if your DNS or hostnames are not set correctly, or the Linux image is not allowed to open applications on your display. You can prevent this by setting a correct variable.
Page 30: Installing Via Nfs
Installation”, you would enter the directory which contains the directory. /location/of/disk/space/ RedHat/ If the NFS server is exporting a mirror of the Red Hat Enterprise Linux installation tree, enter the directory which contains the directory. (If you do not know this directory path, ask your RedHat/ system administrator.) For example, if the NFS site contains the directory...
Page 31: Installing Via Ftp
Enter the name or IP address of the FTP site you are installing from, and the name of the directory containing the installation files for your architecture. For example, if the FTP RedHat/ site contains the directory , enter /mirrors/redhat/arch/RedHat/...
Page 32: Installing Via Http
Enter the name or IP address of the HTTP site you are installing from, and the name of the directory containing the installation files for your architecture. For example, if the HTTP RedHat/ site contains the directory , enter /mirrors/redhat/arch/RedHat/...
Page 33: Welcome To Red Hat Enterprise Linux
Welcome to Red Hat Enterprise Linux You can save disk space by using the ISO images you have already copied to the server. To accomplish this, install Red Hat Enterprise Linux using ISO images without copying them into a single tree by loopback mounting them. For each ISO image: mkdir discX mount -o loop example-1.iso discX...
Page 34: Disk Partitioning Setup
Chapter 2. Installing Red Hat Enterprise Linux installation. The installation program tries to define the appropriate time zone based on what you specify on this screen. Figure 2.6. Language Selection Once you select the appropriate language, click Next to continue. 8.
Page 35 Disk Partitioning Setup Warning The Red Hat Update Agent downloads updated packages to by default. If you partition the system manually, and /var/spool/up2date/ create a separate partition, be sure to create the partition large enough /var/ (3.0 GB more more) to download package updates. Figure 2.7.
Page 36: Partitioning Your System
Chapter 2. Installing Red Hat Enterprise Linux it must be initialized, causing the loss of ALL DATA on this drive. you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program.
Page 37: Graphical Display Of Dasd Device(S)
Graphical Display of DASD Device(s) The partitioning tool used by the installation program is Disk Druid. With the exception of certain esoteric situations, Disk Druid can handle the partitioning requirements for a typical installation. 9.1. Graphical Display of DASD Device(s) Disk Druid offers a graphical representation of your DASD device(s).
Page 38: Recommended Partitioning Scheme
Chapter 2. Installing Red Hat Enterprise Linux point. Double-click on the partition or click the Edit button. • Type: This field shows the partition's file system type (for example, ext2 or ext3). • Format: This field shows if the partition being created will be formatted. •...
Page 39: Editing Partitions
Editing Partitions you perform a full installation, choosing all package groups. Warning You must create a partition of type VFAT and at least 100 MB in /boot/efi/ size as the first primary partition. If your hard drive is more than 1024 cylinders (and your system was manufactured more than two years ago), you may need to create a /boot/ partition if you want the...
Page 40: Network Configuration
Chapter 2. Installing Red Hat Enterprise Linux To edit a partition, select the Edit button or double-click on the existing partition. Note If the partition already exists on your hard disk, you can only change the partition's mount point. To make any other changes, you must delete the partition and recreate it.
Page 41 Network Configuration if DHCP is not selected) and you can choose to activate the device at boot time. If you select Activate on boot, your network interface is started when you boot. If you do not have DHCP client access or you are unsure what to provide here, please contact your network administrator. Note DHCP is not available for automatic configuration of CTC/Escon devices.
Page 42: Firewall Configuration
Chapter 2. Installing Red Hat Enterprise Linux Finally, if you entered the IP and Netmask information manually, you may also enter the Gateway address and the Primary, Secondary, and Tertiary DNS addresses. Even if your computer is not part of a network, you can enter a hostname for your system.
Page 43 Firewall Configuration Figure 2.11. Firewall Configuration Next, you can decide whether to enable a firewall for your Red Hat Enterprise Linux system. No firewall No firewall provides complete access to your system and does no security checking. Security checking is the disabling of access to certain services. This should only be selected if you are running on a trusted network (not the Internet) or plan to do more firewall configuration later.
Page 44 Chapter 2. Installing Red Hat Enterprise Linux Enabling these options allow the specified services to pass through the firewall. Note, these services may not be installed on the system by default. Make sure you choose to enable any options that you may need. Remote Login (SSH) Secure Shell (SSH) is a suite of tools for logging in to and executing commands on a remote machine.
Page 45: Language Support Selection
Choose this state only if you are sure that your system can still properly function with SELinux fully enabled. For additional information about SELinux, refer to the following URLs: • http://www.redhat.com/docs/ • http://www.nsa.gov/selinux/ To change your security configuration after you have completed the installation, use the Security Level Configuration Tool.
Page 46 Chapter 2. Installing Red Hat Enterprise Linux You must select a language to use as the default language. The default language is the language used on the system once the installation is complete. Typically, the default language is the language you selected to use during the installation. If you choose to install other languages during this installation, you can change your default language after the installation.
Page 47: Time Zone Configuration
Time Zone Configuration language you selected for use during the installation is installed. To change the language configuration after you have completed the installation, use the Language Configuration Tool. Type the command in a shell prompt to launch the system-config-language Language Configuration Tool.
Page 48: Set Root Password
Chapter 2. Installing Red Hat Enterprise Linux Figure 2.13. Configuring the Time Zone Select System Clock uses UTC if you know that your system is set to UTC. To change your time zone configuration after you have completed the installation, use the Time and Date Properties Tool. Type the command in a shell prompt to launch the Time system-config-date...
Page 49 Set Root Password machines. 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. Note The root user (also known as the superuser) has complete access to the entire system;...
Page 50: Package Group Selection
Chapter 2. Installing Red Hat Enterprise Linux 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;...
Page 51 Package Group Selection default package selection or customize packages for your system. The Package Installation Defaults screen appears and details the default package set for your Red Hat Enterprise Linux installation. This screen varies depending on the version of Red Hat Enterprise Linux you are installing.
Page 52 Chapter 2. Installing Red Hat Enterprise Linux Figure 2.15. Package Group Selection Select each component you wish to install. Selecting Everything (at the end of the component list) installs all packages included with Red Hat Enterprise Linux. Once a package group has been selected, click on Details to view which packages are installed by default, and to add or remove optional packages from that group.
Page 53: Preparing To Install
Preparing to Install Figure 2.16. Package Group Details 16. Preparing to Install A screen preparing you for the installation of Red Hat Enterprise Linux now appears. For your reference, a complete log of your installation can be found in /root/install.log once you reboot your system.
Page 54: Installing Packages
For more information on using the Setup Agent, refer to the chapter titled Getting Started in the Red Hat Enterprise Linux Step By Step Guide. For information on registering your Red Hat Enterprise Linux subscription, refer to https://www.redhat.com/apps/activate/.
Page 55: Removing Red Hat Enterprise Linux
Appendix A. Removing Red Hat Enterprise Linux To remove Red Hat Enterprise Linux from the S/390 you can either remove the DASD allocation from the VM or you can start the installation program and re-format all of the DASD partitions. Instead of selecting OK you will select Cancel to exit the installation program.
Page 57: Sample Parameter Files
It is specified in a Linux style file name format. The CMS file is specified as . This option is applicable only for users who REDHAT CONF redhat.conf have a CMS formatted disk (z/VM) available. For example: CMSCONFFILE=redhat.conf...
Page 58 Appendix B. Sample Parameter Files qeth: SUBCHANNELS="<read_device_bus_id>,<write_device_bus_id>, <data_device_bus_id>" lcs: SUBCHANNELS="<read_device_bus_id>,<write_device_bus_id>" ctc: SUBCHANNELS="<read_device_bus_id>,<write_device_bus_id>" Due to the length of the qeth command line, it has been broken into two lines. For example (a sample qeth SUBCHANNEL statement): SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 To force a specific CTC protocol, additional parameters can be added. For example: CTCPROT=<n>...
Page 59 NETWORK=<network> Where is the address of your network. <network> NETMASK=<netmask> Where is the netmask. <netmask> BROADCAST=<broadcast> Where is the broadcast address. <broadcast> GATEWAY=<gw> Where is either the gateway-IP for your eth device or the IP address of the <gw> ctc/escon/iucv point-to-point partner. MTU=<mtu>...
Page 60 The Red Hat Enterprise Linux installation program prompts the user for any required parameters not specified in the parameter file. Sample file configuring a CTC networking device: Example of file: redhat.parm root=/dev/ram0 ro ip=off ramdisk_size=40000 CMSDASD=191 CMSCONFFILE=redhat.conf Example of file (pointed to by CMSCONFFILE in redhat.conf redhat.parm DASD=200 HOSTNAME=client.z900.example.com NETTYPE=ctc IPADDR=192.168.0.10...
Page 61: Upgrading Your Current System
This recommended reinstallation method helps to ensure the best system stability possible. For more information about re-installing your Red Hat Enterprise Linux system, refer to the Whitepapers available online at http://www.redhat.com/solutions/info/whitepapers/. If you currently use Red Hat Enterprise Linux 3, you can perform a traditional, installation program-based upgrade.
Page 62: Upgrading Your System
Note If the contents of your file have been changed from the /etc/redhat-release default, your Red Hat Enterprise Linux installation may not be found when attempting an upgrade to Red Hat Enterprise Linux 5.0.0. You can relax some of the checks against this file by booting with the following...
Page 63: Upgrading Packages
At this point, there is nothing left for you to do until all the packages have been upgraded or installed. 4. Upgrade Complete Congratulations! Your Red Hat Enterprise Linux 5.0.0 upgrade is now complete! The installation program prompts you to prepare your system for reboot. For information on registering your Red Hat Enterprise Linux subscription, refer to https://www.redhat.com/apps/activate/.
Page 65: Troubleshooting Your Installation Of Red Hat Enterprise Linux
Appendix D. Troubleshooting Your Installation of Red Hat Enterprise Linux This appendix discusses some common installation problems and their solutions. 1. You are Unable to Boot Red Hat Enterprise Linux 1.1. Is Your System Displaying Signal 11 Errors? A signal 11 error, commonly know as a segmentation fault, means that the program accessed a memory location that was not assigned.
Page 66: Other Partitioning Problems
Appendix D. Troubleshooting Your Installation of Red Hat Enterprise Linux phase of the installation saying something similar to The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive. you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program.
Page 67: Problems After Installation
If you experience such an error, first try to download any available errata for anaconda. Errata can be found at: http://www.redhat.com/support/errata/ The anaconda website may also be a useful reference and can be found online at: http://rhlinux.redhat.com/anaconda/ You can also search for bug reports related to this problem.
Page 68: Problems When You Try To Log In
If the graphical login screen does not appear, check your hardware for compatibility issues. The Hardware Compatibility List can be found at: http://hardware.redhat.com/ 3.3. Your Printer Does Not Work If you are not sure how to set up your printer or are having trouble getting it to work properly, try using the Printer Configuration Tool.
Page 69 Apache-based service/Sendmail httpd make sure the following line is in the file: /etc/hosts 127.0.0.1 localhost.localdomain localhost...
Page 71: Additional Boot Options
Appendix E. Additional Boot Options This appendix discusses additional boot and kernel boot options available for the Red Hat Enterprise Linux installation program. Add these boot options to the parameter file. For more information, refer to Section 5, “Installing under z/VM”.
Page 72 Appendix E. Additional Boot Options This command allows you to install from a VNC server. vncpassword= This command sets the password used to connect to the VNC server.
Page 73: Additional Information For S/390 And Zseries Users
Appendix F. Additional Information for S/390 and zSeries Users 1. The File System sysfs The Linux 2.6 kernel introduces the file system. The file system is described as a sysfs sysfs union of the , and file systems. The file system enumerates the proc devfs devpty...
Page 74: Using The Driver
Appendix F. Additional Information for S/390 and zSeries Users This contains directories that group together similar devices such as ttys, SCSI tape drives, network devices, and other miscellaneous devices. 4. The directory /block/ This directory contains directories for each of the block devices on the system. These are mostly disk type devices such as real DASD, loopback devices, and software raid block devices.
Page 75 Using the Driver zFCP ipt_state 18944 ip_conntrack 57904 1 ipt_state iptable_filter 19712 ip_tables 37888 3 ipt_REJECT,ipt_state,iptable_filter sd_mod 39688 scsi_mod 182904 2 zfcp,sd_mod dm_mod 86408 ext3 179056 92720 1 ext3 dasd_fba_mod 25344 dasd_eckd_mod 77056 dasd_mod 85328 6 dasd_fba_mod,dasd_eckd_mod # cd /sys/bus/ccw/drivers/zfcp/0.0.010a # echo 1 >...
Page 76 Appendix F. Additional Information for S/390 and zSeries Users # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/scsi_id # cat \ /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/0x5719000000000000/scsi_lun # cat /sys/bus/scsi/devices/0\:0\:1\:0/hba_id 0.0.010a # cat /sys/bus/scsi/devices/0\:0\:1\:0/wwpn 0x5005076300c18154 # cat /sys/bus/scsi/devices/0\:0\:1\:0/fcp_lun 0x5719000000000000 # cat /sys/bus/scsi/devices/0\:0\:1\:0/block/dev # cat /sys/bus/scsi/devices/0\:0\:1\:0/block/sda1/dev # cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 01 Lun: 00 Vendor: IBM Model: 2105F20 Rev: .123...
Page 77 Using the Driver zFCP Type: Direct-Access ANSI SCSI revision: 03 # fdisk /dev/sda # mke2fs -j /dev/sda1 # mount /dev/sda1 /mnt # df Filesystem 1K-blocks Used Available Use% Mounted on /dev/dasda1 2344224 1427948 797196 65% / none 511652 511652 0% /dev/shm /dev/dasdb1 2365444 32828...
Page 78 Appendix F. Additional Information for S/390 and zSeries Users `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_fba_mod.ko' -> `/tmp/initrd.cT1534/lib/dasd_fba_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/fs/jbd/jbd.ko' -> `/tmp/initrd.cT1534/lib/jbd.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/fs/ext3/ext3.ko' -> `/tmp/initrd.cT1534/lib/ext3.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/scsi/scsi_mod.ko' -> `/tmp/initrd.cT1534/lib/scsi_mod.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/cio/qdio.ko' -> `/tmp/initrd.cT1534/lib/qdio.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/scsi/zfcp.ko' -> `/tmp/initrd.cT1534/lib/zfcp.ko' `/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/scsi/sd_mod.ko' -> `/tmp/initrd.cT1534/lib/sd_mod.ko' Loading module dasd_mod with options dasd=201,4b2e Loading module dasd_eckd_mod Loading module dasd_fba_mod Loading module jbd Loading module ext3 Loading module scsi_mod...
Page 79: Using Mdadm To Configure Raid-Based And Multipath Storage
Using to Configure RAID-Based and mdadm Syncing disks... Done. 3. Using to Configure RAID-Based and Multipath mdadm Storage Similar to other tools comprising the package set, the command can be used raidtools mdadm to perform all the necessary functions related to administering multiple-device sets. This section explains how can be used to: mdadm...
Page 80: Creating A Multipath Device With
Appendix F. Additional Information for S/390 and zSeries Users Next, use the above configuration and the command to create a RAID 0 array: mdadm mdadm -C /dev/md0 --level=raid0 --raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 \ /dev/sdd1 Continue creating array? yes mdadm: array /dev/md0 started. Once created, the RAID device can be queried at any time to provide status information.
Page 81 Multipath Storage To provide a single device that can remain accessible if an I/O path fails or becomes saturated, includes an additional parameter to its option. This parameter — — mdadm ––level multipath directs the md layer in the Linux kernel to re-route I/O requests from one pathway to another in the event of an I/O path failure.
Page 82: Configuring Ipl From A Scsi Device
Appendix F. Additional Information for S/390 and zSeries Users Working Devices : 4 Failed Devices : 0 Spare Devices : 3 Number Major Minor RaidDevice State active sync /dev/sdd1 spare /dev/sdb1 spare /dev/sdc1 spare /dev/sda1 UUID : 4b564608:fa01c716:550bd8ff:735d92dc Events : 0.1 Another feature of is the ability to force a device (be it a member of a RAID array or a mdadm...
Page 83: Adding Dasd
00: MLOEVL012I: Machine loader up and running (version 0.13). 00: MLOPDM003I: Machine loader finished, moving data to final storage location. Linux version 2.6.7-1.451.2.3 (bhcompile@example.z900.redhat.com) (gcc version 3.4 .1 20040702 (Red Hat Linux 3.4.1-2)) #1 SMP Wed Jul 14 17:52:22 EDT 2004...
Page 84 Appendix F. Additional Information for S/390 and zSeries Users -rw-r--r-- 1 root root 4096 Aug 25 17:04 detach_state -r--r--r-- 1 root root 4096 Aug 25 17:04 devtype -r--r--r-- 1 root root 4096 Aug 25 17:04 discipline -rw-r--r-- 1 root root 4096 Aug 25 17:04 online -rw-r--r-- 1 root root 4096 Aug 25 17:04 readonly -rw-r--r--...
Page 85 Adding DASD # fdasd -a /dev/dasdb auto-creating one partition for the whole disk... writing volume label... writing VTOC... checking ! wrote NATIVE! rereading partition table... Next, make a file system on the new partition: # mke2fs -j /dev/dasdb1 mke2fs 1.35 (28-Feb-2004) Filesystem label= OS type: Linux Block size=4096 (log=2)
Page 86 Appendix F. Additional Information for S/390 and zSeries Users none /dev/pts devpts gid=5,mode=620 none /dev/shm tmpfs defaults none /proc proc defaults none /sys sysfs defaults /dev/dasdb1 /opt ext3 defaults Add the device to the option line for the dasd_mod in Make sure to add /etc/modprobe.conf the new device at the end of the list, otherwise it changes the...
Page 87 Adding a Network Device /lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_eckd_mod.ko (elf64-s390) to /tmp/initrd.AR1182/lib/dasd_eckd_mod.ko (elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_fba_mod.ko (elf64-s390) to /tmp/initrd.AR1182/lib/dasd_fba_mod.ko (elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/fs/jbd/jbd.ko(elf64-s390) to /tmp/initrd.AR1182/lib/jbd.ko(elf64-s390) copy from /lib/modules/2.6.7-1.451.2.3/./kernel/fs/ext3/ext3.ko(elf64-s390) to /tmp/initrd.AR1182/lib/ext3.ko(elf64-s390) Loading module dasd_mod with options dasd=201,4B2E Loading module dasd_eckd_mod Loading module dasd_fba_mod Loading module jbd Loading module ext3 to save the changes to for the next IPL:...
Page 88: Adding A Network Device
Appendix F. Additional Information for S/390 and zSeries Users 6. Adding a Network Device The process of adding a network device has changed greatly for Red Hat Enterprise Linux. This is due in part to the migration of the 2.4 kernel to the 2.6 kernel: •...
Page 89 Adding a Device qeth Due to the length of this command, it has been broken into two lines. In the following example, is 0.0.0600, is 0.0.0601, read_device_bus_id write_device_bus_id is 0.0.0602. The device is a z/VM virtual NIC and the IP address to data_device_bus_id be assigned to this interface is 192.168.70.69.
Page 90 Appendix F. Additional Information for S/390 and zSeries Users A return value of "1" indicates that the device is online, while a return value '0' indicates that the device is offline. Check to see what interface name was assigned to the device: # cat /sys/bus/ccwgroup/drivers/qeth/0.0.0600/if_name eth1 To change the value of...
Page 91 Adding a Device qeth • state • ungroup • vipa For information on how these features work, refer to http://www-128.ibm.com/developerworks/linux/linux390/april2004_documentation.html (Linux for zSeries and S/390 Device Drivers, Features, and Commands). Now you need to create the configuration file for your new interface. The network interface configuration files are placed in /etc/sysconfig/network-scripts/ The network configuration files use the naming convention ifcfg-<...
Page 92 Appendix F. Additional Information for S/390 and zSeries Users If you want your new interface to be activated at boot time, then make sure ONBOOT is set to Make sure the SUBCHANNELS statement matches the hardware addresses for your qeth device.
Page 93: Quick Reference For Adding Network Devices
Quick Reference for Adding Network HWADDR=02:00:00:00:00:01 looks similar to the following: ifcfg-eth1 # IBM QETH DEVICE=eth1 HWADDR=02:00:00:00:00:01 BOOTPROTO=static IPADDR=192.168.70.69 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602 TYPE=Ethernet Check the routing for the new interface: # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.70.0...
Page 94 Appendix F. Additional Information for S/390 and zSeries Users • Set the device online (not applicable to IUCV). • Define the alias (if needed). • Create a configuration script. • Activate the device. The following sections provide basic information for each task of each zSeries network device driver.
Page 95 Devices http://oss.software.ibm.com/developerworks/opensource/linux390/docu/lx26apr04dd01.pdf (Linux for zSeries and S/390 Device Drivers, Features, and Commands) • Set the device online: # echo 1 /sys/bus/ccwgroup/drivers/lcs/<read_device_bus_id>/online • Define the alias. Based on the type interface being added, add a line to that is similar to /etc/modprobe.conf one of the following: eth<n>...
Page 96 Appendix F. Additional Information for S/390 and zSeries Users • Activate the device. Based on the type interface being added, issue an command: ifup # ifup eth<n> # ifup tr<n> 6.2.2. Working With the QETH Device Driver The QETH network device driver supports zSeries HiperSockets, OSA-Express Fast Ethernet, Gigabit Ethernet (including 1000Base-T), High Speed Token Ring, and ATM features (running Ethernet LAN emulation) in QDIO mode.
Page 97 Quick Reference for Adding Network • Set the device online: # echo 1 /sys/bus/ccwgroup/drivers/qeth/<read_device_bus_id>/nline • Define the alias. Based on the type interface being added, add a line to that is like one /etc/modprobe.conf of the following: hsi<n> alias qeth eth<n>...
Page 98 Appendix F. Additional Information for S/390 and zSeries Users Based on the type interface being added, issue an command: ifup # ifup hsi<n> # ifup eth<n> # ifup tr<n> 6.2.3. Working With the CTC Device Driver A Channel-to-Channel (CTC) connection is the typical high speed connection between mainframes.
Page 99 Devices Where is 0, 1, 2, or 3. <protocol> 0 — This protocol provides compatibility with peers other than OS/390, or z/OS, for example, a VM TCP service machine. This is the default. 1 — This protocol provides enhanced package checking for Linux peers. 2 —...
Page 100 Appendix F. Additional Information for S/390 and zSeries Users TYPE=CTC • Activate the device. Based on the type interface being added, issue an command: ifup # ifup ctc<n> 6.2.4. Working With the IUCV Device Driver The Inter-User Communication Vehicle (IUCV) is a VM communication facility that enables a program running in one VM guest to communicate with another VM guest, with a control program, or even with itself.
Page 101 Quick Reference for Adding Network The value is an integer that uniquely identifies the device. is 0 for the first device of <n> <n> that type, 1 for the second, and so on. • Configure the device. Set the maximum buffer size if needed: # echo <value>...
Page 102: Kernel-Related Information
Appendix F. Additional Information for S/390 and zSeries Users NETTYPE=iucv PEERID=TCPIP TYPE=IUCV • Activate the device. Based on the type interface being added, issue an command like the following: ifup # ifup iucv<n> 7. Kernel-Related Information Red Hat Enterprise Linux includes a modification to the way the Linux kernel timer interrupt is handled.
Page 103 If you notice a malfunction related to system accounting, verify that the malfunction disappears if periodic timer interrupts are enabled, then submit a bug at http://bugzilla.redhat.com/bugzilla/ (for malfunctioning bundled tools), or inform the tool vendor (for malfunctioning third-party tools).
Page 105: Index
contact information for this manual, ix Index firewall configuration, 32 customize incoming services, 33 customize trusted services, 33 Symbols security levels enable firewall, 33 /boot/, 29 no firewall, 33 /boot/ partition recommended partitioning, 28 installation, 2, 21 /root/install.log install log file location, 43 /var/ partition graphical installation program recommended partitioning, 28...
Page 106 Index starting, 18 ICUV device driver, 90 installing LCS device driver, 84 without the LPAR CD QETH device driver, 86 using a recent SEW, 13 network installation without the Red Hat Enterprise Linux for preparing for, 2 S/390 CD-ROMs, 13 installing packages, 40 installation, 2, 20 introduction, vii...
Page 107 selecting packages, 40 SELinux x11 forwarding, 18 security levels, 34 XDMCP, 57 steps disk space, 14 steps to get you started, 1 z/VM swap, 29 installing, 5 swap file zFCP driver, 64 upgrade, 52 swap parition recommended partitioning, 28 sysfs file system, 63 time zone configuration, 37 troubleshooting, 55...

This manual is also suitable for:

Enterprise linux 4

Red Hat ENTERPRISE LINUX 4 - INSTALLATION GUIDE FOR IBM S-390 AND IBM ESERVER ZSERIES Installation Manual

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Red Hat ENTERPRISE LINUX 4 - INSTALLATION GUIDE FOR IBM S-390 AND IBM ESERVER ZSERIES

Summary of Contents for Red Hat ENTERPRISE LINUX 4 - INSTALLATION GUIDE FOR IBM S-390 AND IBM ESERVER ZSERIES

This manual is also suitable for:

Table of Contents