The Intel 64 and AMD64 architectures support the simple migration of x86 software to 64 bits. Like the x86 architecture, they constitute a value-for-money alternative.

SUSE Linux Enterprise Server is normally installed as an independent operating system. With the introduction of Virtualization, it is also possible to run multiple instances of SUSE Linux Enterprise Server on the same hardware. However, the installation of the VM Host Server is performed like a typical installation with some additional packages. The installation of virtual guests is described in Book “Virtualization Guide”, Chapter 9 “Guest Installation”.

Depending on the hardware used, the following boot methods are available for the first boot procedure (prior to the installation of SUSE Linux Enterprise Server).

When installing SUSE Linux Enterprise Server, the actual installation data must be available in the network, on a hard disk partition, or on a local DVD. To install from the network, you need an installation server. To make the installation data available, set up any computer in a Unix or Linux environment as an NFS, HTTP, SMB, or FTP server. To make the installation data available from a Windows computer, release the data with SMB.

The installation source is particularly easy to select if you configure an SLP server in the local network. For more information, see Chapter 7, Setting Up the Server Holding the Installation Sources.

Most installations are to a local hard disk. Therefore, it is necessary for the hard disk controllers to be available to the installation system. If a special controller (like a RAID controller) needs an extra kernel module, provide a kernel module update disk to the installation system.

Other installation targets may be various types of block devices that provide sufficient disk space and speed to run an operating system. This includes network block devices like iSCSI or SAN. It is also possible to install on network file systems that offer the standard Unix permissions. However, it may be problematic to boot these, because they must be supported by the initramfs before the actual system can start. Such installations are useful if there is a need to start the same system in different locations or if you intend to use virtualization features like domain migration.

SUSE Linux Enterprise Server offers several methods for controlling installation:

By default, the graphical console is used. If you have many similar computers to install, it is advisable to create an AutoYaST configuration file or a KIWI preload image and make this available to the installation process. See also the documentation for AutoYaST at https://www.suse.com/documentation/sles-12/book_autoyast/data/book_autoyast.html and KIWI at http://doc.opensuse.org/projects/kiwi/doc/.

Booting a computer depends on the capabilities of the hardware used and the availability of media for the respective boot option.

The installation media contain all the necessary packages and meta information that is necessary to install a SUSE Linux Enterprise Server. These must be available to the installation system after booting for installation. Several possibilities for providing the installation media to the system are available with SUSE Linux Enterprise Server.

DVD-ROM and USB storage devices can be used for installation purposes. Adjust your computer to your needs:

An installation server is required to perform the installation by using a network source. The procedure for installing this server is outlined in Chapter 7, Setting Up the Server Holding the Installation Sources.

If you have an SLP server, select SLP as the installation source in the first boot screen. During the boot procedure, select which of the available installation sources to use.

If the DVD is available on the network, use it as an installation source. In this case, specify the parameter install=<URL> with suitable values at the boot prompt. Find a more detailed description of this parameter in Section 9.2.2, “Using Custom Boot Options”.

The simplest way to install SUSE Linux Enterprise Server is using the computer console. With this method, a graphical installation program guides you through the installation. This installation method is discussed in detail in Chapter 6, Installation with YaST.

You can still perform the installation on the console without a working graphics mode. The text-based installation program offers the same functionality as the graphical version. Find some hints about navigation in this mode in Book “Administration Guide”, Chapter 4 “YaST in Text Mode”, Section 4.1 “Navigation in Modules”.

For this installation method, you need a second computer that is connected by a null modem cable to the computer on which to install SUSE Linux Enterprise Server. Depending on the hardware, even the firmware or BIOS of the computer may already be accessible to the serial console. If this is possible, you can carry out the entire installation using this method. To activate the serial console installation, additionally specify the parameter console=ttyS0 at the boot prompt after the boot process has completed and before the installation system starts.

On most computers, there are two serial interfaces, ttyS0 and ttyS1. For the installation, you need a terminal program like minicom or screen. To initiate the serial connection, launch the screen program in a local console by entering the following command:

screen /dev/ttyS0 9600

This means that screen listens to the first serial port with a baud rate of 9600. From this point on, the installation proceeds similarly to the text-based installation over this terminal.

If you do not have direct access to the computer hardware and, for example, the installation should be launched from a management console, control the entire installation process over the network. To do this, enter the parameters ssh=1 and ssh.password=SECRET at the boot prompt. An SSH daemon is then launched in the system and you can log in as user root with the password SECRET.

To connect, use ssh -X. X-Forwarding over SSH is supported, if you have a local X server available. Otherwise, YaST provides a text interface over ncurses. YaST then guides you through the installation. This procedure is described in detail in Section 9.1.5, “Simple Remote Installation via SSH—Dynamic Network Configuration”.

If you do not have a DHCP server available in your local network, manually assign an IP address to the installation system. Do this by entering the option HostIP=IPADDR at the boot prompt.

If you do not have direct access to the system, but want a graphical installation, install SUSE Linux Enterprise Server over VNC. This method is described in detail in Section 9.3.1, “VNC Installation”.

As suitable VNC clients are also available for other operating systems, such as Microsoft Windows and macOS, the installation can also be controlled from computers running those operating systems.

If you need to install SUSE Linux Enterprise Server on several computers with similar hardware, it is recommended you perform the installations with the aid of AutoYaST. In this case, start by installing one SUSE Linux Enterprise Server and use this to create the necessary AutoYaST configuration files.

Boot problems may prevent the YaST installer from starting on your system. Another symptom is when your system does not boot after the installation has been completed.

If an unexpected problem occurs during installation, information is needed to determine the cause of the problem. Use the following directions to help with troubleshooting:

To simplify the installation process and avoid accidental installations, the default setting on the installation DVD for SUSE Linux Enterprise Server is that your system is booted from the first hard disk. At this point, an installed boot loader normally takes over control of the system. This means that the boot DVD can stay in the drive during an installation. To start the installation, choose one of the installation possibilities in the boot menu of the media.

The SUSE® Linux Enterprise Server operating system can be operated on IBM POWER8 servers. To provide you with a guide to help you during the planning phase, the minimum requirements are presented here.

If you want to be sure that a given computer configuration will work, check the database of hardware certified by SUSE. Find a list of certified hardware at http://www.suse.com/yessearch/Search.jsp.

SUSE Linux Enterprise Server may support additional IBM POWER systems not listed below. For the latest information, see the IBM Information Center for Linux at http://www.ibm.com/support/knowledgecenter/linuxonibm/liaam/liaamdistros.htm.

