Novell LINUX ENTERPRISE SERVER 11 - DEPLOYMENT, SUSE LINUX ENTERPRISE SERVER 11 Deployment Manual
Page 1
SUSE Linux Enterprise
Server
www.novell.com11
March23,2009 Deployment Guide
Page 2
Deployment Guide
All content is copyright © 2006- 2009 Novell, Inc.
Legal Notice
This manual is protected under Novell intellectual property rights. By reproducing, duplicating or
distributing this manual you explicitly agree to conform to the terms and conditions of this license
agreement.
This manual may be freely reproduced, duplicated and distributed either as such or as part of a bundled
package in electronic and/or printed format, provided however that the following conditions are fullled:
That this copyright notice and the names of authors and contributors appear clearly and distinctively
on all reproduced, duplicated and distributed copies. That this manual, specically for the printed
format, is reproduced and/or distributed for noncommercial use only. The express authorization of
Novell, Inc must be obtained prior to any other use of any manual or part thereof.
For Novell trademarks, see the Novell Trademark and Service Mark list http://www.novell
.com/company/legal/trademarks/tmlist.html. * Linux is a registered trademark of
Linus Torvalds. All other third party trademarks are the property of their respective owners. A trademark
symbol (®, ™ etc.) denotes a Novell trademark; 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 Novell, Inc., SUSE LINUX Products GmbH, the authors,
nor the translators shall be held liable for possible errors or the consequences thereof.
Page 3
Contents
About This Guide ix
1 Planning for SUSE Linux Enterprise Server 1
1.1 Considerations for Deployment of a SUSE Linux Enterprise Server . . . . . 2
1.2 Deployment of SUSE Linux Enterprise Server . . . . . . . . . . . . . . 3
1.3 Running SUSE Linux Enterprise Server . . . . . . . . . . . . . . . . . 4
Part I Architecture Specic Installation Considerations 5
2 Installation on x86, AMD64, Intel 64, and Itanium 7
2.1 Required Background . . . . . . . . . . . . . . . . . . . . . . . . 7
2.2 System Requirements for Operating Linux . . . . . . . . . . . . . . . 8
2.3 Installation Considerations . . . . . . . . . . . . . . . . . . . . . 11
2.4 Boot and Installation Media . . . . . . . . . . . . . . . . . . . . 14
2.5 Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . 15
2.6 Controlling the Installation . . . . . . . . . . . . . . . . . . . . . 16
2.7 Dealing with Boot and Installation Problems . . . . . . . . . . . . . . 18
3 Installation on IBM POWER 21
3.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2 Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4 Installation on IBM System z 39
4.1 General Information and Requirements . . . . . . . . . . . . . . . . 39
4.2 Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . 46
4.3 Network Connection Types . . . . . . . . . . . . . . . . . . . . . 63
Page 4
4.4 The parmle—Automating the System Conguration . . . . . . . . . . 67
4.5 Using the vt220 Terminal Emulator . . . . . . . . . . . . . . . . . 73
4.6 Further In-Depth Information about IBM System z . . . . . . . . . . . 74
Part II Manual Deployment 77
5 Deployment Strategies 79
5.1 Deploying up to 10 Workstations . . . . . . . . . . . . . . . . . . 79
5.2 Deploying up to 100 Workstations . . . . . . . . . . . . . . . . . . 81
5.3 Deploying More than 100 Workstations . . . . . . . . . . . . . . . 88
6 Installation with YaST 89
6.1 Choosing the Installation Method . . . . . . . . . . . . . . . . . . 89
6.2 The Installation Workow . . . . . . . . . . . . . . . . . . . . . 91
6.3 IBM POWER: System Start-Up for Network Installation . . . . . . . . . 92
6.4 IBM System z: System Start-Up for Installation . . . . . . . . . . . . . 92
6.5 System Start-Up for Installation . . . . . . . . . . . . . . . . . . . 93
6.6 The Boot Screen . . . . . . . . . . . . . . . . . . . . . . . . . 93
6.7 Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.8 IBM System z: Hard Disk Conguration . . . . . . . . . . . . . . . . 99
6.9 Installation Mode . . . . . . . . . . . . . . . . . . . . . . . . 101
6.10 Clock and Time Zone . . . . . . . . . . . . . . . . . . . . . . . 103
6.11 Server Base Scenario . . . . . . . . . . . . . . . . . . . . . . . 105
6.12 Installation Settings . . . . . . . . . . . . . . . . . . . . . . . 105
6.13 Performing the Installation . . . . . . . . . . . . . . . . . . . . 110
6.14 Conguration of the Installed System . . . . . . . . . . . . . . . . 113
6.15 Graphical Login . . . . . . . . . . . . . . . . . . . . . . . . . 124
7 Updating SUSE Linux Enterprise 125
7.1 Updating SUSE Linux Enterprise . . . . . . . . . . . . . . . . . . 125
7.2 Installing Service Packs . . . . . . . . . . . . . . . . . . . . . . 128
7.3 Software Changes from Version 10 to Version 11 . . . . . . . . . . . 128
8 Setting Up Hardware Components with YaST 129
8.1 Probing Your Hardware . . . . . . . . . . . . . . . . . . . . . . 129
8.2 Setting Up Graphics Card and Monitor . . . . . . . . . . . . . . . 130
8.3 Setting Up Keyboard and Mouse . . . . . . . . . . . . . . . . . . 131
8.4 Setting Up Sound Cards . . . . . . . . . . . . . . . . . . . . . . 134
8.5 Setting Up a Printer . . . . . . . . . . . . . . . . . . . . . . . 136
Page 5
9 Installing or Removing Software 141
9.1 Denition of Terms . . . . . . . . . . . . . . . . . . . . . . . . 141
9.2 Using the Qt Interface . . . . . . . . . . . . . . . . . . . . . . 142
9.3 Managing Software Repositories and Services . . . . . . . . . . . . 147
9.4 Keeping the System Up-to-date . . . . . . . . . . . . . . . . . . 149
10 Installing Add-On Products 157
10.1 Add-Ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
10.2 Binary Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . 158
10.3 SUSE Software Development Kit (SDK) 10 . . . . . . . . . . . . . . 158
11 Accessing the Internet 159
11.1 Direct Internet Connection . . . . . . . . . . . . . . . . . . . . 159
11.2 Internet Connection Via Network . . . . . . . . . . . . . . . . . . 162
12 Managing Users with YaST 163
12.1 User and Group Administration Dialog . . . . . . . . . . . . . . . 163
12.2 Managing User Accounts . . . . . . . . . . . . . . . . . . . . . 165
12.3 Additional Options for User Accounts . . . . . . . . . . . . . . . . 167
12.4 Changing Default Settings for Local Users . . . . . . . . . . . . . . 175
12.5 Assigning Users to Groups . . . . . . . . . . . . . . . . . . . . . 176
12.6 Managing Groups . . . . . . . . . . . . . . . . . . . . . . . . 176
12.7 Changing the User Authentication Method . . . . . . . . . . . . . . 178
13 Changing Language and Country Settings with YaST 181
13.1 Changing the System Language . . . . . . . . . . . . . . . . . . . 181
13.2 Changing the Country and Time Settings . . . . . . . . . . . . . . 185
14 Remote Installation 189
14.1 Installation Scenarios for Remote Installation . . . . . . . . . . . . . 189
14.2 Setting Up the Server Holding the Installation Sources . . . . . . . . . 198
14.3 Preparing the Boot of the Target System . . . . . . . . . . . . . . . 208
14.4 Booting the Target System for Installation . . . . . . . . . . . . . . 218
14.5 Monitoring the Installation Process . . . . . . . . . . . . . . . . . 222
15 Advanced Disk Setup 227
15.1 Using the YaST Partitioner . . . . . . . . . . . . . . . . . . . . . 227
15.2 LVM Conguration . . . . . . . . . . . . . . . . . . . . . . . . 235
Page 6
15.3 Soft RAID Conguration . . . . . . . . . . . . . . . . . . . . . 241
16 Subscription Management 247
16.1 Using Kernel Parameters to Access an SMT Server . . . . . . . . . . . 248
16.2 Conguring Clients Using AutoYaST Prole . . . . . . . . . . . . . . 249
16.3 Conguring Clients Using the clientSetup4SMT.sh Script . . . . . . . . 251
16.4 Registering Clients Against SMT Test Environment . . . . . . . . . . . 251
Part III Imaging and Creating Products 253
17 KIWI 255
17.1 Prerequisites for KIWI . . . . . . . . . . . . . . . . . . . . . . 255
17.2 Knowing KIWI’s Build Process . . . . . . . . . . . . . . . . . . . 256
17.3 Image Description . . . . . . . . . . . . . . . . . . . . . . . . 256
17.4 Creating Appliances with KIWI . . . . . . . . . . . . . . . . . . . 260
17.5 For More Information . . . . . . . . . . . . . . . . . . . . . . 262
18 Creating Add-On Products With Add-on Creator 263
18.1 Creating Images . . . . . . . . . . . . . . . . . . . . . . . . . 263
18.2 Add-On Structure . . . . . . . . . . . . . . . . . . . . . . . . 264
18.3 For More Information . . . . . . . . . . . . . . . . . . . . . . 265
19 Creating Images with YaST Product Creator 267
19.1 Prerequisites for Product Creator . . . . . . . . . . . . . . . . . . 267
19.2 Creating Images . . . . . . . . . . . . . . . . . . . . . . . . . 267
19.3 For More Information . . . . . . . . . . . . . . . . . . . . . . 269
20 Deploying Customized Preinstallations 271
20.1 Preparing the Master Machine . . . . . . . . . . . . . . . . . . . 272
20.2 Customizing the Firstboot Installation . . . . . . . . . . . . . . . . 272
20.3 Cloning the Master Installation . . . . . . . . . . . . . . . . . . . 281
20.4 Personalizing the Installation . . . . . . . . . . . . . . . . . . . . 281
Part IV Automated Installations 283
21 Automated Installation 285
21.1 Simple Mass Installation . . . . . . . . . . . . . . . . . . . . . . 285
21.2 Rule-Based Autoinstallation . . . . . . . . . . . . . . . . . . . . 297
Page 7
21.3 For More Information . . . . . . . . . . . . . . . . . . . . . . 302
22 Automated Deployment of Preload Images 303
22.1 Deploying system manually from rescue image . . . . . . . . . . . . 304
22.2 Automated Deployment with PXE Boot . . . . . . . . . . . . . . . 305
Page 8
Page 9
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.
Part I, “Architecture Specic Installation Considerations” (page 5)
The standard deployment instructions differ depending on the architecture used.
For differences and requirements regarding the architecture, see this part.
Part II, “Manual Deployment” (page 77)
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.
Part III, “Imaging and Creating Products” (page 253)
Mass installations often require to prepare images or products furnished with the
features that are needed in this special case. Several options are described that allow
the administrator to prepare this deployment methods.
Part IV, “Automated Installations” (page 283)
To do unattended installations, either use the installation with AutoYaST or prepare
an image with kiwi or rstboot. 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. This
includes 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 http://www.novell.com/documentation 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 on this product:
Page 10
Deployment Guide (page 1)
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 Novell AppArmor (which lets you specify per program which les the program
may read, write, and execute) or the auditing system that reliably collects information about any security-relevant events.
Virtualization with Xen (↑Virtualization with Xen)
Offers an introduction to virtualization technology of your product. It features an
overview of the various elds 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.
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.
x Deployment Guide
Page 11
Linux Audit Quick Start
Gives a short overview how to enable and congure the auditing system and how
to execute key tasks such as setting up audit rules, generating reports, and analyzing
the log les.
Novell AppArmor Quick Start
Helps you understand the main concepts behind Novell® AppArmor.
Find HTML versions of most SUSE Linux Enterprise Server manuals in your installed
system under /usr/share/doc/manual or in the help centers of your desktop.
Find the latest documentation updates at http://www.novell.com/
documentation where you can download PDF or HTML versions of the manuals
for your product.
2 Feedback
Several feedback channels are available:
• To report bugs for a product component or to submit enhancements requests, please
use https://bugzilla.novell.com/. If you are new to Bugzilla, you
might nd the Bug Writing FAQs helpful, available from the Novell Bugzilla home
page.
• We want to hear your comments and suggestions about this manual and the other
documentation included with this product. Please use the User Comments feature
at the bottom of each page of the online documentation and enter your comments
there.
3 Documentation Conventions
The following typographical conventions are used in this manual:
•
/etc/passwd: directory names and lenames
•
placeholder: replace placeholder with the actual value
•
PATH: the environment variable PATH
About This Guide xi
Page 12
•
ls, --help: commands, options, and parameters
•
user: users or groups
•
Alt, Alt + F1: a key to press or a key combination; keys are shown in uppercase as
on a keyboard
•
File, File > Save As: menu items, buttons
• ►amd64 em64t ipf: This paragraph is only relevant for the specied architectures.
The arrows mark the beginning and the end of the text block. ◄
►ipseries zseries: This paragraph is only relevant for the specied architectures.
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.
xii Deployment Guide
Page 13
1
Planning for SUSE Linux
Enterprise Server
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 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 3.3 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).
YaST
Several new conguration options have been developed for YaST. These are normally described in the chapters about the technology involved.
SPident
The management utility SPident gives an overview of the installed software base
and claries the current service pack level of the system.
Directory Services
Several LDAP-compliant directory services are available:
• Microsoft Active Directory
• OpenLDAP
Planning for 1
Page 14
Novell AppArmor
Harden your System with the Novell AppArmor technology. This service is described in depth in Part “Conning Privileges with Novell AppArmor” (↑Security
Guide).
AIDE
This is an intrusion detection system that can be setup to detect unauthorized changes
to the system.
iSCSI
iSCSI provides an easy and reasonably inexpensive solution for connecting Linux
computers to central storage systems. Find more information about iSCSI in the
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 le 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 more comfortable 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 dene 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
method differs. See also Chapter 5, Deployment Strategies (page 79).
2 Deployment Guide
Page 15
• Will the system run as physical host, a virtual machine or as a virtual machine?
•
Will the system be in a hostile environment? Have a look at Chapter 1, Security
and Condentiality (↑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 http://www.novell
.com/linux/suse/portal/index.html.
• Do you need help for your local installation? Novell provides training, support,
and consulting for all topics around SUSE Linux Enterprise Server. Find more in-
formation about this at http://www.novell.com/products/server/.
• Do you need third-party products? Make sure that the required product is also
supported on the desired platform. Novell can also provide help to port software
to different platforms when needed.
1.2 Deployment of SUSE Linux
Enterprise Server
To make sure that your system will run awlessly, always try to use certied hardware.
The hardware certication process is an ongoing process and the database of certied
hardware is updated regularly. Find the search form for certied hardware at http://
developer.novell.com/yessearch/Search.jsp.
Depending on the number of desired installations, it is benecial to use installation
servers or even completely automatic installations. Have a look at Chapter 5, Deployment
Strategies (page 79) for more information. When using the Xen virtualization technolo-
gies, network root le 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 congurations can be made with YaST, the SUSE conguration utility. In addition to that, many manual congurations are described in the corresponding chapters.
Planning for 3
Page 16
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 safe work, you should make regular updates of all the operated
machines. If you have a mission critical server, you should probably run a second
identical machine where you can apply all changes for testing purposes before doing
so on the real system. This also gives you the possibility to switch machines in case of
hardware failure.
4 Deployment Guide
Page 17
Part I. Architecture Specic
Installation Considerations
Page 18
Page 19
2
Installation on x86, AMD64,
Intel 64, and Itanium
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 and provides useful information. 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. It is assumed that:
• 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 http://www.novell.com/documentation.
Installation on x86, AMD64, Intel 64, and Itanium 7
Page 20
2.2 System Requirements for
Operating Linux
The SUSE® Linux Enterprise Server operating system can be operated 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 conguration will work, nd out which
computers have been certied by SUSE. Find a list of these computers at http://
developer.novell.com/yessearch/Search.jsp.
2.2.1 Hardware for x86
Computers based on x86 constitute a cost-effective way of building high-performance
systems. The preconditions to operating SUSE Linux Enterprise Server on this platform
are as follows:
CPU
The number of CPUs supported depends on the kernel used. Specically, these are
as follows:
Table 2.1
CPUs Supported by the Kernel
Maximum Number of
CPUs
Oldest CPU TypeKernel
32PentiumPro, Athlonkernel-default
128Pentium II, Athlon XPkernel-pae
Memory Requirements
A minimum of 512 MB is required. The minimum 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.
8 Deployment Guide
Page 21
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:
Hard Disk RequirementsSystem
1.2 GBMinimal X Window System
3.2 GBGNOME Desktop
2.7 GBKDE Desktop
10 GBAll patterns
Boot Methods
The computer can be booted for installation from DVD, USB hard drive, oppy,
or the network. A special boot server is required to boot over the network. This
boot server can be congured with SUSE Linux Enterprise Server. To use USB
hard drives, the BIOS or rmware must support booting from USB devices. Create
an bootable USB hard drive with mkbootdisk, which is found on the rst installation DVD in the directory /boot/i386/ or /boot/x86_64. For more information, read the documentation below the /boot directory.
2.2.2 Hardware for Itanium
The Itanium architecture is 64-bit and allows operation of large servers.
CPU
Itanium 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 dualcore 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.
Installation on x86, AMD64, Intel 64, and Itanium 9
Page 22
Memory
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:
Hard Disk RequirementsSystem
4 GBMinimal System
10 GBRecommended
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.
CPU
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 128.
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.
10 Deployment Guide
Page 23
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 plan some space for
compatibility libraries. Minimum requirements for different selections are:
Hard Disk RequirementsSystem
1.4 GBMinimal X Window System
3.5 GBGNOME Desktop
3 GBKDE Desktop
8.5 GBAll patterns
Boot Methods
The computer can be booted from CD or network. A special boot server is required
to boot over the network. This can be set up with SUSE Linux Enterprise Server.
2.3 Installation Considerations
This section encompasses many decisions that need to be made 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).
Installation on x86, AMD64, Intel 64, and Itanium 11
Page 24
2.3.2 Boot Methods
Depending on the hardware used, the following boot methods are available for the rst
boot procedure prior to the installation of SUSE Linux Enterprise Server:
Table 2.2
Boot Options
UseBoot Option
The simplest booting method. The system requires a locallyavailable CD-ROM or DVD-ROM drive for this.
CD or DVD drive
Find the images required for creating boot disks on the rst CD
or DVD in the /boot directory. See also the README in the
Floppy or USB
disks
same directory. Booting from a USB memory stick is only
possible if the BIOS of the machine supports booting from it.
Must be supported by the BIOS or by the rmware of the system
used. This option requires a boot server in the network. This
PXE or bootp
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
Hard disk
system (initrd) from the /boot/loader directory of the
rst 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 sever. 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.
12 Deployment Guide
Page 25
The installation source is particularly easy to select if you congure an SLP server in
the local network. For more information, see Section 14.2, “Setting Up the Server
Holding the Installation Sources” (page 198).
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 all kinds of block devices that provide sufcient 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 le 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 conguration le or a KIWI preload
image and make this available to the installation process. See also the documentation
Installation on x86, AMD64, Intel 64, and Itanium 13
Page 26
for autoyast2 in Chapter 21, Automated Installation (page 285) and KIWI in Chap-
ter 17, KIWI (page 255).
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 or Floppy Disk
Depending on the hardware used, it is possible to boot from a USB hard drive or
a oppy disk. The respective media must be created with the utility mkbootdisk,
which can be found together with its documentation on the rst CD or DVD in the
directory /boot/<architecture>.
Booting from the Network
You can only boot a computer directly from the network if this is supported by the
computer's rmware 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 Section 14.1.3, “Remote Installation
via VNC—PXE Boot and Wake on LAN” (page 193).
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
14 Deployment Guide
Page 27
installation system after booting for installation. Several possibilities to provide 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 about how to
run such an installation, refer to Chapter 14, Remote Installation (page 189).
2.5 Installation Procedure
This section offers an overview of the steps required for the complete installation of
SUSE® Linux Enterprise Server in the required mode. Part II, “Manual Deployment”
(page 77) contains a full description of how to install and congure the system with
YaST.
2.5.1 Booting from a Local Interchangeable
Drive
CD-ROM and oppy drives and USB memory sticks can be used for installation purposes. Adjust your computer to your needs:
1. Make sure that the drive is entered as a bootable drive in the BIOS.
2. Insert the boot medium in the drive and start the boot procedure.
3. The boot menu of the CD, DVD, oppy, or USB disk allows transferring different
parameters to the installation system. See also Section 14.4.2, “Using Custom Boot
Options” (page 219). If the installation should be performed over the network,
specify the installation source here.
4. If unexpected problems arise during installation, use safe settings to boot.
Installation on x86, AMD64, Intel 64, and Itanium 15
Page 28
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 Section 14.2, “Setting Up the
Server Holding the Installation Sources” (page 198).
If you have an SLP server, select SLP as the installation source in the rst boot screen.
During the boot procedure, select which of the available installation sources to use.
If the DVD is available in 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 14.4.2, “Using Custom Boot
Options” (page 219).
2.6 Controlling the Installation
Control the installation in one of several ways. The method most frequently used is to
install SUSE® Linux Enterprise Server from the computer console. Other options are
available for different situations. Find more information about the available installation
methods in Chapter 5, Deployment Strategies (page 79).
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 Chapter 6, Installation with YaST
(page 89).
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).
16 Deployment Guide
Page 29
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. De-
pending on the hardware, even the rmware 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 rst 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 prompt.
As soon as you are logged in to the installation system, launch the actual installation
with the command yast for a text-based installation or yast2 to proceed with the
graphical installation. This then guides you through the installation. This procedure is
described in detail in Section 14.1.5, “Simple Remote Installation via SSH—Dynamic
Network Conguration” (page 195).
Installation on x86, AMD64, Intel 64, and Itanium 17
Page 30
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 Sec-
tion 14.5.1, “VNC Installation” (page 222).
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 to 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 conguration les.
AutoYaST is extensively documented in Chapter 21, Automated Installation (page 285).
2.7 Dealing with Boot and Installation
Problems
Prior to delivery, SUSE® 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 rmware or BIOS so that the boot sequence is correct. To
do this, consult the manual for your hardware.
18 Deployment Guide
Page 31
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 pressing 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 Section 2.6, “Controlling the Installation” (page 16).
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.
Boot Disk
The boot disk is a useful interim solution if you have difculties conguring the
other possibilities or if you want to postpone the decision regarding the nal 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 8, 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 nd useful information:
• 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 rmware update xes this problem.
Installation on x86, AMD64, Intel 64, and Itanium 19
Page 32
• 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 rst 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.
20 Deployment Guide
Page 33
3
Installation on IBM POWER
This chapter describes the procedure for preparing the installation of SUSE® Linux
Enterprise Server on IBM POWER systems.
3.1 Requirements
3.1.1 Hardware Requirements
The SUSE® 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 conguration will work, nd out which
computers have been certied by SUSE. Find a list of these computers at http://
developer.novell.com/yessearch/Search.jsp.
pSeries and System p Models
These systems are operated with a PPC64 kernel.
Table 3.1
Supported Models
p615, p630, p650, p655, p670, p690pSeries models
Installation on IBM POWER 21
Page 34
505, 510, 520, 550, 560Q, 570, 570+, 575,
575+, 590, 595, 710, 720, 185
eServer p5, System p, OpenPower, and
ATX Server models
185ATX Workstation
All POWER3 and RS64–based models that were supported by SUSE Linux Enterprise
Server 9 are no longer supported.
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.
Up-to-date hardware information for Linux on System p is available by model from
http://www-03.ibm.com/systems/p/linux/.
BladeCenter
BladeCenter JS12, BladeCenter JS20, BladeCenter JS21, and BladeCenter JS22 are
supported systems.
3.1.2 Software Requirements
IBM pSeries, IBM eServer p5, System p, OpenPower
Find up-to-date rmware at http://www-912.ibm.com/eserver/support/
fixes/fixcentral. Select UNIX servers and Hardware microcode and rmware
to nd your system model. Updates for the Hardware Management Console can also
be selected from this page.
JSxx BladeCenter
Find up-to-date rmware for the BladeCenter at http://www-304.ibm.com/
systems/support/supportsite.wss/docdisplay?lndocid=
MIGR-63017&brandind=5000020 (Software and device drivers — IBM Blade-
Center).
22 Deployment Guide
Page 35
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 Section 3.2.1, “Preparing for Installation on IBM
eServer p5, System p, and OpenPower Models” (page 24)
• For IBM pSeries systems, see Section 3.2.2, “Preparing for Installation on IBM
pSeries Models” (page 30)
• For IBM JS20/JS21/JS22 Blades, see Section 3.2.3, “Preparing an Installation on
IBM JSxx BladeCenter” (page 34)
If SUSE® Linux Enterprise Server should be installed on a number of systems or partitions, it is recommended to create a network installation source. The same source can
also be used for the concurrent installation on several partitions or several systems. The
conguration of a network installation source is described in Section 14.2.1, “Setting
Up an Installation Server Using YaST” (page 198).
The installation can be controlled with a VNC client. For more information about VNC,
see Section 14.1.1, “Simple Remote Installation via VNC—Static Network Congura-
tion” (page 190).
To participate in the linuxppc-dev mailing list, sign up using the forms at
https://ozlabs.org/mailman/listinfo/linuxppc-dev. The following
links are interesting for the maintenance of an installation:
•
http://www.novell.com/suselinuxportal is an 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 http://www.novell.com/linux/security/
securitysupport.html. 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.
Installation on IBM POWER 23
Page 36
•
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® 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 congure the HMC in “Conguring the
HMC using the Guided Setup Wizard”: http://publib.boulder.ibm.com/
infocenter/systems/scope/hw/topic/iphai_p5/confighmcgs.htm
?
Modern Features of IBM eServer p5 Systems
IBM eServer p5 systems offer the possibility to partition 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, rst congure the system over
the HMC. Refer to the IBM documentation for details: http://publib.boulder
.ibm.com/infocenter/systems/scope/hw/topic/iphbi/
iphbikickoff.htm
Hard Disk Space
Make sure that you have sufcient hard disk space for installing SUSE Linux Enterprise
Server. The standard system requires at least 4 GB of free hard disk space.
24 Deployment Guide
Page 37
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—Properties
Procedure 3.1
Assigning a CD-ROM or DVD Drive to an LPAR
1
Open the HMC application and go to Server and Partition > Server Management.
2
From the available servers, expand the server and partition to install.
3
Right-click the prole to use for installation and select Properties—see Figure 3.1,
“HMC: Server Management—Properties” (page 25).
4
In the Logical Partition Prole Properties dialog, select the Physical I/O tab.
5
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” (page 26).
Installation on IBM POWER 25
Page 38
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
1
Open the HMC application and go to Server and Partition > Server Management.
2
From the available servers, open the server and partition to install.
3
Right-click the prole to use for installation and select Properties—see Figure 3.1,
“HMC: Server Management—Properties” (page 25).
4
In the Logical Partition Prole Properties dialog, select the Physical I/O tab.
5
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.
26 Deployment Guide
Page 39
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
conguration of the network installation source is described in Section 14.2.1, “Setting
Up an Installation Server Using YaST” (page 198).
Starting the Installation
To start the installation, reboot the system. Right-click the prole 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 rmware 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
memory keyboard network scsi speaker
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. 2000,2003 All rights reserved.
--------------------------------------------------------------------Main Menu
1. Select Language
2. Setup Remote IPL (Initial Program Load)
3. Change SCSI Settings
Installation on IBM POWER 27
Page 40
4. Select Console
5. Select Boot Options
---------------------------------------------------------------------
Navigation Keys:
X = eXit System Management Services
---------------------------------------------------------------------
Type the number of the menu item and press Enter or select Navigation
Key:5
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. 2000,2003 All rights reserved.
--------------------------------------------------------------------------
Select Device
Device Current Device
Number Position Name
1. - Virtual Ethernet
( loc=U9111.520.10D3CCC-V1-C3-T1 )
2. - Ethernet
( loc=U787A.001.DNZ00XG-P1-T5 )
3. - Ethernet
( loc=U787A.001.DNZ00XG-P1-T6 )
4. - IDE CD-ROM
( loc=U787A.001.DNZ00XG-P4-D3 )
5. 1 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:
Booting from the CD-ROM Drive
Select the CD-ROM drive (4 in this example):
SMS 1.5 (c) Copyright IBM Corp. 2000,2003 All rights reserved.
-------------------------------------------------------------------------Select Task
IDE CD-ROM
( loc=U787A.001.DNZ00XG-P4-D3 )
28 Deployment Guide
Page 41
1. Information
2. Normal Mode Boot
3. 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, conrm
with 1. Yes to exit System Management Services and boot from the device.
The system reads from the CD-ROM drive and the yaboot utility starts:
Welcome to SuSE:SLE-11:GA!
Type "install" to start the YaST installer on this CD/DVD
Type "slp" to start the YaST install via network
Type "rescue" 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
boot:
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 Section “Assigning an Installation Device to an
LPAR” (page 25)), append the option manual to the name of the kernel (install).
For an installation over VNC, append the parameters vnc=1 and
vncpassword=password to the name of the kernel (install). Read more about
VNC in Section 14.1.1, “Simple Remote Installation via VNC—Static Network Con-
guration” (page 190).
Booting from the Network Source
Select an ethernet device that has access to the installation source (2 in this example).
Installation on IBM POWER 29
Page 42
Additional Steps
Proceed as described in Chapter 6, Installation with YaST (page 89) 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® Linux Enterprise Server
on pSeries systems. It explains the installation from a built-in CD-ROM drive or a
network source.
Special Features of IBM pSeries p630, p655, p670, and
p690
IBM p630, p655, p670, and p690 systems offer the possibility to statically partition the
system similarly to eServer p5/System p5 (which is described in Section 3.2.1,
“Preparing for Installation on IBM eServer p5, System p, and OpenPower Models”
(page 24)). 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, rst congure the system over
the HMC. Refer to the Redbook IBM eServer pSeries 690 System Handbook (SG24-
7040-00) for details (http://www.redbooks.ibm.com/redbooks/
SG247040/).
Important notes regarding the conguration:
• 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.
30 Deployment Guide
Page 43
•
The HMC terminal used for the input during the installation is a VT320 emulation.
This emulation can lead to strange effects with some applications. If possible, use
an XTerm for communicating with the LPAR.
Hard Disk Space
Make sure that you have sufcient 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 congured to provide access from the FCHBA through the SAN
Fabric to target logical units (LUNs) on the storage system.
SAN storage devices, if properly congured, are listed among existing hard disks on
your system. Create Custom Partitioning Setup opens the dialog, as described in Sec-
tion 15.1, “Using the YaST Partitioner” (page 227).
For more information, see http://publib.boulder.ibm.com/infocenter/
eserver/v1r2s/en_US/index.htm?info/iphai/confighmcgs.htm.
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 prole. Create a network installation source if SUSE Linux Enterprise Server should 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 conguration of
the network installation source is described in Section 14.2.1, “Setting Up an Installation
Server Using YaST” (page 198).
Starting the Installation
To start the installation, reboot the system. Then enter the system rmware by pressing
F1 or 1 when using the serial console during the system check when the system is re-
booted. See Figure 3.3, “Entering the System Firmware” (page 32).
Installation on IBM POWER 31
Page 44
Figure 3.3
Entering the System Firmware
1 = SMS Menu 5 = Default Boot List
8 = Open Firmware Prompt 6 = Stored Boot List
memory keyboard network scsi speaker
Press F1 or 1 while the SCSI devices are checked. Select 6 MultiBoot to enter the
Multiboot dialog. See Figure 3.4, “Multiboot Dialog” (page 32)
Figure 3.4
Multiboot Dialog
Version M2P01113
(c) Copyright IBM Corp. 2000 All rights reserved.
------------------------------------------------------------------------
Multiboot
1 Select Software
2 Software Default
3 Select Install Device
4 Select Boot Devices
5 OK Prompt
6 Multiboot Startup <ON>
.------.
|X=Exit|
`------'
===>3
32 Deployment Guide
Page 45
Select 3 to set the install device. A list of available devices is displayed. See Figure 3.5,
“Installing the Operating System” (page 33).
Figure 3.5
Installing the Operating System
Install Operating System
Device Device
Number Name
1 Diskette
2 SCSI Tape id=0 ( slot=50322f5a )
3 SCSI CD-ROM id=1 ( slot=50322f5a )
4 Ethernet ( Integrated )
5 SysKonnect PCI FDDI Adapter ( slot=4 )
6 Ethernet ( slot=2 )
7 None
.------.
|X=Exit|
`------'
===>3
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.
->1 SuSE:SLE-11:GA<-
After you select 1, the yaboot utility is started.
Welcome to SuSE:SLE-11:GA!
Type "install" to start the YaST installer on this CD/DVD
Type "slp" to start the YaST install via network
Type "rescue" 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.
Installation on IBM POWER 33
Page 46
To install from a network source (see Section “Setting Up the Installation Source”
(page 31)), append 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 Section 14.1.1, “Simple Remote Installation via VNC—Static
Network Conguration” (page 190).
In LPAR mode, the partition to install must have the CD-ROM in its partition prole.
Booting from the Network Source
Select an ethernet device that has access to the installation source (6 in this example).
Additional Steps
Proceed as described in Chapter 6, Installation with YaST (page 89) to begin installing
the software with linuxrc and YaST.
3.2.3 Preparing an Installation on IBM JSxx
BladeCenter
This section describes the preparatory steps for the installation of SUSE® Linux Enterprise Server on JSxx Blades. It covers installation using the CD-ROM drive of the
BladeCenter and using the network.
Creating a Network Installation Source
Create a network installation source if SUSE Linux Enterprise Server should be installed
over a number of partitions. This provides the advantage that no CDs need to be changed
during installation. The same source can also be used for the concurrent installation of
various systems. Conguration of a network installation source is described in Sec-
tion 14.2.1, “Setting Up an Installation Server Using YaST” (page 198).
Hard Disk Storage Space
Ensure that enough hard disk storage space is available for the installation of SUSE
Linux Enterprise Server. It is recommended to use a dedicated hard disk.
34 Deployment Guide
Page 47
Notes and Information
Introductory Information:
•
JSxx Blades Site: https://www-304.ibm.com/systems/support/
supportsite.wss/brandmain?brandind=5000020
Preparing the System for Boot
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.
Then set up the CD-ROM drive as a boot device. Do this by selecting Blade Tasks then
Conguration while in the BladeCenter Management Module. Then select the JSxx
Blade in the section Boot Sequence. Set the entry for 1st Device on the page for Blade
Boot Sequence to CDROM.
Put CD 1 in the CD-ROM drive and restart the blade.
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 Conguration menu from the Blade
Tasks page. Then select the JSxx Blade in the section Boot Sequence and set 1st Boot
Device to Network — BOOTP on Blade Boot Sequence.
Installation on IBM POWER 35
Page 48
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: ********
system>
The command env -T system:blade[bay number] determines for which
JSxx Blade the subsequent commands are intended. The blades installed in the Blade-
Center are listed by calling list -l 3.
system> list -l 3
system
mm[1] primary
power[1]
power[2]
power[3]
power[4]
blower[1]
blower[2]
switch[1]
switch[3]
blade[1]
sp
cpu[1]
cpu[2]
blade[3]
sp
blade[4]
sp
blade[6]
sp
blade[8]
sp
cpu[1]
cpu[2]
blade[9]
sp
cpu[1]
cpu[2]
blade[10]
sp
36 Deployment Guide
Page 49
blade[11]
sp
blade[13]
sp
mt
system>
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 console.
system> env -T system:blade[9]
OK
system:blade[9]> console
Starting the Installation
The SUSE Linux Enterprise Server boot loader starts after the system check has completed.
Welcome to SuSE:SLE-11:GA!
Type "install" to start the YaST installer on this CD/DVD
Type "slp" to start the YaST install via network
Type "rescue" 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
boot:
Select install from the menu and press Enter.
In the case of an installation over VNC, append the parameters vnc=1 and
vncpassword=password to the command line for the kernel (install).
Additional Steps
Proceed as described in Chapter 6, Installation with YaST (page 89) to begin installing
the software with linuxrc and YaST.
Installation on IBM POWER 37
Page 50
Page 51
4
Installation on IBM System z
This chapter describes the procedure for preparing the installation of SUSE® Linux
Enterprise Server on IBM System z systems. It provides all information needed to
prepare the installation on the LPAR and z/VM side.
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 rst 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.
Hardware
SUSE Linux Enterprise Server has run successfully on the following platforms:
• IBM Series z9 (z9-EC) 2094
Installation on IBM System z 39
Page 52
• IBM Series z9 (z9-BC) 2096
• IBM Series z10 (z10-EC) 2097
• IBM Series z10 (z10-BC) 2098
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 using:
For installation under z/VM.768 MB
For installation under LPAR.1 GB
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.
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:
Default Installation2.6 GB
Recommended (this is with graphical desktop, development packages and java).
3.6 GB+
40 Deployment Guide
Page 53
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 cards:
• OSA Express Ethernet (including Fast and Gigabit Ethernet)
• HiperSockets or Guest LAN
• 10 GBE, VSWITCH
The following interfaces are still included, but no longer supported:
• CTC (or virtual CTC)
• ESCON
• IP network interface for IUCV
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 parmle, and the initrd. Thus, you
need access to a tape unit (3480, 3490, or 3590, for example).
MicroCode Level, APARs, and Fixes
This release of SUSE Linux Enterprise Server is based on the May 2008 codestream
from IBM developerWorks (http://www.ibm.com/developerworks/linux/
linux390/development_recommended.html). The restrictions and require-
ments listed at the Web site also apply for this release of SUSE Linux Enterprise
Server, except where stated differently in this manual. It is recommended always to use
the highest service level available. Contact your IBM support for minimum requirements.
Installation on IBM System z 41
Page 54
VM/ESA and z/VM
z/VM 5.2
z/VM 5.3
z/VM 5.4
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.
Software
To install SUSE Linux Enterprise Server via non-Linux–based NFS or FTP, you might
experience problems with NFS or FTP server software. Especially the Windows standard
FTP server can cause errors, so installing via SMB on these machines is generally recommended.
To connect to the SUSE Linux Enterprise Server installation system, one of the following
methods is required:
SSH 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 Macintosh.
Some of them can be downloaded as free trial versions. A trial version of the Mocha
X Server from MochaSoft can be obtained at http://www.mochasoft.dk/
freeware/x11.htm.
42 Deployment Guide
Page 55
TIP: Additional Information
Consult the README located in the highest directory of DVD 1 of your SUSE
Linux Enterprise Server before installing SUSE Linux Enterprise Server on IBM
System z. This le completes the documentation presented in this book.
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:
LPAR
Installation of SUSE Linux Enterprise Server using a logical partition (LPAR).
VM (z/VM)
Installation of SUSE Linux Enterprise Server as as a guest operating system within
z/VM.
Depending on the mode of installation (LPAR or VM), there are different possibilities
for starting the installation process and IPLing the installed system.
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 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.
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.
Installation on IBM System z 43
Page 56
4.1.3 IPL Options
This section provides the information needed to do an IPL for the rst installation.
Depending on the type of installation, different options need to be used. The channelattached 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.
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>.
VM Reader
To IPL from a VM reader, transfer the necessary les into the reader rst. Then multiple
IPLs are easily done. This is the preferred way on z/VM. For comfortable administration,
it is recommended to create a user linuxmnt that owns a minidisk with the les and
scripts needed for IPL. This minidisk is then accessed read-only by the Linux guests.
Load from CD/DVD-ROM or Server
For IPLing into an LPAR, it is possible to load directly from the SE's or the HMC's
CD/DVD-ROM device. It also allows you to IPL via FTP from a server holding the
SUSE Linux Enterprise Server for IBM System z les. Find this button near the LOAD
button (if you have upgraded to the latest MCL, see Section 4.1, “General Information
and Requirements” (page 39)).
This function can be performed from the HMC. Do this by accessing the Dened CPCs
icon in the Groups Work Area on the HMC desktop. From there, access the Dened
CPCs Work Area. Select a system image and initiate CPC Recovery. Use Single Object
Operations to access the service element remotely.
Access the service element's Groups Work Area. Select the LPAR to perform the load
from CD-ROM or server and initiate CPC recovery for that LPAR. Start Load from
44 Deployment Guide
Page 57
CD ROM or Server from the action menu. Provide information as requested on subsequent windows.
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
Section “IPL from FCP-Attached SCSI DVD” (page 54).
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
dened. The resources can be dedicated or shared among LPARs.
WARNING: Sharing Devices (DASD)
Do not share DASD writable among LPARs because this might result in data
loss. Consider the denition 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 specic LPAR. This LPAR is
referred to as LPAR1.
Example 4.1
Dedicating DASD to One LPAR
CHPID PATH=FD,TYPE=DSD,SHARED
CNTLUNIT CUNUMBR=FD00,PATH=FD,UNITADD=((00,256)),UNIT=3990-2
IODEVICE ADDRESS=(FD03,1),CUNUMBR=FD00,UNIT=3390,PART=LPAR1
To share a DASD among LPARs, delete the PART=LPAR1 part in the IOCDS denition.
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.
Installation on IBM System z 45
Page 58
Network cards like OSA-Express can be used in two different modes. These modes are
known as QDIO and non-QDIO mode. Dene these modes in the IOCDS by using the
TYPE statement. QDIO mode is much faster than non-QDIO mode, but uses three device
addresses instead of two in non-QDIO. Consider the limited number of device addresses
when planning the setup of your IBM System z Linux environment.
Example 4.2
Sharing OSA Express Card among LPARs (non-qdio) on z9
CHPID PATH=(FE),SHARED,PARTITION=((LPAR1,LPAR2)),TYPE=OSE
CNTLUNIT CUNUMBR=FE00,PATH=(FE),UNIT=OSA
IODEVICE ADDRESS=(FE00,016),CUNUMBR=(FE00),UNIT=OSA
IODEVICE ADDRESS=(FEFE,001),CUNUMBR=(FE00),UNIT=OSAD
Example 4.3
Sharing OSA Express Card among LPARs (qdio) on z9
CHPID PATH=(FE),SHARED,PARTITION=((LPAR1,LPAR2)),TYPE=OSD
CNTLUNIT CUNUMBER=FE00,PATH=(FE),UNIT=OSA
IODEVICE ADDRESS=(FE00,016),CUNUMBR=(FE00),UNIT=OSA
IODEVICE ADDRESS=(FEFE,001),CUNUMBR=(FE00),UNIT=OSAD
4.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 nd out about network conguration 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.
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
46 Deployment Guide
Page 59
conveniant if you have restrictions setting up an installation server providing
installation media over your network. The prerequisite is an FCP-attached SCSI
DVD Drive.
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 for x86,
you can set up an installation server (NFS or FTP) using the YaST Installation Server
module as described in Section 14.2.1, “Setting Up an Installation Server Using YaST”
(page 198).
Over NFS
Use NFS (network le system) to make the installation media available.
IMPORTANT: Exporting Mounted Devices with NFS
Exporting the le 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 le, restart the NFS server with the command
rcnfsserver restart.
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 conguration tasks.
Using YaST, the installation step is straightforward: select the package to install and
start the installation. Skip the conguration of the FTP server if no anonymous FTP
should be used for the installation. Instead, use FTP login with a valid username and
password. You might want to create a user account for this task only. The FTP daemon
itself 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.
Installation on IBM System z 47
Page 60
SUSE Linux Enterprise Server on DVD
DVD1 of the SUSE Linux Enterprise Server for IBM System z contains a bootable
Linux image for Intel-based workstations as well as an image for System z.
For Intel-based workstations, boot from this DVD, answer the questions regarding your
language and keyboard layout, and select 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 System z, IPL your LPAR/VM guest from this DVD as described in Section “IPL
from FCP-Attached SCSI DVD” (page 54). After entering your network parameters,
the installation system treats the DVD as the source of installation data. Because System
z cannot have an X11-capable terminal attached directly, choose between VNC or SSH
installation. SSH also provides a graphical installation by tunneling the X connection
through SSH with ssh -X.
Using a Microsoft Windows Workstation
If there is a Microsoft Windows workstation available in your network, use this computer to make the installation media available. The easiest way to do this is to use the
SMB protocol, already included in the Windows operating system. Be sure to activate
SMB over TCP/IP as this enables the encapsulation of SMB packages into TCP/IP
packages. Find details in the Windows online help or other Windows-related documentation that covers networking. Another option is to use FTP. This also requires some
third-party software for Windows.
With SMB
To make the installation media available with SMB, just insert the SUSE Linux Enterprise Server DVD 1 into the DVD drive of the Windows workstation. Then create a
new share using the DVD-ROM drive's letter and make it available for everyone in the
network.
TIP: SMB Installation Path for YaST
Consult the README from the highest directory of DVD 1 for detailed information about the syntax of the installation path for YaST.
48 Deployment Guide
Page 61
With NFS
Refer to the documentation provided with the third party product that enables NFS
server services for your Windows workstation. The DVD-ROM drive containing the
SUSE Linux Enterprise Server DVDs must be in the available NFS path.
With FTP
Refer to the documentation provided with the third party product that is enabling FTP
server services on your Windows workstation. The DVD-ROM drive containing the
SUSE Linux Enterprise Server DVDs must be in the available FTP path.
The FTP server that is part of some Microsoft Windows releases implements only a
subset of the FTP command set and is not suitable for providing the installation data.
However, other products, such as the FTP server that is part of Hummingbird Exceed
or WAR-FTPD, have been reported as functional.
Using an FCP-Attached SCSI DVD Drive
After you IPLed from the SCSI DVD as described in Section “Load from SCSI-Attached
DVD” (page 45), the installation system use the DVD as the installation medium. In
that case, you do not need the installation media on an FTP, NFS, or SMB server.
However, you need the network conguration data for your SUSE Linux Enterprise
Server, because you must set up the network during the installation to perform a
graphical installation by VNC or by X tunneled through SSH.
4.2.2 Installation Types
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 nd 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” (page 46),
there are two different installation modes for Linux on IBM System z:
• LPAR Installation
Installation on IBM System z 49
Page 62
• z/VM Installation
Procedure 4.1
Installation Overview of LPAR Installation
1
Prepare the devices needed for installation. See Section “LPAR Installation”
(page 51).
2
IPL the installation system. See Section “LPAR Installation” (page 54).
3
Congure the network. See Section 4.2.5, “Network Conguration” (page 59).
4
Connect to the SUSE Linux Enterprise Server installation system. See Sec-
tion 4.2.6, “Connecting to the SUSE Linux Enterprise Server Installation System”
(page 61).
5
Start installation using YaST and IPL the installed system. See Chapter 6, Instal-
lation with YaST (page 89).
Procedure 4.2
Installation Overview of z/VM Installation
1
Prepare the devices needed for installation. See Section “z/VM Installation”
(page 52).
2
IPL the installation system. See Section “z/VM Installation” (page 55).
3
Congure the network. See Section “z/VM Installation” (page 60).
4
Connect to the SUSE Linux Enterprise Server installation system. See Sec-
tion 4.2.6, “Connecting to the SUSE Linux Enterprise Server Installation System”
(page 61).
5
Start installation using YaST and IPL the installed system. See Chapter 6, Instal-
lation with YaST (page 89).
50 Deployment Guide
Page 63
4.2.3 Preparing the IPL of the SUSE Linux
Enterprise Server Installation System
LPAR Installation
Congure your IBM System z system to start in ESA/S390 or LINUX only mode with
an appropriate activation prole and IOCDS. Consult IBM documentation for more
about how to achieve this.
IOCDS: Attaching and Conguring Devices
A SUSE Linux Enterprise Server installation needs at least two devices: a DASD and
a network connection device. For an IPL from tape, a tape device should also be accessible. Devices are congured and attached to an LPAR in the IOCDS (input output
conguration data set). This example denes one DASD, one OSA-2 network device,
and a tape device for LPAR Z1. For further information about how to set up the IOCDS
for Linux, refer to IBM hardware documentation of your machine.
Example 4.4
An Example IOCDS
CHPID PATH=(CSS(0),FD),PCHID=120,TYPE=FC
CHPID PATH=(CSS(0),FE),PCHID=320,TYPE=OSD
CHPID PATH=(CSS(0),10),PCHID=3A0,TYPE=CNC
CNTLUNIT CUNUMBR=FD00,PATH=((CSS(0),FD)),UNITADD=((00,1)),UNIT=2105
IODEVICE ADDRESS=(FD00,1),CUNUMBR=(FD00),UNIT=3390B,UNITADD=00
CNTLUNIT CUNUMBR=FE20,PATH=((CSS(0),FE)),UNIT=OSA
IODEVICE ADDRESS=(FE20,1),CUNUMBR=(FE20),UNIT=OSA
IODEVICE ADDRESS=(FEFE,1),CUNUMBR=(FE20),UNIT=OSAD
CNTLUNIT CUNUMBR=100A,PATH=((CSS(0),10)),UNIT=3480,UNITADD=((0A,1))
IODEVICE ADDRESS=(100A,1),CUNUMBR=(100A),UNIT=3480,UNITADD=00
Proceed with Section “LPAR Installation” (page 54).
Installation on IBM System z 51
Page 64
z/VM Installation
Adding a Linux Guest
The rst step is to attach and format one or multiple DASDs in the system to be used
by the Linux guest in z/VM. Next, create a new user in z/VM. The example shows the
directory for a user LINUX1 with the password LINPWD, 256 MB of memory (extendable up to 1024 MB), 32 MB of expanded RAM (XSTORE), some minidisks (MDISK),
two CPUs and an OSA QDIO device.
TIP: Assigning Memory to z/VM guests
When assigning memory to a z/VM guest, make sure that the memory size suits
the needs of your preferred installation type. See Section “Memory Require-
ments” (page 40). To set the memory size to 512 MB, use the command CP
DEFINE STORAGE 512M. After the installation has nished, reset the memory
size to the desired value.
52 Deployment Guide
Page 65
Example 4.5
Conguration of a z/VM Directory
USER LINUX1 LINPWD 256M 1024M G
*____________________________________________
* LINUX1
*____________________________________________
* This VM Linux guest has two CPUs defined.
CPU 01 CPUID 111111
CPU 02 CPUID 111222
IPL CMS PARM AUTOCR
IUCV ANY
IUCV ALLOW
MACH ESA 10
OPTION MAINTCCW RMCHINFO
SHARE RELATIVE 2000
XSTORE 32M
CONSOLE 01C0 3270 A
SPOOL 000C 2540 READER *
SPOOL 000D 2540 PUNCH A
SPOOL 000E 3203 A
* OSA QDIO DEVICE DEFINITIONS
DEDICATE 9A0 9A0
DEDICATE 9A1 9A1
DEDICATE 9A2 9A2
*
LINK MAINT 0190 0190 RR
LINK MAINT 019E 019E RR
LINK MAINT 019D 019D RR
* MINIDISK DEFINITIONS
MDISK 201 3390 0001 0050 DASD40 MR ONE4ME TWO4ME THR4ME
MDISK 150 3390 0052 0200 DASD40 MR ONE4ME TWO4ME THR4ME
MDISK 151 3390 0253 2800 DASD40 MR ONE4ME TWO4ME THR4ME
This example uses minidisk 201 as the guest's home disk. Minidisk 150 with 200
cylinders is the Linux swap device. Disk 151 with 2800 cylinders holds the Linux installation.
Now add (as the user MAINT) the guest to the user directory with DIRM FOR LINUX1
ADD. Enter the name of the guest (LINUX1) and press F5. Set up the environment of
the user with:
DIRM DIRECT
DIRM USER WITHPASS
The last command returns a reader le number. This number is needed for the next
command:
RECEIVE <number> USER DIRECT A (REPL)
Installation on IBM System z 53
Page 66
Assign the directories to the guest with DISKMAP USER DIRECT A. You can now
log in on the guest as user LINUX1.
If you do not have the dirmaint option available, refer to the IBM documentation
to set up this user.
Proceed with Section “z/VM Installation” (page 55).
4.2.4 IPLing the SUSE Linux Enterprise
Server Installation System
LPAR Installation
There are different ways to IPL SUSE Linux Enterprise Server into an LPAR. The
preferred way is to use the Load from CD-ROM or server feature of the SE or HMC.
IPL from CD-ROM
Mark the LPAR to install and select Load from CD-ROM or server. Leave the eld for
the le location blank or enter the path to the root directory of the rst CD-ROM then
select continue. In the list of options that appears, choose the default selection. Operating
system messages should now show the kernel boot messages.
IPL from FCP-Attached SCSI DVD
You can use the Load procedure by selecting SCSI as Load type to IPL from SCSI.
Enter the WWPN (Worldwide port name) and LUN Logical unit number) provided by
your SCSI bridge or storage (16 digits—do not omit the trailing 0s). The boot program
selector must be 2. Use your FCP adapter as Load address and perform an IPL.
IPL from ESCON or FICON Attached Tape
If you cannot IPL from DVD, create a channel attached tape from which to IPL the
SUSE Linux Enterprise Server installation image. Use the LOAD button in the SE or
HMC with the tape device address as the load address to IPL the SUSE Linux Enterprise
Server installation system.
54 Deployment Guide
Page 67
There are many ways to create an IPLable tape. One is to copy the les:
/boot/s390x/tapeipl.ikr
/boot/s390x/parmfile
/boot/s390x/initrd
as binary les from DVD 1 (for example, using FTP from a Linux workstation).
Name them
SLES11 IMAGE
SLES11 PARM
SLES11 INITRD
and write them onto a tape with the REXX from the example.
IMPORTANT: Transferring Binaries using FTP
Do not upload the les as fixed 80. Store them as fixed 1024. Use the
FTP command locsite fix 1024.
Example 4.6
REXX Script to Create an IPLable Tape
'REWIND 181'
'FILEDEF IN1 DISK' SLES11 IMAGE A
'FILEDEF IN2 DISK' SLES11 PARM A
'FILEDEF IN3 DISK' SLES11 INITRD A
'FILEDEF OUT TAP1 (RECFM F BLOCK 1024 LRECL 1024 PERM'
say 'Writing: ' left(file1,23)
'MOVEFILE IN1 OUT'
say 'Writing: ' left(file2,23)
'MOVEFILE IN2 OUT'
say 'Writing: ' left(file3,23)
'MOVEFILE IN3 OUT'
say 'Done.'
'REWIND 181'
exit
The tape in this script is attached as 181. Adjust the script to your needs.
z/VM Installation
This section is about IPLing the installation system to install SUSE Linux Enterprise
Server for IBM System z on a z/VM system.
Installation on IBM System z 55
Page 68
IPL from the z/VM Reader
You need a working TCP/IP connection and an FTP client program within your newly
dened z/VM guest to transfer the installation system via FTP. Setting up TCP/IP for
z/VM is beyond the scope of this manual. Refer to the appropriate IBM documentation.
Log in as the z/VM Linux guest to IPL. Make the content of the directory /boot/
s390x on DVD 1 of the SUSE Linux Enterprise Server for IBM System z available
by FTP within your network. From this directory, get the les vmrdr.ikr, initrd,
parmfile, and sles11.exec. Transfer the les with a xed block size of 80
characters. Specify it with the FTP command locsite fix 80. It is important to
copy vmrdr.ikr (the Linux kernel) and initrd (the installation image) as binary
les, so use the binary transfer mode. parmfile and sles11.exec need to be
transferred in ASCII mode.
The example shows the steps necessary. In this example, the required les are accessible
from an FTP server at the IP address 192.168.0.3 and the login is lininst. It
may differ for your network.
56 Deployment Guide
Page 69
Example 4.7
Transferring the Binaries via FTP
FTP 192.168.0.3
VM TCP/IP FTP Level 530
Connecting to 192.168.0.3, port 21
220 ftpserver FTP server (Version wu-2.4.2-academ[BETA-18](1)
Fri Jan 30 14:58:32 GMT 2009) ready.
USER
lininst
331 Password required for lininst
PASS
******
230 User lininst logged in.
Command:
binary
200 Type set to I
Command:
locsite fix 80
Command:
get /media/dvd1/boot/s390x/vmrdr.ikr sles11.image
200 PORT Command successful
150 Opening BINARY mode data connection for /media/dvd1/boot/s390x/vmrdr.ikr
(6757376 bytes)
226 Transfer complete.
6757376 bytes transferred in 8.826 seconds.
Transfer rate 766.70 Kbytes/sec.
Command:
get /media/dvd1/boot/s390x/initrd sles11.initrd
200 PORT Command successful
150 Opening BINARY mode data connection for /media/dvd1/boot/s390x/initrd
(12654815 bytes)
226 Transfer complete.
12194534 bytes transferred in 16.520 seconds.
Transfer rate 766.70 Kbytes/sec.
Command:
ascii
200 Type set to A
Command:
get /media/dvd1/boot/s390x/parmfile sles11.parmfile
150 Opening ASCII mode data connection for /media/dvd1/boot/s390x/parmfile
(71 bytes)
226 Transfer complete.
71 bytes transferred in 0.092 seconds.
Transfer rate 0.71 Kbytes/sec.
Command:
get /media/dvd1/boot/s390x/sles11.exec sles11.exec
150 Opening ASCII mode data connection for /media/dvd1/boot/s390x/sles11.exec
(891 bytes)
226 Transfer complete.
891 bytes transferred in 0.097 seconds.
Transfer rate 0.89 Kbytes/sec.
Command:
quit
Installation on IBM System z 57
Page 70
Use the REXX script sles11.exec you just downloaded to IPL the Linux installation
system. This script loads the kernel, parmle, and the initial RAM disk into the reader
for IPL.
Example 4.8
SLES11 EXEC
/* REXX LOAD EXEC FOR SUSE LINUX S/390 VM GUESTS */
/* LOADS SUSE LINUX S/390 FILES INTO READER */
SAY ''
SAY 'LOADING SLES11 FILES INTO READER...'
'CP CLOSE RDR'
'PURGE RDR ALL'
'SPOOL PUNCH * RDR'
'PUNCH SLES11 IMAGE A (NOH'
'PUNCH SLES11 PARMFILE A (NOH'
'PUNCH SLES11 INITRD A (NOH'
'I 00C'
With this script you can IPL the SUSE Linux Enterprise Server installation system with
the command sles11. The Linux kernel then starts and prints its boot messages.
To continue the installation, proceed with Section “z/VM Installation” (page 60).
IPL from FCP-Attached SCSI DVD
To IPL in z/VM, prepare the SCSI IPL process by using the SET LOADDEV parameter:
SET LOADDEV PORTNAME 200400E8 00D74E00 LUN 00020000 00000000 BOOT 2
After setting the LOADDEV parameter with the appropriate values, IPL your FCP
adapter, for example:
IPL FC00
To continue the installation, proceed with Section “z/VM Installation” (page 60).
IPL from ESCON or FICON Attached tape
If you cannot IPL from a z/VM reader, create a channel attached tape from which to
IPL the SUSE Linux Enterprise Server installation image. For instructions, refer to
Section “IPL from ESCON or FICON Attached Tape” (page 54).
To continue the installation, proceed with Section “z/VM Installation” (page 60).
58 Deployment Guide
Page 71
4.2.5 Network Conguration
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 or System 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 installing over. Section 4.2.1,
“Making the Installation Data Available” (page 46) describes how to make the instal-
lation data available for the various types of network connections. Currently, FTP,
HTTP, NFS, and SMB/CIFS (Windows le sharing) are supported.
Now set up the network device over which to receive the installation data: OSA-2 or
OSA Express or HiperSockets. The following network adapters are still available and
usable, but no longer supported: CTC, ESCON, IUCV. Next, choose the CCW bus interface and the physical medium (Ethernet). As a result, the respective driver is installed
and you see the corresponding kernel messages.
Proceeding with the installation, linuxrc displays a list of potential usable read, write,
and, if applicable, data channels. After entering the addresses for each channel, you
may also need to enter additional information, such as the port name for OSA ethernet
cards.
Next, decide whether to use DHCP autoconguration for setting up the network interface
parameters. Because DHCP only works on a few devices and requires special hardware
conguration settings, you probably want to say NO here. When you do so, you are
prompted for the networking parameters of your installation network device:
• The IP address of the system to install
• The corresponding netmask
• The IP address of a gateway to reach the server
• The IP address of your domain name server (DNS)
When using an OSA Express Network Card you are now prompted for a relative port
number. This was added to support the new 2 port OSA Express 3 Network devices. If
you are not using an OSA Express 3 device, please enter 0. OSA Express cards also
have the option of running in an “OSI layer 2 support” mode or using the older more
Installation on IBM System z 59
Page 72
common “layer 3” mode. The card mode affects all systems that share the device including systems on other LPARs. If in doubt, please specify 2 for compatibility with the
default mode used by other operating systems such as z/VM and z/OS. Consult with
your hardware administrator for further information on these options.
z/VM Installation
After the kernel has completed its start-up routines, answer a few questions regarding
the network setup. First, select the type of network connection to use: OSA Express or
HiperSockets. In this example installation, OSA Express is used.
The system now displays a possible OSA conguration. Choose rst whether to use
QDIO or LCS OSA. Next, choose the physical medium to use and enter the device addresses. If you prefer another setup, enter the device address of the OSA read channel
(0.0.0700 in this example) then the one of the OSA write channel (0.0.0701) and the
OSA control channel (0.0.0702). After entering the channels, insert the name of the
port to which the OSA card is connected.
SUSE Linux Enterprise Server now tries to load the network module by building a parameter line with the information provided then displays all loaded modules. Loading
was successful if you get an output like:
Example 4.9
Network Device Driver Parameters
qeth: Device 0.0.0700/0.0.0701/0.0.0702 is a Guest LAN QDIO card (level: V448)
with link type GuestLAN QDIO (portname: VSW1)
qeth: Hardware IP fragmentation not supported on eth0
qeth: VLAN enabled
qeth: Multicast enabled
qeth: IPV6 enabled
qeth: Broadcast enabled
qeth: Could not set up broadcast echo filtering on eth0: 0x2
qeth: Using SW checksumming on eth0.
qeth: Outbound TSO not supported on eth0
Next, enter your IP address, netmask, and default gateway. To install over iucv or ctc,
enter additional information, like the the peer address (for a point-to-point adapter) or
the port name.
Finally, the IP address of the DNS server and the MTU size are requested. The MTU
size should always match the one used by the network to which to connect.
60 Deployment Guide
Page 73
Now a summary is displayed. Conrm whether your input is correct. Before the network
is started, enter a password that is valid only during the installation. After having IPLed
the installed system, enter the real root password.
With all basic parameters set up, the network is started. Check the output of ifcong,
which should contain two entries: a loopback (lo) connection and one connection (eth0,
ctc0, escon0, iucv0, or hsi0) with correct settings.
Example 4.10
Example ifcong
/sbin/ifconfig eth0 :
Link encap:Ethernet HWaddr 02:00:01:00:00:27
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::200:100:100:27/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 Mb) TX bytes:0 (0.0 Mb)
4.2.6 Connecting to the SUSE Linux
Enterprise Server Installation System
After setting up your network connection, linuxrc prompts for the details of the installation source chosen earlier in the process, for example, the server IP address and the
directory in which the data is located.
Finally, linuxrc wants to know what type of display you want to use to control the installation procedure. Possible choices are X11 (X Window System), VNC (Virtual
Network Computing protocol), and SSH (text mode or X11 installation via Secure
Shell).
Initiating the Installation for VNC
1
After the installation option VNC has been chosen, the VNC server starts. A short
note displayed in the console provides information about which IP address and
display number is needed for a connection with vncviewer. Alternatively, a URL
is given here for entry into your Java-enabled browser to connect to the installation
system.
Installation on IBM System z 61
Page 74
2
Start a VNC client application on your client system. Either use vncviewer or
the VNC Java client and a Java-enabled Web browser.
3
Enter the IP address and the display number of the SUSE Linux Enterprise
Server installation system when prompted to do so.
If you connect via a Java-enabled browser, enter a URL containing the IP address
of the installation system and the appropriate port number in the format:
http://<IP address of installation system>:5801/
4
After the connection has been established, start installing SUSE Linux Enterprise
Server with YaST.
Initiating the Installation for the X Window System
IMPORTANT: X Authentication Mechanism
The direct installation with the X Window System relies on a primitive authentication mechanism based on hostnames. This mechanism is disabled on current
SUSE Linux Enterprise Server versions. Installation with SSH or VNC is preferred.
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 le
/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.
62 Deployment Guide
Page 75
Initiating the Installation for SSH
To connect to an installation system with the name earth using SSH, execute ssh -X
earth. If your workstation runs on Microsoft Windows, use the ssh and telnet client
and terminal emulator putty, which is available from http://www.chiark
.greenend.org.uk/~sgtatham/putty/. Set Enable X11 forwarding in putty
under Connection > SSH > X11.
A login prompt appears. Enter root and log in with your password. Then enter yast2
to start YaST.
Proceed with the detailed description of the installation procedure that can be found in
Chapter 6, Installation with YaST (page 89).
4.3 Network Connection Types
SUSE Linux Enterprise Server for IBM System z includes network drivers for OSA
devices (ethernet, and gigabit ethernet) and HiperSockets. This chapter describes the
conguration within the SUSE Linux Enterprise Server installation system.
WARNING: CTC, ESCON, and IUCV Interfaces No Longer Supported
CTC, ESCON, and IUCV interfaces are no longer ofcially supported. For compatibility reasons, they are still usable, but with the next release of SUSE Linux
Enterprise Server the support of these interfaces will be dropped completely.
4.3.1 HiperSockets
Select your device from the list of network devices. Then enter the network device read
channel number (such as 0.0.700), the write channel number (like 0.0.701) and the data
channel number (like 0.0.702).
Installation on IBM System z 63
Page 76
Example 4.11
Supported Network Connection Types and Driver Parameters
Choose the network device.
1) IBM parallel CTC Adapter (0.0.0600)
2) IBM parallel CTC Adapter (0.0.0602)
3) IBM parallel CTC Adapter (0.0.0604)
4) IBM Hipersocket (0.0.0700)
5) IBM Hipersocket (0.0.0701)
6) IBM Hipersocket (0.0.0702)
7) IBM OSA Express Network card (0.0.050c)
8) IBM OSA Express Network card (0.0.050d)
9) IBM OSA Express Network card (0.0.050e)
10) IBM OSA Express Network card (0.0.f401)
11) IBM OSA Express Network card (0.0.f400)
12) IBM OSA Express Network card (0.0.f402)
13) IBM IUCV
> 4
Device address for read channel [0.0.700]
>[0.0.700]
Device address for write channel
> 0.0.701
Device address for data channel
> 0.0.702
Next, choose manual conguration then enter the IP address, netmask, broadcast address,
IP address of the gateway, and the searchlist of the DNS server.
64 Deployment Guide
Page 77
Example 4.12
Network Device Name
Automatic configuration via DHCP?
1) Yes
2) No
> 2
Enter your IP address
> 192.168.0.20
Enter your netmask. For a normal class C network, this is usually
255.255.255.0 [255.255.255.0]
> 255.255.255.0
Enter the IP address of the gateway. Leave empty if you don't need one
> 192.168.0.1
Enter your search domains, separated by a space:
> example.com
4.3.2 Gigabit Ethernet with the qeth Module
Select an IBM OSA Express Network card from the list of network devices,
and then 1 for ethernet. When prompted, enter the network device's read, write, and
data channel numbers (for example, 0.0.0600, 0.0.0601, and 0.0.0602) and
the port name, if applicable. Choose whether to enable OSI Layer 2 support.
Installation on IBM System z 65
Page 78
Example 4.13
Network Device Driver Parameters
Detecting and loading network drivers
netiucv.8db02b: driver initialized
Choose the network device.
1) IBM OSA Express Network card (0.0.09a0)
2) IBM OSA Express Network card (0.0.09a1)
3) IBM OSA Express Network card (0.0.09a2)
4) IBM OSA Express Network card (0.0.0600)
5) IBM OSA Express Network card (0.0.0601)
6) IBM OSA Express Network card (0.0.0602)
7) IBM IUCV
>
4
Please choose the physical medium.
1) Ethernet
2) Token Ring
>
1
Enter the relative port number
>
0
Device address for read channel
[0.0.0600]>
0.0.0600
Device address for write channel
>
0.0.0601
Device address for data channel
>
0.0.0602
Portname to use
>
DT70
Enable OSI Layer 2 support?
1) Yes
2) No
>
2
Next, enter the full hostname. Then choose manual conguration and enter the IP address, netmask, broadcast address, IP address of the gateway, and IP address of the
DNS server.
66 Deployment Guide
Page 79
Example 4.14
Network Device Name
Fully qualified hostname> earth.cosmos.com
Automatic configuration via DHCP?
1) Yes
2) No
> 2
Enter your IP address> 192.168.0.20
Enter your netmask. For a normal class C network, this is usually
255.255.255.0 [255.255.255.0]> 255.255.255.0
If you need a gateway to reach the server, enter the IP address of the
gateway. If you do not need a gateway, enter your own IP address
[192.168.0.20]> 192.168.0.1
Enter the IP address of your name server. Leave empty or enter "+++" if you
don't need one
>
4.4 The parmle—Automating the
System Conguration
The installation process can be partly automated by specifying the crucial parameters
in the parmfile. The parmfile contains all the data required for network setup
and DASD conguration. In addition to that, it can be used to set up the connection
method to the SUSE Linux Enterprise Server installation system and the YaST instance
running there. User interaction is thus limited to the actual YaST installation controlled
by YaST dialogs.
The following parameters can be passed to the installation routine, which takes them
as default values for installation. All IP addresses, server names, and numerical values
are just examples. Replace these values with the ones needed in your installation scenario.
The number of lines in the parmle is limited to 10. Specify more than one parameter
on a line. Parameter names are not case-sensitive. Separate the parameters by spaces.
You may specify the parameters in any order. Always keep the PARAMETER=value
string together in one line. For example:
Installation on IBM System z 67
Page 80
Hostname=s390zvm01.suse.de HostIP=10.11.134.65
TIP: Using IPv6 during the Installation
By default you can only assign IPv4 network addresses to your machine. To
enable IPv6 during installation, enter one of the following parameters at the
bootprompt: ipv6=1 (accept IPv4 and IPv6) or ipv6only=1 (accept IPv6
only).
Some of the following parameters are required. If they are missing, the automatic process
pauses and asks for the value interactively.
4.4.1 General Parameters
AutoYaST=<URL> Manual=0
The AutoYaST parameter species the location of the autoinst.xml control
le for automatic installation. The Manual parameter controls whether the other
parameters are only default values that still must be acknowledged by the user. Set
this parameter to 0 if all values should be accepted and no questions asked. Setting
AutoYaST implies setting Manual to 0.
Info=<URL>
Species a location for a le to read more options from. Useful to overcome the
limitations of 10 lines (and 80 characters per line under z/VM) for the parmle.
More documentation on the Info le can be found in Section 21.1.5, “Creating the
info File” (page 293). Since the Info le can typically only be accessed through
the network on System z, you cannot use it to specify options required to setup the
network, i.e. options described in Section 4.4.2, “Conguring the Network Interface”
(page 69). Also other linuxrc specic options such as for debugging have to be
specied in the parmle to be effective.
TIP: Creating a File with Autoinstallation Information
At the very end of the installation of a system you can check Clone This System
for Autoyast. This creates a ready-to-use prole as /root/autoinst.xml
that can be used to create clones of this particular installation. To create an
autoinstallation le from scratch or to edit an existing one, use the YaST module
68 Deployment Guide
Page 81
Autoinstallation. For more information about AutoYaST, refer to Chapter 21,
Automated Installation (page 285).
4.4.2 Conguring the Network Interface
IMPORTANT: Conguring the Network Interface
All settings discussed here only apply to the network interface used during installation. Congure additional network interfaces in the installed system by
following the instructions given in Section “Conguring a Network Connection
Manually” (Chapter 17, Basic Networking, ↑Administration Guide).
Hostname=zseries.example.com
Enter the fully qualied hostname.
Domain=example.com
Domain search path for DNS. Allows you to use short host names instead of fully
qualied ones.
HostIP=192.168.1.2
Enter the IP address of the interface to congure.
Gateway=192.168.1.3
Specify the gateway to use.
Nameserver=192.168.1.4
Specify the DNS server in charge.
InstNetDev=osa
Enter the type of interface to congure. Possible values are osa, hsi. ctc, escon,
and iucv. (CTC, ESCON, and IUCV are no longer ofcially supported).
For the interfaces of type hsi and osa, specify an appropriate netmask and an
optional broadcast address:
Netmask=255.255.255.0
Broadcast=192.168.255.255
For the interfaces of type ctc, escon, and iucv (CTC, ESCON, and IUCV are
no longer ofcially supported), enter the IP address of the peer:
Installation on IBM System z 69
Page 82
Pointopoint=192.168.55.20
OsaInterface=<lcs|qdio> OsaMedium=<eth|tr>
For osa network devices, specify the host interface (qdio or lcs) and the physical medium (eth for ethernet or tr for token ring).
Layer2=<0|1>
For osa QDIO ethernet devices, specify whether to enable OSI Layer 2 support.
PortNo=<0|1>
For osa network devices, specify the port number (provided the device supports
this feature). If not specied, it defaults to 0.
Each of the interfaces requires certain setup options:
•
Interfaces ctc and escon (CTC and ESCON are no longer ofcially supported):
ReadChannel=0.0.0424
WriteChannel=0.0.0425
ReadChannel species the READ channel to use. WriteChannel is the
WRITE channel.
•
For the ctc interface (no longer ofcially supported), specify the protocol that
should be used for this interface:
CTCProtocol=<0/1/2>
Valid entries would be:
Compatibility mode, also for non-Linux peers other than
OS/390 and z/OS (this is the default mode)
0
Extended mode
1
Compatibility mode with OS/390 and z/OS
2
•
Network device type osa with interface lcs:
ReadChannel=0.0.0124
Portname=1
70 Deployment Guide
Page 83
ReadChannel stands for the channel number used in this setup. A second port
number can be derived from this by adding one to ReadChannel. Portnumber
is used to specify the relative port.
•
Interface iucv:
IUCVPeer=PARTNER
Enter the name of the peer machine.
•
Network device type osa with interface qdio for OSA-Express Gigabit Ethernet
and OSA-Express High-speed Token Ring:
ReadChannel=0.0.0524
WriteChannel=0.0.0525
DataChannel=0.0.0526
Portname=FEF400
For ReadChannel, enter the number of the READ channel. For WriteChannel,
enter the number of the WRITE channel. DataChannel species the DATA
channel. For Portname, enter an appropriate port name. Make sure that the READ
channel carries an even device number.
•
Interface hsi for HiperSockets and VM guest LANs:
ReadChannel=0.0.0624
WriteChannel=0.0.0625
DataChannel=0.0.0626
For ReadChannel, enter the appropriate number for the READ channel. For
WriteChannel and DataChannel, enter the WRITE and DATA channel
numbers.
4.4.3 Specifying the Installation Source and
YaST Interface
Install=nfs://server/directory/DVD1/
Specify the location of the installation source to use. Possible protocols are nfs,
smb (Samba/CIFS), ftp, and http.
Installation on IBM System z 71
Page 84
If an ftp or smb URL is given, specify the username and password with the URL.
These parameters are optional and anonymous or guest login is assumed if they
are not given.
Install=ftp://user:password@server/directory/DVD1/
In case of a Samba or CIFS installation, you can also specify the domain that should
be used:
Install=smb://workdomain;user:password@server/directory/DVD1/
UseSSH=1 UseVNC=1 Display_IP=192.168.42.42
Depending on which parameter you give, a remote X server, SSH, or VNC will be
used for installation. UseSSH enables SSH installation, UseVNC starts a VNC
server on the installing machine, and Display_IP causes the installing system
to try to connect to an X server at the given address. Only one of these parameters
should be set at any time.
IMPORTANT: X Authentication Mechanism
The direct installation with the X Window System relies on a primitive authentication mechanism based on hostnames. This mechanism is disabled
on current SUSE Linux Enterprise Server versions. Installation with SSH or
VNC is preferred.
To allow a connection between YaST and the remote X server, run xhost <IP
address> with the address of the installing machine on the remote machine.
For VNC, specify a password of six to eight characters to use for installation:
VNCPassword=<a password>
For SSH, specify a password of six to eight characters to use for installation:
SSHPassword=<a password>
4.4.4 Example Parmles
For an automatic installation with AutoYaST in an LPAR, it is preferred that the
parmle has just one long line. If multiple lines are desired for readability, use blank
characters at the beginning and end of each line. The maximum number of lines in a
parmle is 10.
72 Deployment Guide
Page 85
To receive potential error messages on the console, use
linuxrclog=/dev/console
Example 4.15
Parmle for Installation with NFS, VNC, and IUCV and AutoYaST
with HTTP
ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb
instnetdev=iucv iucvpeer=ROUTER01 pointopoint=192.168.0.1
hostip=192.168.0.2
nameserver=192.168.0.3
install=nfs://192.168.0.4/SLES/SLES-11-s390x/DVD1
autoyast=http://192.168.0.5/autoinst.xml
linuxrclog=/dev/console usevnc=1
vncpassword=testin
Example 4.16
Parmle for Installation with NFS, SSH, and HSI and AutoYaST with
NFS
ramdisk_size=131072 root=/dev/ram1 ro init=/linuxrc TERM=dumb
AutoYast=nfs://192.168.1.1/autoinst/s390.xml
Hostname=zseries.example.com HostIP=192.168.1.2
Gateway=192.168.1.3 Nameserver=192.168.1.4
InstNetDev=hsi layer2=0
Netmask=255.255.255.128 Broadcast=192.168.1.255
readchannel=0.0.702c writechannel=0.0.702d datachannel=0.0.702e
install=nfs://192.168.1.5/SLES-11-s390x/DVD1/
UseSSH=1 SSHPassword=testing linuxrclog=/dev/console
4.5 Using the vt220 Terminal
Emulator
Recent MicroCode Levels allow the use of an integrated vt220 terminal emulator in
addition to the standard line mode terminal. The vt220 terminal is connected to /dev/
ttyS1. The line mode terminal is connected to /dev/ttyS0. If the vt220 emulation
is available, an icon for an integrated vt220 ASCII console appears next to the icon for
the 3215 console on the HMC/SE.
To activate vt220 support on your machine, edit /etc/inittab as user root. Look
for the following line and delete the leading # sign:
#2:2345:respawn:/sbin/mingetty --noclear /dev/ttyS1 xterm
Installation on IBM System z 73
Page 86
Save the le and run telinit q to pass the changes in /etc/inittab to init. The
vt220 terminal should then be ready to use. If not, try hitting Enter at the terminal until
the login prompt appears.
Make sure that you do not apply the changes as described above to a system that does
not support vt220 terminal emulators. Otherwise, login might become impossible on
this system and you will be shown the following message:
INIT respawning too fast, disabled for 5 minutes.
To redirect the kernel messages at boot time from the system console to the vt220 terminal, add the following entries to the parameters line in /etc/zipl.conf:
console=ttyS0 console=ttyS1
The resulting parameters line would look like the following example:
parameters = "root=/dev/dasda2 TERM=dumb console=ttyS0 console=ttyS1"
Save the changes in /etc/zipl.conf, run zipl, and reboot the system.
4.6 Further In-Depth Information
about IBM System z
IBM has published a number of very interesting documents about their System z platform. Find them either on the Internet (http://www.redbooks.ibm.com) or in
your installed system (package redbook) under /usr/share/doc/packages/
redbook.
4.6.1 IBM System z with SUSE Linux
Enterprise Server
Find additional in-depth technical documentation about the kernel and application topics
on IBM System z with SUSE Linux Enterprise Server at the following location:
•
http://www.ibm.com/developerworks/linux/linux390/
documentation_novell_suse.html
74 Deployment Guide
Page 87
4.6.2 Hardware
For a rst glance at the technical details of some systems, refer to:
• IBM System z10 Enterprise Class Technical Introduction (SG24-7515)
• IBM System z9 Business Class Technical Introduction (SG24-7241)
• IBM eServer zSeries 990 Technical Introduction (SG24-6863)
• IBM eServer zSeries 900: Technical Guide (SG24-5975)
• Linux on zSeries Fibre Channel Protocol Implementation Guide (SG24-6344)
4.6.3 General Documents about Linux on
IBM System z
A general coverage of Linux on IBM System z can be found in the following documents:
• Linux on IBM eServer zSeries and S/390: ISP and ASP Solutions (SG24-6299)
These documents might not reect the current state of Linux, but the principles of
Linux deployment outlined there remain accurate.
4.6.4 Technical Issues of Linux on IBM
System z
Refer to the following documents to get in-depth technical information about Linux
kernel and application topics. Refer to the Internet for up-to-date versions of these
documents for the most recent code drop (http://www.ibm.com/
developerworks/linux/linux390/index.html).
• Linux for zSeries and S/390: Device Drivers, Features, and Commands
• zSeries ELF Application Binary Interface Supplement
• Linux for zSeries and S/390: Using the Dump Tools
Installation on IBM System z 75
Page 88
• IBM System z9-109 Technical Introduction (SG26-6669)
• IBM System z10 Enterprise Class Technical Guide (SG24-7516)
There also is a Redbook for Linux application development on http://www
.redbooks.ibm.com:
• Linux on IBM eServer zSeries and S/390: Application Development (SG24-6807)
4.6.5 Advanced Congurations for Linux on
IBM System z
Refer to the following Redbooks, Redpapers, and links for some more complex IBM
System z scenarios:
• Linux on IBM eServer zSeries and S/390: Large Scale Deployment (SG24-6824)
• Linux on IBM eServer zSeries and S/390: Performance Measuring and Tuning
(SG24-6926)
• Linux with zSeries and ESS: Essentials (SG24-7025)
• IBM TotalStorage Enterprise Storage Server Implementing ESS Copy Services
with IBM eServer zSeries (SG24-5680)
• Linux on IBM zSeries and S/390: High Availability for z/VM and Linux (REDP-
0220)
• Saved Segments Planning and Administration
http://publibz.boulder.ibm.com/epubs/pdf/hcsg4a00.pdf
• Linux on System z documentation for "Development stream"
http://www.ibm.com/developerworks/linux/linux390/
development_documentation.html
76 Deployment Guide
Page 89
Part II. Manual Deployment
Page 90
Page 91
5
Deployment Strategies
There are several different ways to deploy SUSE Linux Enterprise Server. Choose from
various approaches ranging from a local installation using physical media or a network
installation server to a mass deployment using a remote-controlled, highly-customized,
and automated installation technique. Select the method that best matches your requirements.
5.1 Deploying up to 10 Workstations
If your deployment of SUSE Linux Enterprise Server only involves 1 to 10 workstations,
the easiest and least complex way of deploying SUSE Linux Enterprise Server is a plain
manual installation as featured in Chapter 6, Installation with YaST (page 89). Manual
installation can be done in several different ways depending on your requirements:
Installing from the SUSE Linux Enterprise Server Media (page 80)
Consider this approach if you want to install a single, disconnected workstation.
Installing from a Network Server Using SLP (page 80)
Consider this approach if you have a single workstation or a small number of
workstations and if a network installation server announced via SLP is available.
Installing from a Network Server (page 81)
Consider this approach if you have a single workstation or a small number of
workstations and if a network installation server is available.
Deployment Strategies 79
Page 92
Table 5.1
Installing from the SUSE Linux Enterprise Server Media
SUSE Linux Enterprise Server media kitInstallation Source
Tasks Requiring Manual Interaction
• Inserting the installation media
• Booting the installation target
• Changing media
• Determining the YaST installation scope
• Conguring the system with YaST system
NoneRemotely Controlled Tasks
Installing from the SUSE Linux Enterprise Server
Media (page 89)
Details
Table 5.2
Installing from a Network Server Using SLP
Network installation server holding the SUSE Linux
Enterprise Server installation media
Installation Source
Tasks Requiring Manual
Interaction
• Inserting the boot disk
• Booting installation target
• Determining the YaST installation scope
• Conguring the system with YaST
None, but this method can be combined with VNCRemotely Controlled Tasks
Section 6.1.1, “Installing from a Network Server Using
SLP” (page 91)
Details
80 Deployment Guide
Page 93
Table 5.3
Installing from a Network Server
Network installation server holding the SUSE Linux
Enterprise Server installation media
Installation Source
Tasks Requiring Manual
Interaction
• Inserting the boot disk
• Providing boot options
• Booting the installation target
• Determining the YaST installation scope
• Conguring the system with YaST
None, but method can be combined with VNCRemotely Controlled Tasks
Section 6.1.2, “Installing from a Network Source without SLP” (page 91)
Details
5.2 Deploying up to 100 Workstations
With a growing numbers of workstations to install, you certainly do not want to install
and congure each one of them manually. There are many automated or semiautomated
approaches as well as several options to perform an installation with minimal to no
physical user interaction.
Before considering a fully-automated approach, take into account that the more complex
the scenario gets the longer it takes to set up. If a time limit is associated with your deployment, it might be a good idea to select a less complex approach that can be carried
out much more quickly. Automation makes sense for huge deployments and those that
need to be carried out remotely.
Choose from the following options:
Simple Remote Installation via VNC—Static Network Conguration (page 83)
Consider this approach in a small to medium scenario with a static network setup.
A network, network installation server, and VNC viewer application are required.
Deployment Strategies 81
Page 94
Simple Remote Installation via VNC—Dynamic Network Conguration (page 83)
Consider this approach in a small to medium scenario with dynamic network setup
through DHCP. A network, network installation server, and VNC viewer application
are required.
Remote Installation via VNC—PXE Boot and Wake on LAN (page 84)
Consider this approach in a small to medium scenario that should be installed via
network and without physical interaction with the installation targets. A network,
a network installation server, network boot images, network bootable target hardware, and a VNC viewer application are required.
Simple Remote Installation via SSH—Static Network Conguration (page 84)
Consider this approach in a small to medium scenario with static network setup.
A network, network installation server, and SSH client application are required.
Remote Installation via SSH—Dynamic Network Conguration (page 85)
Consider this approach in a small to medium scenario with dynamic network setup
through DHCP. A network, network installation server, and SSH client application
are required.
Remote Installation via SSH—PXE Boot and Wake on LAN (page 85)
Consider this approach in a small to medium scenario that should be installed via
network and without physical interaction with the installation targets. A network,
a network installation server, network boot images, network bootable target hardware, and an SSH client application are required.
Simple Mass Installation (page 86)
Consider this approach for large deployments to identical machines. If congured
to use network booting, physical interaction with the target systems is not needed
at all. A network, a network installation server, a remote controlling application
such as a VNC viewer or an SSH client, and an AutoYaST conguration prole
are required. If using network boot, a network boot image and network bootable
hardware are required as well.
Rule-Based Autoinstallation (page 87)
Consider this approach for large deployments to various types of hardware. If
congured to use network booting, physical interaction with the target systems is
not needed at all. A network, a network installation server, a remote controlling
application such as a VNC viewer or an SSH client, and several AutoYaST conguration proles as well as a rule setup for AutoYaST are required. If using network
boot, a network boot image and network bootable hardware are required as well.
82 Deployment Guide
Page 95
Table 5.4
Simple Remote Installation via VNC—Static Network Conguration
NetworkInstallation Source
Preparations • Setting up an installation source
• Booting from the installation media
Remote: VNCControl and Monitoring
small to medium scenarios with varying hardwareBest Suited For
Drawbacks • Each machine must be set up individually
• Physical access is needed for booting
Section 14.1.1, “Simple Remote Installation via
VNC—Static Network Conguration” (page 190)
Details
Table 5.5
Simple Remote Installation via VNC—Dynamic Network Conguration
NetworkInstallation Source
Preparations • Setting up the installation source
• Booting from the installation media
Remote: VNCControl and Monitoring
Small to medium scenarios with varying hardwareBest Suited For
Drawbacks • Each machine must be set up individually
• Physical access is needed for booting
Deployment Strategies 83
Page 96
Section 14.1.2, “Simple Remote Installation via
VNC—Dynamic Network Conguration” (page 191)
Details
Table 5.6
Remote Installation via VNC—PXE Boot and Wake on LAN
NetworkInstallation Source
Preparations • Setting up the installation source
• Conguring DHCP, TFTP, PXE boot, and WOL
• Booting from the network
Remote: VNCControl and Monitoring
Best Suited For • Small to medium scenarios with varying hardware
• Completely remote installs; cross-site deployment
Each machine must be set up manuallyDrawbacks
Section 14.1.3, “Remote Installation via VNC—PXE
Boot and Wake on LAN” (page 193)
Details
Table 5.7
Simple Remote Installation via SSH—Static Network Conguration
NetworkInstallation Source
Preparations • Setting up the installation source
• Booting from the installation media
Remote: SSHControl and Monitoring
Best Suited For • Small to medium scenarios with varying hardware
84 Deployment Guide
Page 97
• Low bandwidth connections to target
Drawbacks • Each machine must be set up individually
• Physical access is needed for booting
Section 14.1.4, “Simple Remote Installation via
SSH—Static Network Conguration” (page 194)
Details
Table 5.8
Remote Installation via SSH—Dynamic Network Conguration
NetworkInstallation Source
Preparations • Setting up the installation source
• Booting from installation media
Remote: SSHControl and Monitoring
Best Suited For • Small to medium scenarios with varying hardware
• Low bandwidth connections to target
Drawbacks • Each machine must be set up individually
• Physical access is needed for booting
Section 14.1.5, “Simple Remote Installation via
SSH—Dynamic Network Conguration” (page 195)
Details
Table 5.9
Remote Installation via SSH—PXE Boot and Wake on LAN
NetworkInstallation Source
Preparations • Setting up the installation source
Deployment Strategies 85
Page 98
• Conguring DHCP, TFTP, PXE boot, and WOL
• Booting from the network
Remote: SSHControl and Monitoring
Best Suited For • Small to medium scenarios with varying hardware
• Completely remote installs; cross-site deployment
• Low bandwidth connections to target
Each machine must be set up individuallyDrawbacks
Section 14.1.6, “Remote Installation via SSH—PXE
Boot and Wake on LAN” (page 197)
Details
Table 5.10
Simple Mass Installation
Preferably networkInstallation Source
Preparations • Gathering hardware information
• Creating AutoYaST prole
• Setting up the installation server
• Distributing the prole
• Setting up network boot (DHCP, TFTP, PXE, WOL)
or
Booting the target from installation media
Local or remote through VNC or SSHControl and Monitoring
86 Deployment Guide
Page 99
Best Suited For • Large scenarios
• Identical hardware
• No access to system (network boot)
Applies only to machines with identical hardwareDrawbacks
Section 21.1, “Simple Mass Installation” (page 285)Details
Table 5.11
Rule-Based Autoinstallation
Preferably networkInstallation Source
Preparations • Gathering hardware information
• Creating AutoYaST proles
• Creating AutoYaST rules
• Setting up the installation server
• Distributing the prole
• Setting up network boot (DHCP, TFTP, PXE, WOL)
or
Booting the target from installation media
Local or remote through SSH or VNCControl and Monitoring
Best Suited For • Varying hardware
• Cross-site deployments
Complex rule setupDrawbacks
Deployment Strategies 87
Page 100
Section 21.2, “Rule-Based Autoinstallation” (page 297)Details
5.3 Deploying More than 100
Workstations
Most of the considerations brought up for medium installation scenarios in Section 5.1,
“Deploying up to 10 Workstations” (page 79) still hold true for large scale deployments.
However, with a growing number of installation targets, the benets of a fully automated
installation method outweigh its disadvantages.
It pays off to invest a considerable amount of time to create a sophisticated rule and
class framework in AutoYaST to match the requirements of a huge deployment site.
Not having to touch each target separately can save you a tremendous amount of time
depending on the scope of your installation project.
As an alternative, and if user settings should be done during the rst bootup, create
preload images with kiwi and rstboot. Deploying such images could even be done by
a PXE boot server specialized for this task. For more details, see Chapter 17, KIWI
(page 255), Chapter 21, Automated Installation (page 285), and Chapter 20, Deploying
Customized Preinstallations (page 271).
88 Deployment Guide
Loading...