linux: installing linux on power systems servers

Linux

Installing Linux on Power Systems servers

IBM

NoteBefore using this information and the product it supports, read the information in “Notices” onpage 31.

Second Edition (June 2013)

© Copyright IBM Corporation 2013.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Installing Linux on Power Systemsservers . . . . . . . . . . . . . . . 1What’s new in Installing Linux on Power Systemsservers . . . . . . . . . . . . . . . . 1Linux on Power installation flow chart . . . . . 2Quick start guides for installing Linux . . . . . . 2Quick start videos for installing Linux . . . . . . 3Preparing to install the Linux operating system . . 18Connecting to your server . . . . . . . . . 18Powering on the server . . . . . . . . . . 19

Using the power button . . . . . . . . . 19Using a console . . . . . . . . . . . . 19Using the ASMI web interface . . . . . . . 20

Specifying a boot method. . . . . . . . . . 21Complete your Linux installation . . . . . . . 21

Complete installation on system with graphicalcapabilities . . . . . . . . . . . . . 21

Complete installation using VNC . . . . . . 22Installing Virtual I/O Server and configuring theIntegrated Virtualization Manager . . . . . . 23

Additional installation methods . . . . . . . 24Kickstart files for Red Hat Enterprise Linux . . 24AutoYaST2 for SUSE Linux Enterprise Server . . 25Network installation . . . . . . . . . . 25

IBM Linux on Power tools repository. . . . . . 26Installing the tools repository . . . . . . . 27Installing packages with the tools repository . . 28

Troubleshooting you Linux on Power installation . . 29PDF file for Installing Linux on Power Systemsservers . . . . . . . . . . . . . . . . 30

Notices . . . . . . . . . . . . . . 31Trademarks . . . . . . . . . . . . . . 32

© Copyright IBM Corp. 2013 iii

iv Linux: Installing Linux on Power Systems servers

Installing Linux on Power Systems servers

There are common methods for installing Linux depending on your hardware and virtualizationrequirements.

For information about installing and configuring PowerKVM, see IBM® PowerKVM.

What’s new in Installing Linux on Power Systems serversThis new release of Installing Linux on Power Systems™ servers includes additional quick start guides,quick start videos, information about installing VIOS and Integrated Virtual Machine (IVM), and a flowchart to help you navigate the installation topics for Linux on Power®.

Quick start guides

New quick start guides have been added for installing VIOS and IVM and installing Linux on a partition

using IVM. Learn more...

Quick start videos

New quick start guides have been added, illustrating how to install VIOS on a Linux on Power server,how to create an IVM-managed LPAR on a Linux on Power system, and how to install Red Hat

Enterprise Linux or SUSE Linux Enterprise Server in an IVM-managed LPAR. Learn more...

Linux on Power installation flow chart

Use this flow chart to navigate installation topics for a Linux on Power server. Learn more...

© Copyright IBM Corp. 2013 1

Linux on Power installation flow chartUse this flow chart to navigate installation topics for a Power Systems server.

Quick start guides for installing LinuxUse these PDF files to find information to get you started installing Linux on a Power Systems server.v Configuring Ubuntu on a preinstalled Power Systems™ server

Use this quick start guide to configure Ubuntu that has been preinstalled on IBM Power Systemsservers.

v Configuring IBM PowerKVM on a Linux on Power Systems serverUse this quick start guide if your Power Systems server is preinstalled with PowerKVM.

v Configuring IBM PowerKVM on a preinstalled Power Systems™ serverUse this quick start guide if your Power Systems server is not preinstalled.

v Quick Start Guide for installing Linux on Power Systems servers using a monitorUse this information to install Linux on a Power Systems server that has a graphics card installed. Thisinstallation assumes an unmanaged (stand-alone) system.

2 Linux: Installing Linux on Power Systems servers

v Quick Start Guide for installing Linux on Power Systems servers using a serial consoleUse this information to install Linux using a serial console on a Power Systems server that does nothave a graphics card installed. This installation assumes an unmanaged (stand-alone) system.

v Quick Start Guide for installing VIOS and IVMUse this information to install Virtual I/O Server (VIOS) and the Integrated Virtual Manager (IVM) ona Power Systems server.

v Quick Start Guide for installing Linux on a partition using IVMUse this information to install Linux on a partition using the Integrated Virtualization Manager (IVM).

Quick start videos for installing LinuxUse these videos to find information to get you started installing Linux on a Power Systems server.v IBM PowerLinux Linux installation quick start with a graphics card.

Use this information to install Linux on a Power Systems server that has a graphics card installed. Thisinstallation assumes a stand-alone (unmanaged) system. For a transcript of the spoken content of thevideo, see Transcript.

v IBM PowerLinux Linux installation quick start without a graphics card.Use this information to install Linux with a serial console on a Power Systems server that does nothave a graphics card installed. This installation assumes a stand-alone (unmanaged) system. For atranscript of the spoken content of the video, see Transcript.

v Installing VIOS quick start.Use this information to install VIOS on a Power Systems server. For a transcript of the spoken contentof the video, see Transcript.

v Creating an IVM-managed LPAR.Use this information to create an IVM-managed LPAR on a Power Systems server. For a transcript ofthe spoken content of the video, see Transcript.

v Installing Red Hat Enterprise Linux in an IVM-managed LPAR.Use this information to install Red Hat Enterprise Linux in an IVM-managed LPAR on a PowerSystems server. For a transcript of the spoken content of the video, see Transcript.

v Installing SUSE Linux Enterprise Server in an IVM-managed LPAR.Use this information to install SUSE Linux Enterprise Server in an IVM-managed LPAR on a PowerSystems server. For a transcript of the spoken content of the video, see Transcript.

IBM PowerLinux Linux installation quick start with a graphics cardvideo transcriptThe following is a transcript of the spoken content of the IBM PowerLinux Linux installation quick startwith a graphics card video.

In this video, I’ll show you how to prepare an unmanaged PowerLinux™ server to install Linux using agraphics card and monitor. An unmanaged server does not use system management interfaces like HMCor IVM.

You'll need a graphics monitor, a USB keyboard, a USB mouse, power cables, an ethernet cable, and theLinux installation media.

This video illustrates installing Linux on an 8246-L2C IBM PowerLinux 7R2 server.

You'll be following these steps. The video redisplays the list of steps along the way.

Installing Linux on Power Systems servers 3

http://www.youtube.com/watch?v=7-rTdxrOqR0

http://www.youtube.com/watch?v=WnZaEenl2hw

http://www.youtube.com/watch?v=UUPQe41bh_k

http://www.youtube.com/watch?v=EMp7NIaR6KY

http://www.youtube.com/watch?v=WJN2f6__TeY

http://www.youtube.com/watch?v=-NwL52Nrw70

To install the PowerLinux server in a rack, see the information located in the Systems HardwareInformation Center. When installed in a rack, the front of the server looks like this. The back of the serverlooks like this. Note the orange power supply shipping bracket, which you must remove beforesupplying power to the server.

Connect the graphics monitor cable by plugging it into the graphics card in the back of the server.

Connect the USB keyboard by plugging it into one of the two USB ports in the back of the server.

Connect the USB mouse by plugging it into the other of the two USB ports in the back of the server.