Find up-to-date firmware at IBM FixCentral (http://www.ibm.com/support/fixcentral/). Select your system from the Product Group list. Additional software is available from the IBM PowerLinux Tools Repository. The IBM Tools Repository is also called the Yum Repository. For more information about using the IBM PowerLinux Tools Repository, see https://ibm.biz/Bdxn3N.

This section covers the preparatory steps for installing on IBM PowerLinux systems with PowerKVM. It explains the installation from an ISO image with the Kimchi Web interface. Kimchi is a tool for administrating IBM PowerKVM.

This section assumes you have PowerKVM running on your IBM PowerLinux server. If PowerKVM is not preinstalled see “Configuring IBM PowerKVM on Power Systems” at http://www.ibm.com/support/knowledgecenter/linuxonibm/liabp/liabpkickoff.htm for installing and setting up PowerKVM.

3.2.1.2 Installing SUSE Linux Enterprise Server as a Guest with Kimchi #Edit source

1. In the Web browser, enter the URL of the PowerLinux server where PowerKVM is running, for example https://POWERLINUX_IP:8001 (replace POWERLINUX_IP with the IP address of your system).

2. Click the Guests tab to activate the Guests page.

3. Click the green plus sign (+) to create the SUSE Linux Enterprise Server guest.

4. Enter a Virtual Machine Name for the SUSE Linux Enterprise Server guest.

   Choose the SUSE Linux Enterprise Server template created in Section 3.2.1.1, “Creating a SUSE Linux Enterprise Server Template with Kimchi” and click Create.

   

5. After the guest is created, it is ready to be started. Click the red power button to start the SUSE Linux Enterprise Server guest. Alternatively, select Actions › Start.

6. Click Actions › Connect, and connect your VNC viewer to the installation process as outlined in Section 9.3.1.2, “Connecting to the Installation Program”.

Tip: Creating Multiple Guests

To create multiple guests of a similar type, select Clone from the Actions menu of an existing guest.

Now you can continue with the default installation via VNC as described in Section 6.3, “Steps of the Installation”.

Alternatively to installing with Kimchi, use the virt-install command line tool to install on Servers with IBM PowerKVM. This is especially useful you need to install multiple virtual machines on IBM PowerLinux Server systems. virt-install allows many installation scenarios; in the following a remote installation scenario via VNC and PXE boot is outlined. For more information about virt-install, see Book “Virtualization Guide”, Chapter 9 “Guest Installation”, Section 9.2 “Installing from the Command Line with virt-install”.

Prepare a repository with the installation sources and PXE boot enabled target system as described in Section 9.1.3, “Remote Installation via VNC—PXE Boot and Wake on LAN”.

On the command line, enter something similar as follows (adjust the options according to your needs and matching your hardware):

virt-install --name server_sle12 --memory 4096 --vcpus=2 --pxe \
--graphics vnc --os-variant sles11 \
--disk pool=default,size=3000,format=qcow2,allocation=1G,bus=virtio \
-w mac=mac_address,model=spapr-vlan

It will use VNC graphics, and it will automatically launch the graphical client. Complete the installation as described in Section 6.3, “Steps of the Installation”.

This guide helps you installing SUSE Linux Enterprise Server on a Power Systems server partition using the Integrated Virtualization Manager (IVM) Web interface. Before starting the installation, make sure the following requirements are met:

Next,create a partition, following these steps:

Now activate the partition you have created:

The machine is set up now and you can boot into the installation:

After the Kernel has started to load, the installer needs some information from the system in order to set up a VNC session. You must have a valid TCP/IP stack in order to use VNC. Either use DHCP or manually define your networking information using directions provided by the installer.

Use this information to install Linux using a serial console or using a monitor and keyboard on a Power Systems server. This installation assumes an unmanaged (stand-alone) system that is ready to boot.

After the Kernel has started to load, the installer needs some information from the system in order to set up a VNC session. You must have a valid TCP/IP stack in order to use VNC. Either use DHCP or manually define your networking information using directions provided by the installer.

This section provides a list of hardware for IBM z Systems supported by SUSE Linux Enterprise Server. Next, the level of the MicroCode (MCL) used in your IBM z Systems 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.

4.1.1.1 Hardware #Edit source

SUSE Linux Enterprise Server has run successfully on the following platforms:

• IBM zEnterprise System z196 (2817)

• IBM zEnterprise System z114 (2818)

• IBM zEnterprise EC12 (zEC12) (2827)

• IBM zEnterprise BC12 (zBC12) (2828)

• IBM z Systems z13 (2964)

• IBM z Systems z13s (2965)

• IBM LinuxONE Emperor (2964)

• IBM LinuxONE Rockhopper (2965)

4.1.1.1.1 Memory Requirements #Edit source

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:

1 GB	For installation under z/VM.
1 GB	For installation under LPAR.
1 GB	For installation under KVM.

Note: 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.

4.1.1.1.2 Disk Space Requirements #Edit source

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:

800 MB	Minimal Installation
1.4 GB	Minimal Installation + Base System
2.6 GB	Default Installation
3.6 GB+	Recommended (this is with graphical desktop, development packages and Java).

4.1.1.1.3 Network Connection #Edit source

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

• RoCE (RDMA over Converged Ethernet)

The following interfaces are still included, but no longer supported:

• CTC (or virtual CTC)

• ESCON

• IP network interface for IUCV

For installations under KVM make sure the following requirements are met to enable the VM Guest to access the network transparently:

• The virtual network interface is connected to a host network interface.

• The host network interface is connected to a network in which the virtual server will participate.

• If the host is set up to have a redundant network connection by grouping two independent OSA network ports into a bonded network interface, the identifier for the bonded network interface is bond0 (or, if more than one bonded interface exists, bond1, bond2, ...). See http://www.ibm.com/support/knowledgecenter/SSNW54_1.1.0/com.ibm.kvm.v110.admin/toc.htm for further information about how to configure network bonding.

• If the host network connection has not been set up redundantly, the identifier of the single network interface needs to be used. It has the form enccw0.0.nnnn, where nnnn is the device number of the desired network interface.

4.1.1.3 Software #Edit source

When installing 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 or VNC are recommended):

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 available from http://www.chiark.greenend.org.uk/~sgtatham/putty/.

VNC Client

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.

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 macOS*. Some 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.

Tip: Additional Information

Consult the README located in the root directory of DVD 1 of your SUSE Linux Enterprise Server before installing SUSE Linux Enterprise Server on IBM z Systems. This file completes the documentation presented in this book.

This section gives an overview of the different types of installation possible with SUSE Linux Enterprise Server for IBM z Systems:

Depending on the mode of installation (LPAR or z/VM), there are different possibilities for starting the installation process and IPLing the installed system.

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 VM reader, load from CD-ROM or server and load from an SCSI-attached DVD-ROM options are discussed. Installing the software packages, which is done over the network, does not require the IPL medium.

This section provides detailed information about making the SUSE Linux Enterprise Server IBM z Systems 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 z Systems system.

Tip: 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.

Note: No Installation “From Hard Disk”

It is not possible to install from hard disk by putting the content of the DVD to a partition on a DASD.

4.2.1.1 Using a Linux Workstation or SUSE Linux Enterprise Server DVD #Edit source

If you have a Linux workstation running in your computer environment, use the workstation to provide the installation data to the IBM z Systems 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 Installation Server module as described in Section 7.1, “Setting Up an Installation Server Using YaST”.

