Red Hat ENTERPRISE LINUX 3 - FOR IBM S-390 AND IBM ESERVER... User manual

Red Hat Enterprise Linux 4
4.5
Installation Guide for the
IBM®S/390®and
IBM®eServer™zSeries®
Architectures
ISBN: N/A
Publication date:

Red Hat Enterprise Linux 4

Red Hat Enterprise Linux 4: Installation Guide for the
IBM®S/390®and IBM®eServer™zSeries®Architectures
Copyright ©You need to override this in your local ent file Red Hat, Inc.
Copyright ©You need to override this in your local ent file Red Hat Inc.. This material may only be distributed subject to
the terms and conditions set forth in the Open Publication License, V1.0 or later with the restrictions noted below (the
latest version of the OPL is presently available at http://www.opencontent.org/openpub/).
Distribution of substantively modified versions of this document is prohibited without the explicit permission of the
copyright holder.
Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is
prohibited unless prior permission is obtained from the copyright holder.
Red Hat and the Red Hat "Shadow Man" logo are registered trademarks of Red Hat, Inc. in the United States and other
countries.
All other trademarks referenced herein are the property of their respective owners.
The GPG fingerprint of the [email protected] key is:
CA 20 86 86 2B D6 9D FC 65 F6 EC C4 21 91 80 CD DB 42 A6 0E
1801 Varsity Drive
Raleigh, NC 27606-2072
USA
Phone: [phone]
Phone: [phone]
Fax: [phone]
PO Box 13588
Research Triangle Park, NC 27709
USA

Red Hat Enterprise Linux 4

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. Basic Overview of the Boot Method ................................................................. 2
3. Preparing for a Network Installation ................................................................. 2
3.1. Using ISO Images for NFS Installs ....................................................... 4
4. Preparing for a Hard Drive Installation ............................................................. 4
5. Installing under z/VM ...................................................................................... 5
6. Installing on a zSeries LPAR: Preparation .......................................................11
6.1. Interactive Setup ................................................................................12
7. Installing in an LPAR using the Red Hat Enterprise Linux LPAR CD .................12
8. Installing in an LPAR without the Red Hat Enterprise Linux for S/390 CD-ROMs 13
9. Installing in an LPAR (Common Steps) ...........................................................13
10. Do You Have Enough Disk Space? ..............................................................14
2. Installing Red Hat Enterprise Linux .........................................................................15
1. The Graphical Installation Program User Interface ...........................................15
2. The Text Mode Installation Program User Interface .........................................15
2.1. Using the Keyboard to Navigate ..........................................................17
3. Running the Installation Program ...................................................................18
3.1. Installation using X11 Forwarding ........................................................18
3.2. Installation using VNC ........................................................................19
4. Installation Methods ......................................................................................19
4.1. Installing from a Hard Drive or DASD ...................................................19
4.2. Installing via NFS ...............................................................................20
4.3. Installing via FTP ................................................................................21
4.4. Installing via HTTP .............................................................................22
5. Welcome to Red Hat Enterprise Linux ............................................................23
6. FCP Devices ................................................................................................23
7. Language Selection ......................................................................................23
8. Disk Partitioning Setup ..................................................................................24
9. Partitioning Your System ...............................................................................26
9.1. Graphical Display of DASD Device(s) ..................................................27
9.2. Disk Druid's Buttons ..........................................................................27
9.3. Partition Fields ...................................................................................27
9.4. Recommended Partitioning Scheme ....................................................28
9.5. Editing Partitions ................................................................................29
10. Network Configuration .................................................................................30
11. Firewall Configuration ..................................................................................32
12. Language Support Selection ........................................................................35
13. Time Zone Configuration .............................................................................37
14. Set Root Password .....................................................................................38
15. Package Group Selection ............................................................................40
v

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. Upgrading Your System ................................................................................52
3. Upgrading Packages .....................................................................................53
4. Upgrade Complete ........................................................................................53
D. Troubleshooting Your Installation of Red Hat Enterprise Linux .................................55
1. You are Unable to Boot Red Hat Enterprise Linux ...........................................55
1.1. Is Your System Displaying Signal 11 Errors? ........................................55
2. Trouble During the Installation .......................................................................55
2.1. No devices found to install Red Hat Enterprise Linux Error
Message ..................................................................................................55
2.2. Trouble with Partition Tables ...............................................................55
2.3. Other Partitioning Problems ................................................................56
2.4. Are You Seeing Python Errors? ...........................................................56
3. Problems After Installation .............................................................................57
3.1. Remote Graphical Desktops and XDMCP ............................................57
3.2. Problems When You Try to Log In .......................................................58
3.3. Your Printer Does Not Work ................................................................58
3.4. Apache-based httpd service/Sendmail Hangs During Startup ..............58
E. Additional Boot Options .........................................................................................61
F. Additional Information for S/390 and zSeries Users .................................................63
1. The sysfs File System ..................................................................................63
2. Using the zFCP Driver ....................................................................................64
3. Using mdadm to Configure RAID-Based and Multipath Storage .........................69
3.1. Creating a RAID Device With mdadm ....................................................69
3.2. Creating a Multipath Device With mdadm ...............................................70
4. Configuring IPL from a SCSI Device ...............................................................72
4.1. IPL the SCSI Disk ..............................................................................72
5. Adding DASD ...............................................................................................73
6. Adding a Network Device ..............................................................................78
6.1. Adding a qeth Device .........................................................................78
6.2. Quick Reference for Adding Network Devices ......................................83
7. Kernel-Related Information ............................................................................92
Index .......................................................................................................................95
Red Hat Enterprise Linux 4
vi

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. Document Conventions
Certain words in this manual are represented in different fonts, styles, and weights. This
highlighting indicates that the word is part of a specific category. The categories include the
following:
Courier font
Courier font represents commands,file names and paths, and prompts .
When shown as below, it indicates computer output:
Desktop about.html logs paulwesterberg.png
Mail backupfiles mail reports
bold Courier font
Bold Courier font represents text that you are to type, such as: service jonas start
If you have to run a command as root, the root prompt (#) precedes the command:
#gconftool-2
italic Courier font
Italic Courier font represents a variable, such as an installation directory:
install_dir/bin/
bold font
Bold font represents application programs and text found on a graphical interface.
When shown like this: OK , it indicates a button on a graphical application interface.
Additionally, the manual uses different strategies to draw your attention to pieces of information.
In order of how critical the information is to you, these items are marked as follows:
vii

Note
A note is typically information that you need to understand the behavior of the
system.
Tip
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.
Warning
A warning indicates potential data loss, as may happen when tuning hardware
for maximum performance.
2. How to Use This Manual
This manual focuses on VM and LPAR installation and is ideal for users (both new and old) who
want a quick and simple installation solution. It helps you prepare your system and walk you
through the installation of Red Hat Enterprise Linux.
Red Hat Enterprise Linux includes multiple installation CD-ROMs. Note that only the first
CD-ROM (CD #1) is bootable. The additional installation CD-ROMs are required, even for a
minimal installation. Red Hat also provides supplementary CD-ROMs containing source RPMs
and documentation for all the packages, as well as a Linux Applications CD (LACD).
If you are an experienced user and you do not need a review of the basics, you can skip ahead
Introduction
viii

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 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. If you have found an error, please include the section number and some of the
surrounding text so we can find it easily.
If you have a support question (for example, if you need help configuring X, or if you are not
sure how to partition your hard drive[s]), use the online support system by registering your
subscriptions at:
http://www.redhat.com/apps/activate/
3. Accessibility Solutions
While the graphic user interface (GUI) is convenient for sighted users, it is often inhibiting to
those with visual impairments because of the difficulty speech synthesizers have interpreting
graphics. Red Hat Enterprise Linux is an ideal operating system for users with visual limitations
because the GUI is not required by the kernel. Most modern tools including email, news, Web
browsers, calendars, calculators, and much more can run on Linux without a graphical
environment. The working environment can also be customized to meet the hardware or
software needs of the user.
Red Hat, Inc. is the distribution of choice for people with special needs because of the
outstanding support that is offered with the purchase of any boxed set. Many Linux distributions
provide limited or nonexistent support to customers. Red Hat Inc.'s installation support is
deliverable via email or via the telephone and special circumstances will be considered and
addressed for users with physical limitations. Customers should inform the support technician if
they require specialized support.
For more information, refer to:
•http://www.tldp.org/HOWTO/Accessibility-HOWTO/
•http://www.tldp.org/HOWTO/Keyboard-and-Console-HOWTO.html
We Need Feedback!
ix

• The README-Accessibility file provides more information and instructions for using some of
the tools available for users with special needs. This file can be found in
/usr/share/doc/redhat-release-X/, where Xis the release number of your installed
subscription.
Introduction
x

1Direct Access Storage Devices (or DASDs) are hard disks that allow a maximum of three (3) partitions per DASD. For
example, dasda has dasda[123].
2Using the zFCP driver over fiber and a dedicated switch, SCSI LUNs can be presented.
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.
Note
For the most current IBM resources, visit http://www.ibm.com/eserver/zseries/.
Before you install Red Hat Enterprise Linux, you must to perform the following steps:
1. Allocate sufficient DASD1or SCSI2partitions to provide suitable disk space (for example, 2
GB is sufficient for server installations, while 5 GB is minimally required to install all
packages).
2. Acquire a minimum of 256 MB RAM (512 MB is strongly recommended) to designate for the
Linux virtual machine.
3. Determine if you need swap space and if so how much. While it is possible (and
recommended) to assign enough memory to z/VM and let z/VM do the necessary swapping,
there may be cases where the amount of required RAM is not predictable. Such instances
should be examined on a case-by-case basis.
4. Decide what environment under which to run the Red Hat Enterprise Linux operating system
(on an LPAR or as a guest operating system on one or more virtual machines).
5. Finally, it is important to review sections 3.3 through 3.8, and Chapters 5 and 6 of the IBM
Linux for S/390 Redbook, as it explains the different configurations and install scenarios
available on the S/390 platform as well as how to setup an initial LPAR or Linux virtual
machine (z/VM).
1. Additional S/390 Hardware Preparation for
Installation Notes
Chapter 1.
1

The network configuration must be determined beforehand. Red Hat Enterprise Linux for S/390
supports multiple network devices including CTC (channel-to-channel), IUCV (inter-user
communication vehicle), LCS (LAN channel station), and QDIO-enabled (Queued Direct I/O)
devices.
For the purposes of this installation, it is recommended that at least 4 GB of disk space (such as
two 2 GB DASD, direct access storage device, partitions or equivalent zSeries SCSI LUNs) be
allocated for the installation process. All DASD disk allocations should be completed prior to the
install process. After the installation, more DASD or SCSI (for zSeries only) disk partitions may
be added or deleted as necessary.
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). You
should edit the CMS configuration file and add information about your DASD. You may also
want to add some information about your network configuration. Once this is started on the
S/390, the networking is configured. You can then use telnet or ssh on another computer to log
into your Red Hat Enterprise Linux installation image. Now you can start an installation script to
install Red Hat Enterprise Linux.
Note
The CMS configuration file is a new file for Red Hat Enterprise Linux 5.0.0. Users
of prior releases should note this addition. This new file is explained in more
detail throughout Chapter 1, Steps to Get You Started.
3. Preparing for a Network Installation
The Red Hat Enterprise Linux installation media must be available for either a network
installation (via NFS, FTP, or HTTP) or installation via local storage. Use the following steps if
you are performing an NFS, FTP, or HTTP installation.
The NFS, FTP, or HTTP server to be used for installation over the network must be a separate
machine which can provide the complete RedHat/ directory. Both the RedHat/base/ and
RedHat/RPMS/ directories must be available and populated with all files from all installation
CD-ROMs.
Note
The directory specified in the following refers to /location/of/disk/space/.
This means it is the directory up to, but not including, the RedHat/ distribution
Chapter 1. Steps to Get You Started
2

directory. For example, if you have Red Hat Enterprise Linux 5.0.0 installation
files located in /export/rhel/ on the installation staging server,
/location/of/disk/space/ would be /export/rhel/.
To copy the RedHat/ directory from the installation CD-ROMs to a Linux machine which acts as
an installation staging server, perform the following steps:
• For each binary CD-ROM, execute the following commands:
•mount /mnt/cdrom
•cp -var /mnt/cdrom/RedHat /location/of/disk/space
where /location/of/disk/space/ is a directory you create such as /export/rhel/
•umount /mnt/cdrom/
• 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.redhat.com/docs/.
• Next, make /location/of/disk/space/ available for network installation via NFS, FTP, or
HTTP and verify access from a client system.
• For NFS, export the directory by adding an entry to /etc/exports to export to a specific
system:
/location/of/disk/space client.ip.address(ro,no_root_squash)
To export to all machines (not appropriate for all NFS systems), add:
/location/of/disk/space *(ro,no_root_squash)
Start the NFS daemon (on a Red Hat Enterprise Linux machine, 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 System
Administration Guide.
Preparing for a Network Installation
3

If the RedHat/ directory does not appear in the NFS shared directory, the wrong path may
have been mounted and/or exported.
• FTP and HTTP installations also support a second type of tree structure. To make it easier to
access the contents of the installation CD-ROMs, mount each CD-ROM or ISO image with
the following mount point on the FTP or HTTP server (where Xis the number of the CD-ROM
or ISO image):
/location/of/disk/space/discX/
For example:
mount -o loop CD1.iso /location/of/disk/space/disc1/
3.1. Using ISO Images for NFS Installs
NFS installations can use ISO (or CD-ROM) images rather than copying an entire installation
tree. After placing the required ISO images (the binary Red Hat Enterprise Linux CD-ROMs) in a
directory, choose to install via NFS. You will then point the installation program at that directory
to perform the installation.
Verifying that the ISO images are intact before you attempt an installation will help to avoid
problems that are often encountered during an NFS installation. To verify the ISO images are
intact prior to performing an installation, use an md5sum program (many md5sum programs are
available for various operating systems). An md5sum program should be available on the same
server as the ISO images.
Additionally, if a file called updates.img exists in the directory from which you install, then it will
be used for installation program updates. Refer to the file install-methods.txt in the
anaconda RPM package for detailed information on the various ways to install Red Hat
Enterprise Linux, as well as how to apply the installation program updates.
Note
You can only have the ISO images for one release and one variant of Red Hat
Enterprise Linux in the directory.
4. Preparing for a Hard Drive Installation
Chapter 1. Steps to Get You Started
4

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.
For each CD-ROM, execute the following command on a Linux system:
dd if=/dev/cdrom of=/tmp/file-name.iso
This command may raise an error message when the data at the end of the CD-ROM is
reached which can be ignored. The ISO images created can now be used for installation,
once copied to the correct DASD.
• Using ISO images — transfer these images to the system to be installed (or to the correct
DASD).
Verifying that ISO images are intact before you attempt an installation, helps to avoid
problems. To verify the ISO images are intact prior to performing an installation, use an
md5sum program (many md5sum programs are available for various operating systems). An
md5sum program should be available on the same Linux machine as the ISO images.
Make the correct DASDs accessible to the new VM or LPAR, and then proceed with
installation.
Additionally, if a file called RedHat/base/updates.img exists in the directory from which you
install, it is used for installation program updates. Refer to the file install-methods.txt in the
anaconda RPM package for detailed information on the various ways to install Red Hat
Enterprise Linux, as well as how to apply the installation program updates.
5. Installing under z/VM
Log onto z/VM as the Linux guest account. 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 OS/2 3270 terminal emulator on the S/390 management console. If you are working
from a Windows based machine, Jolly Giant (http://www.jollygiant.com/
[http://www.jollygiant.com]) offers an SSL-enabled 3270 emulator.
If you are not in CMS mode, enter it now.
Installing under z/VM
5

i cms
If necessary, add the device containing z/VM's TCP/IP tools to your CMS disk list. For example:
vmlink tcpmaint 592 592
If using any of the qdio/qeth based network connection types (such as OSA express or
hipersockets), set the VM guest qioassist parameter off:
set qioassist off
FTP to the machine containing the Red Hat Enterprise Linux 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 and initrd.img image files):
•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. In order to accommodate limitations
with parameter files, a new configuration file on a CMS DASD should be used to configure the
initial network setup and the DASD specification.
A.parm file is still required for the real kernel parameters, such as root=/dev/ram0 ro ip=off
ramdisk_size=40000, and single parameters which are not assigned to variables, such as vnc.
Two new parameters which point the installation program at the new configuration file need to
be added to the .parm file:
Chapter 1. Steps to Get You Started
6

CMSDASD=191 CMSCONFFILE=redhat.conf
CMSDASD is the device ID of the CMS formatted DASD which contains the configuration file.
CMSDASD is usually the '$HOME' DASD 191 of the mainframe user. The name of the
configuration file must be set with CMSCONFFILE and needs to be all lowercase.
The syntax of the CMSCONFFILE is bash style with variable="value" pairs, one on each line.
Example redhat.parm file:
root=/dev/ram0 ro ip=off ramdisk_size=40000
CMSDASD=191 CMSCONFFILE=redhat.conf
vnc
Example redhat.exec file:
/* */
'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 redhat.conf file:
HOSTNAME="foobar.zSeries.example.com"
DASD="200-203"
NETTYPE="qeth"
IPADDR="192.168.17.115"
SUBCHANNELS="0.0.0600,0.0.0601,0.0.0602"
PORTNAME="FOOBAR"
NETWORK="192.168.17.0"
NETMASK="255.255.255.0"
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:
Installing under z/VM
7

•DASD=<dasd-list>
Where <dasd-list> represents the list of DASD devices to be used by Red Hat Enterprise
Linux.
Although autoprobing for DASDs is done if this parameter is omitted, it is highly
recommended to include the DASD= parameter, as the device numbers (and therefore the
device names) can vary when a new DASD is added to the Red Hat Enterprise Linux guest.
This can result in an unusable system.
•root=<file-system>
where <file-system> represents the device on which the root file system can be found. For
installation purposes, it should be set to /dev/ram0, which is the ramdisk containing the Red
Hat Enterprise Linux installation program.
The following parameters are required to set up networking:
•SUBCHANNELS=
Provides required device bus IDs for the various network interfaces.
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>"
For example (a sample qeth SUBCHANNEL statement):
SUBCHANNELS=0.0.0600,0.0.0601,0.0.0602
To force a specific CTC protocol, additionals parameters can be added. For example:
CTCPROT=<n>
Where <n> is one of the following:
·0for compatibility mode (used with non-Linux peers other than S/390 and zSeries operating
systems)
·1for extended mode
·2for CTC-based tty (only supported on Linux-to-Linux connections)
·3for compatibility mode with S/390 and zSeries operating systems
Chapter 1. Steps to Get You Started
8

•PEERID=<userid>
Where <userid> represents the ID of the guest machines you want to connect to. Note that
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.
The following parameters are optional:
•HOSTNAME=<string>
Where <string> is the hostname of the newly-installed Linux guest.
•NETTYPE=<type>
Where <type> must be one of the following: ctc,iucv,lcs,orqeth.
•IPADDR=<IP>
Where <IP> is the IP address of the new Linux guest.
•NETWORK=<network>
Where <network> is the address of your network.
•NETMASK=<netmask>
Where <netmask> is the netmask.
•BROADCAST=<broadcast>
Where <broadcast> is the broadcast address.
•GATEWAY=<gw>
Where <gw> is either the gateway-IP for your eth device or the IP address of the
ctc/escon/iucv point-to-point partner.
•MTU=<mtu>
Where <mtu> is the Maximum Transmission Unit (MTU) for this connection.
•DNS=<server1>:<server2>:…:<serverN>
Where <server1>:<server2>:…:<serverN> is a list of DNS servers, separated by colons.
For example:
Installing under z/VM
9

DNS=10.0.0.1:10.0.0.2
•SEARCHDNS=<domain1>:<domain2>:…:<domainN>
Where <domain1>:<domain2>:…:<domainN> is a list of the search domains, separated by
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: <qeth_portname> is the portname specified on the OSA device
when operating in qeth mode. PORTNAME is only required for z/VM 4.3 or older without
APARs VM63308 and PQ73878.
When using non-qdio mode: <lcs_portnumber> is used to pass the relative port number as
integer in the range of 0 through 15.
•FCP_<n>="<device_number> <SCSI_ID> <WWPN> <SCSI_LUN> <FCP_LUN>"
The variables can be used on systems with FCP devices to preconfigure the FCP setup and
can be subsequently edited in anaconda during the installation. An example value may look
similar to:
FCP_1="0.0.5000 0x01 0x5105074308c212e9 0x0 4010"
•<n> is an integer value (e.g. FCP_1,FCP_2, ...).
•<device_number> is used to specify the address of the FCP device ( 0.0.5000 for device
5000, for example).
•<SCSI_ID> is specified in hex-value, typically sequential values (e.g. 0x01,0x02 ... ) are
used over multiple FCP_ variables.
•<WWPN> is the world wide port name used for routing (often in conjunction with multipathing)
and is as a 16-digit hex value (e.g. 0x5105074308c212e9).
•<SCSI_LUN> 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.
•<FCP_LUN> refers to the storage logical unit identifier and is specified as a hex-value (such
as 0x4010).
Note
Chapter 1. Steps to Get You Started
10