Contents
Abstract
This chapter describes the procedure for preparing the installation of SUSE® Linux Enterprise Server on IBM System z systems. It provides all information needed to prepare the installation on the LPAR and z/VM side.
This section 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 Series z9 (z9-EC) 2094
IBM 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. |
The disk requirements depend largely on the installation. Commonly, you need more space than the installation software itself needs to have a system that works properly. Minimal requirements for different selections are:
2.6 GB |
Default Installation |
3.6 GB+ |
Recommended (this is with graphical desktop, development packages and java). |
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 Express Ethernet (including Fast and Gigabit Ethernet)
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 May 2008 update of the development stream from IBM developerWorks (http://www.ibm.com/developerworks/linux/linux390/development_recommended.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. Contact your IBM support for minimum requirements.
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. 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 available from 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 tightvnc
package. For Windows, tightvnc is also available. Download it from
http://www.tightvnc.com/. 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 the 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 CD-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 CD/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 4.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 4.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 4.2. Sharing OSA Express Card among LPARs (non-qdio) on z9¶
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 4.3. Sharing OSA Express Card among LPARs (qdio) on z9¶
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
In this section, learn how to make the data accessible for installation, install SUSE Linux Enterprise Server using different methods, and prepare and use the IPL of the SUSE Linux Enterprise Server installation system. Also find out about network configuration and network installation.
This section provides detailed information about making the SUSE Linux Enterprise Server IBM System z installation data accessible for installation. Depending on your computer and system environment, choose between NFS or FTP installation. If you are running Microsoft Windows workstations in your environment, you can also use the Windows network (including the SMB protocol) to install SUSE Linux Enterprise Server on your IBM System z system.
![]() | IPL from DVD |
---|---|
Since Service Pack 1 of SUSE Linux Enterprise Server Version 10, it is possible to IPL from DVD and use the DVD as the installation medium. This is very convenient if you have restrictions setting up an installation server providing installation media over your network. The prerequisite is an FCP-attached SCSI DVD Drive. |
If you have a Linux workstation running in your computer environment, use the workstation to provide the installation data to the IBM System z installation process by NFS or FTP. If the Linux workstation runs under SUSE Linux Enterprise Server, you can set up an installation server (NFS or FTP) using the YaST Section 14.2.1, “Setting Up an Installation Server Using YaST”.
module as described inUse NFS (network file system) to make the installation media available.
![]() | Exporting Mounted Devices with NFS |
---|---|
Exporting the file system root ( /media/dvd *(ro)
After changing this file, restart the NFS server with the command
rcnfsserver |
Setting up an FTP server on a Linux system involves the installation of
the server software itself, such as wuftpd or proftpd, as well as other
possible configuration tasks. Using YaST, the installation step is
straightforward: select the package to install and start the
installation. Skip the configuration of the FTP server if no anonymous
FTP should be used for the installation. Instead, use an FTP login with
a valid username and password. You might want to create a user account
for this task only. The FTP daemon does not need to be started by hand.
It can be started by inetd if an FTP connection is requested. To
activate the new settings, enter
rcinetd restart
or
rcxinetd restart
.
DVD1 of the SUSE Linux Enterprise Server for IBM System z contains a bootable Linux image for Intel-based workstations as well as an image for System z.
For Intel-based workstations, boot from this DVD, answer the questions regarding your language and keyboard layout, and select
. You need at least 64 MB RAM for this. No disk space is needed because the entire rescue system resides in the workstation's RAM. This approach takes some Linux and networking experience, because you need to set up the networking of the workstation manually.For System z, IPL your LPAR/VM guest from this DVD as described in Section 4.2.4.1.2, “IPL from FCP-Attached SCSI DVD”. After entering your network parameters, the installation system treats the DVD as the source of installation data. Because System z cannot have an X11-capable terminal attached directly, choose between VNC or SSH installation. SSH also provides a graphical installation by tunneling the X connection through SSH with ssh -X.
If there is a Microsoft Windows workstation available in your network, use this computer to make the installation media available. The easiest way to do this is to use the SMB protocol, already included in the Windows operating system. Be sure to activate
as this enables the encapsulation of SMB packages into TCP/IP packages. Find details in the Windows online help or other Windows-related documentation that covers networking. Another option is to use FTP. This also requires some third-party software for Windows.To make the installation media available with SMB, just insert the SUSE Linux Enterprise Server DVD 1 into the DVD drive of the Windows workstation. Then create a new share using the DVD-ROM drive's letter and make it available for everyone in the network.
![]() | SMB Installation Path for YaST |
---|---|
Consult the |
Refer to the documentation provided with the third party product that enables NFS server services for your Windows workstation. The DVD-ROM drive containing the SUSE Linux Enterprise Server DVDs must be in the available NFS path.
Refer to the documentation provided with the third party product that is enabling FTP server services on your Windows workstation. The DVD-ROM drive containing the SUSE Linux Enterprise Server DVDs must be in the available FTP path.
The FTP server that is bundled with some Microsoft Windows releases implements only a subset of the FTP command set and is not suitable for providing the installation data. However, other products (such as the FTP server that is part of Hummingbird Exceed or WAR-FTPD) have been reported as functional.
After you IPLed from the SCSI DVD as described in Section 4.1.3.4, “Load from SCSI-Attached DVD”, the installation system uses the DVD as the installation medium. In that case, you do not need the installation media on an FTP, NFS, or SMB server. However, you need the network configuration data for your SUSE Linux Enterprise Server, because you must set up the network during the installation to perform a graphical installation by VNC or by X tunneled through SSH.
This section provides information about which steps must be performed to install SUSE Linux Enterprise Server for each of the installation modes and where to find the appropriate information. After the preparations mentioned in the previous chapters have been accomplished, follow the installation overview of the desired installation mode to install SUSE Linux Enterprise Server on your system.
As described in Section 4.2.1, “Making the Installation Data Available”, there are two different installation modes for Linux on IBM System z:
LPAR Installation
z/VM Installation
Procedure 4.1. Overview of LPAR Installation¶
Prepare the devices needed for installation. See Section 4.2.3.1, “LPAR Installation”.
IPL the installation system. See Section 4.2.4.1, “LPAR Installation”.
Configure the network. See Section 4.2.5, “Network Configuration”.
Connect to the SUSE Linux Enterprise Server installation system. See Section 4.2.6, “Connecting to the Installation System”.
Start the installation using YaST and IPL the installed system. See Chapter 6, Installation with YaST.
Procedure 4.2. Installation Overview of z/VM Installation¶
Prepare the devices needed for installation. See Section 4.2.3.2, “z/VM Installation”.
IPL the installation system. See Section 4.2.4.2, “z/VM Installation”.
Configure the network. See Section 4.2.5.1, “z/VM Installation”.
Connect to the SUSE Linux Enterprise Server installation system. See Section 4.2.6, “Connecting to the Installation System”.
Start the installation using YaST and IPL the installed system. See Chapter 6, Installation with YaST.
Configure your IBM System z system to start in ESA/S390 or LINUX-only mode with an appropriate activation profile and IOCDS. Consult IBM documentation for more on how to achieve this.
A SUSE Linux Enterprise Server installation needs at least two devices: a DASD and a network connection device. For an IPL from tape, a tape device should also be accessible. Devices are configured and attached to an LPAR in the IOCDS (input output configuration data set). This example defines one DASD, one OSA-2 network device, and a tape device for LPAR Z1. For further information about how to set up the IOCDS for Linux, refer to your machine's IBM hardware documentation.
Example 4.4. An Example IOCDS¶
CHPID PATH=(CSS(0),FD),PCHID=120,TYPE=FC CHPID PATH=(CSS(0),FE),PCHID=320,TYPE=OSD CHPID PATH=(CSS(0),10),PCHID=3A0,TYPE=CNC CNTLUNIT CUNUMBR=FD00,PATH=((CSS(0),FD)),UNITADD=((00,1)),UNIT=2105 IODEVICE ADDRESS=(FD00,1),CUNUMBR=(FD00),UNIT=3390B,UNITADD=00 CNTLUNIT CUNUMBR=FE20,PATH=((CSS(0),FE)),UNIT=OSA IODEVICE ADDRESS=(FE20,1),CUNUMBR=(FE20),UNIT=OSA IODEVICE ADDRESS=(FEFE,1),CUNUMBR=(FE20),UNIT=OSAD CNTLUNIT CUNUMBR=100A,PATH=((CSS(0),10)),UNIT=3480,UNITADD=((0A,1)) IODEVICE ADDRESS=(100A,1),CUNUMBR=(100A),UNIT=3480,UNITADD=00
Proceed with Section 4.2.4.1, “LPAR Installation”.
The first step is to attach and format one or multiple DASDs in the
system to be used by the Linux guest in z/VM. Next, create a new user
in z/VM. The example shows the directory for a user
LINUX1
with the password LINPWD
,
256 MB of memory (extendable up to 1024 MB), 32 MB of
expanded RAM (XSTORE), some minidisks (MDISK), two CPUs and an OSA QDIO
device.
![]() | Assigning Memory to z/VM guests |
---|---|
When assigning memory to a z/VM guest, make sure that the memory size suits the needs of your preferred installation type. See Section 4.1.1.1.1, “Memory Requirements”. To set the memory size to 512 MB, use the command CP DEFINE STORAGE 512M. After the installation has finished, reset the memory size to the desired value. |
Example 4.5. Configuration of a z/VM Directory¶
USER LINUX1 LINPWD 256M 1024M G *____________________________________________ * LINUX1 *____________________________________________ * This VM Linux guest has two CPUs defined. CPU 01 CPUID 111111 CPU 02 CPUID 111222 IPL CMS PARM AUTOCR IUCV ANY IUCV ALLOW MACH ESA 10 OPTION MAINTCCW RMCHINFO SHARE RELATIVE 2000 XSTORE 32M CONSOLE 01C0 3270 A SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 3203 A * OSA QDIO DEVICE DEFINITIONS DEDICATE 9A0 9A0 DEDICATE 9A1 9A1 DEDICATE 9A2 9A2 * LINK MAINT 0190 0190 RR LINK MAINT 019E 019E RR LINK MAINT 019D 019D RR * MINIDISK DEFINITIONS MDISK 201 3390 0001 0050 DASD40 MR ONE4ME TWO4ME THR4ME MDISK 150 3390 0052 0200 DASD40 MR ONE4ME TWO4ME THR4ME MDISK 151 3390 0253 2800 DASD40 MR ONE4ME TWO4ME THR4ME
This example uses minidisk 201 as the guest's home disk. Minidisk 150 with 200 cylinders is the Linux swap device. Disk 151 with 2800 cylinders holds the Linux installation.
Now add (as the user MAINT
)
the guest to the user directory with DIRM FOR LINUX1
ADD. Enter the name of the guest (LINUX1
)
and press F5. Set up the environment of the user with:
DIRM DIRECT DIRM USER WITHPASS
The last command returns a reader file number. This number is needed for the next command:
RECEIVE <number> USER DIRECT A (REPL)
Assign the directories to the guest with DISKMAP USER DIRECT
A. You can now log in on the guest as user
LINUX1
.
If you do not have the dirmaint
option available,
refer to the IBM documentation to set up this user.
Proceed with Section 4.2.4.2, “z/VM Installation”.
There are different ways to IPL SUSE Linux Enterprise Server into an LPAR. The preferred way is to use the
feature of the SE or HMC.Mark the LPAR to install and select
. Leave the field for the file location blank or enter the path to the root directory of the first DVD-ROM and select continue. In the list of options that appears, choose the default selection. should now show the kernel boot messages.You can use the
procedure by selecting as to IPL from SCSI. Enter the WWPN (Worldwide port name) and LUN Logical unit number) provided by your SCSI bridge or storage (16 digits—do not omit the trailing 0s). The boot program selector must be 2. Use your FCP adapter as and perform an IPL.If you cannot IPL from DVD, create a channel attached tape from which to IPL the SUSE Linux Enterprise Server installation image. Use the
button in the SE or HMC with the tape device address as the load address to IPL the SUSE Linux Enterprise Server installation system.There are many ways to create an IPLable tape. One is to copy the files:
/boot/s390x/tapeipl.ikr /boot/s390x/parmfile /boot/s390x/initrd
as binary files from DVD 1 (for example, using FTP from a Linux workstation).
Name them
SLES11 IMAGE SLES11 PARM SLES11 INITRD
and write them onto a tape with the REXX from the example.
![]() | Transferring Binaries using FTP |
---|---|
Do not upload the files as |
Example 4.6. REXX Script to Create an IPLable Tape¶
'REWIND 181' 'FILEDEF IN1 DISK' SLES11 IMAGE A 'FILEDEF IN2 DISK' SLES11 PARM A 'FILEDEF IN3 DISK' SLES11 INITRD A 'FILEDEF OUT TAP1 (RECFM F BLOCK 1024 LRECL 1024 PERM' say 'Writing: ' left(file1,23) 'MOVEFILE IN1 OUT' say 'Writing: ' left(file2,23) 'MOVEFILE IN2 OUT' say 'Writing: ' left(file3,23) 'MOVEFILE IN3 OUT' say 'Done.' 'REWIND 181' exit
The tape in this script is attached as 181. Adjust the script to your needs.
This section is about IPLing the installation system to install SUSE Linux Enterprise Server for IBM System z on a z/VM system.
You need a working TCP/IP connection and an FTP client program within your newly defined z/VM guest to transfer the installation system via FTP. Setting up TCP/IP for z/VM is beyond the scope of this manual. Refer to the appropriate IBM documentation.
Log in as the z/VM Linux guest to IPL. Make the content of the
directory /boot/s390x
on DVD 1 of the
SUSE Linux Enterprise Server for IBM System z available by FTP within your network.
From this directory, get the files vmrdr.ikr
,
initrd
, parmfile
, and
sles11.exec
. Transfer the files with a fixed block
size of 80 characters. Specify it with the FTP command locsite
fix 80. It is important to copy
vmrdr.ikr
(the Linux kernel) and
initrd
(the installation image) as binary files,
so use the binary
transfer mode.
parmfile
and sles11.exec
need
to be transferred in ASCII mode.
The example shows the steps necessary. In this example, the required
files are accessible from an FTP server at the IP address
192.168.0.3
and the login is
lininst
. It may differ
for your network.
Example 4.7. Transferring the Binaries via FTP¶
FTP 192.168.0.3 VM TCP/IP FTP Level 530 Connecting to 192.168.0.3, port 21 220 ftpserver FTP server (Version wu-2.4.2-academ[BETA-18](1) Thu Feb 11 16:09:02 GMT 2010) ready. USER lininst 331 Password required for lininst PASS ****** 230 User lininst logged in. Command: binary 200 Type set to I Command: locsite fix 80 Command: get /media/dvd1/boot/s390x/vmrdr.ikr sles11.image 200 PORT Command successful 150 Opening BINARY mode data connection for /media/dvd1/boot/s390x/vmrdr.ikr (6757376 bytes) 226 Transfer complete. 6757376 bytes transferred in 8.826 seconds. Transfer rate 766.70 Kbytes/sec. Command: get /media/dvd1/boot/s390x/initrd sles11.initrd 200 PORT Command successful 150 Opening BINARY mode data connection for /media/dvd1/boot/s390x/initrd (12654815 bytes) 226 Transfer complete. 12194534 bytes transferred in 16.520 seconds. Transfer rate 766.70 Kbytes/sec. Command: ascii 200 Type set to A Command: get /media/dvd1/boot/s390x/parmfile sles11.parmfile 150 Opening ASCII mode data connection for /media/dvd1/boot/s390x/parmfile (71 bytes) 226 Transfer complete. 71 bytes transferred in 0.092 seconds. Transfer rate 0.71 Kbytes/sec. Command: get /media/dvd1/boot/s390x/sles11.exec sles11.exec 150 Opening ASCII mode data connection for /media/dvd1/boot/s390x/sles11.exec (891 bytes) 226 Transfer complete. 891 bytes transferred in 0.097 seconds. Transfer rate 0.89 Kbytes/sec. Command: quit
Use the REXX script sles11.exec you just downloaded to IPL the Linux installation system. This script loads the kernel, parmfile, and the initial RAM disk into the reader for IPL.
Example 4.8. SLES11 EXEC¶
/* REXX LOAD EXEC FOR SUSE LINUX S/390 VM GUESTS */ /* LOADS SUSE LINUX S/390 FILES INTO READER */ SAY '' SAY 'LOADING SLES11 FILES INTO READER...' 'CP CLOSE RDR' 'PURGE RDR ALL' 'SPOOL PUNCH * RDR' 'PUNCH SLES11 IMAGE A (NOH' 'PUNCH SLES11 PARMFILE A (NOH' 'PUNCH SLES11 INITRD A (NOH' 'I 00C'
With this script you can IPL the SUSE Linux Enterprise Server installation system with the command sles11. The Linux kernel then starts and prints its boot messages.
To continue the installation, proceed to Section 4.2.5.1, “z/VM Installation”.
To IPL in z/VM, prepare the SCSI IPL process by using the SET LOADDEV parameter:
SET LOADDEV PORTNAME 200400E8 00D74E00 LUN 00020000 00000000 BOOT 2
After setting the LOADDEV parameter with the appropriate values, IPL your FCP adapter, for example:
IPL FC00
To continue the installation, proceed with Section 4.2.5.1, “z/VM Installation”.
If you cannot IPL from a z/VM reader, create a channel attached tape from which to IPL the SUSE Linux Enterprise Server installation image. For instructions, refer to Section 4.2.4.1.3, “IPL from ESCON or FICON Attached Tape”.
To continue the installation, proceed with Section 4.2.5.1, “z/VM Installation”.
Wait until the kernel has completed its start-up routines. If you are installing in basic mode or in an LPAR, open the
on the HMC or SE.First, choose Section 4.2.1, “Making the Installation Data Available” describes how to make the installation data available for the various types of network connections. Currently, , , , and (Windows file sharing) are supported.
in the linuxrc main menu then to start the installation process. Select as your installation medium then select the type of network protocol you will be utilizing for the installation.Now set up the network device over which to receive the installation data:
or . The following network adapters are still available and usable, but no longer supported: CTC, ESCON, IUCV. Next, choose the CCW bus interface and the physical medium ( ). As a result, the respective driver is installed and you see the corresponding kernel messages.Proceeding with the installation, linuxrc displays a list of potential usable read, write, and, if applicable, data channels. After entering the addresses for each channel, you may also need to enter additional information, such as the port name for OSA ethernet cards.
Next, decide whether to use DHCP autoconfiguration for setting up the network interface parameters. Because DHCP only works on a few devices and requires special hardware configuration settings, you probably want to say
here. When you do so, you are prompted for the networking parameters of your installation network device:The IP address of the system to install
The corresponding netmask
The IP address of a gateway to reach the server
The IP address of your domain name server (DNS)
When using an OSA Express Network Card you are now prompted for a
0
. OSA Express cards
also have the option of running in an “OSI layer 2 support”
mode or using the older more common “layer 3” mode. The card
mode affects all systems that share the device including systems on other
LPARs. If in doubt, please specify 2
for compatibility
with the default mode used by other operating systems such as z/VM and
z/OS. Consult with your hardware administrator for further information on
these options.
After the kernel has completed its start-up routines, answer a few questions regarding the network setup. First, select the type of network connection to use: OSA Express or HiperSockets. In this example installation, OSA Express is used.
The system now displays a possible OSA configuration. Choose first whether to use QDIO or LCS OSA. Next, choose the physical medium to use and enter the device addresses. If you prefer another setup, enter the device address of the OSA read channel (0.0.0700 in this example) then the one of the OSA write channel (0.0.0701) and the OSA control channel (0.0.0702). After entering the channels, insert the name of the port to which the OSA card is connected.
SUSE Linux Enterprise Server now tries to load the network module by building a parameter line with the information provided and displaying all loaded modules. Loading was successful if you get an output like:
Example 4.9. Network Device Driver Parameters¶
(portname YSW2) (Port 0) qdio: 0.0.0702 OSA on SC 3 using AI:1 QEBSM:0 PCI:1 TDD:1 SIGA:RW AO qeth.736dae: 0.0.0700: Device is a Guest LAN QDIO card (level: V540) with link type GuestLAN QDIO (portname: YSW2) qeth.47953b: 0.0.0700: Hardware IP fragmentation not supported on eth0 qeth.066069: 0.0.0700: Inbound source MAC-address not supported on eth0 qeth.d7fdb4: 0.0.0700: VLAN enabled qeth.e90c78: 0.0.0700: Multicast enabled qeth.5a9d02: 0.0.0700: IPV6 enabled qeth.184d8a: 0.0.0700: Broadcast enabled qeth.dac2aa: 0.0.0700: Using SW checksumming on eth0. qeth.9c4c89: 0.0.0700: Outbound TSO not supported on eth0
Next, enter your IP address, netmask, and default gateway. To install over iucv or ctc, enter additional information, like the the peer address (for a point-to-point adapter) or the port name.
Finally, the IP address of the DNS server and the MTU size are requested. The MTU size should always match the one used by the network to which you are connecting.
Now a summary is displayed. Confirm if your input is correct. Before the network is started, enter a password that is valid only during the installation. After having IPLed the installed system, enter the real root password.
With all basic parameters set up, the network is started. Check the output of ifconfig, which should contain two entries: a loopback (lo) connection and one connection (eth0, ctc0, escon0, iucv0, or hsi0) with correct settings.
Example 4.10. Example ifconfig¶
/sbin/ifconfig eth0 : Link encap:Ethernet HWaddr 02:00:01:00:00:27 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::200:100:100:27/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 Mb) TX bytes:0 (0.0 Mb)
After setting up your network connection, linuxrc prompts for the details of the installation source chosen earlier in the process, for example, the server IP address and the directory in which the data is located.
Finally, linuxrc wants to know what type of display you want to use to
control the installation procedure. Possible choices are
X11
(X Window System), VNC
(Virtual
Network Computing protocol), and SSH
(text mode or X11
installation via Secure Shell).
After the installation option VNC
has been chosen,
the VNC server starts. A short note displayed in the console provides
information about which IP address and display number is needed for a
connection with vncviewer. Alternatively, a URL is given here for
entry into your Java-enabled browser to connect to the installation
system.
Start a VNC client application on your client system. Either use vncviewer or the VNC Java client and a Java-enabled Web browser.
Enter the IP address and the display number of the SUSE Linux Enterprise Server installation system when prompted to do so.
If you connect via a Java-enabled browser, enter a URL containing the IP address of the installation system and the appropriate port number in the format:
http://<IP address of installation system>:5801/
After the connection has been established, start installing SUSE Linux Enterprise Server with YaST.
![]() | X Authentication Mechanism |
---|---|
The direct installation with the X Window System relies on a primitive authentication mechanism based on hostnames. This mechanism is disabled on current SUSE Linux Enterprise Server versions. Installation with SSH or VNC is preferred. |
Make sure that the X server allows the client (the system that is
installed) to connect. Set the variable
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="yes" in
the file /etc/sysconfig/displaymanager
. Then
restart the X server and allow client binding to the server using
xhost <client IP address>.
When prompted at the installation system, enter the IP address of the machine running the X server.
Wait until YaST opens then start the installation.
To connect to an installation system with the name earth using SSH, execute ssh -X earth. If your workstation runs on Microsoft Windows, use the ssh and telnet client and terminal emulator putty, which is available from http://www.chiark.greenend.org.uk/~sgtatham/putty/. Set in putty under + + .
A login prompt appears. Enter root
and log in with
your password. Enter yast2 to start YaST.
Proceed with the detailed description of the installation procedure that can be found in Chapter 6, Installation with YaST.
SUSE Linux Enterprise Server for IBM System z includes network drivers for OSA devices (ethernet, and gigabit ethernet) and HiperSockets. This chapter describes the configuration within the SUSE Linux Enterprise Server installation system.
![]() | CTC, ESCON, and IUCV Interfaces No Longer Supported |
---|---|
CTC, ESCON, and IUCV interfaces are no longer officially supported. For compatibility reasons, they are still usable, but with the next release of SUSE Linux Enterprise Server the support of these interfaces will be dropped completely. |
Select your device from the list of network devices. Then enter the network device read channel number (such as 0.0.700), the write channel number (like 0.0.701) and the data channel number (like 0.0.702).
Example 4.11. Supported Network Connection Types and Driver Parameters¶
Choose the network device. 1) IBM parallel CTC Adapter (0.0.0600) 2) IBM parallel CTC Adapter (0.0.0602) 3) IBM parallel CTC Adapter (0.0.0604) 4) IBM Hipersocket (0.0.0700) 5) IBM Hipersocket (0.0.0701) 6) IBM Hipersocket (0.0.0702) 7) IBM OSA Express Network card (0.0.050c) 8) IBM OSA Express Network card (0.0.050d) 9) IBM OSA Express Network card (0.0.050e) 10) IBM OSA Express Network card (0.0.f401) 11) IBM OSA Express Network card (0.0.f400) 12) IBM OSA Express Network card (0.0.f402) 13) IBM IUCV > 4 Device address for read channel [0.0.700] >[0.0.700] Device address for write channel > 0.0.701 Device address for data channel > 0.0.702
Next, choose manual configuration then enter the IP address, netmask, broadcast address, IP address of the gateway, and the searchlist of the DNS server.
Example 4.12. Network Device Name¶
Automatic configuration via DHCP? 1) Yes 2) No > 2 Enter your IP address > 192.168.0.20 Enter your netmask. For a normal class C network, this is usually 255.255.255.0 [255.255.255.0] > 255.255.255.0 Enter the IP address of the gateway. Leave empty if you don't need one > 192.168.0.1 Enter your search domains, separated by a space: > example.com
Select an IBM OSA Express Network card
from the list
of network devices, and then 1
for ethernet. When
prompted, enter the network device's read, write, and data channel
numbers (for example, 0.0.0600
,
0.0.0601
, and 0.0.0602
) and the
port name, if applicable. Choose whether to enable OSI Layer 2 support.
Example 4.13. Network Device Driver Parameters¶
Detecting and loading network drivers netiucv.8db02b: driver initialized Choose the network device. 1) IBM OSA Express Network card (0.0.09a0) 2) IBM OSA Express Network card (0.0.09a1) 3) IBM OSA Express Network card (0.0.09a2) 4) IBM OSA Express Network card (0.0.0600) 5) IBM OSA Express Network card (0.0.0601) 6) IBM OSA Express Network card (0.0.0602) 7) IBM IUCV > 4 Please choose the physical medium. 1) Ethernet 2) Token Ring > 1 Enter the relative port number > 0 Device address for read channel [0.0.0600]> 0.0.0600 Device address for write channel > 0.0.0601 Device address for data channel > 0.0.0602 Portname to use > DT70 Enable OSI Layer 2 support? 1) Yes 2) No > 2
Next, deny the DHCP configuration and enter the IP address and netmask. Now enter the IP address of the gateway (if applicable), the search domain(s) and the IP address of the DNS server.
Example 4.14. Network configuration¶
Automatic configuration via DHCP? 1) Yes 2) No > 2 Enter your IPv4 address. Example: 192.168.5.77/24 > 192.168.0.20 Enter your netmask. For a normal class C network, this is usually 255.255.255.0 [255.255.255.0]> 255.255.255.0 Enter the IP address of the gateway. Leave empty if you don't need one > 192.168.0.2 Enter your search domains, separated by a space: > example.net Enter the IP address of your name server. Leave empty or enter "+++" if you don't need one > 192.168.0.1
The installation process can be partly automated by specifying the
crucial parameters in the parmfile
. The
parmfile
contains all the data required for network
setup and DASD configuration. In addition to that, it can be used to set
up the connection method to the SUSE Linux Enterprise Server installation system and the
YaST instance running there. User interaction is thus limited to the
actual YaST installation controlled by YaST dialogs.
The following parameters can be passed to the installation routine, which takes them as default values for installation. All IP addresses, server names, and numerical values are just examples. Replace these values with the ones needed in your installation scenario.
The number of lines in the parmfile is limited to 10. Specify more than
one parameter on a line. Parameter names are not case-sensitive. Separate
the parameters by spaces. You may specify the parameters in any order.
Always keep the PARAMETER=value
string together in one
line. For example:
Hostname=s390zvm01.suse.de HostIP=10.11.134.65
![]() | Using IPv6 during the Installation |
---|---|
By default you can only assign IPv4 network addresses to your machine.
To enable IPv6 during installation, enter one of the following
parameters at the bootprompt: |
Some of the following parameters are required. If they are missing, the automatic process pauses and asks you to enter the value manually.
<URL>
Manual=0
The AutoYaST
parameter specifies the location of the
autoinst.xml
control file for automatic
installation. The Manual
parameter controls if the
other parameters are only default values that still must be
acknowledged by the user. Set this parameter to 0
if all values should be accepted and no questions asked. Setting
AutoYaST
implies setting Manual
to
0
.
<URL>
Specifies a location for a file from which to read additional
options. This helps to overcome the limitations of 10 lines (and 80
characters per line under z/VM) for the parmfile. More documentation
on the Info file can be found in
Section 21.1.5, “Creating the info
File”. Since the Info
file can typically only be accessed through the network on System z,
you cannot use it to specify options required to setup the network,
i.e. options described in Section 4.4.2, “Configuring the Network Interface”.
Also other linuxrc specific options such as for debugging have to be
specified in the parmfile to be effective.
![]() | Creating a File with Autoinstallation Information |
---|---|
At the very end of the installation of a system you can check
|
![]() | Configuring the Network Interface |
---|---|
The settings discussed in this section apply only to the network interface used during installation. Configure additional network interfaces in the installed system by following the instructions given in Section “Configuring a Network Connection Manually” (Chapter 18, Basic Networking, ↑Administration Guide). |
Enter the fully qualified hostname.
Domain search path for DNS. Allows you to use short host names instead of fully qualified ones.
Enter the IP address of the interface to configure.
Specify the gateway to use.
Specify the DNS server in charge.
Enter the type of interface to configure. Possible values are
osa
, hsi
.
ctc
, escon
, and
iucv
. (CTC, ESCON, and IUCV are no longer
officially supported).
For the interfaces of type hsi
and
osa
, specify an appropriate netmask and an
optional broadcast address:
Netmask=255.255.255.0 Broadcast=192.168.255.255
For the interfaces of type ctc
,
escon
, and iucv
(CTC, ESCON,
and IUCV are no longer officially supported), enter the IP address of
the peer:
Pointopoint=192.168.55.20
For osa
network devices, specify the host
interface (qdio
or lcs
) and the
physical medium (eth
for ethernet or
tr
for token ring).
For osa
QDIO ethernet and hsi
devices, specify whether to enable OSI Layer 2 support.
For Layer 2-enabled osa
QDIO ethernet devices,
specify the manual MAC address. Note that this is distinct from
HWAddr, which contains the default MAC address as detected by
linuxrc.
For osa
network devices, specify the port number
(provided the device supports this feature). The default value is 0.
Each of the interfaces requires certain setup options:
Interfaces ctc
and escon
(CTC
and ESCON are no longer officially supported):
ReadChannel=0.0.0424 WriteChannel=0.0.0425
ReadChannel
specifies the READ channel to use.
WriteChannel
specifies the WRITE channel.
For the ctc
interface (no longer officially
supported), specify the protocol that should be used for this
interface:
CTCProtocol=<0/1/2>
Valid entries would be:
|
Compatibility mode, also for non-Linux peers other than OS/390 and z/OS (this is the default mode) |
|
Extended mode |
|
Compatibility mode with OS/390 and z/OS |
Network device type osa
with interface
lcs
:
ReadChannel=0.0.0124 Portname=1
ReadChannel
stands for the channel number used in this
setup. A second port number can be derived from this by adding one to
ReadChannel
. Portnumber
is used to
specify the relative port.
Interface iucv
:
IUCVPeer=PARTNER
Enter the name of the peer machine.
Network device type osa
with interface
qdio
for OSA-Express Gigabit Ethernet and
OSA-Express High-speed Token Ring:
ReadChannel=0.0.0524 WriteChannel=0.0.0525 DataChannel=0.0.0526 Portname=FEF400
For ReadChannel
, enter the number of the READ channel.
For WriteChannel
, enter the number of the WRITE
channel. DataChannel
specifies the DATA channel. For
Portname
, enter an appropriate port name. Make sure
that the READ channel carries an even device number.
Interface hsi
for HiperSockets and VM guest LANs:
ReadChannel=0.0.0624 WriteChannel=0.0.0625 DataChannel=0.0.0626
For ReadChannel
, enter the appropriate number for the
READ channel. For WriteChannel
and
DataChannel
, enter the WRITE and DATA channel numbers.
Specify the location of the installation source to use. Possible
protocols are nfs
, smb
(Samba/CIFS), ftp
, and http
.
If an ftp
or smb
URL is given,
specify the username and password with the URL. These parameters are
optional and anonymous or guest login is assumed if they are not
given.
Install=ftp://user
:password
@server
/directory
/DVD1/
In case of a Samba or CIFS installation, you can also specify the domain that should be used:
Install=smb://workdomain
;user
:password
@server
/directory
/DVD1/
Depending on which parameter you give, a remote X server, SSH, or VNC
will be used for installation. UseSSH
enables SSH
installation, UseVNC
starts a VNC server on the
installing machine, and Display_IP
causes the
installing system to try to connect to an X server at the given
address. Only one of these parameters should be set at any time.
![]() | X Authentication Mechanism |
---|---|
The direct installation with the X Window System relies on a primitive authentication mechanism based on hostnames. This mechanism is disabled on current SUSE Linux Enterprise Server versions. Installation with SSH or VNC is preferred. |
To allow a connection between YaST and the remote X server, run
xhost <IP address>
with the address of the installing machine on the remote machine.
For VNC
, specify a password of six to eight
characters to use for installation:
VNCPassword=<a password>
For SSH
, specify a password of six to eight
characters to use for installation:
SSHPassword=<a password>
For an automatic installation with AutoYaST in an LPAR, it is preferable that the parmfile has just one long line. If multiple lines are desired for readability, use blank characters at the beginning and end of each line. The maximum number of lines in a parmfile is 10.
To receive potential error messages on the console, use
linuxrclog=/dev/console
Example 4.15. Parmfile for Installation with NFS, VNC, and IUCV and AutoYaST with HTTP¶
ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb instnetdev=iucv iucvpeer=ROUTER01 pointopoint=192.168.0.1 hostip=192.168.0.2 nameserver=192.168.0.3 install=nfs://192.168.0.4/SLES/SLES-11-s390x/DVD1 autoyast=http://192.168.0.5/autoinst.xml linuxrclog=/dev/console usevnc=1 vncpassword=testin
Example 4.16. Parmfile for Installation with NFS, SSH, and HSI and AutoYaST with NFS¶
ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb AutoYast=nfs://192.168.1.1/autoinst/s390.xml Hostname=zseries.example.com HostIP=192.168.1.2 Gateway=192.168.1.3 Nameserver=192.168.1.4 InstNetDev=hsi layer2=0 Netmask=255.255.255.128 Broadcast=192.168.1.255 readchannel=0.0.702c writechannel=0.0.702d datachannel=0.0.702e install=nfs://192.168.1.5/SLES-11-s390x/DVD1/ UseSSH=1 SSHPassword=testing linuxrclog=/dev/console
Recent MicroCode Levels allow the use of an integrated vt220 terminal
emulator in addition to the standard line mode terminal. The vt220
terminal is connected to /dev/ttyS1
. The line mode
terminal is connected to /dev/ttyS0
. If the vt220
emulation is available, an icon for an integrated vt220 ASCII console
appears next to the icon for the 3215 console on the HMC/SE.
To activate vt220 support on your machine, edit
/etc/inittab
as user
root
. Look for the
following line and delete the leading #
sign:
#2:2345:respawn:/sbin/mingetty --noclear /dev/ttyS1 xterm
Save the file and run telinit q
to pass the changes in /etc/inittab
to init. The
vt220 terminal should then be ready to use. If not, try hitting
Enter at the terminal until the login prompt appears.
Make sure that you do not apply the changes as described above to a system that does not support vt220 terminal emulators. Otherwise, login might become impossible on this system and you will be shown the following message:
INIT respawning too fast, disabled for 5 minutes.
To redirect the kernel messages at boot time from the system console to
the vt220 terminal, add the following entries to the
parameters
line in
/etc/zipl.conf
:
console=ttyS0 console=ttyS1
The resulting parameters
line would look like the
following example:
parameters = "root=/dev/dasda2 TERM=dumb console=ttyS0 console=ttyS1"
Save the changes in /etc/zipl.conf
, run
zipl, and reboot the system.
IBM has published a number of very interesting documents about their System z platform. Find them at http://www.redbooks.ibm.com.
Find additional in-depth technical documentation about the kernel and application topics on IBM System z with SUSE Linux Enterprise Server at the following location:
For a first glance at the technical details of some systems, refer to:
IBM System z10 Enterprise Class Technical Introduction (SG24-7515)
IBM System z9 Business Class Technical Introduction (SG24-7241)
Linux on zSeries Fibre Channel Protocol Implementation Guide (SG24-6344)
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 reflect the current state of Linux, but the principles of Linux deployment outlined there remain accurate.
Refer to the following documents to get in-depth technical information about the 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 on System z Device Drivers, Features, and Commands
zSeries ELF Application Binary Interface Supplement
Linux on System z Device Drivers, Using the Dump Tools
IBM System z9-109 Technical Introduction (SG26-6669)
IBM System z10 Enterprise Class Technical Guide (SG24-7516)
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)
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)
Linux on IBM zSeries and S/390: High Availability for z/VM and Linux (REDP-0220)
Saved Segments Planning and Administration
Linux on System z documentation for "Development stream"
http://www.ibm.com/developerworks/linux/linux390/development_documentation.html