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 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/eserver/v1r3s/index.jsp?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.

Figure 2.1. HMC: Server Management—Properties¶

The result should look like Figure 2.2, “HMC: Managed System I/O Devices”.

Figure 2.2. HMC: Managed System I/O Devices¶

Now insert the SUSE Linux Enterprise Server CD1 or DVD1 in the drive.

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 configuration of the network installation source is described in Section “Setting Up an Installation Server Using YaST” (Chapter 4, Remote Installation, ↑Installation and Administration).

To start the installation, reboot the system. Right-click the profile 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 documentation. 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 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 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
 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:

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 2. Normal Mode Boot to install from this device. On the next screen, confirm 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”), 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 VNC in Section “Simple Remote Installation via VNC—Static Network Configuration” (Chapter 4, Remote Installation, ↑Installation and Administration).

Select an ethernet device that has access to the installation source (2 in this example).

Proceed as described in Chapter Installation with YaST (↑Installation and Administration) to begin installing the software with linuxrc and YaST.

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”). 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:

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. Create Custom Partitioning Setup opens the dialog, as described in Section “Partitioning” (Chapter 3, Installation with YaST, ↑Installation and Administration).

For more information, see http://publib.boulder.ibm.com/infocenter/eserver/v1r3s/index.jsp?topic=/iphai/confighmcgs.htm.

If 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 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 configuration of the network installation source is described in Section “Setting Up an Installation Server Using YaST” (Chapter 4, Remote Installation, ↑Installation and Administration).

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 2.3, “Entering the System Firmware”.

Figure 2.3. Entering the System Firmware¶

Press F1 or 1 while the SCSI devices are checked. Select 6 MultiBoot to enter the Multiboot dialog. See Figure 2.4, “Multiboot Dialog”

Figure 2.4. Multiboot Dialog¶

Select 3 to set the install device. A list of available devices is displayed. See Figure 2.5, “Installing the Operating System”.

Figure 2.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 Linux SLES-10101010101010101010 (PPC)<-

After you select 1, the yaboot utility is started.

  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

Select install from the menu and press Enter. Alternatively, just press Enter to start the installer, the default option.

