Novell LINUX ENTERPRISE SERVER 10 SP1 - ARCHITECTURE-SPECIFIC INFORMATION... Manual

SUSE Linux Enterprise
Server
www.novell.com10 SP1
March15,2007 Architecture-Specific Information

Architecture-Specic Information
All content is copyright © 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 ful-
lled:
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, specically 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.

Contents
Preface v
1Requirements 1
1.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . 3
2Preparation 5
2.1 Preparing for Installation on IBM eServer i5/p5, System i5/p5, and OpenPower
Models.............................. 6
2.2 Preparing for Installation on an IBM pSeries Models . . . . . . . . . . 13
2.3 Preparing an Installation on IBM JS20/JS21 Blades . . . . . . . . . . . 18
2.4 Preparing an Installation on IBM iSeries Models . . . . . . . . . . . . 22
AAppendix 39
A.1 Editing the Built-In Kernel Command Line in a zImage . . . . . . . . . 39

Preface
This manual describes the steps for installing SUSE® Linux Enterprise Server on IBM
eServer i5 and eServer p5, pSeries, JS20/JS21 Blades, and iSeries systems. It contains
all necessary information for the preparation of the installation of SUSE Linux Enterprise
Server. The installation of SUSE Linux Enterprise Server is described in Chapter 3,
Installation with YaST (↑Installation and Administration).
Whenever possible, this manual refers to relevant information sources and other docu-
mentation on the Internet and on your installed system. Detailed information about
Linux device drivers and other technical details are covered in the IBM (online) docu-
mentation. Note the respective references.
1 Structure of This Manual
This manual provides information about the hardware and software requirements for
successfully installing SUSE Linux Enterprise Server on your system, necessary steps
on i5/OS, and the preparation of the eServer i5/p5 rmware, pSeries, JS20/JS21 Blades,
and iSeries.
TIP: For More Information about SUSE Linux Enterprise Server on IBM
POWER
Find a short introduction to SUSE Linux Enterprise Server on IBM POWER in
the Start-Up Guide manual of which you received a printed copy. Find a detailed
description of the installation procedure and the administration of SUSE Linux
Enterprise Server in the Installation and Administration manual, which you can
nd in the local directory /usr/share/doc/manual or on the rst installa-
tion medium in the directory /docu.
2 Target Group
Readers of this manual should have some experience in the following areas:
• Use of i5/OS or the pSeries rmware.

• Knowledge of the hardware environment of the IBM pSeries or iSeries system,
especially of the network environment.
• Basic Linux and Unix skills.
3 Acknowledgments
The history of Linux is a success story of countless developers around the world who
continue what Linus Torvalds once started as a one-man show. We sincerely appreciate
their tireless commitment.
We would particularly like to thank all who are involved in the pSeries and iSeries
project at IBM and SUSE. Many thanks to the developers at SUSE and IBM, the testers
at SUSE, and all beta testers and editors at IBM.
vi Architecture-Specic Information

1
Requirements
1.1 Hardware Requirements
1.1.1 iSeries and i5 Models
Table 1.1 Supported Models
i800, i810, i825, i870, i890iSeries models
510, 520, 550, 570, 570+, 590, 595eServer i5 and System i5 models
The systems in Table 1.1, “Supported Models” (page 1) were supported by SUSE®
Linux Enterprise Server 9. They are no longer supported but should still run.
Table 1.2 Unsupported Models
i270, i820, i830, i840iSeries models
A standard installation requires at least 256 MB of RAM. An installation over VNC
requires at least 448 MB of RAM. The installation of a standard system requires at least
1.8 GB of free hard disk space.
Refer to http://www-1.ibm.com/servers/eserver/iseries/linux/
pdfs/guide.pdf for a detailed list of all feature codes. An older version of this list
Requirements 1

is also available at http://penguinppc.org/ppc64/machines.php. Up-to-
date hardware information for Linux on System i5 is available at http://www-03
.ibm.com/systems/i/os/linux/servers.html.
1.1.2 pSeries and p5 Models
These systems are operated with a PPC64 kernel.
Table 1.3 Supported Models
p615, p630, p650, p655, p670, p690pSeries models
505, 510, 520, 550, 560Q, 570, 570+, 575,
575+, 590, 595, 710, 720, 185
eServer p5, System p5, 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, but should still run.
A standard installation requires at least 256 MB of RAM. An installation over VNC
requires at least 448 MB of RAM. The installation of a standard system requires at least
1.8 GB of free hard disk space.
Up-to-date hardware information for Linux on System p5 is available by model from
http://www-03.ibm.com/systems/p/linux/.
1.1.3 BladeCenter
BladeCenter JS20 except JS20 GA1 (model 8842-21X), BladeCenter JS20V, and
BladeCenter JS21 are supported systems at the time of printing.
2Architecture-Specic Information