4.2.1.1.1 Over NFS #Edit source

Use NFS (network file system) to make the installation media available.

Important: Exporting Mounted Devices with NFS

Exporting the file system root (/) does not imply the export of mounted devices, such as DVD. Explicitly name the mount point in /etc/exports:

/media/dvd  *(ro)

After changing this file, restart the NFS server with the command sudo systemctl restart nfsserver.

4.2.1.1.2 Over FTP #Edit source

Setting up an FTP server on a Linux system involves the installation of the server software itself, such as vsftpd , and other possible configuration tasks. If you are using SUSE Linux Enterprise Server, refer to Book “Administration Guide”, Chapter 30 “Setting Up an FTP Server with YaST” for installation instructions. Downloading the installation data via anonymous login is not supported, therefore you need to configure the FTP server to support user authentication.

4.2.1.1.3 SUSE Linux Enterprise Server on DVD #Edit source

DVD1 of the SUSE Linux Enterprise Server for IBM z Systems contains a bootable Linux image for Intel-based workstations and an image for z Systems.

For Intel-based workstations, boot from this DVD, answer the questions regarding your language and keyboard layout, and select Start rescue system. 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 z Systems, 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 z Systems 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.

smb://DOMAIN;USER:PW@SERVERNAME/SHAREPATH

cobbler import --path=PATH1 --name=IDENTIFIER2 --arch=s390x

cobbler distro add --arch=s390 --breed=suse --name="IDENTIFIER"1 \
  --os-version=sles122 \
  --initrd=/srv/www/cobbler/ks_mirror/IDENTIFIER/boot/s390x/initrd3 \
  --kernel=/srv/www/cobbler/ks_mirror/IDENTIFIER/boot/s390x/linux4 \
  --kopts="install=http://cobbler.example.com/cobbler/ks_mirror/IDENTIFIER"5

cobbler distro edit \
--name=IDENTIFIER1 --os-version=sles102 --ksmeta=""3
--kopts="install=http://cobbler.example.com/cobbler/ks_mirror/IDENTIFIER"4

cobbler system add --name=linux01 --hostname=linux01.example.com \
--profile=IDENTIFIER --interface=qdio \
--ip-address=192.168.2.103 --subnet=192.168.2.255 --netmask=255.255.255.0 \
--name-servers=192.168.1.116 --name-servers-search=example.com \
--gateway=192.168.2.1 --kopts="KERNEL_OPTIONS"

--kopts=" \
AutoYaST=http://192.168.0.5/autoinst.xml \
Hostname=linux01.example.com \
Domain=example.com \
HostIP=192.168.2.103 \
Gateway=192.168.2.1 \
Nameserver=192.168.1.116 \
Searchdns=example.com \
InstNetDev=osa; \
Netmask=255.255.255.0 \
Broadcast=192.168.2.255 \
OsaInterface=qdio \
Layer2=0 \
PortNo=0 \
ReadChannel=0.0.0700 \
WriteChannel=0.0.0701 \
DataChannel=0.0.0702 \
DASD=600"

4.2.1.4 Installing from DVD or Flash Disk of the HMC #Edit source

To install SUSE Linux Enterprise Server on IBM z Systems servers, usually a network installation source is needed. However, in certain environments, it could occur that this requirement cannot be fulfilled. With SUSE Linux Enterprise Server, you can use the existing DVD or the flash disk of the Hardware Management Console (HMC) as an installation source for installation on an LPAR.

To install from the media in the DVD or the flash disk of the HMC, proceed as follows:

• Add

  install=hmc:/

  to the parmfile (see Section 4.3, “The parmfile—Automating the System Configuration”) or kernel options.

• Alternatively, in manual mode, in linuxrc, choose:

  Start Installation, then

  Installation, then

  Hardware Management Console.

  The installation medium must be inserted in the HMC.

Important: Configure Network

Do not forget to configure the network in linuxrc before starting the installation. There is no way to pass on boot parameters later in time, and it is very likely that you will need network access. In linuxrc, go to Start Installation, then choose Network Setup.

Important: Linux System Must Boot First

Before granting access to the media in the DVD or the flash disk of the HMC, wait until the Linux system is booting. IPLing can disrupt the connection between the HMC and the LPAR. If the first attempt to use the described method fails, you can grant the access and retry the option HMC.

Note: Installation Repository

Because of the transitory nature of the assignment, the DVD or the flash disk files will not be kept as a repository for installation. If you need an installation repository, register and use the online repository.

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 three different installation modes for Linux on IBM z Systems:

Wait until the kernel has completed its start-up routines. If you are installing in basic mode or in an LPAR, open the Operating System Messages on the HMC or SE.

First, choose Start Installation in the linuxrc main menu then Start Installation or Update to start the installation process. Select Network as your installation medium then select the type of network protocol you will be using for the installation. 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, FTP, HTTP, NFS, and SMB/CIFS (Windows file sharing) are supported.

Now choose an OSA or HiperSockets network device over which to receive the installation data from the list of available devices. The list may also contain CTC, ESCON, or IUCV devices, but they are no longer supported on SUSE Linux Enterprise Server.

Choose the network device.

 1) IBM parallel CTC Adapter (0.0.0600)
 2) IBM parallel CTC Adapter (0.0.0601)
 3) IBM parallel CTC Adapter (0.0.0602)
 4) IBM Hipersocket (0.0.0800)
 5) IBM Hipersocket (0.0.0801)
 6) IBM Hipersocket (0.0.0802)
 7) IBM OSA Express Network card (0.0.0700)
 8) IBM OSA Express Network card (0.0.0701)
 9) IBM OSA Express Network card (0.0.0702)
10) IBM OSA Express Network card (0.0.f400)
11) IBM OSA Express Network card (0.0.f401)
12) IBM OSA Express Network card (0.0.f402)
13) IBM IUCV

> 4

Device address for read channel. (Enter '+++' to abort).
[0.0.800]> 0.0.800

Device address for write channel. (Enter '+++' to abort).
[0.0.801]> 0.0.801

Device address for data channel. (Enter '+++' to abort).
[0.0.802]> 0.0.802

Choose the network device.

 1) IBM parallel CTC Adapter (0.0.0600)
 2) IBM parallel CTC Adapter (0.0.0601)
 3) IBM parallel CTC Adapter (0.0.0602)
 4) IBM Hipersocket (0.0.0800)
 5) IBM Hipersocket (0.0.0801)
 6) IBM Hipersocket (0.0.0802)
 7) IBM OSA Express Network card (0.0.0700)
 8) IBM OSA Express Network card (0.0.0701)
 9) IBM OSA Express Network card (0.0.0702)
10) IBM OSA Express Network card (0.0.f400)
11) IBM OSA Express Network card (0.0.f401)
12) IBM OSA Express Network card (0.0.f402)
13) IBM IUCV

> 7

Enter the relative port number. (Enter '+++' to abort).
> 0

Device address for read channel. (Enter '+++' to abort).
[0.0.0700]> 0.0.0700