Connect a network cable from the network router with a DHCP server to the eth0 port of the networkinterface card on the back of the server, which is typically the top-most port. When the Linux installerruns, it will automatically configure the server network settings with information obtained from theDHCP server.

Verify that the power cables and supplies match the plug and voltage requirements of the server. If youhave not already done so, remove the power supply shipping brackets. Install the power cables in theback of the server by first pushing in the power modules. Then, plug the cables into the power modules.

Now it's time to power on the server. Locate the control panel in the front of the server. Left to right, ithas a round, white power button, 3 LEDs, a USB port, another LED, and a rectangular button that ejectsthe control panel from the body of the server. Wait for the power LED, which is the leftmost, to beflashing green.

Press the round power button with an object that allows you to hold it in until the power LED is solidgreen, which indicates the system is powering on. Press the eject button so that the control panel is nolonger completely in the server body, and pull it toward you until you can swivel it downward.

Signs that the system is powering on include reference codes appearing on the control panel display, andthe sound of the cooling fans operating.

Insert the Linux installation media into the DVD tray on the front of the server. If the tray eject buttondoes not eject the tray, push a paper clip into the hole on the front of the tray to eject it manually.

Now it's time to boot the installer for your Linux distribution.

If prompted, press the appropriate key to select the monitor as the active console.

On the Language Keyboard Selection Menu, select option 3 to continue booting.

On the License Agreement Menu, assuming you want to accept the printed license agreement providedwith the server, select option 1 to accept it.

Type the password for the FSP admin account, and press Enter. The default password depends on howyou ordered your server. If you ordered your server preloaded, the admin password is “passw0rd”,spelled “p-a-s-s-w-0-r-d”. If you ordered it without a preload, the admin password is “admin”, spelled“a-d-m-i-n”. Either way, the letters in the password are all lowercase.

You are now in the System Management Services (or SMS) menus.

On the SMS Main Menu, select option 5 to select boot options.

On the Multiboot menu, select option 1 to select the boot device.

On the Select Device Type menu, select option 7 to list all devices.


If you don't see the CD-ROM device in the list, press the N key to display the next page in the list. Whenyou see the CD-ROM device in the list, type its corresponding device number, and press Enter to select it.

On the Select Task menu, select option 2 to select a normal mode boot.

Finally, select option 1 to confirm that you want to exit SMS and boot the server. The server boots to theboot prompt for the installer of your Linux distribution.

To boot the installer, type the word linux for Red Hat, or the word install for SuSE, and press Enter.This video shows Red Hat.

After a while, you are prompted to test the installation media, or skip the test. This video skips that test.

Next, you are presented with the first menu of installer. Proceed to install Linux as usual.

If you're installing Red Hat, you may encounter an issue where the installer requires more memory thanthe firmware has allocated to the installer. The memory issue appears in the form of the kernel failing toload, and your being presented with an Open Firmware prompt, which looks like a zero and a rightangle bracket. If you see this, proceed as follows.

Type printenv real-base and press Enter to display the value of the real-base open firmwareenvironment variable value. The value is likely a 2 followed by six zeros. Change the value by typingsetenv real-base c followed by five zeros, and pressing Enter. Verify that the new value has been set byrunning the previous printenv command again.

Finally, type reset-all and press Enter. This instructs open firmware to reboot the server, leading to theboot prompt for the installer.

Once again, type the word linux in lowercase, and press Enter to boot the installer and proceed to installLinux.

We’d love to hear your feedback about this video. To get involved in the conversation, join thePowerLinux Community on IBM developerWorks®. You can find a quick start document describing thisprocess. You can find more information about PowerLinux in the IBM Linux Information Center. You canfind complete information about the 8246-L2C IBM PowerLinux 7R2 server in the IBM Systems HardwareInformation Center.

IBM PowerLinux Linux installation quick start without a graphics cardvideo transcriptThe following is a transcript of the spoken content of the IBM PowerLinux Linux installation quick startwithout a graphics card video.

In this video, I’ll show you how to prepare an unmanaged PowerLinux server to install Linux using aserial console emulator. An unmanaged server does not use system management interfaces like HMC orIVM.

You'll need a serial console emulation environment consisting of a Linux or Windows PC, a serial to RJ45cable, a serial console emulator, and a VNC client.

The VNC client is important because Linux installers sometimes differentiate between a text-mode installand a graphics-mode install, and the graphics-mode install typically results in the installation of a morerobust set of packages.

You'll also need power cables, an Ethernet cable, and the Linux installation media.


This video illustrates installing Linux on an 8246-L2C IBM PowerLinux 7R2 server using the PuTTYterminal emulator and the RealVNC VNC client on a PC running Windows.

You'll be following these steps. The video redisplays the list of steps along the way.

To install the PowerLinux server in a rack, see the information located in the Systems HardwareInformation Center.

When installed in the rack, the front of the server looks like this. The back of the server looks like this.Note the orange power supply shipping bracket, which you must remove before supplying power to theserver.

If the PowerLinux server contains any graphics cards, you must remove them to prevent the Linuxinstaller from possibly attempting to switch the console from the serial console to a graphics monitor.

Verify that the power cables and supplies match the plug and voltage requirements of the server. If youhave not already done so, remove the power supply shipping brackets. Install the power cables in theback of the server by first pushing in the power modules. Then, plug the cables into the power modules.

Connect the serial to RJ45 cable. The serial end plugs into the PC. The RJ45 end plugs into the S1 port onthe back of the server.

Attach a network cable from the network router with a DHCP server to the eth0 port of the networkinterface card on the back of the server, which is typically the top-most port.

Now it's time to set up the terminal emulator for the console.

First, verify that the green power LED on the control panel is flashing.

Configure the serial console emulator application for a speed of 19,200 bits per second, with 8 data bits, 1stop bit, and no parity. If the application is running on Windows, specify the COM port associated withthe serial port of the PC, which is most likely COM1.

Finally, start the console.

Configure the Flexible Service Processor, or FSP, for basic information like date and time, adminpassword, and how to boot when powering on the server.

If you don't yet see the FSP login prompt, press Enter.

The default FSP User ID is “admin”, spelled “a-d-m-i-n”. The default password depends on how youordered your server. If you ordered your server preloaded, the admin password is “passw0rd”, spelled“p-a-s-s-w-0-r-d”. If you ordered it without a preload, the admin password is “admin”, spelled“a-d-m-i-n”. In all cases, the letters in the password are all lowercase.

You're then prompted for the User ID whose password you must change. Enter “admin”, enter thecurrent admin password, and enter the new admin password twice. Be sure you're paying attention tothe password you're entering, and write it down immediately.

Once the new password is established, press Enter to continue. You are prompted for the number ofcolumns and lines the FSP should consider your console having. The defaults are 80 columns and 24lines. Supplying these brings you to the main menu, which shows your system name, version, andprimary FSP task options.

On the main menu, select option 4 to view and change the system configuration.


On the system configuration menu, select option 3 to configure system date and time.

On the Time of Day menu, select either option to change them from their current values. If you'resatisfied with the current values, select option 98 to return to the System Configuration menu. From theSystem Configuration menu, select option 98 to return to the main menu.

