Novell LINUX ENTERPRISE SERVER 10 - ARCHITECTURE-SPECIFIC INFORMATION... Manual

SUSE Linux Enterprise
Server
www.novell.com10
August04,2006 Architecture-Specific Information

Architecture-Specic Information
List of Authors: Wolfgang Engel, Berthold Gunreben, Ulrich Hecht, Jana Jaeger, Bernhard Kaindl,
Ihno Krumreich, Susanne Oberhauser, Hannes Reinecke, Jörg Reuter, Tanja Roth, Thomas Rölz,
Thomas Schraitle, Frank Sundermeyer, Rebecca Walter
This publication is intellectual property of Novell Inc.
Its contents can be duplicated, either in part or in whole, provided that a copyright label is visibly lo-
cated on each copy.
All information found in this book has been compiled with utmost attention to detail. However, this
does not guarantee complete accuracy. Neither SUSE LINUX GmbH, the authors, nor the translators
shall be held liable for possible errors or the consequences thereof.
Novell, the Novell logo, the N logo and SUSE are registered trademarks of Novell, Inc. in the United
States and other countries. * Linux is a registered trademark of Linus Torvalds. All other third party
trademarks are the property of their respective owners.

Contents
Introduction v
1General Information and Requirements 11
1.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 InstallationTypes......................... 15
1.3 IPLOptions ........................... 16
1.4 TheIOCDS............................ 18
2Preparing for Installation 21
2.1 Making the Installation Data Available . . . . . . . . . . . . . . . . 21
2.2 InstallationTypes......................... 24
2.3 Preparing the IPL of the SUSE Linux Enterprise Server Installation System . 26
2.4 IPLing the SUSE Linux Enterprise Server Installation System . . . . . . . 29
2.5 Network Conguration . . . . . . . . . . . . . . . . . . . . . . 33
2.6 Connecting to the SUSE Linux Enterprise Server Installation System . . . . 36
AAppendix 39
A.1 Network Connection Types . . . . . . . . . . . . . . . . . . . . . 39
A.2 The parmle—Automating the System Conguration . . . . . . . . . . 42
A.3 Using the vt220 Terminal Emulator . . . . . . . . . . . . . . . . . 47

Introduction
This book describes the procedure for preparing the installation of SUSE® Linux En-
terprise Server on IBM System z systems. It provides all information needed to prepare
the installation on the LPAR and z/VM side.
1 Structure
Basically, this manual is divided in two parts.
General Information and Requirements
This part provides information about the requirements both on the hardware and
the software side that need to be met to install SUSE Linux Enterprise Server suc-
cessfully on your machine.
Preparing for Installation
This part covers the preparation procedure for the installation of SUSE Linux En-
terprise Server on IBM System z. Learn which basic preparations need to be per-
formed on the LPAR and z/VM side. It guides you to the point where YaST, the
SUSE® Linux Enterprise Server installation and conguration tool, takes over.
Additionally, the appendix contains a chapter featuring an overview of possible network
connection types. The second chapter in the appendix focuses on automated system
conguration using the parmle.
TIP: Further Information about SUSE Linux Enterprise Server on IBM
System z
Find a short introduction to SUSE Linux Enterprise Server on IBM System z in
Start-Up Guide of which you received a printed copy. Find a detailed description
of the installation procedure and the administration of SUSE Linux Enterprise
Server in Installation and Administration, which you can nd in the local direc-
tory /usr/share/doc/manual/ or on the rst installation medium in the
directory /docu.

2 Required Background
Several assumptions have been made concerning your background knowledge when
writing this document.
• You are familiar with IBM System z terminology.
• You have a good knowledge of the IBM System z devices attached to your system,
especially its network environment.
• You have a basic understanding of handling a Linux or Unix system.
3 Documentation Conventions
The following typographical conventions are used in this manual:
•/etc/passwd: lenames and directory names
•placeholder: replace placeholder with the actual value
•PATH: the environment variable PATH
•ls,--help: commands, options, and parameters
•user: users or groups
•Alt ,Alt +F1 : a key to press or a key combination; keys are shown in uppercase
as on a keyboard
•File,File →Save As: menu items, buttons
• This paragraph is only relevant for the specied architectures. The arrows mark
the beginning and the end of the text block.
•Dancing Penguins (Chapter Penguins, ↑Reference): This is a reference to a chapter
in another book.
vi Architecture-Specic Information

