Summary of Contents for Novell LINUX ENTERPRISE SERVER 10 SP1 - ARCHITECTURE-SPECIFIC INFORMATION 15-03-2007
Page 1
SUSE Linux Enterprise Server 10 SP1 www.novell.com Architecture-Specific Information March 15, 2007...
Page 2
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...
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.
Page 6
• 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.
Requirements 1.1 Hardware Requirements 1.1.1 iSeries and i5 Models Table 1.1 Supported Models iSeries models i800, i810, i825, i870, i890 eServer i5 and System i5 models 510, 520, 550, 570, 570+, 590, 595 The systems in Table 1.1, “Supported Models” (page 1) were supported by SUSE®...
Page 8
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 pSeries models p615, p630, p650, p655, p670, p690 eServer p5, System p5, OpenPower, 505, 510, 520, 550, 560Q, 570, 570+, 575, and ATX Server models...
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 firmware at http://www-912.ibm.com/eserver/support/ fixes/fixcentral. Select System i5 family and Server Firmware to find your system model. Updates for the Hardware Management Console can also be selected from this page.
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”...
• is an effective help tool http://www.novell.com/suselinuxportal 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.
Page 13
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.
Page 14
Figure 2.1 HMC: Server Management—Properties Procedure 2.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 profile to use for installation and select Properties—see Figure 2.1, “HMC: Server Management—Properties”...
Page 15
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 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.
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.
Page 17
Setup Remote IPL (Initial Program Load) Change SCSI Settings Select Console 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.
Page 18
IDE CD-ROM ( loc=U787A.001.DNZ00XG-P4-D3 ) Information Normal Mode Boot 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.
VNC in Section 4.1.1, “Simple Remote Installation via VNC—Static Network Confi- 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 (2 in 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.
Page 20
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 effec- tively. • For the installation, select SMS as the boot mode for the respective partition. •...
Page 21
the network installation source is described in Section 4.2.1, “Setting Up an Installation Server Using YaST” (Chapter 4, Remote Installation, ↑Installation and Administration). 2.2.4 Starting the Installation 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 re- booted.
Page 22
Figure 2.4 Multiboot Dialog Version M2P01113 (c) Copyright IBM Corp. 2000 All rights reserved. ------------------------------------------------------------------------ Multiboot Select Software Software Default Select Install Device Select Boot Devices OK Prompt Multiboot Startup <ON> .------. |X=Exit| `------' ===>3 Select 3 to set the install device. A list of available devices is displayed. See Figure 2.5, “Installing the Operating System”...
Page 23
2.2.5 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 Linux SLES-9 (PPC)<- After you select 1 , the yaboot utility is started. Welcome to SuSE Linux Enterprise 10 (PPC)! Type "install"...
2.2.6 Booting from the Network Source Select an ethernet device that has access to the installation source (6 in this example). 2.2.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.3 Preparing an Installation on IBM JS20/JS21 Blades This section describes the preparatory steps for the installation of SUSE®...
Page 25
• JS20/JS21 Blades Site: http://www-03.ibm.com/servers/eserver/ bladecenter/literature/ 2.3.4 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.
Page 26
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 JS20/JS21 Blade the subsequent commands are intended.
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 JS20/JS21 Blade over Serial over LAN (SOL) with the command console. system> env -T system:blade[9] system:blade[9]>...
The support portal often features articles about common problems. Access this portal at http://www.novell.com/suselinuxportal. This chapter was compiled in close cooperation with Christopher Abbey, James Srebbing, Jay S. Bryant, and Brent Baude. 2.4.1 Resources Introductory Resources •...
Page 29
• Information about Linux on LPARs: http://publib.boulder.ibm.com/ iseries/v5r1/ic2924/index.htm?info/rzalm/ rzalmlinuxkickoff.htm 2.4.2 Necessary Steps Concerning i5/OS The following section assists in the configuration of an iSeries system when installing SUSE Linux Enterprise Server. Detailed reference information about how to create partitions for Linux is contained in the following documents: •...
Page 30
Figure 2.6 Creating a New Partition Create New Partition System: SUSE1 Complete blanks, press Enter. Partition identifier and name ..GINGER__ Number of available system processors . . . : Number of partition processors ..Minimum / maximum number of processors ...
Page 31
Try to plan your minimum and maximum values for the processor (Minimum / maximum number of processors) and main storage (Minimum / maximum size of main storage) accurately because changing these values requires a primary partition IPL. Figure 2.8 Changing Partition Processing Resources Change Partition Processing Resources System: SUSE1...
Page 32
Figure 2.9 Working with the Virtual LAN Configuration Work with Virtual LAN Configuration System: SUSE1 Type options, press Enter. 2=Change --------------Virtual LAN Identifiers--------------- Opt ID Name 0 PRIMARY 1 PEPPER 2 CURRY 3 GINGER '1' Indicates LAN in use. '.' Indicates LAN not in use. F3=Exit F9=Show only partitions using Virtu F11=Display communication options...
Page 33
Partitioning Tips—Processors, Memory, NWSDs, and LPARs • Run STRSST (Start System Service Tools) and select 5 (Work with system parti- tions), then 3 (Work with partition configuration), and assign the host partition for the guest by entering 13 in the field next to the partition name. •...
Page 34
Figure 2.11 Creating NWS Storage Space (CRTNWSSTG) Create NWS Storage Space (CRTNWSSTG) Type choices, press Enter. Network server storage space.. > GINGER0_ Name Size....9000___ *CALC, 1-64000 megabytes From storage space..
Page 35
Figure 2.12 Creating a Network Server Description (CRTNWSD) Create Network Server Desc (CRTNWSD) Type choices, press Enter. Network server description . . . ginger__ Name Resource name ..*NONE___ Name, *NONE Network server type .
Page 36
• Text description = SUSE Linux Enterprise Server • Online at IPL = *YES Figure 2.13 Creating a Network Server Description (CRTNWSD) Create Network Server Desc (CRTNWSD) Type choices, press Enter. Network server description ... > GINGER__ Name Resource name ...
Page 37
Linking the Network Storage Space with the Network Server Description (WRKNWSSTG) The newly created storage space needs to be linked with the Server Description. First select the storage space from the list. Figure 2.14 Work with Network Server Storage Spaces Work with Network Server Storage Spaces System: SUSE1...
Page 38
Figure 2.15 Adding the Network Server Storage Link (ADDNWSSTGL) Add Network Server Storage Link (ADDNWSSTGL) Type choices, press Enter. Network server storage space . . > GINGER0 Name Network server description . . . > GINGER Name Drive letter ..*FIRSTAVAIL Dynamic storage link .
Page 39
Operating System Terminal Support Linux Standard Xterm Fully supported Linux GNOME terminal Fully supported Linux KDE terminal Fully supported Linux screen Fully supported Windows PuTTY Fully supported Windows Telnet client in Windows 98 Not supported Windows Telnet client in Windows 2000 Not supported Windows Telnet client in Windows XP...
Page 40
be displayed black instead of reflecting the color indicated by the installation software. To achieve this, insert the following entry in the file ~/.screenrc: defbce on To change this setting for just one single window, use Ctrl + A : , enter bce, and press Enter .
Page 41
Troubleshooting Terminal Problems • Ctrl + L redraws the screen. This is useful if it looks odd or broken. • linuxrc displays broken line art. This is a known problem that is not related to the terminal application. • A terminal connected when an installation aborted (for example, by a sudden shutdown of the LPAR) may be badly configured upon reconnection.
Page 42
ftp> cd /kernels ftp> bin ftp> put ISERIES64 ftp> bye The installation can then be started as described before. Do not forget to change the IPL Source before doing this: IPL source ... *STMF__ *SAME, *NWSSTG, *PANEL... IPL stream file .
Page 43
Figure 2.16 Working with the Configuration Status Work with Configuration Status SUSE1 12/03/01 17:45:21 Position to ..____ Starting characters Type options, press Enter. 1=Vary on 2=Vary off 5=Work with job 8=Work with description 9=Display mode status 13=Work with APPN status...
Page 44
Network Allows the installation from an NFS share. The necessary network parameters are requested along with the hostname or IP address of the NFS server. Also enter the path to the NFS share. Hard Disk Use this when the installation files are available on another hard disk. Enter the device name including the partition and the path to the installation files (for example, /dev/sdb1 and /suse).
Appendix A.1 Editing the Built-In Kernel Command Line in a zImage For kernels on POWER systems the mkzimage_cmdline utility adds kernel command line options to the kernel image. This options string is passed to the kernel, its contents overwriting the contents of /options/boot-file. This utility is available on all architectures, but it only works on POWER kernel images.
Page 46
If an ftp or smb URL is given, specify the user and password for installation. These parameters are optional and an anonymous or guest login is assumed if they are not given. Username=<a user name> Password=<a password> For a Samba or CIFS installation, you can also specify the domain that should be used: Workdomain=<a domain>...
Page 47
A.1.2 For More Information Find alternative documentation for the setup of a network installation server and client on the first installation medium in /docu as PureNetworkInstall.HOWTO. Appendix...
Need help?
Do you have a question about the LINUX ENTERPRISE SERVER 10 SP1 - ARCHITECTURE-SPECIFIC INFORMATION 15-03-2007 and is the answer not in the manual?
Questions and answers