Abstract
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 first installation, and information about the IOCDS.
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.
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-EC) 2094
IBM eServer Series z9 (z9-BC) 2096
IBM Series z10 (z10-EC) 2097
IBM Series z10 (z10-BC) 2098
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:
768 MB |
For installation under z/VM. |
1 GB |
For installation under LPAR. |
![]() | Memory Requirements with Remote Installation Sources |
---|---|
For installation from NFS, FTP, or SMB installation sources or whenever VNC is used, 512MB of memory is required as a minimum. Otherwise, the installation attempt is likely to fail. Further note that the number of devices visible to the z/VM guest or LPAR image affects memory requirements. Installation with literally hundreds of accessible devices (even if unused for the installation) may require more memory. |
2 GB disk space is required for the installation of SUSE Linux Enterprise Server.
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
IP network interface for IUCV
For an LPAR installation, the
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 parmfile, and the initrd. Thus, you need access to a tape unit (3480, 3490, or 3590, for example).This release of SUSE Linux Enterprise Server is based on the October 2005 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.
Driver 52G, EC, J12558 at level 116 or later
Driver 52G, EC, J12558 at level 116 or later
Driver 3G, OSA microcode level 3.0A
MCLs: J11204.007 and J11204.008 (available May 3, 2002)
Driver 3C, OSA microcode level 2.26
MCLs: J10630.013 and J10630.014 (available May 20, 2002)
Driver 3G, OSA microcode level 3.0A
MCLs: J11204.007 and J11204.008 (available May 3, 2002)
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.
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 recommended.
To connect to the SUSE Linux Enterprise Server installation system, one of the following methods is required:
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 DVD 1 in the directory
/dosutils/putty
. Get more information about
Putty at
http://www.chiark.greenend.org.uk/~sgtatham/putty/.
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 DVD 1. Copy
the tightvnc-1.2.9-setup.exe
file to the hard
disk of your Windows machine and install it. Alternatively, use the
VNC Java client and a Java-enabled Web browser.
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 the Mocha X Server from MochaSoft can be obtained at http://www.mochasoft.dk/freeware/x11.htm.
![]() | Additional Information |
---|---|
Consult the |
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:
Installation of SUSE Linux Enterprise Server using a logical partition (LPAR).
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.
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.
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 Enterprise Server guests is simple and you are able to run hundreds of Linux instances simultaneously.
This section provides the information needed to do an IPL for the first installation. Depending on the type of installation, different options need to be used. The channel-attached tape, VM reader, and load from DVD-ROM or server options are discussed. Installing the software packages, which is done over the network, does not require the IPL medium.
IPLing from a channel-attached tape is possible on all systems connected
to a tape library. 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>
.
To IPL from a VM reader, transfer the necessary files into the reader
first. Then multiple IPLs are easily done. This is the preferred way on
z/VM. For convenience of administration, it is recommended to create a
user linuxmnt
that owns a minidisk with the files and
scripts needed for IPL. This minidisk is then accessed read-only by the
Linux guests.
For IPLing into an LPAR, it is possible to either load the kernel image
directly from the SE's or the HMC's DVD-ROM device or from any remote
system accessible through FTP. This function can be performed from the
HMC. The installation process requires a file with a mapping of the
location of the installation data in the file system and the memory
locations where the data is to be copied. For SUSE Linux Enterprise Server this file is
called suse.ins
and located in the root directory
of the file system on the DVD 1.
In the left navigation pane of the HMC expand
and select the mainframe system you want to work with. Choose the LPAR where you want to boot SUSE Linux Enterprise Server from the table of LPARs displayed in the upper content area on the right. In the Tasks area, expand and click .
Now either choose suse.ins
file is not located in the root
directory of the server, provide the path to this file. Continue to the
menu and select the
suse.ins
entry. Start the installation with
.
To IPL from a SCSI DVD, you need access to an FCP adapter connected to a DVD drive. You need values like the WWPN and LUN from the SCSI drive. For details, see Section 2.4.1.2, “IPL from FCP-Attached SCSI DVD”.
This section provides some necessary information about the IOCDS and how
to customize 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 defined. The resources can
be dedicated or shared among LPARs.
![]() | Sharing Devices (DASD) |
---|---|
Do not share writable DASD among LPARs because this might result in data loss. Consider the definition of the necessary resources in advance when planning the setup for SUSE Linux Enterprise Server on IBM System z. |
This example shows how to dedicate a DASD to one specific 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 definition. 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. Define 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=(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