To install an operating system, you must configure the FSP to boot your server to the firmware servicesthat will give you the ability to specify a boot device and kernel boot options.

On the Main Menu, select option 1 to select Power/Restart Control.

On the Power/Restart Control menu, select option 1 to select Power On/Off System.

On the Power On/Off System menu, the AIX/Linux partition boot setting, which is option 4, shouldhave a value of “boot to SMS menu”. If it doesn't, select option 4 to change it.

On the AIX/Linux partition mode boot menu, select option 3 to change this setting to “boot to SMSmenu”. You are returned to the Power On/Off System menu.

Now it's time to power on the server from the FSP.

Continuing on the Power On/Off System menu, select option 8 to power on your server. The FSP tellsyou that the system is powering on, and that you should press Enter to continue.

You are returned to the Power On/Off System menu.

After a few moments, you are automatically logged out of the FSP as the server is being powered on.Signs that the system is powering on include reference codes appearing in the console and on the controlpanel display, the sound of the cooling fans operating, and the green power LED on the control paneltransitioning from flashing green to solid green.

Eventually, you are prompted to select your console going forward. Press the recommended key tocontinue using the serial console you've been using.

The server firmware displays the Language Selection Menu. Unless you want to change the defaultcurrent language, select option 2 to continue boot.

Assuming you want to accept the printed license agreement provided with the server, select option 1 toaccept it.

Your server boots. Press the 1 key during the bootup screen to enter the SMS menus.

On the Language Selection Menu, change the language if you desire, or select option 2 to continue.

Type the FSP admin password that you set earlier, and press Enter.

This brings you to the SMS Main Menu.

Insert the Linux installation media into the DVD tray on the front of the server. If the tray eject buttondoes not eject the tray, push a paper clip into the hole in the front of the tray to eject it manually.

Now you're ready to set up to boot the Linux distribution installer for a VNC graphical install.

On the Main Menu, select option 5 to select boot options.

On the Multiboot menu, select option 1 to select install/boot device.


On the Select Device Type menu, select option 7 to list all devices.

If you don't see the CD-ROM device in the list, press the N key to display the next page in the list.

Continue to press the N key until you see the CD-ROM device.

When you see the CD-ROM device in the list, type its corresponding device number, and press Enter toselect it.

On the Select Task menu, select option 2 to select a normal mode boot.

Finally, select option 1 to confirm that you want to exit SMS and boot the server.

Don't enter the SMS menus as you did previously. Allow the boot to proceed until you see the installerwelcome screen and boot prompt.

If you're installing Red Hat, you may encounter an issue where the installer requires more memory thanthe firmware has allocated to the installer.

To boot the Red Hat installer, type linux vnc=1 and press Enter.

The memory issue appears in the form of the kernel failing to load, and your being presented with anOpen Firmware prompt, which looks like a zero and a right angle bracket. If you see this, proceed asfollows.

Type printenv real-base and press Enter to display the value of the real-base open firmwareenvironment variable value. The value is likely a 2 followed by six zeros.

Change the value by typing setenv real-base c followed by five zeros, and press Enter.

Finally, type reset-all and press Enter. This instructs Open Firmware to reboot the server.

If you performed the workaround while installing Red Hat, or you were installing SuSE and thus did notneed the workaround, you're now ready to proceed with the installation as usual.

At the boot prompt, type linux vnc=1 for Red Hat, or install vnc=1 vncpassword=your-password forSuSE, and press Enter. This video shows Red Hat.

The Linux kernel boots, and with it the initial stages of the installer, which asks you which networkingdevice to use.

Having plugged the network cable into the top port of the network interface device earlier, select the eth0device.

There is sometimes a mismatch between the menu items and where the cursor rests in the menu.

The installer probably expected a larger console window.

Experiment with the tab key to get a feel for where the first device in the list actually is beforeproceeding.

After finding the eth0 device, press the space key to select it.

Then, press the tab key until it is on or near the OK button in the menu, and press the space key tocontinue.


You can see how the console might display menu items and buttons as being slightly displaced fromwhere they are actually selected.

The installer obtains networking information from the router DHCP server, and prompts for the option totest the media before installation. This video skips that test.

Eventually, the installer displays the hostname and port information you need to connect your VNCclient to the installer's VNC server.

Connect the VNC client to the host and port displayed by the installer.

Don't forget the port number, or the colon character between the hostname and the port number.

You're now ready to complete the Linux installation by following the installer instructions displayed inthe VNC client.

In this video, the installer screens captured were larger than the screen capture size, and not resizeable, sothe video shows scrollbars being used to navigate the installer screens in a way that you won't have to.

You're prompted for basic information like this whether this is a fresh install, the server short hostname,the timezone, and the root password.

Eventually, you get to the point where the rest of the installation is automatic, the installation completes,and you can log in to Linux as root on your server.

We’d love to hear your feedback about this video. To get involved in the conversation, join thePowerLinux Community on IBM developerWorks.

You can find a quick start document describing this process.

You can find more information about PowerLinux in the IBM Linux Information Center.

You can find complete information about the 8246-L2C IBM PowerLinux 7R2 server in the IBM SystemsHardware Information Center.

IBM PowerLinux Linux installing VIOS video transcriptThe following is a transcript of the spoken content of the IBM PowerLinux Linux installing VIOS video.

Let me show you how to install the Virtual I/O Server, or VIOS.

I'll assume you have first set up a serial console using the cabling and applications you're used to, andplaced the first VIOS disc in the DVD-ROM tray.

Login to the Advanced System Management Interface or ASMI web interface as admin in a browser.

Expand Power/Restart Control in the navigation frame.

Click Power On/Off System.

Change the AIX/Linux partition mode boot setting to Boot to SMS menu.

Click Save settings and power on.

ASMI shows that the system is powered on, and displays power-on related settings.


Expand System Information.

Click Real-time Progress Indicator.

The progress indicator appears as a new browser window.

It mirrors the system's physical control panel display.

Note the changing status codes.

Switch window focus to the console.

Select option 2 to continue to password entry.

Enter the ASMI padmin password and press Enter.

Select option 5 to Select Boot Options.

Select option 1 to Select Install/Boot Device.

Select option 7 to List all Devices.

Select the CD-ROM device.

Select option 2 for Normal Mode Boot.

Select option 1 to exit SMS.

The VIOS installer boots.

Define the system console by selecting the recommended number and pressing Enter.

Select the installation language and press Enter.

Select option 2 to Change/Show Installation Settings and Install.

Select option 0 to Install with the settings listed above.

Go back to ASMI in the browser window.

Click Power On/Off System.

Change the AIX/Linux partition mode boot setting to Continue to operating system.

Click Save settings.

Go to the console window.

After a while you are prompted to change the VIOS installation discs.

Insert the second disc, and press Enter.

VIOS continues to install.

Then VIOS reboots the system.


Simply let the system reboot.

VIOS starts.

Wait for a login prompt.

Login to the VIOS server as padmin.

Enter a new password for the padmin account.

Accept the software maintenance terms and conditions by selecting 'a' and pressing Enter.

Accept the license by entering "license -accept" and pressing Enter.

Configure networking with the cfgassist command.

Use the arrow keys to navigate the cursor, and press enter to select an option.

Select the VIOS TCP/IP Configuration option.