Device address for write channel. (Enter '+++' to abort).
[0.0.0701]> 0.0.0701

Device address for data channel. (Enter '+++' to abort).
[0.0.0702]> 0.0.0702

Enable OSI Layer 2 support?

0) <-- Back <--
1) Yes
2) No

> 1

MAC address. (Enter '+++' to abort).
> +++

Automatic configuration via DHCP?

0) <-- Back <--
1) Yes
2) No

> 2

Enter your IP address with network prefix.

You can enter more than one, separated by space, if necessary.
Leave empty for autoconfig.

Examples: 192.168.5.77/24 2001:db8:75:fff::3/64. (Enter '+++' to abort).
> 192.168.0.20/24

Enter your name server IP address.

You can enter more than one, separated by space, if necessary.
Leave empty if you don't need one.

Examples: 192.168.5.77 2001:db8:75:fff::3. (Enter '+++' to abort).
> 192.168.0.1

Enter your search domains, separated by a space:. (Enter '+++' to abort).
> example.com

Enter the IP address of your name server. Leave empty if you do not need one. (En
ter '+++' to abort).
> 192.168.0.1

After having loaded the installation system, 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), SSH (text mode or X11 installation via Secure Shell), or ASCII Console. Selecting VNC or SSH is recommended.

When selecting the latter (ASCII Console), YaST will be started in text mode and you can perform the installation directly within your terminal. See Book “Administration Guide”, Chapter 4 “YaST in Text Mode” for instructions on how to use YaST in text mode. Using the ASCII Console is only useful when installing into LPAR.

Note: Terminal Emulation for ASCII Console

To be able to work with YaST in text mode, it needs to run in a terminal with VT220/Linux emulation (also called ASCII console). You cannot use YaST in a 3270 terminal, for example.

4.2.6.2 Initiating the Installation for the X Window System #Edit source

Important: X Authentication Mechanism

The direct installation with the X Window System relies on a primitive authentication mechanism based on host names. This mechanism is disabled on current SUSE Linux Enterprise Server versions. Installation with SSH or VNC is preferred.

1. 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>.

2. When prompted at the installation system, enter the IP address of the machine running the X server.

3. Wait until YaST opens then start the installation.

The boot process for SLES 10 and 11 followed the scheme provided below. For in-depth information refer to the documentation provided at http://www.ibm.com/developerworks/linux/linux390/documentation_suse.html.

With SLES 12 the way SUSE Linux Enterprise Server is booted on IBM z Systems has changed. Several reasons led to this change:

For those reasons, starting with SLES 12, GRUB 2 replaces zipl on IBM SUSE Linux Enterprise Server for z Systems. GRUB 2 on the AMD64/Intel 64 architecture includes device drivers on the firmware level to access the file system. On the mainframe there is no firmware and adding ccw to GRUB 2 would not only be a huge task, but also would be a reimplementation of zipl in GRUB 2. Therefore SUSE Linux Enterprise Server uses a two-stage approach:

Important: 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 Book “Administration Guide”, Chapter 15 “Basic Networking”, Section 15.5 “Configuring a Network Connection Manually”.

Each of the interfaces requires certain setup options:

The maximum capacity of a parmfile is 860 characters. As a rule of thumb, the parmfile should contain a maximum of 10 lines with no more than 79 characters. When reading a parmfile, all lines are concatenated without adding white spaces, therefore the last character (79) of each line needs to be a Space.

To receive potential error messages on the console, use

linuxrclog=/dev/console

ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb
instnetdev=osa osainterface=qdio layer2=1 osahwaddr=
pointopoint=192.168.0.1
hostip=192.168.0.2
nameserver=192.168.0.3
install=nfs://192.168.0.4/SLES/SLES-12-Server/s390x/DVD1
autoyast=http://192.168.0.5/autoinst.xml
linuxrclog=/dev/console vnc=1
VNCPassword=testing

ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb
AutoYast=nfs://192.168.1.1/autoinst/s390.xml
Hostname=zsystems.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-12-Server/s390x/DVD1/
ssh=1 ssh.password=testing linuxrclog=/dev/console

A general coverage of Linux on IBM z Systems can be found in the following documents:

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).

There also is a Redbook for Linux application development at http://www.redbooks.ibm.com:

Refer to the following Redbooks, Redpapers, and links for some more complex IBM z Systems scenarios:

Refer to the following documents at https://www.ibm.com/developerworks/linux/linux390/documentation_dev.html for more information on KVM on IBM z Systems:

SUSE Linux Enterprise Server is normally installed as an independent operating system. With the introduction of Virtualization, it is also possible to run multiple instances of SUSE Linux Enterprise Server on the same hardware. However, the installation of the VM Host Server is performed like a typical installation with some additional packages. The installation of virtual guests is described in Book “Virtualization Guide”, Chapter 9 “Guest Installation”.

Depending on the hardware used, the following boot methods are available for the first boot procedure (prior to the installation of SUSE Linux Enterprise Server).

When installing SUSE Linux Enterprise Server, the actual installation data must be available in the network, on a hard disk partition, or on a local DVD. To install from the network, you need an installation server. To make the installation data available, set up any computer in a Unix or Linux environment as an NFS, HTTP, SMB, or FTP server. To make the installation data available from a Windows computer, release the data with SMB.

The installation source is particularly easy to select if you configure an SLP server in the local network. For more information, see Chapter 7, Setting Up the Server Holding the Installation Sources.

Most installations are to a local hard disk. Therefore, it is necessary for the hard disk controllers to be available to the installation system. If a special controller (like a RAID controller) needs an extra kernel module, provide a kernel module update disk to the installation system.

Other installation targets may be various types of block devices that provide sufficient disk space and speed to run an operating system. This includes network block devices like iSCSI or SAN. It is also possible to install on network file systems that offer the standard Unix permissions. However, it may be problematic to boot these, because they must be supported by the initramfs before the actual system can start. Such installations are useful if there is a need to start the same system in different locations.

SUSE Linux Enterprise Server offers several methods for controlling installation:

By default, the graphical console is used. If you have many similar computers to install, it is advisable to create an AutoYaST configuration file or a KIWI preload image and make this available to the installation process. See also the documentation for AutoYaST at https://www.suse.com/documentation/sles-12/book_autoyast/data/book_autoyast.html and KIWI at http://doc.opensuse.org/projects/kiwi/doc/.

Booting a computer depends on the capabilities of the hardware used and the availability of media for the respective boot option.

The installation media contain all the necessary packages and meta information that is necessary to install a SUSE Linux Enterprise Server. These must be available to the installation system after booting for installation. Several possibilities for providing the installation media to the system are available with SUSE Linux Enterprise Server.

DVD-ROM and USB storage devices can be used for installation purposes. Adjust your computer to your needs:

An installation server is required to perform the installation by using a network source. The procedure for installing this server is outlined in Chapter 7, Setting Up the Server Holding the Installation Sources.

If you have an SLP server, select SLP as the installation source in the first boot screen. During the boot procedure, select which of the available installation sources to use.

