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 completeaccuracy. Neither Novell, Inc., SUSE LINUX Products GmbH, the authors,
nor the translators shall be held liable for possible errors or the consequences thereof.
Contents
About This Guidexv
Part I Deployment1
1 Planning for SUSE Linux Enterprise3
1.1Considerations for Deployment of a SUSE Linux Enterprise . . . . . . . .5
51.7IBM System z: Using initrd as a Rescue System . . . . . . . . . . . .946
Index951
About This Guide
This guide is intended for use by professional network and system administrators during
the actual planning, deployment, conguration, and operation of SUSE Linux Enterprise®. As such, it is solely concerned with ensuring that SUSE Linux Enterprise is
properly congured and that the required services on the network are available to allow
it to function properly as initially installed. This guide does not cover the process of
ensuring that SUSE Linux Enterprise offers proper compatibility with your enterprise's
application software or that its core functionality meets those requirements. It assumes
that a full requirements audit has been done and the installation has been requested or
that a test installation, for the purpose of such an audit, has been requested.
This guide contains the following:
Deployment
Before you install SUSE Linux Enterprise, choose the deployment strategy and
disk setup that is best suited for your scenario. Learn how to install your system
manually, how to use network installation setups, and how to perform an autoinstallation. Congure the installed system with YaST to adapt it to your requirements.
Administration
SUSE Linux Enterprise offers a wide range of tools to customize various aspects
of the system. This part introduces a few of them.
System
Learn more about the underlying operating system by studying this part. SUSE
Linux Enterprise supports a number of hardware architectures and you can use this
to adapt your own applications to run on SUSE Linux Enterprise. The boot loader
and boot procedure information assists you in understanding how your Linux system
works and how your own custom scripts and applications may blend in with it.
Services
SUSE Linux Enterprise is designed to be a network operating system. It offers a
wide range of network services, such as DNS, DHCP, Web, proxy, and authentication services, and integrates well into heterogeneous environments including MS
Windows clients and servers.
Security
This edition of SUSE Linux Enterprise includes several security-related features.
It ships with Novell® AppArmor, which enables you to protect your applications
by restricting privileges. Secure login, rewalling, and le system encryption are
covered as well.
Troubleshooting
SUSE Linux Enterprise includes a wealth of applications, tools, and documentation
should you need them in case of trouble. Some of the most common problems that
can occur with SUSE Linux Enterprise and their solutions are discussed in detail.
1Feedback
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.
2Documentation Updates
For the latest version of this documentation, see the SUSE Linux Enterprise Server
Web site [http://www.novell.com/documentation/sles10/index
.html].
3Additional Documentation
For additional documentation on this product, refer to http://www.novell.com/
documentation/sles10/index.html:
Start-Up Guide
Basic information about installation types and work ows.
Architecture-Specic Information
Architecture-specic information needed to prepare a SUSE Linux Enterprise
Server target for installation.
xviInstallation and Administration
Novell AppArmor Administration Guide
An in-depth administration guide to Novell AppArmor that introduces application
connement for heightened security in your environment.
Storage Administration Guide
An introduction to managing various types of storage devices on SUSE Linux Enterprise.
Heartbeat Guide
An in-depth administration guide to setting up high availability scenarios with
Heartbeat.
Novell Virtualization Technology User Guide
An introduction to virtualization solutions based on SUSE Linux Enterprise and
the Xen* virtualization technology.
For a documentation overview on the SUSE® Linux Enterprise Desktop product, refer
to http://www.novell.com/documentation/sled10/index.html. The
following manuals are exclusively available for SUSE Linux Enterprise Desktop:
GNOME User Guide
A comprehensive guide to the GNOME desktop and its most important applications.
KDE User Guide
A comprehensive guide to the KDE desktop and its most important applications.
Deployment Guide
An in-depth guide for administrators facing the deployment and management of
SUSE Linux Enterprise Desktop.
Novell AppArmor Administration Guide
An in-depth administration guide to Novell AppArmor that introduces application
connement for heightened security in your environment.
Many chapters in this manual contain links to additional documentationresources. This
includes additional documentation that is available on the system as well as documentation available on the Internet.
About This Guidexvii
4Documentation Conventions
The following typographical conventions are used in this manual:
• /etc/passwd: lenames and directory names
• placeholder: replace placeholder with the actual value
• PATH: the environment variable PATH
• ls, --help: commands, options, and parameters
• user: users or groups
•
Alt, Alt + F1: a key to press or a key combination; keys are shown in uppercase as
on a keyboard
•
File, File > Save As: menu items, buttons
• ►amd64 ipf: This paragraph is only relevant for the specied architectures. The
arrows mark the beginning and the end of the text block.◄
►ipseries s390 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.
xviiiInstallation and Administration
Part I. Deployment
Planning for SUSE Linux
Enterprise
The implementation of an operating system either in an existing IT environment or as
a completely new rollout must be carefully prepared. With SUSE Linux Enterprise 10,
get 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.0 Virtualization
Runs many virtual machines on a single server, each with its own instance of an
operating system. For more information about this technology, see the virtualization
manual on http://www.novell.com/documentation/sles10/index
.html.
YaST
Several new conguration options have been developed for YaST. These are normally described in the chapters about the technology involved.
CIM Management with openWBEM
The Common Information Model Object Manager (CIMON) is a Web-based enterprise management utility. It provides a mature management framework. See also
Chapter 11, OpenWBEM (page 241).
SPident
The management utility SPident gives an overview of the installed software base
and claries the current service pack level of the system.
1
Directory Services
Several LDAP-compliant directory services are available:
Planning for SUSE Linux Enterprise3
• Microsoft Active Directory
• OpenLDAP
Novell AppArmor
Harden your System with the Novell AppArmor technology. This service is described in depth in Novell AppArmor Administration Guide (↑Novell AppArmor
Administration Guide).
iSCSI
iSCSI provides an easy and reasonably inexpensive solution for connecting Linux
computers to central storage systems. Find more information about iSCSI in
Chapter 12, Mass Storage over IP Networks—iSCSI (page 271).
Network File System v4
Starting with version 10, SUSE Linux Enterprise supports NFS also in version 4.
This gives you performance improvements, strong security, and a “stateful” protocol.
See also Chapter 38, Sharing File Systems with NFS (page 715).
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 Chapter 14, Oracle
Cluster File System 2 (page 287).
Heartbeat 2
Heartbeat 2 provides a cluster membership and messaging infrastructure. The setup
of such a cluster is described in the Heartbeat Guide.
Multipath I/O
Device mapping multipath IO features automatic conguration of the subsystem
for a large variety of setups. For details, see the chapter about multipath I/O in
Storage Administration 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.
4Installation and Administration
1.1Considerations for Deployment of
a SUSE Linux Enterprise
At the beginning of the planning process, you should try to dene the project goals and
needed features. This must 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 2, Deployment Strategies (page 7).
•
Will the system be in a hostile environment? Have a look at Chapter 49, Security
and Condentiality (page 881) 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/suselinuxportal.
• Do you need help for your local installation? Novell provides training, support,
and consulting for all topics around SUSE Linux Enterprise. Find more information
about this at http://www.novell.com/products/
linuxenterpriseserver/.
• 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.2Deployment of SUSE Linux
Enterprise
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 2, Deployment
Planning for SUSE Linux Enterprise5
Strategies (page 7) for more information. When using the Xen virtualization technolo-
gies, network root le systems or network storage solutions like iSCSI should be considered. See also Chapter 12, Mass Storage over IP Networks—iSCSI (page 271).
SUSE Linux Enterprise provides you with a broad variety of services. Find an overview
of the documentation in this book in About This Guide (page xv). 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.
In addition to the plain software installation, you should consider training the end users
of the systems as well as help desk staff.
1.3Running SUSE Linux Enterprise
The SUSE Linux Enterprise 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.
6Installation and Administration
Deployment Strategies
There are several different ways to deploy SUSE® Linux Enterprise. 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.
2.1Deploying up to 10 Workstations
If your deployment of SUSE Linux Enterprise only involves 1 to 10 workstations, the
easiest and least complex way of deploying SUSE Linux Enterprise is a plain manual
installation as featured in Chapter 3, Installation with YaST (page 17). Manual installa-
tion can be done in several different ways depending on your requirements:
Installing from the SUSE Linux Enterprise Media (page 8)
Consider this approach if you want to install a single, disconnected workstation.
Installing from a Network Server Using SLP (page 8)
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.
2
Installing from a Network Server (page 9)
Consider this approach if you have a single workstation or a small number of
workstations and if a network installation server is available.
Deployment Strategies7
Table 2.1
Installing from the SUSE Linux Enterprise Media
SUSE Linux Enterprise media kitInstallation Source
Tasks Requiring Manual Interaction
Details
Table 2.2
Installation Source
Tasks Requiring Manual
Interaction
Installing from a Network Server Using SLP
• Inserting the installation media
• Booting the installation target
• Changing media
• Determining the YaST installation scope
• Conguring the system with YaST system
NoneRemotely Controlled Tasks
Section 3.3.2, “Installing from the SUSE Linux Enterprise Media” (page 19)
Network installation server holding the SUSE Linux
Enterprise installation media
• Inserting the boot disk
• Booting installation target
Details
8Installation and Administration
• Determining the YaST installation scope
• Conguring the system with YaST
None, but this method can be combined with VNCRemotely Controlled Tasks
Section 3.3.3, “Installing from a Network Server Using
SLP” (page 19)
Table 2.3
Installing from a Network Server
Installation Source
Tasks Requiring Manual
Interaction
Details
Network installation server holding the SUSE Linux
Enterprise installation media
• 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 3.3.4, “Installing from a Network Source without SLP” (page 20)
2.2Deploying 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 11)
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 Strategies9
Simple Remote Installation via VNC—Dynamic Network Conguration (page 11)
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 12)
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 12)
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 13)
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 13)
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 14)
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 15)
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.
10Installation and Administration
Table 2.4
Preparations• Setting up an installation source
Drawbacks• Each machine must be set up individually
Simple Remote Installation via VNC—Static Network Conguration
NetworkInstallation Source
• Booting from the installation media
Remote: VNCControl and Monitoring
small to medium scenarios with varying hardwareBest Suited For
• Physical access is needed for booting
Details
Table 2.5
Preparations• Setting up the installation source
Drawbacks• Each machine must be set up individually
Simple Remote Installation via VNC—Dynamic Network Conguration