Select the en0 network interface.

Fill in all of the entry fields:v short hostnamev internet addressv network maskv default gatewayv nameserver internet addressv and nameserver domain name

Press enter to make the changes.

Verify that the changes were made.

Press the escape key followed by the zero key to exit the cfgassist menu dialog.

Congratulations, you have successfully installed and configured VIOS.

Now it's time to configure some virtualization settings in the Integrated Virtualization Manager, or IVM.

Go to the VIOS IP address in a browser, using the https protocol in the URL.

Login to IVM as padmin.

Click View/Modify Partitions.

Note that the VIOS or management partition is already listed.

Click View/Modify Virtual Ethernet.

Click Initialize Virtual Ethernet.

Click Apply.


Virtual ethernet is initialized. Note the confirmation at the top of the window.

Some installations require networking outside the virtual network you initialized.

Establishing such an external connection is called bridging.

To create a virtual ethernet bridge, click on the Virtual Ethernet Bridge tab.

Select the physical adapter to bridge.

Click Apply.

The bridge is established. Note the confirmation at the top of the window.

Visit these links for an installation flow chart and more details about configuration options.

IBM PowerLinux Linux create LPAR video transcriptThe following is a transcript of the spoken content of the IBM PowerLinux Linux create LPAR video.

Creating a logical partition is easy in the Integrated Virtualization Manager, or IVM. I'll show you how inIVM 2.2.

First, log into IVM as padmin.

Verify that you are in the View/Modify Partitions screen.

Click on the Create Partition button.

Name the new partition.

Click next. Be sure not to click Finish until the very end of the dialog.

Configure memory assigned to the partition and click Next. I'll set it to 2 Gigabytes.

Configure processor settings for the partition, and click Next. I'll use the defaults.

Configure virtual ethernet for the partition by selecting one or more devices, and clicking Next. I'll usethe defaults.

Create a virtual disk for the partition, and click Next.

Set the size of the virtual disk, and click Next. I'll set it to 40 Gigabytes.

Configure optical devices for the partition.

Click to show available physical optical devices. A DVD-RAM drive is available. Select it if you want it tobe available to the partition.

Click to show available virtual optical devices.

If you created virtual optical media in the management partition's media library, click on modify to seeand select it.

Select the virtual optical device if you want it to be available to the partition.


The optical device assignments and settings can be changed after the LPAR is created.

Click Next.

Verify the partition configuration settings.

Click Finish.

The new partition is created. You can see some of its settings in the partition list.


IBM PowerLinux Linux installing Red Hat Enterprise Linux in anIVM-managed LPAR from optical media video transcriptThe following is a transcript of the spoken content of the IBM PowerLinux Linux installing Red HatEnterprise Linux in an IVM-managed LPAR from optical media video.

Installing Red Hat Enterprise Linux in a logical partition is easy in the Integrated Virtualization Manager,or IVM. I'll show you how in IVM 2.2, with Red Hat 6.3.


If the partition needs to communicate outside the private virtual network, click Verify/Modify VirtualEthernet and then the Virtual Ethernet Bridge tab. If a physical adapter isn't listed, select one and clickApply to establish an external network bridge.


Click the partition in which to install Linux. A new dialog window appears, showing that partition'sconfiguration settings.

Click the Optical/Tape Devices tab.

Click Physical Optical Devices and Virtual Optical Devices to expand those sections.

Select the physical optical device and deselect any virtual optical devices.

Click OK.

Check the box next to the partition to select it.

Click Open terminal window under the More Tasks pulldown.

Log in as padmin to authenticate to IVM and complete opening the terminal.

Switch the window focus to IVM.

Select the partition if it isn't still selected.

Click Activate.

Confirm that you want to activate the partition by clicking OK.

Quickly return to the console and press the 1 key while the boot options are being listed.


This selects the SMS Menus.



Select option 7 to List All Devices.

Place the installation disk in the disk tray, and select the CD-ROM device.



Let the partition boot without interruption.

At the boot prompt, type linux vnc=1 vncpassword=yourpassword as one line, and press Enter.

The installer boots.

Unless you want to test the installation media, tab to the word Skip and press Enter.

The installer launches a VNC server.

Start a VNC client and connect to the server with the connection information displayed, and clickConnect.

Enter the password that you set at the installer boot prompt, and click OK.

I'll show a simple default install.

Click Next to begin the installation.

Select the installation language, and click Next.

Select the type of storage devices, and click Next.

Verify the virtual disk is appropriate, and click Yes, discard any data.

Enter the short hostname.

If you want to configure static network information, click Configure Network. I'll skip that and letDHCP obtain the network information.

Click Next.

Select the timezone, and click Next.

Provide a root password, and click Next.

Select an installation disk usage type of “Use All Space”, and click Next.

Confirm that you want to configure the virtual disk by clicking Write changes to disk.

System configuration begins.


Select the installation type you want, and click Next.

The installation is performed.

Red Hat is installed.

Click Reboot to change the boot device.

Quickly return to the console.

Press the 1 key while the boot options are listed.


Select option 2 to Configure Boot Device Order.

SMS boot device order is analogous to PC BIOS boot priority.

Select option 1 to Select 1st Boot Device.


Select the virtual hard disk on which Linux was installed.

Select option 2 to Set Boot Sequence: Configure as 1st Boot Device.

The hard disk is now the first boot device.

Select option x followed by option 1 to exit SMS.

The partition reboots from the virtual hard disk containing Linux.

Let it reboot without interruption.

Login as root with the password supplied during the install.

You can run ifconfig -a to verify that the virtual ethernet device was configured.

Switch back to the IVM window and click View/Modify Partitions.

Note that the partition is now running Linux.


IBM PowerLinux Linux installing SUSE Linux Enterprise Server in anIVM-managed LPAR from optical media video transcriptThe following is a transcript of the spoken content of the IBM PowerLinux Linux installing SUSE LinuxEnterprise Server in an IVM-managed LPAR from optical media video.

Installing SUSE Linux Enterprise Server in a logical partition is easy in the Integrated VirtualizationManager, or IVM. I'll show you how in IVM 2.2, with SLES 11.



If the partition needs to communicate outside the private virtual network, click Verify/Modify VirtualEthernet and then the Virtual Ethernet Bridge tab. If a physical adapter isn't listed, select one and clickApply to establish an external network bridge.


Click the partition in which to install Linux. A new dialog window appears, showing that partition'sconfiguration settings.

Click the Optical/Tape Devices tab.

Click Physical Optical Devices and Virtual Optical Devices to expand those sections.

Select the physical optical device and deselect any virtual optical devices.

Click OK.

Check the box next to the partition to select it.

Click Open terminal window under the More Tasks pulldown.

Log in as padmin to authenticate to IVM and complete opening the terminal.

Switch the window focus to IVM.

Select the partition if it isn't still selected.

Click Activate.

Confirm that you want to activate the partition by clicking OK.

Quickly return to the console and press the 1 key while the boot options are being listed.

This selects the SMS Menus.




Place the installation disk in the disk tray, and select the CD-ROM device.



Let the partition boot without interruption.

At the boot prompt, type install vnc=1, and press Enter.

The installer boots.

Enter a password for VNC.