If the DVD is available on the network, use it as an installation source. In this case, specify the parameter install=<URL> with suitable values at the boot prompt. Find a more detailed description of this parameter in Section 9.2.2, “Using Custom Boot Options”.

The simplest way to install SUSE Linux Enterprise Server is using the computer console. With this method, a graphical installation program guides you through the installation. This installation method is discussed in detail in Chapter 6, Installation with YaST.

You can still perform the installation on the console without a working graphics mode. The text-based installation program offers the same functionality as the graphical version. Find some hints about navigation in this mode in Book “Administration Guide”, Chapter 4 “YaST in Text Mode”, Section 4.1 “Navigation in Modules”.

For this installation method, you need a second computer that is connected by a null modem cable to the computer on which to install SUSE Linux Enterprise Server. Hardware and firmware of both machines need to support the serial console. Some firmware implementations are already configured to send the boot console output to a serial console (by providing a device tree with /chosen/stdout-path set appropriately). In this case no additional configuration is required.

If the firmware is not set up to use the serial console for the boot console output, you need to provide the following boot paramater at the boot prompt of the installation system (see Book “Administration Guide”, Chapter 11 “The Boot Loader GRUB 2”, Section 11.2.5 “Editing Menu Entries during the Boot Procedure” for details): console=TTY,BAUDRATE

BAUDRATE needs to be replaced by the baud rate for the interface. Valid values are 115200, 38400, or 9600. TTY needs to be replaced by the name of the interface. On most computers, there is one or more serial interfaces. Depending on the hardware, the names of the interfaces may vary:

For the installation, you need a terminal program like minicom or screen. To initiate the serial connection, launch the screen program in a local console by entering the following command:

screen /dev/ttyUSB0 115200

This means that screen listens to the first serial port with a baud rate of 115200. From this point on, the installation proceeds similarly to the text-based installation over this terminal.

If you do not have direct access to the computer hardware and, for example, the installation should be launched from a management console, control the entire installation process over the network. To do this, enter the parameters ssh=1 and ssh.password=SECRET at the boot prompt. An SSH daemon is then launched in the system and you can log in as user root with the password SECRET.

To connect, use ssh -X. X-Forwarding over SSH is supported, if you have a local X server available. Otherwise, YaST provides a text interface over ncurses. YaST then guides you through the installation. This procedure is described in detail in Section 9.1.5, “Simple Remote Installation via SSH—Dynamic Network Configuration”.

If you do not have a DHCP server available in your local network, manually assign an IP address to the installation system. Do this by entering the option HostIP=IPADDR at the boot prompt.

If you do not have direct access to the system, but want a graphical installation, install SUSE Linux Enterprise Server over VNC. This method is described in detail in Section 9.3.1, “VNC Installation”.

As suitable VNC clients are also available for other operating systems, such as Microsoft Windows and macOS, the installation can also be controlled from computers running those operating systems.

If you need to install SUSE Linux Enterprise Server on several computers with similar hardware, it is recommended you perform the installations with the aid of AutoYaST. In this case, start by installing one SUSE Linux Enterprise Server and use this to create the necessary AutoYaST configuration files.

Boot problems may prevent the YaST installer from starting on your system. Another symptom is when your system does not boot after the installation has been completed.

If an unexpected problem occurs during installation, information is needed to determine the cause of the problem. Use the following directions to help with troubleshooting:

To simplify the installation process and avoid accidental installations, the default setting on the installation DVD for SUSE Linux Enterprise Server is that your system is booted from the first hard disk. At this point, an installed boot loader normally takes over control of the system. This means that the boot DVD can stay in the drive during an installation. To start the installation, choose one of the installation possibilities in the boot menu of the media.

For IBM z Systems platforms, the system is booted (IPL, Initial Program Load) as described in Section 4.2.4, “IPLing the SUSE Linux Enterprise Server Installation System”. SUSE Linux Enterprise Server does not show a splash screen on these systems. During the installation, load the kernel, initrd, and parmfile manually. YaST starts with its installation screen when a connection has been established to the installation system via VNC, X, or SSH. Because there is no splash screen, kernel or boot parameters cannot be entered on screen, but must be specified in a parmfile (see Section 4.3, “The parmfile—Automating the System Configuration”).

SUSE Linux Enterprise Server supports several boot options from which you can choose, depending on the hardware available and on the installation scenario you prefer. Booting from the SUSE Linux Enterprise Server media is the most straightforward option, but special requirements might call for special setups:

Table 6.1: Boot Options #

Boot Option	Description
DVD	This is the easiest boot option. This option can be used if the system has a local DVD-ROM drive that is supported by Linux.
Flash Disks (USB Mass Storage Device)	In case your machine is not equipped with an optical drive, you can boot the installation image from a flash disk. To create a bootable flash disk, you need to copy either the DVD or the Mini CD ISO image to the device using the dd command (the flash disk must not be mounted, all data on the device will be erased): dd if=PATH_TO_ISO_IMAGE of=USB_STORAGE_DEVICE bs=4M Important: Compatibility Note that booting from a USB Mass Storage Device is not supported on UEFI machines and on the POWER architecture.
PXE or BOOTP	Booting over the network must be supported by the system's BIOS or firmware, and a boot server must be available in the network. This task can also be handled by another SUSE Linux Enterprise Server system. Refer to Chapter 9, Remote Installation for more information.
Hard Disk	SUSE Linux Enterprise Server installation can also be booted from the hard disk. To do this, copy the kernel (linux) and the installation system (initrd) from the directory /boot/architecture/ on the installation media to the hard disk and add an appropriate entry to the existing boot loader of a previous SUSE Linux Enterprise Server installation.

Tip: Booting from DVD on UEFI Machines

DVD1 can be used as a boot medium for machines equipped with UEFI (Unified Extensible Firmware Interface). Refer to your vendor's documentation for specific information. If booting fails, try to enable CSM (Compatibility Support Module) in your firmware.

Note: Add-on Product Installation Media

Media for add-on products (extensions or third-party products) cannot be used as stand-alone installation media. They can either be embedded as additional installation sources during the installation process (see Section 6.9, “Extension Selection”) or be installed from the running system using the YaST Add-on Products module (see Chapter 13, Installing Modules, Extensions, and Third Party Add-On Products for details).

6.2.2.1 The Boot Screen on Machines Equipped with Traditional BIOS #Edit source

The boot screen displays several options for the installation procedure. Boot from Hard Disk boots the installed system and is selected by default, because the CD is often left in the drive. Select one of the other options with the arrow keys and press Enter to boot it. The relevant options are:

Installation

The normal installation mode. All modern hardware functions are enabled. In case the installation fails, see F5Kernel for boot options that disable potentially problematic functions.

Upgrade

Perform a system upgrade. For more information refer to Chapter 18, Upgrading SUSE Linux Enterprise.

Rescue System

Starts a minimal Linux system without a graphical user interface. For more information, see Book “Administration Guide”, Chapter 38 “Common Problems and Their Solutions”, Section 38.6.2 “Using the Rescue System”.

