Chapter 3. Installation Considerations

Contents

3.1. Types of Installation
3.2. IPL Options
3.3. Installation Source
3.4. Installation Targets
3.5. Connecting to the Installation System

This chapter summarizes all decisions to make before starting an installation of SUSE® Linux Enterprise Server on IBM POWER hardware. The current hardware and software requirements for installing SUSE Linux Enterprise Server on IBM POWER devices are listed in the Chapter Requirements (↑Architecture-Specific Information), provided as a printable PDF document in the directory /docu on the first CD.

3.1. Types of Installation

SUSE Linux Enterprise Server offers two different types of installation on IBM POWER: an installation on the entire system and an installation in a logical partition (LPAR).

iSeries

Linux can only be installed in an LPAR on this type of machine. The installation on iSeries requires a telnet connection that allows control over the installation process throughout its course. An installation server in the network qualifies as a good source of installation.

pSeries

Linux can be installed on the entire system here. On IBM pSeries p630, p655, p670, and p690, it is also possible to install Linux in an LPAR. You can also start these two systems without partitioning and install on the entire system (full system partition). A CD-ROM drive, DVD drive, or an installation server in the network can be used as the installation source.

eServer i5/p5, System i5/p5, OpenPower

Linux can be installed on the entire system (unmanaged mode) or on an LPAR. A CD-ROM drive, DVD drive, or an installation server in the network can be used as the installation source.

JS20 Blade, JS21 Blade

Linux can only be installed on the entire system—on a blade—on this type of machine. A CD-ROM drive, DVD drive, or an installation server in the network can be used as the installation source.

IntelliStation, ATX Workstation and Server

Linux can only be installed on the entire system. A CD-ROM drive, DVD drive, or an installation server in the network can be used as the installation source.

3.2. IPL Options

Depending on the hardware used and on the chosen type of installation, the following options for the initial IPL are available for installing SUSE Linux Enterprise Server:

Table 3.1. IPL Options

IPL Option

Use

CD or DVD drive

Simplest booting procedure. The system requires a locally available CD-ROM or DVD drive for this.

Network

SUSE Linux Enterprise Server can also be booted from the network. This requires copying the appropriate kernel (suseboot/inst64 or ISERIES64) from the first CD to a boot server. Booting from network can be selected in the firmware or with i5/OS.


3.3. Installation Source

For installing SUSE Linux Enterprise Server, the installation files must be available in the local network or on a locally provided CD-ROM or DVD. Provide a network source by setting up a Linux or Unix system as an HTTP, NFS, or FTP server. It is also possible to share the installation files over SMB from a computer running Windows.

Configuring an SLP server in the local network simplifies selection of an installation source. This is described in Section “Setting Up an Installation Server Using YaST” (Chapter 4, Remote Installation, ↑Installation and Administration).

3.4. Installation Targets

SUSE Linux Enterprise Server can be installed on different types of mass storage media on IBM Power.

iSeries
  • DASD (hard disk)

  • IBM iSeries virtual disk

pSeries
  • DASD (hard disk)

  • SAN over Fiber Channel

eServer i5/p5, System i5/p5, OpenPower
  • DASD (hard disk)

  • Virtual SCSI

  • SAN over Fiber Channel

JS20 Blade, JS21 Blade
  • Local hard disk

IntelliStation, ATX Workstation and Server
  • Local hard disk

3.5. Connecting to the Installation System

SUSE Linux Enterprise Server offers a selection of four different ways of connecting to the installation system: SSH, VNC, serial console, and screen console. The versions of the SSH, VNC, or terminal software vary depending on the operating system running on the workstation initiating the connection to the installation system.

It is advisable to create an AutoYaST configuration file if many identical partitions or machines need to be installed. It can then drive the installation process. Refer to the documentation for AutoYaST in Section “Rule-Based Autoinstallation” (Chapter 5, Automated Installation, ↑Installation and Administration).