Select option 1 to automatically configure network settings via DHCP.


The installer launches a VNC server.


Enter the VNC password that you set earlier, and click OK.

Check the box next to I Agree to the License Terms, and click Next.

Click Next to skip the media check.

I'll show a simple default install.

Select an installation mode of New Installation, and click Next.

Select a timezone, and click Next.

Verify the installation settings, and click Install.

Click I Agree to confirm the agfa-fonts package license.

Click Install.

System configuration and package installation begins.

Click OK to reboot the system.

Return to the console.



The installer launches a VNC server again.


Enter the VNC password that you set earlier, and click OK.

Enter a password for the root account, and click Next.

Click Next to accept the hostname and domain name obtained via DHCP.

Click Next to accept the network configuration.

Select whether or not to test the internet connection, and click Next.

Review the installation overview, and click Next.

Select the Local user authentication method, and click Next.

Click Next and then Yes to skip adding a new local user.

Read the release notes, and click Next.


SLES installation is complete. Click Finish.



Log in as root with the password supplied during the install.

You can verify the hostname and IP address.

Switch back to the IVM window and click View/Modify Partitions.

Note that the partition is now running Linux.


Preparing to install the Linux operating systemLearn how to prepare for installing a Linux distribution by completing these planning tasks.

Before you install Linux, find information for your hardware. :v See IBM Linux on Power Systems documentation for information that you can use throughout the

entire initial setup of your server.v See Server upgrades and data migration for information about migrating or upgrading to a new

hardware release, upgrading your server model, or upgrading to a new hardware feature.v See IBM PowerKVM to plan for PowerKVM on your system.v See Getting started with PowerVM to plan for PowerVM on your system.

Next, visit the Linux on IBM site before you begin to install Linux on your IBM Power Systems server.This link provides the latest information, fixes, and procedures that might help you avoid problemsduring the installation of Linux on IBM Power Systems servers.

Connecting to your serverBefore installing Linux, you need to establish a connection to your server. This connection can be througha management interface such as HMC or IVM, through a console connection, or, if you have a graphicsadapter, by connecting a monitor and keyboard.

Connecting to a management interface

To connect to your server to a management interface, see the following topics in the Hardwareinformation center:v Hardware Management Console: http://www.ibm.com/support/knowledgecenter/POWERLINUX/

p7eedl/p7eedcableandsethmc.htmv Integrated Virtualization Manager: http://www.ibm.com/support/knowledgecenter/POWERLINUX/

p7eedl/p7eedcableandsetivm.htm

Connecting through a serial console

To connect a serial console to your system, connect your laptop or PC to the serial connection port 1 onthe server and set your terminal emulator communications to use a 19200 baud with data bits of 8, aparity of None, and stop bits of 1.


http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/info/LinuxAlerts.html

Connecting through the graphics adapter

To connect to your server through the graphics adapter, follow these steps:1. Locate the graphics adapter on the back of the server.2. Connect a standard monitor to the graphics adapter.3. Connect a keyboard and mouse to the USB ports.

Powering on the serverYou can power on your Power Systems server using the power button, a console connection, or theAdvanced System Management Interface (ASMI) web interface.

Using the power buttonYou can use the white power button, located on the front of the server, to power on your system.

Procedure1. Connect the power cables for the server. For more information, see the Connecting the power cables

to the system topic at http://www.ibm.com/support/knowledgecenter/8246-L1C/p7eedl/p7eed_plug.htm.After you connect the power cables, the firmware boots. Wait for a few minutes for this process tocomplete. Look for the green power LED on the control panel to start flashing, indicating that it isready to use, and for the prompt "01 N V=N" to appear on the display. For more information, see theControl Panel topic.

2. After the control panel prompt appears, power on the server by pressing and holding the whitepower-on button on the front of the control panel for 3 seconds.As the system powers up, you might notice the following:v System reference codes appear on the control panel display while the system is being started.v The power LED continues to flash and speed up.v The system cooling fans are activated after approximately 30 seconds and begin to accelerate to

operating speed.v The power LED on the control panel stops flashing and remains on, indicating that system power is

on.When the system has completely powered on, enter the SMS menu to select a boot option.

Using a consoleYou can power on the system by connecting to the FSP using a console.

Procedure1. Connect your laptop or PC to the serial connection port 1 on the server using the serial console.2. Set your terminal emulator communications to use a 19200 baud with data bits of 8, a parity of None,

and stop bits of 1.3. Connect an Ethernet cable to the top network port on the back of your system and to your network.4. Connect the power cables for the server. For more information, see the Connecting the power cables

to the system topic at http://www.ibm.com/support/knowledgecenter/8246-L1C/p7eedl/p7eed_plug.htm.After the power cables are connected, the firmware boots. Wait for a few minutes for this process tocomplete. Look for the green power LED on the control panel to start flashing, indicating that it isready to use, and for the prompt 01 N V=N to appear on the display. For more information, see theControl Panel topic.

5. The first time you connect to the FSP, enter the default user and password:


v User ID: adminv Password: admin

After logging in, you must change the password. Be sure to remember this password! After changingthe password, the firmware main menu appears.

6. Set the date and time for your hardware.a. From the main menu, select System Configuration->Time of Day.b. Verify or change to the correct date and time.

7. Set or verify the power on parameters for your system.a. From the main menu, select Power/Restart Control->Power On/Off System.b. Set AIX/Linux partition mode boot to Boot to SMS menu.

8. Power on the system by selecting the Power On from Power On/Off System menu.As the system powers up, you might notice the following:v System reference codes appear on the control panel display while the system is being started.v The power LED continues to flash and might speed up.v The system cooling fans are activated after approximately 30 seconds and begin to accelerate to


on.When the system has completely powered on, you are asked if you want to continue using theconsole. Enter 0 to continue using the console.

Using the ASMI web interfaceYou can power on the system by connecting to the Flexible Service Processor (FSP) using the AdvancedSystem Management Interface (ASMI) web interface.

Before you begin

Before connecting the power cables for the server, connect an Ethernet cable to the top network port onthe back of your system and to your network.

For information about accessing ASMI by setting your PC or notebook to the default IP address of theserver, see the Connecting your server to a PC or notebook topic at http://www.ibm.com/support/knowledgecenter/8246-L1C/p7hbyl/areaaconnectpc.htm.

About this task

Procedure1. Connect the power cables for the server. For more information, see the Connecting the power cables

to the system topic at http://www.ibm.com/support/knowledgecenter/8246-L1C/p7eedl/p7eed_plug.htm.After the power cables are connected, the firmware boots. Wait for a few minutes for this process tocomplete. Look for the green power LED on the control panel to start flashing, indicating that it isready to use, and for the prompt 01 N V=N to appear on the display. For more information, see theControl Panel topic.

2. Open a web browser and connect to the ASMI web interface for your server. For information aboutconnecting to the ASMI web interface, see Accessing ASMI through a web browser

3. The first time you connect to the FSP, enter the default user and password:v User ID: adminv Password: admin


After logging in, you must change the password. Be sure to remember this password! After changingthe password, the firmware main menu appears.

4. In the navigation area, expand Power/Restart Control and select Power On/Off System.5. Set the boot settings for your server.6. Click Save settings and power on.