Check Installation Media

This option is only available when you install from media created from downloaded ISOs. In this case it is recommended to check the integrity of the installation medium. This option starts the installation system before automatically checking the media. In case the check was successful, the normal installation routine starts. If a corrupt media is detected, the installation routine aborts.

Warning: Failure of Media Check

If the media check fails, your medium is damaged. Do not continue the installation because installation may fail or you may lose your data. Replace the broken medium and restart the installation process.

Memory Test

Tests your system RAM using repeated read and write cycles. Terminate the test by rebooting. For more information, see Book “Administration Guide”, Chapter 38 “Common Problems and Their Solutions”, Section 38.2.4 “Fails to Boot”.

Figure 6.1: The Boot Screen on Machines with a Traditional BIOS #

Use the function keys indicated in the bar at the bottom of the screen to change the language, screen resolution, installation source or to add an additional driver from your hardware vendor:

F1Help

Get context-sensitive help for the active element of the boot screen. Use the arrow keys to navigate, Enter to follow a link, and Esc to leave the help screen.

F2Language

Select the display language and a corresponding keyboard layout for the installation. The default language is English (US).

F3Video Mode

Select various graphical display modes for the installation. By Default the video resolution is automatically determined using KMS (Kernel Mode Settings). If this setting does not work on your system, choose No KMS and, optionally, specify vga=ask on the boot command line to get prompted for the video resolution. Choose Text Mode if the graphical installation causes problems.

F4Source

Normally, the installation is performed from the inserted installation medium. Here, select other sources, like FTP or NFS servers. If the installation is deployed on a network with an SLP server, select an installation source available on the server with this option. Find information about setting up an installation server with SLP at Chapter 7, Setting Up the Server Holding the Installation Sources.

F5Kernel

If you encounter problems with the regular installation, this menu offers to disable a few potentially problematic functions. If your hardware does not support ACPI (advanced configuration and power interface) select No ACPI to install without ACPI support. No local APIC disables support for APIC (Advanced Programmable Interrupt Controllers) which may cause problems with some hardware. Safe Settings boots the system with the DMA mode (for CD/DVD-ROM drives) and power management functions disabled.

If you are not sure, try the following options first: Installation—ACPI Disabled or Installation—Safe Settings. Experts can also use the command line (Boot Options) to enter or change kernel parameters.

F6Driver

Press this key to notify the system that you have an optional driver update for SUSE Linux Enterprise Server. With File or URL, load drivers directly before the installation starts. If you select Yes, you are prompted to insert the update disk at the appropriate point in the installation process.

Tip: Getting Driver Update Disks

Driver updates for SUSE Linux Enterprise are provided at http://drivers.suse.com/. These drivers have been created via the SUSE SolidDriver Program.

6.2.2.2 The Boot Screen on Machines Equipped with UEFI #Edit source

UEFI (Unified Extensible Firmware Interface) is a new industry standard which replaces and extends the traditional BIOS. The latest UEFI implementations contain the “Secure Boot” extension, which prevents booting malicious code by only allowing signed boot loaders to be executed. See Book “Administration Guide”, Chapter 12 “UEFI (Unified Extensible Firmware Interface)” for more information.

The boot manager GRUB 2, used to boot machines with a traditional BIOS, does not support UEFI, therefore GRUB 2 is replaced with GRUB 2 for EFI. If Secure Boot is enabled, YaST will automatically select GRUB 2 for EFI for installation. From an administrative and user perspective, both boot manager implementations behave the same and are called GRUB 2 in the following.

Tip: UEFI and Secure Boot are Supported by Default

The installation routine of SUSE Linux Enterprise automatically detects if the machine is equipped with UEFI. All installation sources also support Secure Boot. If an EFI system partition already exists on dual boot machines (from a Microsoft Windows 8 installation, for example), it will automatically be detected and used. Partition tables will be written as GPT on UEFI systems.

Warning: Using Non-Inbox Drivers with Secure Boot

There is no support for adding non-inbox drivers (that is, drivers that do not come with SLE) during installation with Secure Boot enabled. The signing key used for SolidDriver/PLDP is not trusted by default.

To solve this problem, it is necessary to either add the needed keys to the firmware database via firmware/system management tools before the installation or to use a bootable ISO that will enroll the needed keys in the MOK list at first boot. For more information, see Book “Administration Guide”, Chapter 12 “UEFI (Unified Extensible Firmware Interface)”, Section 12.1 “Secure Boot”.

The boot screen displays several options for the installation procedure. Change the selected option with the arrow keys and press Enter to boot it. The relevant options are:

Installation

The normal installation mode.

Upgrade

Perform a system upgrade. For more information refer to Chapter 18, Upgrading SUSE Linux Enterprise.

Rescue System

Starts a minimal Linux system without a graphical user interface. For more information, see Book “Administration Guide”, Chapter 38 “Common Problems and Their Solutions”, Section 38.6.2 “Using the Rescue System”.

Check Installation Media

This option is only available when you install from media created from downloaded ISOs. In this case it is recommended to check the integrity of the installation medium. This option starts the installation system before automatically checking the media. In case the check was successful, the normal installation routine starts. If a corrupt media is detected, the installation routine aborts.

Figure 6.2: The Boot Screen on Machines with UEFI #

GRUB 2 for EFI on SUSE Linux Enterprise Server does not support a boot prompt or function keys for adding boot parameters. By default, the installation will be started with American English and the boot media as the installation source. A DHCP lookup will be performed to configure the network. To change these defaults or to add additional boot parameters you need to edit the respective boot entry. Highlight it using the arrow keys and press E. See the on-screen help for editing hints (note that only an English keyboard is available now). The Installation entry will look similar to the following:

setparams 'Installation'

    set gfxpayload=keep
    echo 'Loading kernel ...'
    linuxefi /boot/x86_64/loader/linux splash=silent
    echo 'Loading initial ramdisk ...'
    initrdefi /boot/x86_64/loader/initrd

Add space-separated parameters to the end of the line starting with linuxefi. To boot the edited entry, press F10. If you access the machine via serial console, press Esc–0. A complete list of parameters is available at http://en.opensuse.org/Linuxrc. The most important ones are:

Table 6.2: Installation Sources #

CD/DVD (default)	install=cd:/
Hard disk	install=hd:/?device=sda/PATH_TO_ISO
SLP	install=slp:/
FTP	install=ftp://ftp.example.com/PATH_TO_ISO
HTTP	install=http://www.example.com/PATH_TO_ISO
NFS	install=nfs:/PATH_TO_ISO
SMB / CIFS	install=smb://PATH_TO_ISO

Table 6.3: Network Configuration #

DHCP (default)	netsetup=dhcp
Prompt for Parameters	netsetup=hostip,netmask,gateway,nameserver
Host IP address	hostip=192.168.2.100 hostip=192.168.2.100/24
Netmask	netmask=255.255.255.0
Gateway	gateway=192.168.5.1
Name Server	nameserver=192.168.1.116 nameserver=192.168.1.116,192.168.1.118
Domain Search Path	domain=example.com

