Abstract
This chapter describes the procedure for preparing the installation of SUSE® Linux Enterprise Server on IBM POWER systems.
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 configuration will work, find out which hardware has been certified by SUSE. Find a list of these computers at http://developer.novell.com/yessearch/Search.jsp.
These systems are operated with a PPC64 kernel.
Table 3.1. Supported Models
pSeries models |
p615, p630, p650, p655, p670, p690 |
eServer p5, System p, OpenPower, and ATX Server models |
505, 510, 520, 550, 560Q, 570, 570+, 575, 575+, 590, 595, 710, 720, 185 |
ATX Workstation |
185 |
All POWER3, POWER4, PPC970 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/.
BladeCenter JS12, BladeCenter JS20, BladeCenter JS21, and BladeCenter JS22 are supported systems.
Find up-to-date firmware at http://www-912.ibm.com/eserver/support/fixes/fixcentral. Select and to find your system model. Updates for the Hardware Management Console can also be selected from this page.
Find up-to-date firmware for the BladeCenter at http://www-304.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-63017&brandind=5000020 (Software and device drivers — IBM BladeCenter).
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”
For IBM pSeries systems, see Section 3.2.2, “Preparing for Installation on IBM pSeries Models”
For IBM JS20/JS21/JS22 Blades, see Section 3.2.3, “Preparing an Installation on IBM JSxx BladeCenter”
If SUSE® Linux Enterprise Server needs to be installed on a number of systems or partitions, it is recommended you create a network installation source. The same source can also be used for the concurrent installation on several partitions or several systems. The configuration of a network installation source is described in Section 14.2.1, “Setting Up an Installation Server Using YaST”.
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 Configuration”.
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 pertinent to the maintenance of an installation:
http://www.novell.com/support/products/server/ 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 security alerts.
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 configure the HMC in “Configuring the HMC using the Guided Setup Wizard”: http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/iphai_p5/confighmcgs.htm?
IBM eServer p5 systems offer the possibility of partitioning the system. This enables the concurrent operation of up to 254 operating systems on one machine. These operating systems are installed in LPARs (logical partitions). One or several of these partitions can contain a SUSE Linux Enterprise Server environment.
To prepare an LPAR for SUSE Linux Enterprise Server, first configure the system over the HMC. Refer to the IBM documentation for details: http://publib.boulder.ibm.com/infocenter/systems/scope/hw/topic/iphbi/iphbikickoff.htm
Make sure that you have sufficient hard disk space for installing SUSE Linux Enterprise Server. The standard system requires at least 4 GB of free hard disk space.
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.
Procedure 3.1. Assigning a CD-ROM or DVD Drive to an LPAR¶
Open the HMC application and go to
+ .From the available servers, expand the server and partition to install.
Right-click the profile to use for installation and select Figure 3.1, “HMC: Server Management—Properties”.
—seeIn the
dialog, select the tab.From
, select the from the bus where it is installed. To assign this DVD drive to the partition, click .The result should look like Figure 3.2, “HMC: Managed System I/O Devices”.
Now insert the SUSE Linux Enterprise Server CD1 or DVD1 in the drive.
Procedure 3.2. Assigning a Network Device to an LPAR
Open the HMC application and go to
+ .From the available servers, open the server and partition to install.
Right-click the profile to use for installation and select Figure 3.1, “HMC: Server Management—Properties”.
—seeIn the
dialog, select the tab.From
, select from the bus where it is installed. Then click .If you plan to install using a virtual ethernet adapter, refer to the IBM documentation.
Create a network installation source if SUSE Linux Enterprise Server should be installed on a number of partitions. This eliminates the need to change CDs during installation. The same source can also be used for concurrent installation of various systems. The configuration of the network installation source is described in Section 14.2.1, “Setting Up an Installation Server Using YaST”.
To start the installation, reboot the system. Right-click the profile name, select
, and press 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
in the dialog.Enter the system firmware by pressing F1 or 1 when using a serial console or a virtual console during the system check when the system is rebooted:
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM 1 = SMS Menu 5 = Default Boot List 8 = Open Firmware Prompt 6 = Stored Boot List memory keyboard network scsi speaker
Press F1 or 1 while the SCSI devices are checked. Select 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 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 Install Device. Go to to see the list of available devices:
to set theVersion 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:
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 ) 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
to install from this device. On the next screen, confirm with to exit 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 Enter.
and press
To read the installation data from a network install source rather than
continuing the installation from the CD-ROM (see
Section 3.2.1.3, “Assigning an Installation Device to an LPAR”), append the option
manual
to the name of the kernel
(install
).
For an installation over VNC, append the parameters
vnc=1
and
vncpassword=
to the
name of the kernel (password
install
). Read more about VNC in
Section 14.1.1, “Simple Remote Installation via VNC—Static Network Configuration”.
Select an ethernet device that has access to the installation source
(2
in this example).
Proceed as described in Chapter 6, Installation with YaST to begin installing the software with linuxrc and YaST.
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.
IBM p630, p655, p670, and p690 systems offer the possibility of statically partitioning the system similarly to eServer p5/System p5 (which is described in Section 3.2.1, “Preparing for Installation on IBM eServer p5, System p, and OpenPower Models”). This enables the concurrent operation of up to 16 operating systems on one machine. These operating systems are installed in LPARs (logical partitions). One or several of these partitions can contain a SUSE Linux Enterprise Server environment.
To prepare an LPAR for SUSE Linux Enterprise Server, first configure the system over the HMC. Refer to the Redbook IBM eServer pSeries 690 System Handbook (SG24-7040-00) for details (http://www.redbooks.ibm.com/redbooks/SG247040/).
Important notes regarding the configuration:
The recommended maximum number of processors for a SUSE Linux Enterprise Server LPAR is eight, because the kernel can only manage eight processors effectively.
For the installation, select
as the boot mode for the respective partition.The HMC terminal used for the input during the installation is a VT320 emulation. This emulation can lead to strange results with some applications. If possible, use an XTerm for communicating with the LPAR.
Make sure that you have sufficient hard disk space for installing SUSE Linux Enterprise Server. The use of a separate hard disk is recommended.
SUSE Linux also supports installing to Fibre Channel–attached storage. Before beginning installation, the Fibre Channel Host Bus Adapter (FCHBA), SAN fabric, and storage system must each be configured to provide access from the FCHBA through the SAN Fabric to target logical units (LUNs) on the storage system.
SAN storage devices, if properly configured, are listed among existing hard disks on your system. Section 15.1, “Using the YaST Partitioner”.
opens the dialog, as described inIf you plan to install from CD-ROM, insert CD1 in the drive. In LPAR mode, the partition to install must have the CD-ROM in its partition profile. Create a network installation source if SUSE Linux Enterprise Server needs to be installed over a number of partitions. This eliminates the need to change CDs during installation. The same source can also be used for concurrent installation of various systems. The configuration of the network installation source is described in Section 14.2.1, “Setting Up an Installation Server Using YaST”.
To start the installation, reboot the system. Then enter the system firmware by pressing F1 or 1 when using the serial console during the system check when the system is rebooted. See Figure 3.3, “Entering the System Firmware”.
Press F1 or 1 while the SCSI devices are checked. Select to enter the dialog. See Figure 3.4, “Multiboot Dialog”
Select 3
to set the install device. A list of
available devices is displayed. See
Figure 3.5, “Installing the Operating System”.
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 Enter. Alternatively, just press Enter to start the installer, the default option.
and press
To install from a network source (see
Section 3.2.2.3, “Setting Up the Installation Source”), append
manual
to the kernel to install. For
an installation over VNC, append the parameters vnc=1
and vncpassword=
to
install. Read more about VNC in
Section 14.1.1, “Simple Remote Installation via VNC—Static Network Configuration”.
password
In LPAR mode, the partition to install must have the CD-ROM in its partition profile.
Select an ethernet device that has access to the installation source
(6
in this example).
Proceed as described in Chapter 6, Installation with YaST to begin installing the software with linuxrc and YaST.
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.
Create a network installation source if SUSE Linux Enterprise Server needs to be installed over a number of partitions. This provides the advantage of no CDs needing to be changed during installation. The same source can also be used for the concurrent installation of various systems. Configuration of a network installation source is described in Section 14.2.1, “Setting Up an Installation Server Using YaST”.
Ensure that enough hard disk storage space is available for the installation of SUSE Linux Enterprise Server. It is recommended you use a dedicated hard disk.
Introductory Information:
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
in the menu then activate . Assign the CD-ROM drive to the desired blade in the menu of the new window.Set up the CD-ROM drive as a boot device. Do this by selecting
then while in the BladeCenter Management Module. Select the JSxx Blade in the section . Set the entry for on the page for to .Put CD 1 in the CD-ROM drive and restart the blade.
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
menu from the page. Select the JSxx Blade in the section and set to on .Reboot the JSxx Blade from the item
of the menu in the BladeCenter Management Module. A table appears, showing the power status of the blades in the column. Mark the check box of the desired blade and restart it with .
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
BladeCenter 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 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
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 Enter.
from the menu and press
In the case of an installation over VNC, append the parameters
vnc=1
and
vncpassword=
to the
command line for the kernel (install).
password
Proceed as described in Chapter 6, Installation with YaST to begin installing the software with linuxrc and YaST.