As the system powers up, you might notice the following:v System reference codes appear on the control panel display while the system is being started.v The power LED continues to flash and might speed up.v The system cooling fans are activated after approximately 30 seconds and begin to accelerate to


on.

Specifying a boot methodUse this information to specify a boot method from the SMS menu.

Before you begin

Before you follow these steps, you need to connect to the system using either a monitor and keyboard ora console connection. Your system also needs to be powered on.

Procedure1. At the Boot selection window, enter 1 to select the SMS Menu.2. At this time, you can insert the distribution media into the disk drive.3. Enter 2 to Continue to password entry on the Language selection menu. Enter admin4. On the main SMS menu, enter 5 to select the Select Boot Options option.5. Enter 1 to select Install/Boot Device.6. Enter 7 to view all of the available boot devices.7. Enter the number corresponding to the device you want to use.8. Enter 2 to perform a Normal Mode Boot.9. Enter 1 to leave the SMS menu and to start the boot process.

Complete your Linux installationUse these tasks to complete your Linux installation.

Before you can complete your Linux installation, you need complete these tasks:1. “Connecting to your server” on page 182. “Powering on the server” on page 193. “Specifying a boot method”

Complete installation on system with graphical capabilitiesYou can install Red Hat Enterprise Linux or SUSE Enterprise Linux Server distributions using either thegraphical or text method. Both Red Hat and SUSE recommend using the graphical installer. Use theseinstructions to complete your Linux installation on a system that has graphical capabilities.


Before you begin

Before you can install Linux, you need complete these tasks:1. “Connecting to your server” on page 182. “Powering on the server” on page 193. “Specifying a boot method” on page 21

About this task

After you have completed the prerequisites, follow these steps:

Procedure1. At the boot prompt from the installer, type linux to install Red Hat Enterprise Linux or install to

install SUSE Enterprise Linux Server and press Enter. The kernel will begin loading.2. Follow the installer screens to install Linux.

For specific installation instructions for Red Hat Enterprise Linux, see Red Hat ProductDocumentation at https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/.For specific installation instructions for SUSE Linux Enterprise Server, see SUSE Documentation athttps://www.suse.com/documentation/.

Complete installation using VNCIf your system does not have a graphical capabilities or you are installing Linux on a partition, you canstill take advantage of a graphical installation by using VNC to perform the Linux installation.

Before you begin


About this task


Procedure1. At the boot prompt from the installer, type linux vnc to install Red Hat Enterprise Linux or install

vnc=1 vncpassword=abc12345 to install SUSE Linux Enterprise Server and press Enter. The kernel willbegin loading.Continue the installation by setting up a VNC session.

2. On the Network device window, select eth0 as your network device. Select OK and enter.3. If you are installing your server from media that you created from downloading an ISO, you can

perform a media check to validate the installation media. Select OK to test the media. Select Skip tocontinue with the installation.

4. After the system has started the VNC server, you will see a message to connect your VNC clientfollowed by an IP address. Take note of this IP address.

5. Start your VNC client on your laptop or PC.6. Enter the IP address from the system as your VNC Server. Add :1 to the end of the IP address.7. Click Connect.8. Complete the installation by following the installer screens to install Linux.


https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/


https://www.suse.com/documentation/

For specific installation instructions for Red Hat Enterprise Linux, see Red Hat ProductDocumentation at https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/.For specific installation instructions for SUSE Linux Enterprise Server, see SUSE Documentation athttps://www.suse.com/documentation/.

Installing Virtual I/O Server and configuring the IntegratedVirtualization ManagerWhen you install the Virtual I/O Server (VIOS) without connecting to a Hardware Management Console(HMC), VIOS automatically creates a management partition to use the Integrated Virtualization Manager.

Before you begin


About this task


Procedure1. After the boot process starts, confirm the console by entering a 1 and pressing Enter.2. Select a language for the installation and press Enter.3. Select Change/Show Installation Settings and Install.4. Verify your settings. If your settings are correct, type 0 and then press Enter.

The installation begins. After a while, you are prompted to insert the second disk. After theinstallation is complete, the system restarts and the login prompt is displayed.

5. Log in to the management partition with the user ID: padmin.6. When prompted, change the login password to a secure password.7. Press Enter to accept the VIOS maintenance terms and conditions.8. Accept the Virtual I/O Server license agreement by using the license command: license -accept.

For more information about using this command, see Virtual I/O Server and IVM commands.9. Configure the TCP/IP connection for the Virtual I/O Server management partition. You must

configure TCP/IP before you can perform any dynamic logical partitioning operations.v Using the cfgassist menu dialog:a. Run the cfgassist command to launch the cfgassist menu dialog.b. Using the arrow keys to move and Enter to select, select VIOS TCP/IP Configuration.c. Select en0 network interface.d. Enter values for the following fields:v Hostnamev Internet ADDRESSv Network MASKv Default Gatewayv Internet ADDRESSv DOMAIN Name

e. Press Enter to set the values.f. Verify that the command ran successfully.




https://www.suse.com/documentation/

g. Press ESC and 0 to exit the cfgassist dialog.v Using the command interface:a. Enter lstcpip –adapters to display a list of Ethernet adapters.b. If you are unsure of which physical adapter is referred to by which interface, enter the following

command to get the physical location code: lsdev -dev entx -field name description physlocstatus -fmt , where entx is a specific interface. Notice the space before the comma. Thiscommand returns a physical location code, similar to the following location code:U78AB.001.WZSGRE5-P1-C7-T1

Look for the physical slot (P1), the slot number (C7), and the port number (T1).c. Use the mktcpip command to configure TCP/IP for a specific adapter. For example: mktcpip

-hostname fred -inetaddr 9.5.4.40 -interface en0 -start -netmask 255.255.255.128-gateway 9.5.4.1 -nsrvaddr 9.10.244.200 -nsrvdomain austin.century.com. This commandassigns an IP address to the en0 interface.

d. Run the lstcpip -stored command to verify the configuration. You should see output similar tothis example:attributes: en0

IPv4 address = 9.5.4.40Network Mask = 255.255.255.128State = up

e. Run the lstcpip –routtable command to verify routing.10. Open a web browser window, and connect using the HTTP or HTTPS protocol to the IP address that

was assigned to the Integrated Virtualization Manager during the installation process. For example,enter https://123.456.7.890 in your web browser, where 123.456.7.890 is the IP address that isassigned to the Integrated Virtualization Manager.

11. Enter the default user ID of padmin, and enter the password that you defined during the installationprocess.

12. In the Integrated Virtualization Manager interface, select View/Modify Virtual Ethernet.13. Click Initialize Virtual Ethernet. A virtual Ethernet provides Ethernet connectivity among the

partitions.14. Click Apply.15. If your installation requires external networking, create a virtual Ethernet bridge:

a. Select Virtual Ethernet Bridge.b. Select the physical adapter to bridge.c. Click Apply.

Additional installation methodsThere are several additional methods that you can use to install Linux on your system. This topiccontains some of the methods.

Kickstart files for Red Hat Enterprise LinuxA kickstart file is a simple text file that contains configuration information for a Red Hat Enterprise Linuxinstallation. The system reads this configuration information at boot time and carries out the installationprocess without any further input from you. You can also use a kickstart file to upgrade your system to anew release.