Table 6.4: Miscellaneous #

Driver Updates: Prompt	dud=1
Driver Updates: URL	dud=ftp://ftp.example.com/PATH_TO_DRIVER dud=http://www.example.com/PATH_TO_DRIVER
Installation Language	Language=LANGUAGE Supported values for LANGUAGE are, among others, cs_CZ, de_DE, es_ES, fr_FR, ja_JP, pt_BR, pt_PT, ru_RU, zh_CN, and zh_TW.
Kernel: No ACPI	acpi=off
Kernel: No Local APIC	noapic
Video: Disable KMS	nomodeset
Video: Start Installer in Text Mode	Textmode=1

In case you want to configure access to a local SMT or supportconfig server for the installation, you can specify boot parameters that will be parsed by the installation routine to set up these services. The same is also true if you need IPv6 support during the installation.

6.2.3.1 Providing Data to Access an SMT Server #Edit source

By default, updates for SUSE Linux Enterprise Server are delivered by the SUSE Customer Center. If your network provides a so called SMT server to provide a local update source, you need to equip the client with the server's URL. Client and server communicate solely via HTTPS protocol, therefore you also need to enter a path to the server's certificate if the certificate was not issued by a certificate authority.

Note: Non-Interactive Installation Only

Providing parameters for accessing an SMT server is only needed for non-interactive installations. During an interactive installation the data can be provided during the installation (see Section 6.8, “SUSE Customer Center Registration” for details).

regurl

URL of the SMT server. This URL has a fixed format https://FQN/center/regsvc/. FQN needs to be a fully qualified host name of the SMT server. Example:

regurl=https://smt.example.com/center/regsvc/

regcert

Location of the SMT server's certificate. Specify one of the following locations:

URL

Remote location (HTTP, HTTPS or FTP) from which the certificate can be downloaded. Example:

regcert=http://smt.example.com/smt-ca.crt

local path

Absolute path to the certificate on the local machine. Example:

regcert=/data/inst/smt/smt-ca.cert

Interactive

Use ask to open a pop-up menu during the installation where you can specify the path to the certificate. Do not use this option with AutoYaST. Example

regcert=ask

Deactivate certificate installation

Use done if either the certificate will be installed by an add-on product, or if you are using a certificate issued by an official certificate authority. Example:

regcert=done

Warning: Beware of Typing Errors

Make sure the values you enter are correct. If regurl has not been specified correctly, the registration of the update source will fail. If a wrong value for regcert has been entered, you will be prompted for a local path to the certificate.

In case regcert is not specified, it will default to http://FQN/smt.crt with FQN being the name of the SMT server.

supporturl=http://support.example.com/supportconfig/data/

l>proxy=http://USER:PASSWORD@proxy.example.com:PORT

security=selinux selinux=1

self_update=1

self_update=https://updates.example.com/

The process can be broken down into two different parts:

6.4.1.1 Determining the Update Repository Location #Edit source

Installer Self-Updates are distributed as regular RPM packages via a dedicated repository, so the first step is to find out the repository URL.

Important: Installer Self-Update Repository Only

No matter which of the following options you use, only the installer self-update repository URL is expected, for example:

self_update=https://updates.suse.com/SUSE/Updates/SLE-SERVER-INSTALLER/12-SP2/x86_64/update/

Do not supply any other repository URL—for example the URL of the software update repository.

YaST will try the following sources of information:

1. The self_update boot parameter. (For more details, see Section 6.2.3.6, “Enabling the Installer Self-Update”.) If you specify a URL, it will take precedence over any other method.

2. The /general/self_update_url profile element in case you are using AutoYaST.

3. A registration server. YaST will query the registration server for the URL. The server to be used is determined in the following order:

   1. By evaluating the regurl boot parameter (Section 6.2.3.1, “Providing Data to Access an SMT Server”).

   2. By evaluating the /suse_register/reg_server profile element if you are using AutoYaST.

   3. By performing an SLP lookup. If an SLP server is found, YaST will ask you whether it should be used because there is no authentication involved and everybody on the local network could announce a registration server.

   4. By querying the SUSE Customer Center,

4. If none of the previous attempts worked, the fallback URL (defined in the installation media) will be used.

6.4.1.2 Downloading and Applying the Updates #Edit source

When the updates repository is determined, YaST will check whether an update is available. If so, all the updates will be downloaded and applied to the installation system.

Finally, YaST will be restarted to load the new version and the welcome screen will be shown. If no updates were available, the installation will continue without restarting YaST.

Note: Update Integrity

Update signatures will be checked to ensure integrity and authorship. If a signature is missing or invalid, you will be asked whether you want to apply the update.

To download installer updates, YaST needs network access. By default, it tries to use DHCP on all network interfaces. If there is a DHCP server in the network, it will work automatically.

If you need a static IP setup, you can use the ifcfg boot argument. For more details, see the linuxrc documentation at https://en.opensuse.org/Linuxrc.

YaST can use a user-defined repository instead of the official one by specifying a URL through the self_update boot option. However, the following points should be considered:

Note: Only One Repository

Currently, it is not possible to use more than one repository as source for installer self-updates.

After selecting Configure DASD Disks, an overview lists all available DASDs. To get a clearer picture of the available devices, use the text box located above the list to specify a range of channels to display. To filter the list according to such a range, select Filter.

Figure 6.5: IBM z Systems: Selecting a DASD #

Specify the DASDs to use for the installation by selecting the corresponding entries in the list. Use Select All to select all DASDs currently displayed. Activate and make the selected DASDs available for the installation by selecting Perform Action › Activate. To format the DASDs, select Perform Action › Format. Alternatively, use the YaST partitioner later as described in Section 11.1, “Using the YaST Partitioner”.

To use zFCP disks for the SUSE Linux Enterprise Server installation, select Configure zFCP Disks in the selection dialog. This opens a dialog with a list of the zFCP disks available on the system. In this dialog, select Add to open another dialog in which to enter zFCP parameters.

To make a zFCP disk available for the SUSE Linux Enterprise Server installation, choose an available Channel Number from the drop-down box. Get WWPNs (World Wide Port Number) and Get LUNs (Logical Unit Number) return lists with available WWPNs and FCP-LUNs, respectively, to choose from. When completed, exit the zFCP dialog with Next and the general hard disk configuration dialog with Finish to continue with the rest of the configuration.

To make the registration more convenient, you can also store your registration codes on a USB storage device such as a flash disk. YaST will automatically pre-fill the corresponding text box. This is particularly useful when testing the installation or if you need to register many systems or extensions.

Note: Limitations

Currently flash disks are only scanned during installation or upgrade, but not when registering a running system.

Create a file named regcodes.txt or regcodes.xml on the USB disk. If both are present, the XML takes precedence.

In that file, identify the product with the name returned by zypper search --type product and assign it a registration code as follows:

SLES    cc36aae1
SLED    309105d4

