SUSE Linux Enterprise Server 11 SP4: Deployment GuideSUSE Linux Enterprise Server 11 SP4Deployment Guide
Copyright (C)
SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or (at
your option) version 1.3; with the Invariant Section being this copyright
notice and license. A copy of the license version 1.2 is included in the
section entitled “GNU Free Documentation License”.
For SUSE and Novell trademarks, see the Novell Trademark and Service Mark list
All other third party trademarks are the property of their respective
owners. A trademark symbol ((R), (TM) etc.) denotes a SUSE or Novell
an asterisk (*) denotes a third party trademark.
All information found in this book has been compiled with utmost attention
to detail. However, this does not guarantee complete accuracy. Neither
SUSE LLC, its affiliates, the authors nor the translators shall be held
liable for possible errors or the consequences thereof.
ContentsList of Figures3.1. 3.2. 3.3. 3.4. 3.5. 6.1. 6.2. 6.3. 6.4. 6.5. 6.6. 6.7. 6.8. 6.9. 7.1. 7.2. 9.1. 9.2. 9.3. 12.1. 15.1. 15.2. 15.3. 15.4. 15.5. 15.6. 21.1. 21.2. List of Tables2.1. 2.2. 5.1. 5.2. 5.3. 5.4. 5.5. 5.6. 5.7. 5.8. 5.9. 5.10. 5.11. 6.1. 7.1. 7.2. 14.1. 14.2. 17.1. List of Examples4.1. 4.2. 4.3. 4.4. 4.5. 4.6. 4.7. 4.8. 4.9. 4.10. 4.11. 4.12. 4.13. 4.14. 4.15. 4.16. 7.1. 7.2. 17.1. 20.1. 20.2. 20.3. About This Guide
Installations of SUSE Linux Enterprise Server are possible in many different ways. It is
impossible to cover all combinations of boot, or installation server,
automated installations or deploying images. This manual should help with
selecting the appropriate method of deployment for your installation.
The standard deployment instructions differ depending on the
architecture used. For differences and requirements regarding the
architecture, see this part.
Most tasks that are needed during installations are described here.
This includes the manual setup of your computer as well as additional
software and remote installations.
Mass installations often require the preparation of images or products
furnished with the features that are needed in this special case.
Several options are described that allow the administrator to prepare
these deployment methods.
To do unattended installations, either use the installation with AutoYaST
or prepare an image with kiwi or firstboot. This part describes methods
to deploy these installations with a minimum of user interaction.
Many chapters in this manual contain links to additional documentation
resources, including additional documentation that is available on the
system as well as documentation available on the Internet.
For an overview of the documentation available for your product and the
latest documentation updates, refer to
or to the following section.
1. Available Documentation
We provide HTML and PDF versions of our books in different languages.
The following manuals for users and
administrators are available for this product:
Shows how to install single or multiple systems and how to exploit the
product inherent capabilities for a deployment infrastructure. Choose
from various approaches, ranging from a local installation or a network
installation server to a mass deployment using a remote-controlled,
highly-customized, and automated installation technique.
Administration Guide (↑Administration Guide)
Covers system administration tasks like maintaining, monitoring, and
customizing an initially installed system.
Security Guide (↑Security Guide)
Introduces basic concepts of system security, covering both local and
network security aspects. Shows how to make use of the product inherent
security software like AppArmor (which lets you specify per program which
files the program may read, write, and execute), and the auditing
system that reliably collects information about any security-relevant
Security and Hardening (↑Security and Hardening)
Deals with the particulars of installing and setting up a secure SUSE Linux Enterprise Server,
and additional post-installation processes required to further secure
and harden that installation. Supports the administrator with
security-related choices and decisions.
System Analysis and Tuning Guide (↑System Analysis and Tuning Guide)
An administrator's guide for problem detection, resolution and
optimization. Find how to inspect and optimize your system by means of
monitoring tools and how to efficiently manage resources. Also contains
an overview of common problems and solutions, and of additional help
and documentation resources.
Virtualization with Xen (↑Virtualization with Xen)
Offers an introduction to virtualization technology of your product. It
features an overview of the various fields of application and
installation types of each of the platforms supported by SUSE Linux Enterprise Server as well
as a short description of the installation procedure.
Virtualization with KVM for IBM System z (↑Virtualization with KVM for IBM System z)
Offers an introduction to setting up and managing virtualization with
KVM (Kernel-based Virtual Machine) on SUSE Linux Enterprise Server. Learn how to manage KVM
with libvirt or QEMU. The guide also contains detailed information
about requirements, limitations, and support status.
AutoYaST (↑AutoYaST)
AutoYaST is a system for installing one or more SUSE Linux Enterprise systems automatically
and without user intervention, using an AutoYaST profile that contains
installation and configuration data. The manual guides you through the
basic steps of auto-installation: preparation, installation, and
configuration.
Storage Administration Guide (↑Storage Administration Guide)
Provides information about how to manage storage devices on a SUSE Linux Enterprise Server.
In addition to the comprehensive manuals, several quick start guides are
available:
Installation Quick Start (↑Installation Quick Start)
Lists the system requirements and guides you step-by-step through the
installation of SUSE Linux Enterprise Server from DVD, or from an ISO image.
Linux Audit Quick Start
Gives a short overview how to enable and configure the auditing system
and how to execute key tasks such as setting up audit rules, generating
reports, and analyzing the log files.
AppArmor Quick Start
Helps you understand the main concepts behind AppArmor(R).
Virtualization with Linux Containers (LXC) (↑Virtualization with Linux Containers (LXC))
Gives a short introduction to LXC (a lightweight
“virtualization” method) and shows how to set up an LXC
host and LXC containers.
Find HTML versions of most product manuals in your installed system under
/usr/share/doc/manual or in the help centers of your
desktop. Find the latest documentation updates at
where you can download PDF or HTML
versions of the manuals for your product.
2. Feedback
Several feedback channels are available:
Bugs and Enhancement Requests
For services and support options available for your product, refer to
To report bugs for a product component, log in to the Novell Customer Center from
and select My Support+Service Request.
User Comments
We want to hear your comments about and suggestions for this manual and
the other documentation included with this product. Use the User
Comments feature at the bottom of each page in the online documentation
your comments there.
For feedback on the documentation of this product, you can also send a
mail to doc-team@suse.de. Make sure to include the
document title, the product version, and the publication date of the
documentation. To report errors or suggest enhancements, provide a
concise description of the problem and refer to the respective section
number and page (or URL).
3. Documentation Conventions
The following typographical conventions are used in this manual:
/etc/passwd: directory names and filenames
placeholder: replace
placeholder with the actual value
PATH: the environment variable PATH
ls, --help: commands, options, and
parameters
user: users or groups
Alt, Alt+F1: a
key to press
keys are shown in uppercase as on a
File, File+Save As: menu items, buttons
?amd64 em64t ipf:
This paragraph is only relevant for the architectures
amd64, em64t, and
ipf. The arrows mark the beginning and the end of the
text block.
??ipseries zseries:
This paragraph is only relevant for the architectures
System z and ipseries. The arrows
mark the beginning and the end of the text block.
Dancing Penguins (Chapter
Penguins, ↑Another Manual): This is a
reference to a chapter in another manual.
Chapter 1. Planning for SUSE Linux Enterprise ServerContents
The implementation of an operating system either in an existing IT
environment or as a completely new rollout must be carefully prepared.
SUSE Linux Enterprise Server 11 SP4 provides a variety of new features. It is
impossible to describe all the new features here. The following is just a
list of major enhancements that might be of interest.
Xen 4.0 Virtualization
Runs many virtual machines on a single server, each with its own
instance of an operating system. For more information, see
Virtualization with Xen (↑Virtualization with Xen).
Several new configuration options have been developed for YaST. These
are normally described in the chapters about the technology involved.
The management utility SPident gives an overview of the installed
software base and clarifies the current service pack level of the
Directory Services
Several LDAP-compliant directory services are available:
Microsoft Active Directory
Harden your System with the AppArmor technology. This service is described
in depth in Part “Confining Privileges with AppArmor” (↑Security Guide).
This is an intrusion detection system that can be setup to detect
unauthorized changes to the system.
iSCSI provides an easy and reasonably inexpensive solution for
connecting Linux computers to central storage systems. Find more
information about iSCSI in Storage Administration Guide (↑Storage Administration Guide).
Network File System v4
Starting with version 10, SUSE Linux Enterprise Server supports NFS also in version 4. This
gives you performance improvements, strong security, and a
“stateful” protocol.
Oracle Cluster File System 2
OCFS2 is a general-purpose journaling file system that is fully
integrated in the Linux 2.6 kernel and later. Find an
overview of OCFS2 in the High Availability Guide.
Linux Kernel Crash Dump
Debugging kernel-related problems is now much easier when using Kexec
and Kdump. This technology is available on x86, AMD64, Intel 64,
and POWER platforms.
1.1. Considerations for Deployment of a SUSE Linux Enterprise Server
At the beginning of the planning process, you should try to define the
project goals and needed features. This must always be done individually
for each project, but the questions to answer should include the
following:
How many installations should be done? Depending on this, the best
deployment methods differ. See also
Will the system run as physical host or as a virtual machine?
Will the system be in a hostile environment? Have a look at
Chapter 1, Security and Confidentiality (↑Security Guide) to get an overview of consequences.
How will you get regular updates? All patches are provided online for
registered users. Find the registration and patch support database at
Do you need help for your local installation? Novell provides training,
support, and consulting for all topics pertaining to SUSE Linux Enterprise Server. Find more
information about this at
Do you need third-party products? Make sure that the required product
is also supported on the desired platform. Novell can provide help to
support software on different platforms when needed.
1.2. Deployment of SUSE Linux Enterprise Server
To make sure that your system will run flawlessly, always try to use
certified hardware. The hardware certification process is an ongoing
process and the database of certified hardware is updated regularly. Find
the search form for certified hardware at
Depending on the number of desired installations, it is beneficial to use
installation servers or even completely automatic installations. Have a
for more information. When using
Xen virtualization technologies, network root file systems or network
storage solutions like iSCSI should be considered.
SUSE Linux Enterprise Server provides you with a broad variety of services. Find an overview of
the documentation in this book in About This Guide (↑Administration Guide). Most of
the needed configurations can be made with YaST, the SUSE
configuration utility. In addition, many manual configurations are
described in the corresponding chapters.
In addition to the plain software installation, you should consider
training the end users of the systems as well as help desk staff.
1.3. Running SUSE Linux Enterprise Server
The SUSE Linux Enterprise Server operating system is a well-tested and stable system.
Unfortunately, this does not prevent hardware failures or other causes
for downtime or data loss. For any serious computing task where data loss
could occur, a regular backup should be done.
For optimal security and data safety, you should make regular updates of
all the operated machines. If you have a mission critical server, you
should run a second identical (pre-production) machine where you can
apply all changes for testing purposes before doing so in production.
This also gives you the possibility of switching machines in the case of
hardware failure.
Part I. Architecture Specific Installation ConsiderationsContentsChapter 2. Installation on x86, AMD64, Intel 64, and ItaniumContentsAbstract
This chapter describes the steps necessary to prepare for the
installation of SUSE Linux Enterprise Server on x86, AMD64, Intel 64, and Itanium
computers. It introduces the steps required to prepare for various
installation methods. The list of hardware requirements provides an
overview of supported systems supported by SUSE Linux Enterprise Server. Find information about
available installation methods and several common known problems. Also
learn how to control the installation, provide installation media, and
boot with regular methods.
2.1. Required Background
To keep the scope of these guidelines manageable, certain technical
assumptions have been made:
You have some computer experience and are familiar with common
technical terms.
You are familiar with the documentation for your system and the network
on which it runs.
You have a basic understanding of Linux systems.
For an overview of the documentation available for your product and the
latest documentation updates, refer to
2.2. System Requirements for Operating Linux
The SUSE(R) Linux Enterprise Server operating system can be deployed on a wide range of hardware.
It is impossible to list all the different combinations of hardware SUSE Linux Enterprise Server
supports. However, 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, find
out which platforms have been certified by SUSE. Find a list at
2.2.1. Hardware for x86
Computers based on x86 constitute a cost-effective way of building
high-performance systems. The preconditions for operating SUSE Linux Enterprise Server on this
platform are as follows:
The number of CPUs supported depends on the kernel used. Specifically,
these are as follows:
Table 2.1. CPUs Supported by the Kernel
Oldest CPU Type
Maximum Number of CPUs
kernel-default
PentiumPro, Athlon
kernel-pae
Pentium II, Athlon XP
Memory Requirements
A minimum of 512 MB is required. The recommended memory is
1 GB. For a multiprocessor system, 256 MB per processor is
required. Systems with less than 1 GB main memory need additional
swap space that extends the virtual memory to 1 GB.
Hard Disk Requirements
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:
Boot Methods
The computer can be booted for installation from DVD, USB hard drive,
or the network. A special boot server is required to boot over the
network. This boot server can be configured with SUSE Linux Enterprise Server. To use USB
hard drives, the BIOS or firmware must support booting from USB
devices. Create a bootable USB hard drive as described in
2.2.2. Hardware for Itanium
The Itanium architecture is 64-bit and allows the operation of large
II (older Itanium CPUs are no longer supported). Dual core CPUs and
hyperthreading are also supported.
Maximum Number of CPUs
At most, 4096 CPUs are supported. For the calculation of the CPU
count, a dual-core CPU counts as two CPUs and a hyperthreaded CPU with
two siblings also counts as two CPUs. 1024 CPUs could mean 512 dual
cores, 512 single cores with hyperthreading, or 256 dual cores with
hyperthreading.
A minimum of 1GB RAM per CPU socket is recommended.
Hard Disk Requirements
The disk requirements depend largely on the installation selected.
Commonly, you need more space than the installed software itself needs
to have a system that works properly. Minimal requirements for
different selections are:
Boot Methods
Options for booting the computer depend on the available hardware. All
boot methods available to the machine should work. A special boot
server is required to use PXE boot over the network. This may also be
set up with SUSE Linux Enterprise Server.
2.2.3. Hardware for AMD64 and Intel 64
The AMD64 and Intel 64 architectures support the simple migration of
x86 software to 64 bits. Like the x86 architecture, they constitute a
value-for-money alternative.
All CPUs available on the market to date are supported. This includes
dual-core CPUs.
Maximum Number of CPUs
The maximum number of CPUs supported by AMD64 and Intel 64 is 4096.
Memory Requirements
A minimum of 512 MB of memory is required. Requirements depend on the
application. However, the minimum recommended is 1024 MB or 512 MB per
CPU on multiprocessor computers. The theoretical upper limit on the
amount of memory supported by the kernel is 512 GB.
Hard Disk Requirements
The disk requirements depend largely on the installation selected. The
required space for this architecture is similar to x86 but you
should allocate some space for compatibility libraries. Minimum
requirements for different selections are:
Boot Methods
The computer can be booted from a CD or a network. A special boot
server is required to boot over the network. This can be set up with
SUSE Linux Enterprise Server.
2.2.4. Supported Virtualization Hosts
The i586 and x86_64 version of SUSE Linux Enterprise Server can also be installed as
VM Guests on various virtualization hosts. The following host operating
systems and virtualization platforms are supported:
KVM on SLES 11 SP2+
XEN on SLES 10 SP4 / 11 SP1+
Citrix XenServer 6.0 / 6.1
Microsoft Windows 2008 SP2+ /
2008 R2+ / 2012+
Oracle VM 3.0 / 3.1 / 3.2
VMware ESX 5.1 / ESXi 5.1 / ESX 5.2 / ESXi 5.2
2.3. Installation Considerations
This section encompasses many factors that need to be considered before
installing SUSE Linux Enterprise Server on x86, AMD64, Intel 64, and Itanium hardware.
2.3.1. Installation Type
SUSE Linux Enterprise Server is normally installed as an independent operating system.
With the introduction of Xen, it is also possible to run multiple
instances of SUSE Linux Enterprise Server on the same hardware. However, the controlling
Domain-0 installation for Xen is performed like a typical installation
with some additional packages. The installation of Xen guests is
described in Chapter 3, Setting Up Virtual Machines (↑Virtualization with Xen).
2.3.2. Boot Methods
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).
Table 2.2. Boot Options
Boot Option
CD or DVD drive
The simplest booting method. The system requires a locally-available
CD-ROM or DVD-ROM drive for this.
Floppy or USB disks
Find the images required for creating boot disks on the first CD or
DVD in the /boot directory. See also the
README in the same directory. Booting from a
USB memory stick is only possible if the BIOS of the machine
supports this method.
PXE or bootp
Must be supported by the BIOS or by the firmware of the system used.
This option requires a boot server in the network. This task can be
handled by a separate SUSE Linux Enterprise Server.
SUSE Linux Enterprise Server can also be booted from hard disk. For this, copy the
kernel (linux) and the installation system
(initrd) from the
/boot/loader directory of the first CD or DVD
onto the hard disk and add an appropriate entry to the boot loader.
2.3.3. Installation Source
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
2.3.4. Installation Target
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 Xen features like domain
migration.
2.3.5. Different Installation Methods
SUSE Linux Enterprise Server offers several different methods for controlling
installation:
Installation on the console
Installation via serial console
Installation with AutoYaST
Installation with KIWI images
Installation via SSH
Installation with VNC
By default, the graphical console is used. If you have a large number of
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
autoyast2 in
2.4. Boot and Installation Media
When installing the system, the media for booting and for installing the
system may be different. All combinations of supported media for booting
and installing may be used.
2.4.1. Boot Media
Booting a computer depends on the capabilities of the hardware used and
the availability of media for the respective boot option.
Booting from DVD
This is the most common possibility of booting a system. It is
straightforward for most computer users, but requires a lot of
interaction for every installation process.
Booting from a USB Hard Drive
Depending on the hardware used, it is possible to boot from a USB hard
drive. The respective media must be created as described in
Booting from the Network
You can only boot a computer directly from the network if this is
supported by the computer's firmware or BIOS. This booting method
requires a boot server that provides the needed boot images over the
network. The exact protocol depends on your hardware. Commonly you
need several services, such as TFTP and DHCP or pxeboot. If you need a
boot server, also read
2.4.2. Installation Media
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.
Installation from DVD
All necessary data is delivered on the boot media. Depending on the
selected installation, a network connection or add on media may be
necessary.
Networked Installation
If you plan to install several systems, providing the installation
media over the network makes things a lot easier. It is possible to
install from many common protocols, such as NFS, HTTP, FTP, or SMB.
For more information on how to run such an installation, refer to
2.5. Installation Procedure
This section offers an overview of the steps required for the complete
installation of SUSE(R) Linux Enterprise Server in the required mode.
contains a full description of how to
install and configure the system with YaST.
2.5.1. Booting from a Local Interchangeable Drive
CD-ROM and floppy drives and USB memory sticks can be used for
installation purposes. Adjust your computer to your needs:
Make sure that the drive is entered as a bootable drive in the BIOS.
Insert the boot medium in the drive and start the boot procedure.
The boot menu of the CD, DVD, floppy, or USB disk allows transferring
different parameters to the installation system. See also
installation should be performed over the network, specify the
installation source here.
If unexpected problems arise during installation, use safe settings to
2.5.2. Installing over the Network
An installation server is required to perform the installation by using a
network source. The procedure for installing this server is outlined in
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
2.6. Controlling the Installation
Control the installation in one of several ways. The method most
frequently used is to install SUSE(R) Linux Enterprise Server from the computer console.
Other options are available for different situations. Find more
information about the available installation methods in
2.6.1. Installation on the Computer Console
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
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 Section “Navigation in Modules” (Chapter 3, YaST in Text Mode, ↑Administration Guide).
2.6.2. Installation Using a Serial Console
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.
2.6.3. Installation with SSH
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 UseSSH=1 and
SSHPassword=&secret& at the boot prompt. An SSH
daemon is then launched in the system and you can log in to the system as
user root with the password
“secret”. To connect, use the command
ssh -X root@&ipaddr&.
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
As soon as you are logged in to the installation system, launch the
actual installation with the command yast. The
installation will start in the graphical mode if
DISPLAY is set. This then guides you through the
installation. This procedure is described in detail in
2.6.4. Installation over VNC
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 .
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.
2.6.5. Installation with AutoYaST
If you need to install SUSE Linux Enterprise Server on a number of 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.
AutoYaST is extensively documented in
2.7. Dealing with Boot and Installation Problems
Prior to delivery, SUSE(R) Linux Enterprise Server is subjected to an extensive test
program. Despite this, problems occasionally occur during boot or
installation.
2.7.1. Problems Booting
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.
Installed System Boots, Not Media
Change your computer's firmware or BIOS so that the boot sequence is
correct. To do this, consult the manual for your hardware.
The Computer Hangs
Change the console on your computer so that the kernel outputs are
visible. Be sure to check the last outputs. This is normally done by
Ctrl+Alt+F10.
If you are unable to resolve the problem, consult the SUSE Linux Enterprise Server
support staff. To log all system messages at boot time, use a serial
connection as described in .
The Itanium Boot Loader
If you have manually altered the kernel or initrd on your system, run
/sbin/elilo before shutting down the computer. If
you leave out this step, your system may not be bootable.
The boot disk is a useful interim solution if you have difficulties
setting the other configurations or if you want to postpone the
decision regarding the final boot mechanism. A boot disk may also be a
suitable solution in connection with OS/2 or Windows NT. Fore
more details on creating boot disks, see
Section “Creating Boot CDs” (Chapter 11, The Boot Loader GRUB, ↑Administration Guide).
Virus Warning after Installation
There are BIOS variants that check the structure of the boot sector
(MBR) and erroneously display a virus warning after the installation
of GRUB or LILO. Solve this problem by entering the BIOS and
looking for corresponding adjustable settings. For example, switch off
virus protection. You can switch this option back
on again later. It is unnecessary, however, if Linux is the only
operating system you use.
2.7.2. Problems Installing
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:
Check the outputs on the various consoles. You can switch consoles with
the key combination Ctrl+Alt+Fn.
For example, obtain a shell in which to execute various commands by
pressing Ctrl+Alt+F2.
Try launching the installation in failsafe mode. If the installation
works without problems in this case, there is an incompatibility that
causes either ACPI or
APIC to fail. In some cases, a BIOS or
firmware update fixes this problem.
Check the system messages on a console in the installation system by
entering the command dmesg.
2.7.3. Redirecting the Boot Source to the Boot DVD
To facilitate 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.
Chapter 3. Installation on IBM POWERContentsAbstract
This chapter describes the procedure for preparing the installation of
SUSE(R) Linux Enterprise Server on IBM POWER systems.
3.1. Requirements
A standard installation requires at least 256 MB of RAM. The installation
of a standard system requires at least 2.0 GB of free hard disk space.
3.1.1. Hardware Requirements
The SUSE(R) Linux Enterprise Server operating system can be operated on a wide range of
hardware. 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
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
Find up-to-date firmware at IBM FixCentral
(). Select your
system from the Product Group list.
All systems listed below are operated with a PPC64 kernel.
3.1.1.1. IBM POWER7 SystemsPOWER7 systems
Power 710 Express
Power 720 Express
Power 730 Express
Power 740 Express
Power 750 Express
POWER7 BladeCenter Models
IBM BladeCenter PS700
IBM BladeCenter PS701
IBM BladeCenter PS702
IBM BladeCenter PS703
IBM BladeCenter PS704
3.1.1.2. IBM PowerLinux Systems
IBM PowerLinux 7R2
3.1.1.3. IBM POWER5 and POWER6 SystemsPOWER5 Systems
OpenPower 710
System p5 520
System i5 520
POWER6 Systems
IBM Power 550
IBM Power 570
POWER6 BladeCenter models
IBM BladeCenter JS12
IBM BladeCenter JS22
IBM BladeCenter JS23
IBM BladeCenter JS43
3.2. Preparation
This section describes the preparatory steps that must be taken before the
actual installation. The installation procedure depends on the system
used. See the following documentation:
For IBM eServer p5 Systems, see
For IBM pSeries systems, see
For IBM JS20/JS21/JS22 Blades, see
If SUSE(R) Linux Enterprise Server needs to be installed on a number of systems or partitions, it
is recommended you create a network installation source. The same source
can also be used for the concurrent installation on several partitions or
several systems. The configuration of a network installation source is
described in .
The installation can be controlled with a VNC client. For more information
about VNC, see
To participate in the linuxppc-dev mailing list, sign
up using the forms at
following links are pertinent to the maintenance of an installation:
effective help tool for assisting customers in solving problems. A
corresponding article is published whenever SUSE discover that a
special case could lead to serious problems. Search the portal using
keywords like PPC or POWER.
Find security alerts at
. SUSE also
maintains two security-related mailing lists to which anyone may
subscribe.
suse-security — General discussion of
security regarding Linux and SUSE. All security alerts for SUSE Linux Enterprise Server are
sent to this list.
suse-security-announce — The SUSE mailing
list exclusively for security alerts.
3.2.1. Preparing for Installation on IBM eServer p5, System p, and OpenPower Models
This section covers the preparatory steps for installing SUSE(R) Linux Enterprise Server on IBM
eServer p5 systems. It explains the installation from a built-in CD-ROM
drive and over the network.
This section assumes you have set up your HMC and connected it to your
system. Find more information about using the wizard to configure the HMC
in “Configuring the HMC using the Guided Setup Wizard”:
3.2.1.1. Modern Features of IBM eServer p5 Systems
IBM eServer p5 systems offer the possibility of partitioning the system.
This enables the concurrent operation of up to 254 operating systems on
one machine. These operating systems are installed in
LPARs (logical partitions). One or several of these
partitions can contain a SUSE Linux Enterprise Server environment.
To prepare an LPAR for SUSE Linux Enterprise Server, first configure the system over the
HMC. Refer to the IBM documentation for details:
3.2.1.2. Hard Disk Space
Make sure that you have sufficient hard disk space for installing SUSE Linux Enterprise Server.
The standard system requires at least 4 GB of free hard disk space.
3.2.1.3. Assigning an Installation Device to an LPAR
SUSE Linux Enterprise Server can be installed from a CD-ROM or DVD drive or using a network
installation source. Make the CD-ROM, DVD drive, or network device
available to the LPAR to install.
Figure 3.1. HMC: Server Management—PropertiesProcedure 3.1. Assigning a CD-ROM or DVD Drive to an LPAR
Open the HMC application and go to Server and
Partition+Server Management.
From the available servers, expand the server and partition to install.
Right-click the profile to use for installation and select
Properties—see
In the Logical Partition Profile Properties dialog,
select the Physical I/O tab.
From Managed system I/O devices, select the
Other Mass Storage Controller from the bus where it
is installed. To assign this DVD drive to the partition, click
Add as required.
The result should look like
Figure 3.2. HMC: Managed System I/O Devices
Now insert the SUSE Linux Enterprise Server CD1 or DVD1 in the drive.
Procedure 3.2. Assigning a Network Device to an LPAR
Open the HMC application and go to Server and
Partition+Server Management.
From the available servers, open the server and partition to install.
Right-click the profile to use for installation and select
Properties—see
In the Logical Partition Profile Properties dialog,
select the Physical I/O tab.
From Managed system I/O devices, select PCI
10/100/1000Mbps Ethernet UTP 2-port from the bus where it is
installed. Then click Add as required.
If you plan to install using a virtual ethernet adapter, refer to the
IBM documentation.
Create a network installation source if SUSE Linux Enterprise Server should be installed on a
number of partitions. This eliminates the need to change CDs during
installation. The same source can also be used for concurrent
installation of various systems. The configuration of the network
installation source is described in
3.2.1.4. Starting the Installation
To start the installation, reboot the system. Right-click the profile
name, select Activate, and press OK
in the following dialog.
Use the screen console or connect to a serial console as described in the
IBM documentation.
One simple way to start a serial console is to open a VTerm while
activating the partition. To do this, activate Open a terminal
window or console session in the Activate Logical
Partition dialog.
Enter the system firmware by pressing F1 or
1 when using a serial console or a virtual console
during the system check when the system is rebooted:
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
1 = SMS Menu
5 = Default Boot List
8 = Open Firmware Prompt
6 = Stored Boot List
Press F1 or 1 while the SCSI devices
are checked. Select 5. Select Boot Options to enter
the boot options dialog:
Version SF220_004
SMS 1.5 (c) Copyright IBM Corp.
All rights reserved.
---------------------------------------------------------------------
Select Language
Setup Remote IPL (Initial Program Load)
Change SCSI Settings
Select Console
Select Boot Options
---------------------------------------------------------------------
Navigation Keys:
X = eXit System Management Services
---------------------------------------------------------------------
Type the number of the menu item and press Enter or select Navigation
Select 1. Select Install/Boot Device to set the
Install Device. Go to 7. List all
Devices to see the list of available devices:
Version SF220_011
SMS 1.5 (c) Copyright IBM Corp.
All rights reserved.
--------------------------------------------------------------------------
Select Device
Virtual Ethernet
( loc=UD3CCC-V1-C3-T1 )
( loc=U787A.001.DNZ00XG-P1-T5 )
( loc=U787A.001.DNZ00XG-P1-T6 )
IDE CD-ROM
( loc=U787A.001.DNZ00XG-P4-D3 )
SCSI 73407 MB Harddisk
( loc=U787A.001.DNZ00XG-P1-T10-L8-L0 )
--------------------------------------------------------------------------
Navigation keys:
M = return to Main Menu
ESC key = return to previous screen
X = eXit System Management Services
--------------------------------------------------------------------------
Type the number of the menu item and press Enter or select Navigation Key:
3.2.1.5. Booting from the CD-ROM Drive
Select the CD-ROM drive (4 in this example):
SMS 1.5 (c) Copyright IBM Corp.
All rights reserved.
--------------------------------------------------------------------------
Select Task
IDE CD-ROM
( loc=U787A.001.DNZ00XG-P4-D3 )
Information
Normal Mode Boot
Service Mode Boot
--------------------------------------------------------------------------
Navigation keys:
M = return to Main Menu
ESC key = return to previous screen
X = eXit System Management Services
--------------------------------------------------------------------------
Type the number of the menu item and press Enter or select Navigation Key:
Choose 2. Normal Mode Boot to install from this
device. On the next screen, confirm with 1. Yes to
exit System Management Services and boot from the
The system reads from the CD-ROM drive and the yaboot utility starts:
Welcome to SuSE:SLE-11:GA!
to start the YaST installer on this CD/DVD
to start the YaST install via network
to start the rescue system on this CD/DVD
Welcome to yaboot version 1.3.11.SuSE
Enter "help" to get some basic usage information
Type install and press Enter.
To read the installation data from a network install source rather than
continuing the installation from the CD-ROM (see
), append the option
manual to the name of the kernel
(install).
For an installation over VNC, append the parameters
vncpassword=password to the
name of the kernel (install). Read more about VNC in
3.2.1.6. Booting from the Network Source
Select an ethernet device that has access to the installation source
(2 in this example).
3.2.1.7. Additional Steps
Proceed as described in
to begin installing
the software with linuxrc and YaST.
3.2.2. Preparing for Installation on IBM pSeries Models
This section covers the preparatory steps for installing SUSE(R) Linux Enterprise Server on
pSeries systems. It explains the installation from a built-in CD-ROM drive
or a network source.
3.2.2.1. Special Features of IBM pSeries p630, p655, p670, and p690
IBM p630, p655, p670, and p690 systems offer the possibility of
statically partitioning the system similarly to eServer p5/System p5
(which is described in ). This enables
the concurrent operation of up to 16 operating systems on one machine.
These operating systems are installed in LPARs
(logical partitions). One or several of these partitions can contain a
SUSE Linux Enterprise Server environment.
To prepare an LPAR for SUSE Linux Enterprise Server, first configure the system over the
HMC. Refer to the Redbook IBM eServer
pSeries 690 System Handbook (SG24-7040-00) for details
Important notes regarding the configuration:
The recommended maximum number of processors for a SUSE Linux Enterprise Server LPAR is eight,
because the kernel can only manage eight processors effectively.
For the installation, select SMS as the boot mode
for the respective partition.
The HMC terminal used for the input during the
installation is a VT320 emulation. This emulation can lead to strange
results with some applications. If possible, use an XTerm for
communicating with the LPAR.
3.2.2.2. Hard Disk Space
Make sure that you have sufficient hard disk space for installing SUSE Linux Enterprise Server.
The use of a separate hard disk is recommended.
SUSE Linux also supports installing to Fibre Channel–attached
storage. Before beginning installation, the Fibre Channel Host Bus
Adapter (FCHBA), SAN fabric, and storage system must each be configured
to provide access from the FCHBA through the SAN Fabric to target logical
units (LUNs) on the storage system.
SAN storage devices, if properly configured, are listed among existing
hard disks on your system. Create Custom Partitioning
Setup opens the dialog, as described in
3.2.2.3. Setting Up the Installation Source
If you plan to install from CD-ROM, insert CD1 in the drive. In LPAR
mode, the partition to install must have the CD-ROM in its partition
profile. Create a network installation source if SUSE Linux Enterprise Server needs to be
installed over a number of partitions. This eliminates the need to change
CDs during installation. The same source can also be used for concurrent
installation of various systems. The configuration of the network
installation source is described in
3.2.2.4. Starting the Installation
To start the installation, reboot the system. Then enter the system
firmware by pressing F1 or 1 when using
the serial console during the system check when the system is rebooted.
Figure 3.3. Entering the System Firmware
Press F1 or 1 while the SCSI devices
are checked. Select 6 MultiBoot to enter the
Multiboot dialog. See
Figure 3.4. Multiboot Dialog
Select 3 to set the install device. A list of
available devices is displayed. See
Figure 3.5. Installing the Operating System3.2.2.5. Booting from the CD-ROM Drive
Select the respective CD-ROM drive (3 in this
example). The system reads from the CD-ROM drive and displays the
identstring.
SuSE:SLE-11:GA&-
After you select 1, the yaboot utility is started.
Welcome to SuSE:SLE-11:GA!
to start the YaST installer on this CD/DVD
to start the YaST install via network
to start the rescue system on this CD/DVD
Type install and press Enter.
Alternatively, just press Enter to start the installer,
the default option.
To install from a network source (see
manual to the kernel to install. For
an installation over VNC, append the parameters vnc=1
and vncpassword=password to
install. Read more about VNC in
In LPAR mode, the partition to install must have the CD-ROM in its
partition profile.
3.2.2.6. Booting from the Network Source
Select an ethernet device that has access to the installation source
(6 in this example).
3.2.2.7. Additional Steps
Proceed as described in
to begin installing the software with linuxrc
3.2.3. Preparing an Installation on IBM JSxx BladeCenter
This section describes the preparatory steps for the installation of
SUSE(R) Linux Enterprise Server on JSxx Blades. It covers installation using the CD-ROM drive of
the BladeCenter and using the network.
3.2.3.1. Creating a Network Installation Source
Create a network installation source if SUSE Linux Enterprise Server needs to be installed over
a number of partitions. This provides the advantage of no CDs needing to
be changed during installation. The same source can also be used for the
concurrent installation of various systems. Configuration of a network
installation source is described in
3.2.3.2. Hard Disk Storage Space
Ensure that enough hard disk storage space is available for the
installation of SUSE Linux Enterprise Server. It is recommended you use a dedicated hard disk.
3.2.3.3. Preparing the System for Boot3.2.3.3.1. Preparing to Boot from the CD-ROM Drive
Perform the steps described in this section if an installation from
CD-ROM is desired.
Assign the CD-ROM drive to the Blade chosen for installation by
connecting (with a Web browser) to a BladeCenter Management Module, then
logging in. After login, select the function Remote
Control in the menu Blade Tasks then
activate Start Remote Control. Assign the CD-ROM
drive to the desired blade in the menu Change Media Tray
Owner of the new window.
Set up the CD-ROM drive as a boot device. Do this by selecting
Blade Tasks then Configuration
while in the BladeCenter Management Module. Select the JSxx Blade in the
section Boot Sequence. Set the entry for 1st
Device on the page for Blade Boot Sequence
Put CD 1 in the CD-ROM drive and restart the blade.
3.2.3.3.2. Preparing to Boot from the Network
Perform the steps as described in this section if an installation over
the network is desired.
Connect to the BladeCenter Management Module using a Web browser and log
in. Set the boot device to the network by accessing the
Configuration menu from the Blade
Tasks page. Select the JSxx Blade in the section Boot
Sequence and set 1st Boot Device to
Network — BOOTP on Blade Boot
3.2.3.3.3. Rebooting and Connecting to the Console of the JSxx Blade
Reboot the JSxx Blade from the item Power/Restart of
the Blade Tasks menu in the BladeCenter Management
Module. A table appears, showing the power status of the blades in the
Pwr column. Mark the check box of the desired blade
and restart it with Power On Blade.
Connect to the BladeCenter with the command telnet
bladecenter and log in.
username: user
password: ********
The command env -T system:blade[bay
number] determines for which JSxx Blade the
subsequent commands are intended. The blades installed in the
BladeCenter are listed by calling list -l 3.
system& list -l 3
The command target is then determined. To work, for
example, with blade number 9, enter env -T
system:blade[9]. Connect with the console of the JSxx Blade
over Serial over LAN (SOL) with the command
system& env -T system:blade[9]
system:blade[9]& console
3.2.3.3.4. Starting the Installation
The SUSE Linux Enterprise Server boot loader starts after the system check has completed.
Welcome to SuSE:SLE-11:GA!
to start the YaST installer on this CD/DVD
to start the YaST install via network
to start the rescue system on this CD/DVD
Welcome to yaboot version 1.3.11.SuSE
Enter "help" to get some basic usage information
Select install from the menu and press
In the case of an installation over VNC, append the parameters
vncpassword=password to the
command line for the kernel (install).
3.2.3.3.5. Additional Steps
Proceed as described in
to begin installing the software with linuxrc
Chapter 4. Installation on IBM System zContentsAbstract
This chapter describes the procedure for preparing the installation of
SUSE(R) Linux Enterprise Server on IBM System z systems. It provides all information
needed to prepare the installation on the LPAR and z/VM side.
4.1. General Information and Requirements
This section gives basic information about the system requirements (like
supported hardware), level of MicroCode, and software. It also covers the
different installation types, how to do an IPL for the first installation,
and information about the IOCDS.
4.1.1. System Requirements
This section provides a list of hardware for IBM System z supported by
SUSE Linux Enterprise Server. Next, the level of the MicroCode (MCL) used in your IBM
System z system, which is very important for the installation, is
covered. Additional software to install and use for installation is
mentioned at the end of this section.
4.1.1.1. Hardware
SUSE Linux Enterprise Server has run successfully on the following platforms:
IBM Series z9 (z9-EC) 2094
IBM Series z9 (z9-BC) 2096
IBM Series z10 (z10-EC) 2097
IBM Series z10 (z10-BC) 2098
IBM zEnterprise System z196 2817
IBM zEnterprise System z114 2818
IBM zEnterprise EC12 (zEC12) 2827
4.1.1.1.1. Memory Requirements
Different installation methods have different memory requirements
during installation. After installation is completed, the system
administrator may reduce memory to the desired size. SUSE recommends
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
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:
4.1.1.1.3. Network Connection
A network connection is needed to communicate with your SUSE Linux Enterprise Server
system. This can be one or more of the following connections or network
OSA Express Ethernet (including Fast and Gigabit Ethernet)
HiperSockets or Guest LAN
10 GBE, VSWITCH
The following interfaces are still included, but no longer supported:
CTC (or virtual CTC)
IP network interface for IUCV
4.1.1.1.4. IPL Options
For an LPAR installation, the Load from CD-ROM or
Server option is the preferred way to IPL the installation
kernel and initrd (initial RAM disk). If this option is not available
and you cannot use z/VM for installing the system, you need to IPL from
a channel attached tape with the tapeipl kernel, the parmfile, and the
initrd. Thus, you need access to a tape unit (, or 3590, for
4.1.1.2. MicroCode Level, APARs, and Fixes
Documentation about restrictions and requirements for this release of SUSE
Linux Enterprise Server can be found on IBM developerWorks at .
It is recommended always to use the highest service level
available. Contact your IBM support for minimum requirements.
4.1.1.2.1. z/VMz/VM 5.4z/VM 6.2
Negotiate the order of installation with your IBM support, because it
might be necessary to activate the VM APARs before installing the new
MicroCode levels.
4.1.1.3. Software
To install SUSE Linux Enterprise Server via non-Linux–based NFS or FTP, you might
experience problems with NFS or FTP server software. 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 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
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
. Alternatively, use the VNC
Java client and a Java-enabled Web browser.
Find a suitable X server implementation on any Linux or Unix
workstation. There are many commercial X Window System environments
for Windows and Macintosh. Some of them can be downloaded as free
trial versions. A trial version of the Mocha X Server from MochaSoft
can be obtained at
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 System z. This file completes the documentation presented in this
4.1.2. Installation Types
This section gives an overview of the different types of installation
possible with SUSE Linux Enterprise Server for IBM System z. Basically, these two types
are given:
Installation of SUSE Linux Enterprise Server using a logical partition (LPAR).
Installation of SUSE Linux Enterprise Server as as a guest operating system within
Depending on the mode of installation (LPAR or VM), there are different
possibilities for starting the installation process and IPLing the
installed system.
4.1.2.1. LPAR
If you install SUSE Linux Enterprise Server for IBM System z into a separate logical
partition (LPAR), allow SUSE Linux Enterprise Server to use a special part of the
physical memory in your system. Also decide how many processors are used
by SUSE Linux Enterprise Server. In this mode, you can run different operating systems
simultaneously on your IBM System z system.
4.1.2.2. z/VM
Running SUSE Linux Enterprise Server for IBM System z in z/VM means that SUSE Linux Enterprise Server
is a guest system within z/VM. An advantage of this mode is that you
have full control over SUSE Linux Enterprise Server from z/VM. This is very helpful for
kernel development or kernel-based debugging. It is also very easy to
add or remove hardware to and from Linux guests. Creating additional
SUSE Linux Enterprise Server guests is simple and you are able to run hundreds of Linux
instances simultaneously.
4.1.3. IPL Options
This section provides the information needed to do an IPL for the first
installation. Depending on the type of installation, different options
need to be used. The channel-attached tape, VM reader, and load from
CD-ROM or server options are discussed. Installing the software packages,
which is done over the network, does not require the IPL medium.
4.1.3.1. ESCON or FICON Attached Tape
IPLing from a channel-attached tape is possible on all systems connected
to a tape library. The only prerequisite is that the LPAR in which to
install (or allowing z/VM to run) is allowed to access the tape unit.
For this, the IODEVICE statement in the IOCDS must
have the attribute SHARED or
PART=&LPARName&.
4.1.3.2. VM Reader
To IPL from a VM reader, transfer the necessary files into the reader
first. Then multiple IPLs are easily done. This is the preferred way on
z/VM. For convenience of administration, it is recommended to create a
user linuxmnt that owns a minidisk with the files and
scripts needed for IPL. This minidisk is then accessed read-only by the
Linux guests.
4.1.3.3. Load from CD/DVD-ROM or Server
For IPLing into an LPAR, it is possible to either load the kernel image
directly from the SE's or the HMC's CD/DVD-ROM device or from any remote
system accessible through FTP. This function can be performed from the
HMC. The installation process requires a file with a mapping of the
location of the installation data in the file system and the memory
locations where the data is to be copied. For SUSE Linux Enterprise Server this file is
called suse.ins and located in the root directory
of the file system on the DVD 1.
In the left navigation pane of the HMC expand Systems
Management and Servers and select the mainframe system you
want to work with. Choose the LPAR where you want to boot SUSE Linux Enterprise Server
from the table of LPARs displayed in the upper content area on the
right. In the Tasks area, expand Recovery and click
Load from CD-ROM, DVD, or Server.
Now either choose
Hardware Management Console CD-ROM/DVD
or FTP Source. If having chosen the latter
option, provide the servers address or name and your credentials. In
case the suse.ins file is not located in the root
directory of the server, provide the path to this file. Continue to the
Select the software to load menu and select the
suse.ins entry. Start the installation with
4.1.3.4. Load from SCSI-Attached DVD
To IPL from a SCSI DVD, you need access to an FCP adapter connected to a
DVD drive. You need values like the WWPN and LUN from the SCSI drive.
For details, see .
4.1.3.5. Load from the Network with zPXE
IPLing from the Network with zPXE requires a Cobbler server providing the
kernel, RAM disk and a parmfile. zPXE is only available on z/VM and is
initiated by running the ZPXE EXEC script. See
for details.
4.1.4. The IOCDS
This section provides some necessary information about the IOCDS and how
to customize some settings for sharing network cards or DASDs among
several LPARs. In the IOCDS, the chpid and types of
the devices connected to the IBM System z are defined. The resources can
be dedicated or shared among LPARs.
Do not share writable DASD among LPARs because this might result in data
loss. Consider the definition of the necessary resources in advance when
planning the setup for SUSE Linux Enterprise Server on IBM System z.
This example shows how to dedicate a DASD to one specific LPAR. This LPAR
is referred to as LPAR1.
Example 4.1. Dedicating DASD to One LPARCHPID PATH=FD,TYPE=DSD,SHARED
CNTLUNIT CUNUMBR=FD00,PATH=FD,UNITADD=((00,256)),UNIT=3990-2
IODEVICE ADDRESS=(FD03,1),CUNUMBR=FD00,UNIT=3390,PART=LPAR1
To share a DASD among LPARs, delete the PART=LPAR1
part in the IOCDS definition. This might be useful for high availability
reasons or for sharing data among LPARs read-only.
Several Linux systems can use the same network device if you share it
among LPARs or z/VM guests. This reduces the number of network devices
that must be provided to the Linux system. On the other hand, you might
provide more than one network device to one Linux system to make it more
available in case one connection fails.
Network cards like OSA-Express can be used in two different modes. These
modes are known as QDIO and non-QDIO mode. Define these modes in the
IOCDS by using the TYPE statement. QDIO mode is much
faster than non-QDIO mode, but uses three device addresses instead of two
in non-QDIO. Consider the limited number of device addresses when
planning the setup of your IBM System z Linux environment.
Example 4.2. Sharing OSA Express Card among LPARs (non-qdio) on z9CHPID PATH=(FE),SHARED,PARTITION=((LPAR1,LPAR2)),TYPE=OSE
CNTLUNIT CUNUMBR=FE00,PATH=(FE),UNIT=OSA
IODEVICE ADDRESS=(FE00,016),CUNUMBR=(FE00),UNIT=OSA
IODEVICE ADDRESS=(FEFE,001),CUNUMBR=(FE00),UNIT=OSADExample 4.3. Sharing OSA Express Card among LPARs (qdio) on z9CHPID PATH=(FE),SHARED,PARTITION=((LPAR1,LPAR2)),TYPE=OSD
CNTLUNIT CUNUMBER=FE00,PATH=(FE),UNIT=OSA
IODEVICE ADDRESS=(FE00,016),CUNUMBR=(FE00),UNIT=OSA
IODEVICE ADDRESS=(FEFE,001),CUNUMBR=(FE00),UNIT=OSAD4.2. Preparing for Installation
In this section, learn how to make the data accessible for installation,
install SUSE Linux Enterprise Server using different methods, and prepare and use the IPL
of the SUSE Linux Enterprise Server installation system. Also find out about network
configuration and network installation.
4.2.1. Making the Installation Data Available
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.
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.
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
If you have a Linux workstation running in your computer environment,
use the workstation to provide the installation data to the IBM
System z installation process by NFS or FTP. If the Linux workstation
runs under SUSE Linux Enterprise Server, you can set up an installation server (NFS or
FTP) using the YaST Installation Server module as
described in
4.2.1.1.1. Over NFS
Use NFS (network file system) to make the installation media available.
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
After changing this file, restart the NFS server with the command
rcnfsserver restart.
4.2.1.1.2. Over FTP
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.
4.2.1.1.3. SUSE Linux Enterprise Server on DVD
DVD1 of the SUSE