1.2 Software Requirements
1.2.1 IBM iSeries
Find up-to-date information about software requirements at http://www.ibm.com/
servers/eserver/iseries/linux/reqs.html.
1.2.2 IBM eServer i5 and System i5
Find up-to-date rmware at http://www-912.ibm.com/eserver/support/
fixes/fixcentral. Select System i5 family and Server Firmware to nd your
system model. Updates for the Hardware Management Console can also be selected
from this page.
1.2.3 IBM pSeries, IBM eServer p5, System
p5, 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.
1.2.4 JS20 Blade and JS21 Blade
Find up-to-date rmware for the BladeCenter at http://www-304.ibm.com/
jct01004c/systems/support/supportsite.wss/brandmain
?brandind=5000020.
Requirements 3

2
Preparation
This chapter describes the preparatory steps that must be taken before the actual instal-
lation. The installation procedure depends on the system used. See the following docu-
mentation:
• For IBM eServer i5/p5 Systems, see Section 2.1, “Preparing for Installation on
IBM eServer i5/p5, System i5/p5, and OpenPower Models” (page 6)
• For IBM pSeries systems, see Section 2.2, “Preparing for Installation on an IBM
pSeries Models” (page 13)
• For IBM JS20/JS21 Blades, see Section 2.3, “Preparing an Installation on IBM
JS20/JS21 Blades” (page 18)
•For IBM iSeries systems, see Section 2.4, “Preparing an Installation on IBM iSeries
Models” (page 22)
If SUSE® Linux Enterprise Server should be installed on a number of systems or par-
titions, it is recommended to create a network installation source. This eliminates the
need to change CDs during the installation. The same source can also be used for the
concurrent installation on several partitions or several systems. The conguration of a
network installation source is described in Section 4.2.1, “Setting Up an Installation
Server Using YaST” (Chapter 4, Remote Installation, ↑Installation and Administration).
For eServer i5, System i5, and iSeries, a network installation source can be set up in a
special partition. See Section 2.4.4, “Creating a Network Installation Source” (page 35)
for iSeries.
Preparation 5

The installation can be controlled with a VNC client. For more information about VNC,
see Section 4.1.1, “Simple Remote Installation via VNC—Static Network Conguration”
(Chapter 4, Remote Installation, ↑Installation and Administration).
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.
•suse-security-announce — The SUSE mailing list exclusively for secu-
rity alerts.
2.1 Preparing for Installation on IBM
eServer i5/p5, System i5/p5, and
OpenPower Models
This section covers the preparatory steps for installing SUSE® Linux Enterprise Server
on IBM eServer i5/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 congure the HMC in “Conguring the
HMC using the Guided Setup Wizard”: http://publib.boulder.ibm.com/
infocenter/eserver/v1r3s/index.jsp?topic=/iphai/confighmcgs
.htm
6Architecture-Specic Information

2.1.1 Modern Features of IBM eServer i5/p5
Systems
IBM eServer i5/p5 systems offer the possibility to partition the system like on IBM
iSeries systems. 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 environ-
ment.
To prepare an LPAR for SUSE Linux Enterprise Server, rst congure the system over
the HMC. Refer to the IBM documentation for details: http://publib.boulder
.ibm.com/infocenter/eserver/v1r3s/index.jsp?topic=/iphbi/
iphbikickoff.htm
2.1.2 Hard Disk Space
Make sure that you have sufcient hard disk space for installing SUSE Linux Enterprise
Server. The standard system requires at least 4 GB of free hard disk space.
2.1.3 Assigning an Installation Device to an
LPAR
SUSE Linux Enterprise Server can be installed from a CD-ROM or DVD drive or using
a network installation source. Make the CD-ROM, DVD drive, or network device
available to the LPAR to install.
Preparation 7