sle-we  5eedd26a
sle-live-patching 8c541494

<?xml version="1.0"?>
<profile xmlns="http://www.suse.com/1.0/yast2ns"
 xmlns:config="http://www.suse.com/1.0/configns">
  <suse_register>
    <addons config:type="list">
      <addon>
        <name>SLES</name>
        <reg_code>cc36aae1</reg_code>
      </addon>
      <addon>
        <name>SLED</name>
        <reg_code>309105d4</reg_code>
      </addon>
      <addon>
        <name>sle-we</name>
        <reg_code>5eedd26a</reg_code>
      </addon>
      <addon>
        <name>sle-live-patching</name>
        <reg_code>8c541494</reg_code>
      </addon>
    </addons>
  </suse_register>
</profile>

Note that SLES and SLED are not extensions, but listing them as add-ons allows for combining several base product registration codes in a single file. See Book “AutoYaST”, Chapter 4 “Configuration and Installation Options”, Section 4.3.1 “Extensions” for details.

Click Change in the Create User dialog to import users from a previous installation (if present). Also change the password encryption type in this dialog.

The default authentication method is Local (/etc/passwd). If a former version of SUSE Linux Enterprise Server or another system using /etc/passwd is detected, you may import local users. To do so, check Read User Data from a Previous Installation and click Choose. In the next dialog, select the users to import and finish with OK.

By default the passwords are encrypted with the SHA-512 hash function. Changing this method is not recommended unless needed for compatibility reasons.

SUSE Linux Enterprise Server contains several software patterns for various application purposes. Click Software to open the Software Selection and System Tasks screen where you can modify the pattern selection according to your needs. Select a pattern from the list and see a description in the right-hand part of the window. Each pattern contains several software packages needed for specific functions (for example Web and LAMP server or a print server). For a more detailed selection based on software packages to install, select Details to switch to the YaST Software Manager.

You can also install additional software packages or remove software packages from your system at any later time with the YaST Software Manager. For more information, refer to Chapter 12, Installing or Removing Software.

Figure 6.15: Software Selection and System Tasks #

Note: Graphical Desktop

By default SUSE Linux Enterprise Server is installed with X Window and the GNOME desktop environment. If you do not need X Window, deselect the two respective patterns in the Software Selection and System Tasks screen. As an alternative to GNOME, the light-weight window manager IceWM can be installed. Select Details from the Software Selection and System Tasks screen and search for icewm.

Tip: IBM z Systems: Hardware Cryptography Support

The hardware cryptography stack is not installed by default. To install it, select System z HW crypto support in the Software Selection and System Tasks screen.

Tip: Adding Secondary Languages

The language you selected with the first step of the installation will be used as the primary (default) language for the system. You can add secondary languages from within the Software dialog by choosing Details › View › Languages.

The installer proposes a boot configuration for your system. Other operating systems found on your computer, such as Microsoft Windows or other Linux installations, will automatically be detected and added to the boot loader. However, SUSE Linux Enterprise Server will be booted by default. Normally, you can leave these settings unchanged. If you need a custom setup, modify the proposal according to your needs. For information, see Book “Administration Guide”, Chapter 11 “The Boot Loader GRUB 2”, Section 11.3 “Configuring the Boot Loader with YaST”.

Important: Software RAID 1

Booting a configuration where /boot resides on a software RAID 1 device is supported, but it requires to install the boot loader into the MBR (Boot Loader Location › Boot from Master Boot Record). Having /boot on software RAID devices with a level other than RAID 1 is not supported. Also see Book “Storage Administration Guide”, Chapter 8 “Configuring Software RAID for the Root Partition”.

By default SuSEFirewall2 is enabled on all configured network interfaces. To globally disable the firewall for this computer, click Disable (not recommended).

Note: Firewall Settings

If the firewall is activated, all interfaces are configured to be in the “External Zone”, where all ports are closed by default, ensuring maximum security. The only port you can open during the installation is port 22 (SSH), to allow remote access. All other services requiring network access (such as FTP, Samba, Web server, etc.) will only work after having adjusted the firewall settings. Refer to Book “Security Guide”, Chapter 15 “Masquerading and Firewalls” for more information.

To enable remote access via the secure shell (SSH), make sure the SSH service is enabled and the SSH port is open.

Tip: Existing SSH Host Keys

If you install SUSE Linux Enterprise Server on a machine with one or more existing Linux installations, the installation routine imports the SSH host key with the most recent access time from an existing installation by default. See also Section 6.15.7, “Import SSH Host Keys and Configuration”.

In case you are performing a remote administration over VNC, you can also configure whether the machine should be accessible via VNC even after the installation. Note that enabling VNC also requires you to set the Default systemd Target to graphical.

Using Kdump, you can save a dump of the kernel (in case of a crash) to analyze what went wrong. Use this dialog to enable and configure Kdump. Find detailed information at Book “System Analysis and Tuning Guide”, Chapter 17 “Kexec and Kdump”.

To save memory, all channels for devices currently not in use are blacklisted by default (each channel that is not blacklisted occupies approximately 50 KB of memory). To configure additional hardware in the installed system using channels that are currently blacklisted, run the respective YaST module to enable the respective channels first.

To disable blacklisting, click disable.

SUSE Linux Enterprise Server can boot into two different targets (formerly known as “runlevels”). The graphical target starts a display manager, whereas the multi-user target starts the command line interface.

The default target is graphical. In case you have not installed the X Window System patterns, you need to change it to multi-user. If the system should be accessible via VNC, you need to choose graphical.

If an existing Linux installation on your computer was detected, YaST will import the most recent SSH host key found in /etc/ssh by default, optionally including other files in the directory as well. This makes it possible to reuse the SSH identity of the existing installation, avoiding the REMOTE HOST IDENTIFICATION HAS CHANGED warning on the first connection. Note that this item is not shown in the installation summary if YaST has not discovered any other installations.

Figure 6.16: Import SSH Host Keys and Configuration #

This screen lists all the hardware information the installer could obtain about your computer. When opened for the first time, the hardware detection is started. Depending on your system, this may take some time. Select any item in the list and click Details to see detailed information about the selected item. Use Save to File to save a detailed list to either the local file system or a removable device.

Advanced users can also change the PCI ID Setup and Kernel Settings by choosing Kernel Settings. A screen with two tabs opens:

YaST usually reboots into the installed system on the IBM z Systems platform. Known exceptions to this are installations where the boot loader resides on an FCP device in environments with LPAR on a machine older than z196 or with z/VM older than release 5.4. The boot loader gets written to a separate partition mounted as /boot/zipl/.

In cases where an automatic reboot is not possible, YaST will show a dialog containing information about from which device to do an IPL. Accept the shutdown option and perform an IPL after the shutdown. The procedure varies according to the type of installation:

After IPLing the system, establish a connection via VNC, SSH, or X to log in to the installed system. Using either VNC or SSH is recommended. To customize the system configuration or to install additional software packages, start YaST.

http://IP_OF_INSTALLED_SYSTEM:5801/