Contents
Abstract
In this chapter, 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 for x86, you can set up an installation server (NFS or FTP) using the YaST
module as described in Section “Setting Up an Installation Server Using YaST” (Chapter 4, Remote Installation, ↑Installation and Administration).Use 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
.
DVD 1 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 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 DVD 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 DVD 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 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 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 2.1. Overview of LPAR Installation¶
Prepare the devices needed for installation. See Section 2.3.1, “LPAR Installation”.
IPL the installation system. See Section 2.4.1, “LPAR Installation”.
Configure the network. See Section 2.5, “Network Configuration”.
Connect to the SUSE Linux Enterprise Server installation system. See Section 2.6, “Connecting to the SUSE Linux Enterprise Server Installation System”.
Start the installation using YaST and IPL the installed system. See Chapter Installation with YaST (↑Installation and Administration).
Procedure 2.2. Installation Overview of z/VM Installation¶
Prepare the devices needed for installation. See Section 2.3.2, “z/VM Installation”.
IPL the installation system. See Section 2.4.2, “z/VM Installation”.
Configure the network. See Section 2.5.1, “z/VM Installation”.
Connect to the SUSE Linux Enterprise Server installation system. See Section 2.6, “Connecting to the SUSE Linux Enterprise Server Installation System”.
Start the installation using YaST and IPL the installed system. See Chapter Installation with YaST (↑Installation and Administration).
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 IBM hardware documentation of your machine .
Example 2.1. An Example IOCDS¶
CHPID PATH=FD,TYPE=DSD,PART=(Z1) CHPID PATH=FE,TYPE=OSA,PART=(Z1) CHPID PATH=10,TYPE=CNC,PART=(Z1) CNTLUNIT CUNUMBR=FD00,PATH=FD,UNITADD=((00,1)),UNIT=3990-2 IODEVICE ADDRESS=(FD00,1),CUNUMBR=FD00,UNIT=3390 CNTLUNIT CUNUMBR=FE20,PATH=FE,UNIT=OSA,UNITADD=((20,1)) IODEVICE ADDRESS=(FE20,1),CUNUMBR=FE20,UNIT=OSA,PART=Z1 CNTLUNIT CUNUMBR=100A,PATH=10,UNIT=3480,UNITADD=((0A,1)) IODEVICE ADDRESS=100A,CUNUMBR=100A,UNIT=3480,PART=Z1
Proceed with Section 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 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 2.2. 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 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 then select . 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-ROM, 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/tapeipl.ikr /boot/parmfile /boot/initrd
as binary files from DVD 1 (for example, using FTP from a Linux workstation).
Name them
SLES10 IMAGE SLES10 PARM SLES10 INITRD
and write them onto a tape with the REXX from the example.
![]() | Transferring Binaries using FTP |
---|---|
Do not upload the files as |
Example 2.3. REXX Script to Create an IPLable Tape¶
'REWIND 181' 'FILEDEF IN1 DISK' SLES10 IMAGE A 'FILEDEF IN2 DISK' SLES10 PARM A 'FILEDEF IN3 DISK' SLES10 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
sles10.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 sles10.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 2.4. 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) Fri Jan 30 14:58:32 GMT 2009) 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 sles10.image 200 PORT Command successful 150 Opening BINARY mode data connection for /media/dvd1/boot/s390x/vmrdr.ikr (7186760 bytes) 226 Transfer complete. 7186760 bytes transferred in 8.826 seconds. Transfer rate 814.27 Kbytes/sec. Command: get /media/dvd1/boot/s390x/initrd sles10.initrd 200 PORT Command successful 150 Opening BINARY mode data connection for /media/dvd1/boot/s390x/initrd (8624134 bytes) 226 Transfer complete. 8624134 bytes transferred in 9.720 seconds. Transfer rate 887.26 Kbytes/sec. Command: ascii 200 Type set to A Command: get /media/dvd1/boot/s390x/parmfile sles10.parmfile 150 Opening ASCII mode data connection for /media/dvd1/boot/s390x/parmfile (63 bytes) 226 Transfer complete. 63 bytes transferred in 0.082 seconds. Transfer rate 0.63 Kbytes/sec. Command: get /media/dvd1/boot/s390x/sles10.exec sles10.exec 150 Opening ASCII mode data connection for /media/dvd1/boot/s390x/sles10.exec (896 bytes) 226 Transfer complete. 896 bytes transferred in 0.097 seconds. Transfer rate 0.89 Kbytes/sec. Command: quit
Use the REXX script sles10.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 2.5. SLES10 EXEC¶
/* REXX LOAD EXEC FOR SUSE LINUX S/390 VM GUESTS */ /* LOADS SUSE LINUX S/390 FILES INTO READER */ SAY '' SAY 'LOADING SLES10 FILES INTO READER...' 'CP CLOSE RDR' 'PURGE RDR ALL' 'SPOOL PUNCH * RDR' 'PUNCH SLES10 IMAGE A (NOH' 'PUNCH SLES10 PARMFILE A (NOH' 'PUNCH SLES10 INITRD A (NOH' 'I 00C'
With this script you can IPL the SUSE Linux Enterprise Server installation system with the command sles10. The Linux kernel then starts and prints its boot messages.
To continue the installation, proceed to Section 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 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 2.4.1.3, “IPL from ESCON or FICON Attached Tape”.
To continue the installation, proceed with Section 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 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 (for example, or ). 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.
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 then displays all loaded modules. Loading was successful if you get an output like:
Example 2.6. Network Device Driver Parameters¶
qeth: Device 0.0.0700/0.0.0701/0.0.0702 is a Guest LAN QDIO card (level: V448) with link type GuestLAN QDIO (portname: VSW1) qeth: Hardware IP fragmentation not supported on eth0 qeth: VLAN enabled qeth: Multicast enabled qeth: IPV6 enabled qeth: Broadcast enabled qeth: Could not set up broadcast echo filtering on eth0: 0x2 qeth: Using SW checksumming on eth0. qeth: Outbound TSO not supported on eth0
Next, enter your IP address, netmask, and default gateway. To install over token ring, 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 (tr0, eth0, ctc0, escon0, iucv0, or hsi0) with correct settings.
Example 2.7. 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 on DVD 1 in the
directory /dosutils/putty/
. Set in putty under + + .
A login prompt appears. Enter root
and log in with
your password. Then enter yast2 to start YaST.
Proceed with the detailed description of the installation procedure that can be found in Chapter Installation with YaST (↑Installation and Administration).