You can create a kickstart file using the Kickstart Configurator available from Red Hat, copy a kickstartconfiguration another system, or write your own kickstart file. The Red Hat Enterprise Linux installationprocess automatically creates a kickstart file that contains the settings for the installed system. You canuse this file to repeat the installation with identical settings or modify the file to contain specificconfiguration instructions for a different system installation.


To use a kickstart file to install Red Hat Enterprise Linux, you must:1. Create a kickstart file.2. Create boot media for the kickstart file.3. Ensure that the installation tree for the distribution is available.4. Start the kickstart installation.

Elements in a kickstart file need to be in a specific order. Items that are required cannot be omitted or theinstallation program will prompt for a response. After the a response is given, the installation willcontinue.

For information about the options available for kickstart files, see the Red Hat Enterprise LinuxInstallation guide for your release at https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/.

For kickstart upgrades, the following items are required:v Languagev Installation methodv Device specification (if device is needed to perform the installation)v Keyboard setupv The upgrade keywordv Boot loader configuration

You can run a kickstart installation from any of these sources:v DVD drive: ks=cdrom:/directory/ks.cfgv Hard Drive: ks=hd:/device/directory/ks.cfgv Other Device: ks=file:/device/directory/ks.cfgv HTTP Server: ks=http://server.mydomain.com/directory/ks.cfgv HTTPS Server: ks=https://server.mydomain.com/directory/ks.cfgv FTP Server: ks=ftp://server.mydomain.com/directory/ks.cfgv NFS Server: ks=nfs:server.mydomain.com:/directory/ks.cfg

AutoYaST2 for SUSE Linux Enterprise ServerAutoYaST2 is used to automatically install SUSE Linux Enterprise Server. Configuration information isstored in an XML configuration file called an AutoyaST profile. The installer reads the profile and installsthe system based on the options given. AutoYaST only works for initial installations and cannot be usedfor upgrading.

An AutoyaST profile can be created using the Configuration Management System (CMS), editing anexisting profile, or creating a profile manually. You can also select to create an AutoYaST profile wheninstalling a system with SUSE Linux Enterprise Server. The resulting XML file can be used to create acloned system or customized to create a different system.

An AutoyaST profile can be provided locally or over a network using NFS, HTTP, TFTP, or FTP.

For more information about using AutoYaST, see SUSE Linux Enterprise Server documentation athttps://www.suse.com/products/server/technical-information/#Documentation.

Network installationYou can install Linux on your server through your network.


https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/

https://access.redhat.com/knowledge/docs/Red_Hat_Enterprise_Linux/

https://www.suse.com/products/server/technical-information/#Documentation

NFS, FTP, HTTP, or HTTPS

You can use NFS, FTP, HTTP, or HTTPS server to install Linux on your server. The server must be aseparate, network-accessible server and must provide the contents of the installation media.

For information about installing Red Hat Enterprise Linux using an NFS, FTP, HTTP, or HTTPS server,see Preparing for a Network Installation topic in the Red Hat Enterprise Server Installation Guide athttps://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-Preparing-ppc.html.

For information about installing SUSE Linux Enterprise Server using an NFS, FTP, HTTP, or HTTPSserver, see Setting Up an Installation Server Using YaST in the SUSE Linux Enterprise Server DeploymentGuide at https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec_deployment_remoteinst_instserver.html#sec_deployment_remoteinst_instserver_sles9.

AIX Network Installation Manager (NIM)

The AIX Network Installation Manager (NIM) allows you to install operating systems on one or moresystems through your network. You can install a group of servers with a common deployment orcustomize an installation for each server.

For information about installing a Linux distribution using NIM, see Network Installation Management inthe AIX information at http://www.ibm.com/support/knowledgecenter/ssw_aix_71/com.ibm.aix.install/nim_intro.htm.

IBM Linux on Power tools repositoryThe IBM Linux on Power tools repository allows administrators to use the standard Linux packagemanagement tools to deploy and maintain IBM tools on Linux on Power systems.

Note: The IBM Linux on Power tools repository is also known as the yum repository.

Installing tools on your IBM Linux on Power system can be problematic. Many tools have prerequisitesthat must be completed before installation. Tools must be installed in the correct order. The toolsrepository enables the use of your standard Linux package management tools, yum for Red Hat EnterpriseLinux and zypper for SUSE Linux Enterprise Server, to automatically install the packages you need in theorder that is required by the system.

The Linux on Power tools repository supports the following Linux distributions:v Red Hat Enterprise Linux 6v Red Hat Enterprise Linux 7v SUSE Linux Enterprise Server 11v SUSE Linux Enterprise Server 12

Fedora and CentOS are available but unsupported.

For information about installing tools for Ubuntu, see Install service and productivity tools for Ubuntu.

The tools repository provides access to the following tools:

IBM Linux on Power service and productivity toolsService and productivity tools include hardware inventory tools, hardware and service diagnosticaids, performance tools, Power RAID utilities, and installation aids for Linux on Power

The service and productivity tools packages included in the repository vary according todistribution and hardware platform.


https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/ch-Preparing-ppc.html

https://www.suse.com/documentation/sles11/book_sle_deployment/data/sec_deployment_remoteinst_instserver.html#sec_deployment_remoteinst_instserver_sles9

Table 1. Service and productivity tools packages included by distribution and platform

SUSE Linux Enterprise Server Red Hat Enterprise Linux

BladeCenter or Flex System (http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/suselinux/bladecenter/sles12.html)

BladeCenter or Flex System (http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/bladecenter/rhel7.html)

HMC- or IVM-managed servers (http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/suselinux/hmcmanaged/sles12.html)

HMC- or IVM-managed servers (http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/hmcmanaged/rhel7.html)

Other non-managed servers (http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/suselinux/other/sles12.html)

Other non-managed servers (http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/other/rhel7.html)