To install from a network source (see Section 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=password to install. Read more about VNC in Section “Simple Remote Installation via VNC—Static Network Configuration” (Chapter 4, Remote Installation, ↑Installation and Administration).

In LPAR mode, the partition to install must have the CD-ROM in its partition profile.

If yaboot cannot be started, launch the loading process manually:

Select an ethernet device that has access to the installation source (6 in this example).

Proceed as described in Chapter Installation with YaST (↑Installation and Administration) to begin installing the software with linuxrc and YaST.

Create a network installation source if SUSE Linux Enterprise Server should be installed over a number of partitions. This provides the advantage that no CDs need 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 “Setting Up an Installation Server Using YaST” (Chapter 4, Remote Installation, ↑Installation and Administration).

Ensure that enough hard disk storage space is available for the installation of SUSE Linux Enterprise Server. It is recommended to use a dedicated hard disk.

Introductory Information:

Introductory Resources

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:

The Redbook Linux on iSeries (SG24-6232-00) provides detailed information (http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg246232.html).

The configuration of a system on the i5/OS side requires an i5/OS system access with *SERVICE permissions and authority to access SST. A DST password for creation of a console user is also required. A 5250 terminal or a 5250 emulation package is required to be able to connect to i5/OS (like TN5250 on Linux or PCS or Client Access on Windows).

2.4.2.1. Partitioning the System¶

Create a new system partition for SUSE Linux Enterprise Server first. Use the main option number 5 Work with System Partitions, suboption 5 Create a new Partition in STRSST. Use the main option 3 Work with Partition Configuration, suboption 2 Change Partition Processing Resources if the partition already exists.

Figure 2.6. Creating a New Partition¶

Figure 2.7. Changing Partition Processing Resources¶

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¶

Confirm the changes with Enter to start the process for creating a new partition.

An IPL is required after creating a new partition.

2.4.2.2. Configurating the Virtual Ethernet (System Tools)¶

Use System Service Tools (STRSST) to configure the Virtual Ethernet. Select F5 (Work with system partitions), F3 (Work with partition configuration), then F10 to change the virtual LAN configuration. Pressing F9 shows all partitions, even the ones not yet linked.

Figure 2.9. Working with the Virtual LAN Configuration¶

Figure 2.10. Changing the Virtual LAN Configuration¶

2.4.2.4. Assigning Network Storage Space¶

Next, assign SUSE Linux Enterprise Server some storage space. Do this with the utility CRTNWSSTG.

Figure 2.11. Creating NWS Storage Space (CRTNWSSTG)¶

2.4.2.5. Creating the Network Server Description¶

The Network Server Description combines the individual configuration settings to one object.

Figure 2.12. Creating a Network Server Description (CRTNWSD)¶

Change the following settings:

• NWSD name

• Network server type = *GUEST

• Partition = enter the partition name here

• Code page = 437

• IPL source = *STMF

• IPL stream file = '/QOPT/SLES100.001/SUSEBOOT/inst64'. SU90.001 is the disk label of the boot CD. To find out the disk label, insert the CD and enter DSPLNK QOPT at a command prompt. For Service Pack 2, for example, the parameter is /QOPT/SLES100SP2.001/SUSEBOOT/inst64.

  The statements made in Section 2.4.4, “Creating a Network Installation Source” are valid for network-based installations.

• IPL parameters = 'vnc=1 vncpassword=suseinst'

• Text description = SUSE Linux Enterprise Server

• Online at IPL = *YES

Figure 2.13. Creating a Network Server Description (CRTNWSD)¶

It is possible to pass additional IPL parameters for VNC. Refer to Section “Booting the Target System for Installation” (Chapter 4, Remote Installation, ↑Installation and Administration).

The IPL stream file can be queried from the i5/OS command line with the command DSPLNK('QOPT').

2.4.2.6. 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¶

The link to the Network Server Description is then established.

Figure 2.15. Adding the Network Server Storage Link (ADDNWSSTGL)¶

This section describes the configuration of telnet access to the virtual console.

2.4.3.1. Supported Terminals¶

Table 2.1. Supported Terminal Emulators¶

Operating System	Terminal	Support
Linux	Linux console	Fully supported
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	Not supported
AIX	aix xterm	Not supported

Using a fully supported terminal emulator makes all features of the installation software accessible, including key combinations and colors.

When installing from a Windows machine, the freely available telnet client PuTTY should be used in all cases. The configuration and operation of PuTTY is described as part of the documentation coming with the PuTTY (see /dosutils/putty on the installation medium or http://the.earth.li/~sgtatham/putty/0.58/htmldoc/). The telnet client shipped with Windows 98 is not supported. The telnet clients shipped with Windows 2000 and Windows XP can be used, but offers only a restricted usage of the installation software.

aixterm generally does not cooperate too well with Linux. A workaround solution is to start an xterm on AIX and set the terminal manually with TERM=vt100. Because this is not possible during installation, a different platform should be used.

When operating the Linux terminal multiplexer screen, it is recommended to adjust the setting for background-color-erase because the background would otherwise 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.

2.4.3.2. Recognizing the Virtual Console Terminal¶

When accessing the virtual iSeries console with telnet, Linux probes the telnet client to attain the best operability. The following settings are especially important:

• Is more than one connection active? (If yes, a warning is issued)

• What type of terminal is connecting?

• Is it a Windows-based terminal?

• What is the screen size?

This probe is performed during the start-up phase of the installation software as well as during logins to the installed system.

The i5/OS telnet server offers the possibility to maintain several concurrent connections to a Linux console.

The probe fails if more than one session is connected, resulting in erroneous assumptions regarding terminal settings. Multiple concurrent connections should therefore be avoided.

Create a network installation 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 configuration of the network installation source is described in Section “Setting Up an Installation Server Using YaST” (Chapter 4, Remote Installation, ↑Installation and Administration).

Copy the file ISERIES64 from the installation source to the i5/OS IFS using FTP:

ftp iseries
(login)
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 . . . . . . . . '/kernels/ISERIES64'_______
IPL parameters . . . . . . . . . 'vnc=1 vncpassword=suseinst'__

It is additionally possible to pass parameters for VNC. Refer to the Installation and Administration manual for information.

Establish a connection to the virtual console with PuTTY or to telnetd port 2301 with one of the supported terminals. Start the installation kernel (IPL) by activating Option 1 in the target NWSD. Watch the kernel messages on the virtual console carefully.

Figure 2.16. Working with the Configuration Status¶

Watch the virtual console. linuxrc appears in the case of a network or VNC installation and requests the user to make a few choices.

The IPL of the file ISERIES64 starts linuxrc in the case of a network installation. The following steps are then necessary:

You are then directed to start the VNC client. See Example 2.1, “The Installation over VNC Can Begin”.

starting VNC server...
a log can be found in /tmp/vncserver.log ...
*** *** You can connect to 192.168.0.154, display :1 now ***
(When YaST2 is finished, close your VNC viewer and return to this
window.)

Start the VNC client with the displayed parameters (192.168.0.154:1 in this example) and enter the VNC password (suseinst in this example). The graphical interface of VNC appears and YaST starts a few seconds later.