Red Hat Enterprise Linux 4 Installation Guide for the IBM® S/390® and IBM® eServer™ zSeries® Architectures
Red Hat Enterprise Linux 4: Installation Guide for the IBM® S/390® and IBM® eServer™ zSeries® Architectures Copyright © 2005 Red Hat, Inc. Red Hat, Inc. 1801 Varsity Drive Raleigh NC 27606-2072 USA Phone: +1 919 754 3700 Phone: 888 733 4281 Fax: +1 919 754 3701 PO Box 13588 Research Triangle Park NC 27709 USA rhel-ig-s390(EN)-4-Print-RHI (2004-09-24T13:10) Copyright © 2005 by Red Hat, Inc.
Table of Contents Introduction.......................................................................................................................................... i 1. Document Conventions .......................................................................................................... i 2. How to Use This Manual ..................................................................................................... iii 2.1. We Need Feedback! .....................................................
A. Removing Red Hat Enterprise Linux......................................................................................... 37 B. Sample Parameter Files ............................................................................................................... 39 C. Upgrading Your Current System................................................................................................ 43 C.1. Determining Whether to Upgrade or Re-Install ............................................................
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 4. 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. Document Conventions When you read this manual, certain words are represented in different fonts, typefaces, sizes, and weights.
ii Introduction text found on a GUI interface A title, word, or phrase found on a GUI interface screen or window is shown in this style. Text shown in this style is being used to identify a particular GUI screen or an element on a GUI screen (such as text associated with a checkbox or field). Example: Select the Require Password checkbox if you would like your screensaver to require a password before stopping.
Introduction iii The directory for the kernel source is /usr/src//, where is the version of the kernel installed on this system. Additionally, we use several different strategies to draw your attention to certain pieces of information. In order of how critical the information is to your system, these items are marked as a note, tip, important, caution, or warning. For example: Note Remember that Linux is case sensitive. In other words, a rose is not a ROSE is not a rOsE.
iv Introduction If you are an experienced user and you do not need a review of the basics, you can skip ahead to Chapter 2 Installing Red Hat Enterprise Linux to begin the installation process. 2.1. We Need Feedback! If you discover a typo in the Red Hat Enterprise Linux Installation Guide or have thought of a way to make this manual better, we would love to hear from you. Submit a bug report against the component rhel-ig-s390 in Bugzilla at: http://bugzilla.redhat.
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/ 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. Note For the most current IBM resources, visit http://www.ibm.
2 Chapter 1. Steps to Get You Started After the installation, more DASD or SCSI (for zSeries only) disk partitions may be added or deleted as necessary. 1.2. Basic Overview of the Boot Method To prepare for installation, you must have the Linux kernel (kernel.img), the ram disk (initrd.img), a CMS configuration file (generic.conf) and a parameter file. Sample parameter and CMS configuration files are provided (generic.prm and generic.conf).
Chapter 1. Steps to Get You Started • 3 Note that the Release Notes are not included in the RedHat directory. Unless they are specifically copied over, the Release Notes will not be available during your installation of Red 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.
4 Chapter 1. Steps to Get You Started 1.4. Preparing for a Hard Drive Installation Note DASD installations only work from ext2 or ext3 file systems. If you have a file system other than ext2 or ext3 you will not be able to perform a DASD installation. To prepare your system for a hard drive installation, you must set the system up in one of the following ways: • Using a set of CD-ROMs — Create CD-ROM ISO image files from each installation CD-ROM.
Chapter 1. Steps to Get You Started 5 • cd /location/of/boot/images/ • locsite fix 80 • bin • get kernel.img (repl • get initrd.img (repl • ascii • get redhat.parm (repl • quit You may now create the parameter file (for example, redhat.parm). Refer to Appendix B Sample Parameter Files for sample parm files. Below is an explanation of the parm file contents. There is a limit of 32 total parameters in the parameter file.
6 Chapter 1. Steps to Get You Started BROADCAST="192.168.17.255" SEARCHDNS="example.com:zSeries.example.com" GATEWAY="192.168.17.254" DNS="192.168.17.1" MTU="4096" The following parameters are required and must be included in the parameter file: • DASD= Where represents the list of DASD devices to be used by Red Hat Enterprise Linux.
Chapter 1. Steps to Get You Started 7 • NETTYPE= Where must be one of the following: ctc, iucv, lcs, or qeth. • IPADDR= Where is the IP address of the new Linux guest. • NETWORK= Where is the address of your network. • NETMASK= Where is the netmask. • BROADCAST= Where is the broadcast address.
8 Chapter 1. Steps to Get You Started • • refers to the local SCSI logical unit value and is specified as a hex-value, typically sequential values (e.g. 0x00, 0x01, ...) are used over multiple FCP_ variables. refers to the storage logical unit identifier and is specified as a hex-value (such as 0x4010). Note Each of the values used in the FCP parameters (FCP_1, FCP_2, ...) are site-specific and are normally supplied by the FCP storage administrator.
Chapter 1. Steps to Get You Started 9 1.6. Installing in an LPAR using the Red Hat Enterprise Linux LPAR CD The following steps must be taken when installing Red Hat Enterprise Linux onto an LPAR. • Log in on the Hardware Master Console (HMC) or the Support Element Workplace (SEW) as a user with sufficient privileges to install a new OS to an LPAR. The SYSPROG user is recommended. • Select Images, then select the LPAR to which you wish to install.
10 Chapter 1. Steps to Get You Started 1.8. Installing in an LPAR (Common Steps) Once the Red Hat Enterprise Linux installation program has started (if the red field behind the 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.
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 • Selecting an installation method • Configuration steps during the installation (language, keyboard, mouse, partitioning, etc.) • Finishing the installation 2.1.
12 Chapter 2. Installing Red Hat Enterprise Linux Figure 2-1. Installation Program Widgets as seen in Boot Loader Configuration 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 and Figure 2-2: • Window — Windows (usually referred to as dialogs in this manual) appear on your screen throughout the installation process. At times, one window may overlay another; in these cases, you can only interact with the window on top.
Chapter 2. Installing Red Hat Enterprise Linux 13 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.
14 Chapter 2. Installing Red Hat Enterprise Linux the graphical installation offers more package selection details and other options not available in text-based installs. It is strongly recommended to use the graphical installation whenever possible. To run the graphical installation, use a workstation that has an X Window System server or VNC client installed. Use an SSH client that allows X11 forwarding or a Telnet client.
Chapter 2. Installing Red Hat Enterprise Linux 15 After you have identified the disk partition, the Welcome dialog appears. 2.5. Installing via NFS The NFS dialog applies only if you are installing from an NFS server (if you selected NFS Image in the Installation Method dialog). Enter the domain name or IP address of your NFS server. For example, if you are installing from a host named eastcoast in the domain example.com, enter eastcoast.example.com in the NFS Server field.
16 Chapter 2. Installing Red Hat Enterprise Linux Figure 2-4. FTP Setup Dialog Enter the name or IP address of the FTP site you are installing from, and the name of the directory containing the RedHat/ installation files for your architecture. For example, if the FTP site contains the directory /mirrors/redhat/arch/RedHat/, enter /mirrors/redhat/arch/ (where arch is replaced with the architecture type of your system, such as i386, ia64, ppc, or s390).
Chapter 2. Installing Red Hat Enterprise Linux 17 Figure 2-5. HTTP Setup Dialog Next, the Welcome dialog appears. Tip 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 2.8. Welcome to Red Hat Enterprise Linux The Welcome screen does not prompt you for any input.
18 Chapter 2. Installing Red Hat Enterprise Linux 2.10. Language Selection Using your mouse, select a language to use for the installation (refer to Figure 2-6). 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. Figure 2-6. Language Selection Once you select the appropriate language, click Next to continue. 2.11.
Chapter 2. Installing Red Hat Enterprise Linux 19 Warning The Red Hat Update Agent downloads updated packages to /var/spool/up2date/ by default. If you partition the system manually, and create a separate /var/ partition, be sure to create the partition large enough (3.0 GB more more) to download package updates. Figure 2-7. Disk Partitioning Setup If you chose to manually partition using Disk Druid, refer to Section 2.13 Partitioning Your System.
20 Chapter 2. Installing Red Hat Enterprise Linux 2.12. Automatic Partitioning Automatic partitioning allows you to have some control concerning what data is removed (if any) from your system. Your options are: • Remove all Linux partitions on this system — select this option to remove only Linux partitions (partitions created from a previous Linux installation). This does not remove other partitions you may have on your hard drive(s).
Chapter 2. Installing Red Hat Enterprise Linux 21 for you in Disk Druid appear. You can make modifications to these partitions if they do not meet your needs. Click Next once you have made your selections to proceed. 2.13. Partitioning Your System If you chose to partition manually, you must tell the installation program where to install Red Hat Enterprise Linux. This is done by defining mount points for one or more disk partitions in which Red Hat Enterprise Linux is installed. Figure 2-9.
22 Chapter 2. Installing Red Hat Enterprise Linux 2.13.2. Disk Druid’s Buttons These buttons control Disk Druid’s actions. They are used to change the attributes of a partition (for example the file system type and mount point) and also to create RAID devices. Buttons on this screen are also used to accept the changes you have made, or to exit Disk Druid.
Chapter 2. Installing Red Hat Enterprise Linux • The amount of physical RAM is installed on the machine. • The version of the OS. 23 Swap should equal 2x physical RAM for up to 2 GB of physical RAM, and then 1x physical RAM for any amount above 2 GB, but never less than 32 MB. Using this formula, a system with 2 GB of physical RAM would have 4 GB of swap, while one with 3 GB of physical RAM would have 5 GB of swap.
24 Chapter 2. Installing Red Hat Enterprise Linux Figure 2-10. Network Configuration The installation program automatically detects any network devices you have and display them in the Network Devices list. Once you have selected a network device, click Edit. From the Edit Interface pop-up screen, you can choose to configure the IP address and Netmask of the device via DHCP (or manually if DHCP is not selected) and you can choose to activate the device at boot time.
Chapter 2. Installing Red Hat Enterprise Linux 25 Figure 2-11. Editing a Network Device Note Do not use the numbers as seen in this sample configuration. These values will not work for your own network configuration. If you are not sure what values to enter, contact your network administrator for assistance.
26 Chapter 2. Installing Red Hat Enterprise Linux 2.15. Firewall Configuration Red Hat Enterprise Linux offers firewall protection for enhanced system security. A firewall exists between your computer and the network, and determines which resources on your computer remote users on the network can access. A properly configured firewall can greatly increase the security of your system. Figure 2-12.
Chapter 2. Installing Red Hat Enterprise Linux 27 Remote Login (SSH) Secure Shell (SSH) is a suite of tools for logging in to and executing commands on a remote machine. If you plan to use SSH tools to access your machine through a firewall, enable this option. You need to have the openssh-server package installed in order to access your machine remotely, using SSH tools. Web Server (HTTP, HTTPS) The HTTP and HTTPS protocols are used by Apache (and by other Web servers) to serve webpages.
28 • Chapter 2. Installing Red Hat Enterprise Linux Active — Select Active if you want SELinux to act in a fully active state. The Active state enforces all policies, such as denying access to unauthorized users for certain files and programs, for additional system protection. 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.
Chapter 2. Installing Red Hat Enterprise Linux 29 Figure 2-13. Language Support Selection To use more than one language on your system, choose specific languages to be installed or select all languages to have all available languages installed on your Red Hat Enterprise Linux system. Use the Reset button to cancel your selections. Resetting reverts to the default; only the language you selected for use during the installation is installed.
30 Chapter 2. Installing Red Hat Enterprise Linux Figure 2-14. Configuring the Time Zone Select System Clock uses UTC if you know that your system is set to UTC. Tip 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.
Chapter 2. Installing Red Hat Enterprise Linux 31 Figure 2-15. Root Password Use the root account only for system administration. Create a non-root account for your general use and su - to root when you need to fix something quickly. These basic rules minimize the chances of a typo or an incorrect command doing damage to your system. Tip 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].
32 Chapter 2. Installing Red Hat Enterprise Linux Note Do not use one of the example passwords offered in this manual. Using one of these passwords could be considered a security risk. Tip To change your root password after you have completed the installation, use the Root Password Tool. Type the system-config-rootpassword command in a shell prompt to launch the Root Password Tool. If you are not root, it prompts you for the root password to continue. 2.19.
Chapter 2. Installing Red Hat Enterprise Linux 33 Figure 2-16. 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. Figure 2-17.
34 Chapter 2. Installing Red Hat Enterprise Linux 2.20. 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. Warning If, for some reason, you would rather not continue with the installation process, this is your last opportunity to safely cancel the process and reboot your machine.
Chapter 2. Installing Red Hat Enterprise Linux 35 2.23. Activate Your Subscription Before you can access service and software maintenance information, and the support documentation included in your subscription, you must activate your subscription by registering with Red Hat.
36 Chapter 2.
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.
38 Appendix A.
Appendix B. Sample Parameter Files The IBM S/390(R) and IBM eServer zSeries(R) architectures use a special parameter file to set up networking before the installation program (anaconda) can be started. This section describes the contents of the parameter file. The parameter file has a limit of 32 total parameters. To accommodate limitations of the parameter files, a new configuration file on a CMS DASD should be used to configure the initial network setup and the DASD specification. The .
40 Appendix B. Sample Parameter Files To force a specific CTC protocol, additional parameters can be added.
Appendix B. Sample Parameter Files 41 SEARCHDNS=::...: Where ::...: is a list of the search domains, separated by colons. For example: SEARCHDNS=example.com:example.org PORTNAME= | This variable supports OSA devices operating in qdio mode or in non-qdio mode. When using qdio mode: is the portname specified on the OSA device when operating in qeth mode. PORTNAME is only required for z/VM 4.
42 Appendix B.
Appendix C. Upgrading Your Current System This appendix explains the various methods available for upgrading your Red Hat Enterprise Linux system. C.1. Determining Whether to Upgrade or Re-Install Although upgrades are supported from Red Hat Enterprise Linux 3, you are more likely to have a consistent experience by backing up your data and then installing this release of Red Hat Enterprise Linux 4 over your previous Red Hat Enterprise Linux installation.
44 Appendix C. Upgrading Your Current System lems. Otherwise, the upgrade procedure takes care of these dependencies, but it may need to install additional packages which are not on your system. Depending on how you have partitioned your system, the upgrade program may prompt you to add an additional swap file. If the upgrade program does not detect a swap file that equals twice your RAM, it asks you if you would like to add a new swap file.
Appendix D. Troubleshooting Your Installation of Red Hat Enterprise Linux This appendix discusses some common installation problems and their solutions. D.1. You are Unable to Boot Red Hat Enterprise Linux D.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.
46 Appendix D. Troubleshooting Your Installation of Red Hat Enterprise Linux D.2.3. Other Partitioning Problems If you are using Disk Druid to edit partitions, but cannot move to the next screen, you probably have not created all the partitions necessary for Disk Druid’s dependencies to be satisfied. You must have the following partitions as a bare minimum: • A / (root) partition • A partition of type swap Tip When defining a partition’s type as swap, you do not have to assign it a mount point.
Appendix D. Troubleshooting Your Installation of Red Hat Enterprise Linux 47 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. To search Red Hat’s bug tracking system, go to: http://bugzilla.redhat.
48 Appendix D. Troubleshooting Your Installation of Red Hat Enterprise Linux D.3.2. Problems When You Try to Log In If you did not create a user account in the Setup Agent, log in as root and use the password you assigned to root. If you cannot remember your root password, boot your system as linux single. Once you have booted into single user mode and have access to the # prompt, you must type passwd root, which allows you to enter a new password for root.
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 Section 1.5 Installing under z/VM. parameter file. For more information, refer to Boot Time Command Arguments askmethod This command asks you to select the installation method you would like to use when booting from the Red Hat Enterprise Linux CD-ROM.
50 Appendix E. Additional Boot Options vncpassword= This command sets the password used to connect to the VNC server.
Appendix F. Additional Information for S/390 and zSeries Users F.1. The sysfs File System The Linux 2.6 kernel introduces the sysfs file system. The sysfs file system is described as a union of the proc, devfs, and devpty file systems. The sysfs file system enumerates the devices and busses attached to the system into a file system hierarchy that can be accessed from user space.
52 Appendix F. Additional Information for S/390 and zSeries Users F.2. Using the zFCP Driver During the initial installation, you are prompted to enter SCSI/FCP information. If this information is entered, it creates the /etc/zfcp.conf file which contains your SCSI configuration. It also adds the line alias scsi_hostadapter zFCP to /etc/modprobe.conf. This loads the required zFCP modules. # cat /etc/zfcp.conf 0.0.010a 0x01 0x5005076300c18154 0x00 0x5719000000000000 # cat /etc/modprobe.
Appendix F. Additional Information for S/390 and zSeries Users detach_state failed scsi_id unit_add 53 wwnn # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/scsi_host_no 0x0 # cat /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/scsi_id 0x1 # cat \ /sys/bus/ccw/drivers/zfcp/0.0.010a/0x5005076300c18154/0x5719000000000000/scsi_lun 0x0 # cat /sys/bus/scsi/devices/0\:0\:1\:0/hba_id 0.0.
54 Appendix F. Additional Information for S/390 and zSeries Users ./kernel/drivers/s390/cio/qdio.ko ./kernel/drivers/s390/scsi/zfcp.ko ./kernel/drivers/scsi/sd_mod.ko Using loopback device /dev/loop0 /sbin/nash -> /tmp/initrd.cT1534/bin/nash /sbin/insmod.static -> /tmp/initrd.cT1534/bin/insmod ‘/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_mod.ko’-> ‘/tmp/initrd.cT1534/lib/dasd_mod.ko’ ‘/lib/modules/2.6.7-1.451.2.3/./kernel/drivers/s390/block/dasd_eckd_mod.ko’ -> ‘/tmp/initrd.
Appendix F. Additional Information for S/390 and zSeries Users 55 F.3. Using mdadm to Configure RAID-Based and Multipath Storage Similar to other tools comprising the raidtools package set, the mdadm command can be used to perform all the necessary functions related to administering multiple-device sets. This section explains how mdadm can be used to: • Create a RAID device • Create a multipath device F.3.1. Creating a RAID Device With mdadm To create a RAID device, edit the /etc/mdadm.
56 Appendix F. Additional Information for S/390 and zSeries Users Update Time : Mon Mar 1 13:49:10 2004 State : dirty, no-errors Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Chunk Size : 64K Number Major Minor RaidDevice State 0 8 1 0 active sync 1 8 17 1 active sync 2 8 33 2 active sync 3 8 49 3 active sync UUID : 25c0f2a1:e882dfc0:c0fe135e:6940d932 Events : 0.1 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 F.3.2.
Appendix F. Additional Information for S/390 and zSeries Users 57 The configuration of /dev/md0 can be examined more closely using the command mdadm --detail /dev/md0 to verify that it is, in fact, a multipath device: /dev/md0: Version : 00.90.00 Creation Time : Tue Mar 2 10:56:37 2004 Raid Level : multipath Array Size : 3905408 (3.72 GiB 3.
58 Appendix F. Additional Information for S/390 and zSeries Users Ready; T=0.01/0.01 15:47:56 IPL the SCSI disk using the FCP device defined to the guest. q fcp 00: FCP 010A ON FCP 010ACHPID C1 SUBCHANNEL = 0000 00: 010A QDIO-ELIGIBLE QIOASSIST-ELIGIBLE Ready; T=0.01/0.01 15:51:29 i 010a 00: I 010A 00: HCPLDI2816I Acquiring the machine loader from the processor controller. 00: HCPLDI2817I Load completed from the processor controller. 00: HCPLDI2817I Now starting machine loader version 0001.
Appendix F.
60 Appendix F. Additional Information for S/390 and zSeries Users 30040 blocks (5.
Appendix F. Additional Information for S/390 and zSeries Users 61 # mkinitrd -v initrd-2.6.7-1.451.2.3.img 2.6.7-1.451.2.3 Looking for deps of module ide-disk Looking for deps of module dasd_mod Looking for deps of module dasd_eckd_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module dasd_fba_mod dasd_mod Looking for deps of module dasd_mod Looking for deps of module ext3 jbd Looking for deps of module jbd Using modules: ./kernel/drivers/s390/block/dasd_mod.ko .
62 Appendix F. Additional Information for S/390 and zSeries Users Adding #1: IPL section ’linux’ (default) kernel image......: /boot/vmlinuz-2.6.7-1.451.2.3 at 0x10000 kernel parmline...: ’root=LABEL=/’ at 0x1000 initial ramdisk...: /boot/initrd-2.6.7-1.451.2.3.img at 0x800000 Preparing boot device: dasda (0201). Preparing boot menu Interactive prompt......: disabled Menu timeout............: disabled Default configuration...: ’linux’ Syncing disks... Done. F.6.
Appendix F. Additional Information for S/390 and zSeries Users 63 In the following example, read_device_bus_id is 0.0.0600, write_device_bus_id is 0.0.0601, and data_device_bus_id is 0.0.0602. The device is a z/VM virtual NIC and the IP address to be assigned to this interface is 192.168.70.69. # echo 0.0.0600,0.0.0601,0.0.0602 > /sys/bus/ccwgroup/drivers/qeth/group Next, verify that the qeth group device was created properly: # ls /sys/bus/ccwgroup/drivers/qeth 0.0.0600 0.0.
64 Appendix F. Additional Information for S/390 and zSeries Users • card_type • checksumming • chpid • detach_state • fake_broadcast • fake_ll • ipa_takeover • portno • priority_queueing • recover • route4 • rxip • state • ungroup • vipa For information on how these features work, refer to http://oss.software.ibm.com/developerworks/opensource/linux390/docu/lx26apr04dd01.pdf (Linux for zSeries and S/390 Device Drivers, Features, and Commands).
Appendix F. Additional Information for S/390 and zSeries Users 65 Modify the NETMASK statement as needed. If you want your new interface to be activated at boot time, then make sure ONBOOT is set to yes. Make sure the SUBCHANNELS statement matches the hardware addresses for your qeth device. /etc/sysconfig/network-scripts/ifcfg-eth1 # IBM QETH DEVICE=eth1 BOOTPROTO=static IPADDR=192.168.70.87 NETMASK=255.255.255.0 ONBOOT=yes NETTYPE=qeth SUBCHANNELS=0.0.0600,0.0.0601,0.0.
66 Appendix F. Additional Information for S/390 and zSeries Users # route Kernel IP routing table Destination Gateway 192.168.70.0 * 9.12.20.0 * 169.254.0.0 * default pdlrouter-if5.p Genmask 255.255.255.0 255.255.255.0 255.255.0.0 0.0.0.0 Flags U U U UG Metric 0 0 0 0 Ref 0 0 0 0 Use 0 0 0 0 Iface eth1 eth0 eth1 eth0 Verify your changes by using the ping command to ping the gateway: # ping -c 1 192.168.70.8 PING 192.168.70.8 (192.168.70.8) 56(84) bytes of data. 64 bytes from 192.168.70.
Appendix F. Additional Information for S/390 and zSeries Users 67 For more information about configuration of the LCS driver, refer to the following: 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//online • Define the alias. Based on the type interface being added, add a line to /etc/modprobe.
68 Appendix F. Additional Information for S/390 and zSeries Users # modprobe qeth • Create the group device: # echo ,, > /sys/bus/ccwgroup/drivers/qeth/group Due to the length of this command, it has been broken into two lines. • Configure the device. For more information about configuration of the QETH driver, refer to the following: http://oss.software.ibm.com/developerworks/opensource/linux390/docu/lx26apr04dd01.
Appendix F. Additional Information for S/390 and zSeries Users 69 F.6.2.3. Working With the CTC Device Driver A Channel-to-Channel (CTC) connection is the typical high speed connection between mainframes. The CTC device driver can be used to establish a point-to-point TCP/IP or tty connection between two Linux for zSeries and S/390 instances or between a Linux for zSeries and S/390 instance and another mainframe operating system instance such as z/OS, OS/390, z/VM, or z/VSE.
70 Appendix F. Additional Information for S/390 and zSeries Users SUBCHANNELS=0.0.1b00,0.0.1b01 NETTYPE=ctc CTCPROT=0 TYPE=CTC • Activate the device. Based on the type interface being added, issue an ifup command: # ifup ctc F.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.
Appendix F. Additional Information for S/390 and zSeries Users • 71 Create a configuration script. Create a file in /etc/sysconfig/network-scripts/ with a name like the following: ifcfg-iucv The file should look like this: /etc/sysconfig/network-scripts/ifcfg-iucv0 # IBM IUCV DEVICE=iucv0 BOOTPROTO=static IPADDR=192.168.70.136 GATEWAY=172.16.70.136 NETMASK=255.255.255.255 ONBOOT=yes NETTYPE=iucv PEERID=TCPIP TYPE=IUCV • Activate the device.
72 Appendix F. Additional Information for S/390 and zSeries Users Note Disabling periodic timer interrupts can violate basic assumptions in system accounting tools. 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).
Index F /boot/, 23 /boot/ partition recommended partitioning, 22 /root/install.
74 installing without the LPAR CD using a recent SEW, 9 without the Red Hat Enterprise Linux for S/390 CD-ROMs, 9 installing packages, 32 introduction, i IPL configuration from a SCSI device, 57 NFS installation, 2, 15 O online help hiding, 17 K kernel boot options, 49 Kernel Related Information, 71 keyboard navigating the installation program using, 13 P packages groups, 32 selecting, 32 L language selecting, 18 support for multiple languages, 28 LPAR installing common steps, 10 using the LPAR CD, 9 w
75 S V SCSI-over-fiber driver (zFCP), 52 security levels firewall configuration, 26 SELinux, 27 selecting packages, 32 SELinux security levels, 27 steps disk space, 10 steps to get you started, 1 subscription registration, 35 swap, 22 swap file upgrade, 44 swap parition recommended partitioning, 22 sysfs file system, 51 VM (see z/VM) VNC, 14 T time zone configuration, 29 troubleshooting, 45 after the installation Apache-based httpd service hangs during startup, 48 after the installation, 47 graphical l
Colophon The manuals are written in DocBook SGML v4.1 format. The HTML and PDF formats are produced using custom DSSSL stylesheets and custom jade wrapper scripts. The DocBook SGML files are written in Emacs with the help of PSGML mode. Garrett LeSage created the admonition graphics (note, tip, important, caution, and warning). They may be freely redistributed with the Red Hat documentation. The Red Hat Product Documentation Team consists of the following people: Sandra A.
78 Nadine Richter — German translations Audrey Simons — French translations Francesco Valente — Italian translations Sarah Wang — Simplified Chinese translations Ben Hung-Pin Wu — Traditional Chinese translations