Figure 2.1 HMC: Server Management—Properties
Procedure 2.1 Assigning a CD-ROM or DVD Drive to an LPAR
1Open the HMC application and go to Server and Partition >Server Management.
2From the available servers, expand the server and partition to install.
3Right-click the prole to use for installation and select Properties—see Figure 2.1,
“HMC: Server Management—Properties” (page 8).
4In the Logical Partition Prole Properties dialog, select the Physical I/O tab.
5From 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 2.2, “HMC: Managed System I/O Devices” (page 9).
8Architecture-Specic Information

Figure 2.2 HMC: Managed System I/O Devices
Now insert the SUSE Linux Enterprise Server CD1 or DVD1 in the drive.
Procedure 2.2 Assigning a Network Device to an LPAR
1Open the HMC application and go to Server and Partition >Server Management.
2From the available servers, open the server and partition to install.
3Right-click the prole to use for installation and select Properties—see Figure 2.1,
“HMC: Server Management—Properties” (page 8).
4In the Logical Partition Prole Properties dialog, select the Physical I/O tab.
5From 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 documen-
tation.
Preparation 9

Create a network installation source if SUSE Linux Enterprise Server should be installed
on a number of partitions. This eliminates the need to change installation media during
installation. The same source can also be used for concurrent installation of various
systems. The conguration of the network installation source is described in Sec-
tion 4.2.1, “Setting Up an Installation Server Using YaST” (Chapter 4, Remote Instal-
lation, ↑Installation and Administration).
2.1.4 Starting the Installation
To start the installation, reboot the system. Right-click the prole 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 documen-
tation. 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 1when 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 1while 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
10 Architecture-Specic Information

2. Setup Remote IPL (Initial Program Load)
3. Change SCSI Settings
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:
2.1.5 Booting from the CD-ROM Drive
Select the CD-ROM drive (4in this example):
SMS 1.5 (c) Copyright IBM Corp. 2000,2003 All rights reserved.
--------------------------------------------------------------------------
Select Task
Preparation 11

IDE CD-ROM
( loc=U787A.001.DNZ00XG-P4-D3 )
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, conrm
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 Linux Enterprise 10 (PPC)!
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 10.1.22-r938.SuSE
booted from ...
Enter "help" to get some basic usage information
boot:
Select install from the menu and press Enter. To continue the installation from a different
network installation source, select slp instead.
To read the installation data from a network install source rather than continuing the
installation from the CD-ROM (see Section 2.1.3, “Assigning an Installation Device
to an LPAR” (page 7)), 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
12 Architecture-Specic Information

VNC in Section 4.1.1, “Simple Remote Installation via VNC—Static Network Con-
guration” (Chapter 4, Remote Installation, ↑Installation and Administration).
2.1.6 Booting from the Network Source
Select an ethernet device that has access to the installation source (2in this example).
2.1.7 Additional Steps
Proceed as described in Chapter 3, Installation with YaST (↑Installation and Adminis-
tration) to begin installing the software with linuxrc and YaST.
2.2 Preparing for Installation on an
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.
2.2.1 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 2.1, “Preparing
for Installation on IBM eServer i5/p5, System i5/p5, and OpenPower Models”
(page 6)). 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 congure 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/).
Preparation 13

Important notes regarding the conguration:
• The recommended maximum number of processors for a SUSE Linux Enterprise
Server LPAR is eight, because the kernel can only manage eight processors effec-
tively.
•For the installation, select SMS as the boot mode for the respective partition.
•The HMC terminal used for the input during the installation is a VT320 emulation.
This emulation can lead to strange effects with some applications. If possible, use
an XTerm for communicating with the LPAR.
2.2.2 Hard Disk Space
Make sure that you have sufcient 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 congured to provide access from the FCHBA through the SAN
Fabric to target logical units (LUNs) on the storage system.
SAN storage devices, if properly congured, are listed among existing hard disks on
your system. Create Custom Partitioning Setup opens the dialog, as described in Sec-
tion 3.7.2, “Partitioning” (Chapter 3, Installation with YaST, ↑Installation and Admin-
istration).
For more information, see http://publib.boulder.ibm.com/infocenter/
eserver/v1r3s/index.jsp?topic=/iphai/confighmcgs.htm.
2.2.3 Setting Up the Installation Source
If you plan to install from CD-ROM, insert CD1 in the drive. In LPAR mode, the par-
tition to install must have the CD-ROM in its partition prole. Create a network instal-
lation 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 conguration of
14 Architecture-Specic Information