KVM guest system(http://www-14.ibm.com/webapp/set2/sas/f/lopdiags/suselinux/kvmguest/sles12.html)

KVM guest system (http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/kvmguest/rhel7.html)

KVM host system (http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/baremetal/rhel7.html)

IBM Software Development Toolkit for Linux on PowerThe IBM SDK for Linux on Power provides you with an all-in-one solution for developingsoftware on Linux on Power servers. It also provides integration of open source and IBM toolsinto a single graphical user interface.

IBM Advance Toolchain for Linux on PowerThe IBM Advance Toolchain for Linux on Power provides early and easy access to libraries andthe latest compiler technologies for Linux distributions.

Installing the tools repositoryTo use the IBM Linux on Power tools repository, download and install the ibm-power-repo RPM packageand then run /opt/ibm/lop/configure.

About this task

'To use the IBM Linux on Power tools repository, download and install the ibm-power-repo RPMpackage, and then run /opt/ibm/lop/configure.

The ibm-power-repo RPM package can be downloaded from http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/yum.html. The same package is valid for Red Hat Enterprise Linux, Fedora, CentOS,and SUSE Enterprise Linux Server.

Install the ibm-power-repo RPM package by following these steps:

Procedure1. Download the ibm-power-repo RPM package from http://www14.software.ibm.com/webapp/set2/

sas/f/lopdiags/yum.html.2. Install the ibm-power-repo RPM package. Run the command:

rpm -ivh ibm-power-repo<version number>.noarch.rpm

3. After you install the RPM package, run the following command by using root user privileges:/opt/ibm/lop/configure

4. Verify that the IBM Tools Repository is available:On Red Hat Enterprise Linux, Fedora, or CentOS Linux: yum repolist enabled.On SUSE Linux Enterprise Server: zypper lr


http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/suselinux/bladecenter/sles12.html

http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/bladecenter/rhel7.html

http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/suselinux/hmcmanaged/sles12.html

http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/hmcmanaged/rhel7.html

http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/suselinux/other/sles12.html

http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/other/rhel7.html

https://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/suselinux/kvmguest/sles12.html

http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/kvmguest/rhel7.html

http://www-304.ibm.com/webapp/set2/sas/f/lopdiags/redhat/baremetal/rhel7.html

http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/yum.html




Results

After you have installed the IBM Tools Repository, you can use it to install recommended packages foryour system.

Installing packages with the tools repositoryAfter you have downloaded and installed the IBM Linux on Power tools repository, you can use it toinstall recommended packages for Linux on Power Systems servers.

About this task

Procedure1. To install service and productivity tools, enter the following command for your server type and Linux

distribution:v Blade, HMC-managed, or IVM-managed server

Red Hat Enterprise Linux 7yum install ibm-power-managed-rhel7

Red Hat Enterprise Linux 6yum install ibm-power-managed-rhel6

SUSE Linux Enterprise Server 12zypper install ibm-power-managed-sles12

SUSE Linux Enterprise Server 11zypper install ibm-power-managed-sles11

v Unmanaged server

Red Hat Enterprise Linux 6yum install ibm-power-nonmanaged-rhel6

Red Hat Enterprise Linux 5yum install ibm-power-nonmanaged-rhel5

SUSE Linux Enterprise Server 11zypper install ibm-power-nonmanaged-sles11

SUSE Linux Enterprise Server 10zypper install ibm-power-nonmanaged-sles10

v KVM guest system

Red Hat Enterprise Linux 7yum install ibm-power-kvmguest-rhel7

Red Hat Enterprise Linux 6yum install ibm-power-kvmguest-rhel6

SUSE Linux Enterprise Server 12zypper install ibm-power-kvmguest-sles12

SUSE Linux Enterprise Server 11zypper install ibm-power-kvmguest-sles11

v KVM host system

Red Hat Enterprise Linux 7yum install ibm-power-baremetal-rhel7

SUSE Linux Enterprise Server 12zypper install ibm-power-baremetal-sles12

The following unsupported packages are also available:v KVM guest system


CentOSyum install ibm-power-kvmguest-centos

Fedorayum install ibm-power-kvmguest-fedora

v KVM host system

CentOSyum install ibm-power-baremetal-centos

Fedorayum install ibm-power-baremetal-fedora

v Blade, HMC-managed, or IVM-managed server

CentOSyum install ibm-power-managed-centos

Fedorayum install ibm-power-managed-fedora

v Unmanaged server

CentOSyum install ibm-power-nonmanaged-centos

Fedorayum install ibm-power-nonmanaged-fedora

2. To install the IBM Advance Toolchain for Linux on Power, enter the following command for yourLinux distribution:v On Red Hat Enterprise Linux: yum install advance-toolchain-at6* where advance-toolchain-at6 is

the version of IBM Advance Toolchain that you want to install.v On SUSE Linux Enterprise Server: zypper install advance-toolchain-at6* where

advance-toolchain-at6 is the version of IBM Advance Toolchain that you want to install.v On Fedora (unsupported): yum install advance-toolchain-at6* where advance-toolchain-at6 is the

version of IBM Advance Toolchain that you want to install.3. To install the IBM SDK for Linux on Power servers, enter the following command for your Linux

distribution.v On Red Hat Enterprise Linux: yum install ibm-sdk-lop.ppc64v On SUSE Linux Enterprise Server: zypper install ibm-sdk-lop.ppc64v On Fedora (unsupported): yum install ibm-sdk-lop.ppc64

Troubleshooting you Linux on Power installationFind additional information to help you troubleshoot the installation of Linux.

IBM Power Systems informationIf you have problems with a partitioned system, find troubleshooting information in the PowerSystems Information Center to determine if the problem is specific to logical partitions or if it is asystem problem. If your problem is specific to logical partitions, reference codes may help you toresolve the error. However, specific recovery actions and tasks might require the assistance ofservice support.

http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/index.jsp

IBM Linux on Power communityThis developerWorks group provides community-based information resource for Linux users onIBM PowerLinux and IBM Power Systems servers.

https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32


https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32

Linux on IBMVisit this site before you begin to install Linux on your IBM Power Systems server. This linkprovides the latest information, fixes, and procedures that might help you avoid problems duringthe installation of Linux on IBM Power Systems servers.


PDF file for Installing Linux on Power Systems serversYou can view and print a PDF file of this information.

To view or download the PDF version of this document, select Installing Linux on Power Systems servers

(about 136 KB).

Saving PDF files

To save a PDF on your workstation for viewing or printing:1. Right-click the PDF link in your browser.2. Click the option that saves the PDF locally.3. Navigate to the directory in which you want to save the PDF.4. Click Save.

Downloading Adobe Reader

You need Adobe Reader installed on your system to view or print these PDFs. You can download a free

copy from the Adobe Web site (www.adobe.com/products/acrobat/readstep2.html) .



http://www.adobe.com/products/acrobat/readstep2.html

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries.Consult your local IBM representative for information on the products and services currently available inyour area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program,or service that does not infringe any IBM intellectual property right may be used instead. However, it isthe user's responsibility to evaluate and verify the operation of any non-IBM product, program, orservice.

IBM may have patents or pending patent applications covering subject matter described in thisdocument. The furnishing of this document does not grant you any license to these patents. You can sendlicense inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

The following paragraph does not apply to the United Kingdom or any other country where suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFNON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certain transactions, therefore, thisstatement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM CorporationDept. LRAS/Bldg. 90311501 Burnet RoadAustin, TX 78758-3400U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases,payment of a fee.

The licensed program described in this document and all licensed material available for it are providedby IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement orany equivalent agreement between us.

© Copyright IBM Corp. 2013 31

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual PropertyDepartment in your country or send inquiries, in writing, to:

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

IBM may use or distribute any of the information you supply in any way it believes appropriate withoutincurring any obligation to you.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part ofthe materials for this IBM product and use of those Web sites is at your own risk.

This information contains examples of data and reports used in daily business operations. To illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to the names and addresses used by anactual business enterprise is entirely coincidental.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. If these and other IBM trademarkedterms are marked on their first occurrence in this information with a trademark symbol (® and ™), thesesymbols indicate U.S. registered or common law trademarks owned by IBM at the time this informationwas published. Such trademarks may also be registered or common law trademarks in other countries. Acurrent list of IBM trademarks is available on the Web at Copyright and trademark information atwww.ibm.com/legal/copytrade.shtml

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarksof Adobe Systems Incorporated in the United States, and/or other countries.

Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.


Notices 33

IBM®

Printed in USA

linux: installing linux on power systems servers

Documents