4Further In-Depth Information about
IBM System z
IBM has published a number of very interesting documents about their System z plat-
form. Find them either on the Internet (http://www.redbooks.ibm.com) or in
your installed system (package redbook) under /usr/share/doc/packages/
redbook.
4.1 Hardware
For a rst glance at the technical details of some systems, refer to:
• IBM eServer zSeries 990 Technical Introduction (SG24-6863)
• IBM eServer zSeries 900: Technical Guide (SG24-5975)
• Technical Introduction: IBM eServer zSeries 800 (SG24-6515)
• Linux on zSeries Fibre Channel Protocol Implementation Guide (SG24-6344)
4.2 General Documents about Linux on IBM
System z
A general coverage of Linux on IBM System z can be found in the following documents:
• Linux on IBM eServer zSeries and S/390: ISP and ASP Solutions (SG24-6299)
These documents might not reect the current state of Linux, but the principles of
Linux deployment outlined there remain accurate.
Introduction vii

4.3 Technical Issues of Linux on IBM System
z
Refer to the following documents to get in-depth technical information about Linux
kernel and application topics. Refer to the Internet for up-to-date versions of these
documents for the most recent code drop (http://www.ibm.com/
developerworks/linux/linux390/index.html).
• Linux for zSeries and S/390: Device Drivers, Features, and Commands
• zSeries ELF Application Binary Interface Supplement
• Linux for zSeries and S/390: Using the Dump Tools
• IBM-System z9-109 Technical Introduction (SG26-6669)
There also is a Redbook for Linux application development on http://www
.redbooks.ibm.com:
• Linux on IBM eServer zSeries and S/390: Application Development (SG24-6807)
4.4 Advanced Congurations for Linux on
IBM System z
Refer to the following Redbooks, Redpapers, and links for some more complex IBM
System z scenarios:
• Linux on IBM eServer zSeries and S/390: Large Scale Deployment (SG24-6824)
• Linux on IBM eServer zSeries and S/390: Performance Measuring and Tuning
(SG24-6926)
• Linux with zSeries and ESS: Essentials (SG24-7025)
• IBM TotalStorage Enterprise Storage Server Implementing ESS Copy Services
with IBM eServer zSeries (SG24-5680)
viii Architecture-Specic Information

• Linux on IBM zSeries and S/390: High Availability for z/VM and Linux (REDP-
0220)
• Saved Segments Planning and Administration
http://www.vm.ibm.com/pubs/pdf/hcsg4a00.pdf
• Linux for zSeries and S/390: How to Improve Performance with PAV
http://www.ibm.com/developerworks/linux/linux390/index
.html
• How to Improve the Performance of Linux on z/VM with Execute-in-Place Tech-
nology
http://www.ibm.com/developerworks/linux/linux390/index
.html
5 Acknowledgments
The history of Linux is a success story about countless developers all around the world
contributing to what originally started as a one-man show by Linus Torvalds. Thanks
to all of them for their tremendous efforts.
Especially we would like to thank all the people involved in the Linux for IBM System
z project at IBM and SUSE. Thanks to the (information) developers at SUSE and IBM,
the test team at SUSE, and all beta-testers and proofreaders at IBM. Thank you for
making SUSE Linux Enterprise Server for IBM System z possible.
Introduction ix

1
General Information and
Requirements
This chapter gives basic information about the system requirements, like supported
hardware, level of MicroCode, and software. It also covers the different installation
types, how to do an IPL for the rst installation, and information about the IOCDS.
1.1 System Requirements
This section provides a list of hardware for IBM System z supported by SUSE® Linux
Enterprise Server. Next, the level of the MicroCode (MCL) used in your IBM System
z system, which is very important for the installation, is covered. Additional software
to install and use for installation is mentioned at the end of this section.
1.1.1 Hardware
SUSE Linux Enterprise Server has run successfully on the following platforms:
• IBM eServer zSeries 800 (z800) 2066
• IBM eServer zSeries 890 (z890) 2086
• IBM eServer zSeries 900 (z900) 2064
• IBM eServer zSeries 990 (z990) 2084
• IBM eServer Series z9 (z9-109) 2094
General Information and Requirements 11

Memory Requirements
Different installation methods have different memory requirements during installation.
After installation is completed, the system administrator may reduce memory to the
desired size. SUSE recommends using:
For installation from NFS or SMB installation sources.512 MB
For installation using VNC. Graphical feedback is provided through
a Java-enabled Web browser. Installation sources are accessible over
512 MB
FTP. The increased memory requirement during installation results
from using temporary disk space in memory (RAM disk) during the
package transfers.
Disk Space Requirements
1.6 GB disk space is required for the installation of SUSE Linux Enterprise Server.
Network Connection
A network connection is needed to communicate with your SUSE Linux Enterprise
Server system. This can be one or more of the following connections or network cards:
• OSA-2 (Token Ring and Ethernet, only available on z900)
• OSA Express Ethernet (including Fast and Gigabit Ethernet)
• OSA Express High-Speed Token Ring (only available on z800, z900, z890, and
z990)
• HiperSockets or Guest LAN
• 10 GBE, VSWITCH
The following interfaces are still included, but no longer supported:
• CTC (or virtual CTC)
• ESCON
12 Architecture-Specic Information

• IP network interface for IUCV
IPL Options
For an LPAR installation, the Load from CD-ROM or Server option is the preferred
way to IPL the installation kernel and initrd (initial RAM disk). If this option is not
available and you cannot use z/VM for installing the system, you need to IPL from a
channel attached tape with the tapeipl kernel, the parmle, and the initrd. Thus, you
need access to a tape unit (3480, 3490, or 3590, for example).
1.1.2 MicroCode Level, APARs, and Fixes
This release of SUSE Linux Enterprise Server is based on the April 2004 codestream
from IBM developerWorks (http://www.ibm.com/developerworks/linux/
linux390/october2005_technical.html). The restrictions and requirements
listed at the Web site also apply for this release of SUSE Linux Enterprise Server, except
where stated differently in this manual.
It is recommended always to use the highest service level available. For installation
under VM, you need at least z/VM 4.2 with service level 0103. To use HiperSockets
under VM on z900 (2064), you need MicroCode EC E26949 level 013 or higher. For
an IPL from SCSI on z900, you need SCSI enabler MCL, feature code 9904, EC J12811.
For the installation of SUSE Linux Enterprise Server on IBM System z, the MicroCode
levels and z/VM APARs outlined in the following are required.
OSA-Express QDIO
zSeries 990
Driver 52G, EC, J12558 at level 116 or later
zSeries 890
Driver 52G, EC, J12558 at level 116 or later
zSeries 900
Driver 3G, OSA microcode level 3.0A
MCLs: J11204.007 and J11204.008 (available May 3, 2002)
General Information and Requirements 13

zSeries 900
Driver 3C, OSA microcode level 2.26
MCLs: J10630.013 and J10630.014 (available May 20, 2002)
zSeries 800
Driver 3G, OSA microcode level 3.0A
MCLs: J11204.007 and J11204.008 (available May 3, 2002)
VM/ESA and z/VM
z/VM 5.2
z/VM 5.1
z/VM 4.4
All necessary xes and enhancements included.
Level RSU 0402 is required to implement z990 Queued I/O Assist. Find more in-
formation at http://www.vm.ibm.com/perf/aip.html.
Negotiate the order of installation with your IBM support, because it might be necessary
to activate the VM APARs before installing the new MicroCode levels.
1.1.3 Software
To install SUSE Linux Enterprise Server via non-Linux–based NFS or FTP, you might
experience problems with NFS or FTP server software. Especially the Windows standard
FTP server can cause errors, so installing via SMB on these machines is generally rec-
ommended.
To connect to the SUSE Linux Enterprise Server installation system, one of the following
methods is required:
SSH with Terminal Emulation (xterm compatible)
SSH is a standard Unix tool that should be present on any Unix or Linux system.
For Windows, there is an SSH client called Putty. It is free to use and is included
on CD 1 in the directory /dosutils/putty. Get more information about Putty
at http://www.chiark.greenend.org.uk/~sgtatham/putty.html.
14 Architecture-Specic Information

VNC Client
For Linux, a VNC client called vncviewer is included in SUSE Linux Enterprise
Server as part of the XFree86-Xvnc package. For Windows, a VNC client is
included in the present SUSE Linux Enterprise Server. Find it in /dosutils/
tightvnc of CD 1. Copy the tightvnc-1.2.9-setup.exe le to the hard
disk of your Windows machine and install it. Alternatively, use the VNC Java client
and a Java-enabled Web browser.
X Server
Find a suitable X server implementation on any Linux or Unix workstation. There
are many commercial X Window System environments for Windows and Macintosh.
Some of them can be downloaded as free trial versions. A trial version of MI/X
(MicroImages X Server) can be obtained at http://www.microimages.com/
mix.
TIP: Additional Information
Consult the README located in the highest directory of CD 1 of your SUSE
Linux Enterprise Server before installing SUSE Linux Enterprise Server on IBM
System z. This le completes the documentation presented in this book.
1.2 Installation Types
This section gives an overview of the different types of installation possible with SUSE
Linux Enterprise Server for IBM System z. Basically, these two types are given:
LPAR
Installation of SUSE Linux Enterprise Server using a logical partition (LPAR).
VM (z/VM)
Installation of SUSE Linux Enterprise Server as as a guest operating system within
z/VM.
Depending on the mode of installation (LPAR or VM), there are different possibilities
for starting the installation process and IPLing the installed system.
General Information and Requirements 15

1.2.1 LPAR
If you install SUSE Linux Enterprise Server for IBM System z into a separate logical
partition (LPAR), allow SUSE Linux Enterprise Server to use a special part of physical
memory in your system. Also decide how many processors are used by SUSE Linux
Enterprise Server. In this mode, you can run different operating systems simultaneously
on your IBM System z system.
1.2.2 z/VM
Running SUSE Linux Enterprise Server for IBM System z in z/VM means that SUSE
Linux Enterprise Server is a guest system within z/VM. An advantage of this mode is
that you have full control over SUSE Linux Enterprise Server from z/VM. This is very
helpful for kernel development or kernel-based debugging. It is also very easy to add
or remove hardware to and from Linux guests. Creating additional SUSE Linux Enter-
prise Server guests is simple and you are able to run hundreds of Linux instances simul-
taneously.
1.3 IPL Options
This section provides the information needed to do an IPL for the rst installation.
Depending on the type of installation, different options need to be used. The channel-
attached tape, VM reader, and load from CD-ROM or server options are discussed.
Installing the software packages, which is done over the network, does not require the
IPL medium.
1.3.1 ESCON or FICON Attached Tape
IPLing from a channel-attached tape is possible on all systems connected to a tape li-
brary. The only prerequisite is that the LPAR in which to install (or allowing z/VM to
run) is allowed to access the tape unit. For this, the IODEVICE statement in the IOCDS
must have the attribute SHARED or PART=<LPARName>.
16 Architecture-Specic Information

1.3.2 VM Reader
To IPL from a VM reader, transfer the necessary les into the reader rst. Then multiple
IPLs are easily done. This is the preferred way on z/VM. For comfortable administration,
it is recommended to create a user linuxmnt that owns a minidisk with the les and
scripts needed for IPL. This minidisk is then accessed read-only by the Linux guests.
1.3.3 Load from CD-ROM or Server
For IPLing into an LPAR, it is possible to load directly from the Support Element's
(SE) CD-ROM device. It also allows you to IPL via FTP from a server holding the
SUSE Linux Enterprise Server for IBM System z les. Find this button near the LOAD
button (if you have upgraded to the latest MCL, see Chapter 1, General Information
and Requirements (page 11)).
Figure 1.1 HMC CPC Group Work Area
This function can be performed from the HMC. Do this by accessing the Dened CPCs
icon in the Groups Work Area on the HMC desktop. From there, access the Dened
CPCs Work Area. Select a system image and initiate CPC Recovery. Use Single Object
Operations to access the service element remotely.
General Information and Requirements 17

Figure 1.2 Specifying the Load Option on the SE's Groups Work Area
Access the service element's Groups Work Area. Select the LPAR to perform the load
from CD-ROM or server and initiate CPC recovery for that LPAR. Start Load from
CD ROM or Server from the action menu. Provide information as requested on subse-
quent windows.
1.4 The IOCDS
This section provides some necessary information about the IOCDS and how to cus-
tomize some settings for sharing network cards or DASDs among several LPARs. In
the IOCDS, the chpid and types of the devices connected to the IBM System z are
dened. The resources can be dedicated or shared among LPARs.
WARNING: Sharing Devices (DASD)
Do not share DASD writable among LPARs because this might result in data
loss. Consider the denition of the necessary resources in advance when plan-
ning the setup for SUSE Linux Enterprise Server on IBM System z.
18 Architecture-Specic Information

This example shows how to dedicate a DASD to one specic LPAR. This LPAR is
referred to as LPAR1.
Example 1.1 Dedicating DASD to One LPAR
CHPID PATH=FD,TYPE=DSD,SHARED
CNTLUNIT CUNUMBR=FD00,PATH=FD,UNITADD=((00,256)),UNIT=3990-2
IODEVICE ADDRESS=(FD03,1),CUNUMBR=FD00,UNIT=3390,PART=LPAR1
To share a DASD among LPARs, delete the PART=LPAR1 part in the IOCDS denition.
This might be useful for high availability reasons or for sharing data among LPARs
read-only.
Several Linux systems can use the same network device if you share it among LPARs
or z/VM guests. This reduces the number of network devices that must be provided to
the Linux system. On the other hand, you might provide more than one network device
to one Linux system to make it more available in case one connection fails.
Network cards like OSA-Express can be used in two different modes. These modes are
known as QDIO and non-QDIO mode. Dene these modes in the IOCDS by using the
TYPE statement. QDIO mode is much faster than non-QDIO mode, but uses three device
addresses instead of two in non-QDIO. Consider the limited number of device addresses
when planning the setup of your IBM System z Linux environment.
Example 1.2 Sharing OSA Express Card among LPARs (non-qdio) on z900
CHPID PATH=(FE),SHARED,PARTITION=((LPAR1,LPAR2)),TYPE=OSE
CNTLUNIT CUNUMBR=FE00,PATH=(FE),UNIT=OSA
IODEVICE ADDRESS=(FE00,016),CUNUMBR=(FE00),UNIT=OSA
IODEVICE ADDRESS=(FEFE,001),CUNUMBR=(FE00),UNIT=OSAD
Example 1.3 Sharing OSA Express Card among LPARs (qdio) on z900
CHPID PATH=(FE),SHARED,PARTITION=((LPAR1,LPAR2)),TYPE=OSD
CNTLUNIT CUNUMBER=FE00,PATH=(FE),UNIT=OSA
IODEVICE ADDRESS=(FE00,016),CUNUMBR=(FE00),UNIT=OSA
IODEVICE ADDRESS=(FEFE,001),CUNUMBR=(FE00),UNIT=OSAD
General Information and Requirements 19