Vous êtes sur la page 1sur 88

Linux

Installing Linux with the IBM Installation Toolkit for PowerLinux

Linux

Installing Linux with the IBM Installation Toolkit for PowerLinux

Note Before using this information and the product it supports, read the information in Notices on page 77.

Tenth Edition (December 2013) Copyright IBM Corporation 2009, 2013. US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents
About this guide . . . . . . . . . . . v Installing Linux with the IBM Installation Toolkit for PowerLinux . . . . . . . . 1
Introducing IBM Installation Toolkit . . . . . . 1 What's new in IBM Installation Toolkit 5.5 . . . 1 Simplified Setup Tool . . . . . . . . . . 1 Supported Linux distributions . . . . . . . 2 Hardware and software requirements . . . . . 2 IBM Installation Toolkit media contents . . . . 3 Planning for IBM Installation Toolkit . . . . . . 5 IBM Installation Toolkit running modes . . . . . 7 Downloading the IBM Installation Toolkit . . . . 9 Determining a boot method . . . . . . . . 9 Creating a DVD . . . . . . . . . . . . 10 Creating and assigning a virtual optical device 10 Creating a bootable USB key. . . . . . . . 11 Configuring the boot method to be used by the system . . . . . . . . . . . . . . . . 12 Determining the location for the distribution media 13 Accessing the user interface . . . . . . . . . 13 Opening the user interface . . . . . . . . 14 Using the text interface . . . . . . . . . 14 Accessing the user interface remotely . . . . . 15 Installing a Linux distribution . . . . . . . . 15 Manually partitioning disks . . . . . . . . 18 Working with partitions or LVM logical volumes . . . . . . . . . . . . . 18 Working with software RAID arrays . . . . 19 Working with LVM volume groups . . . . 20 Creating a network installation server . . . . . 21 Configuring the boot server for IBM Installation Toolkit . . . . . . . . . . . . . . . 21 Manually configuring the boot server for IBM Installation Toolkit . . . . . . . . . . 22 Managing client systems for the boot server . . 23 Adding a client . . . . . . . . . . . 23 Editing a client . . . . . . . . . . . 24 Deleting a client . . . . . . . . . . . 25 Adding a subnet. . . . . . . . . . . 25 Editing a subnet . . . . . . . . . . . 26 Deleting a subnet . . . . . . . . . . 26 Editing DHCP headers . . . . . . . . 27 Applying changes . . . . . . . . . Manually configuring a client system for the IBM Installation Toolkit boot server . . . Managing Linux installation repositories available on the server. . . . . . . . . Adding a repository . . . . . . . . Deleting a repository . . . . . . . . Adding an exported path . . . . . . . Removing an exported path . . . . . . Manually creating a network installation repository . . . . . . . . . . . . Mounting the DVD media . . . . . Configuring the network . . . . . . . . . Updating an installed system . . . . . . . Installing IBM Installation Toolkit on a system already running Linux. . . . . . . . . Manually installing IBM Installation Toolkit using a Yum repository . . . . . . . Managing software installation repositories . . Installing IBM packages on the system . . . Updating your firmware . . . . . . . . . Cloning your system . . . . . . . . . . Cloning devices . . . . . . . . . . . Restoring devices . . . . . . . . . . Migrating an x86 server running Linux to an IBM Power Systems server . . . . . . . . . . Server Consolidation environment . . . . . Server Consolidation tool considerations. . . Supported Linux distributions for migration . Using the migration wizard . . . . . . . Creating an LPAR . . . . . . . . . . Recovering your system . . . . . . . . . Monitoring IBM Installation Toolkit tasks . . . Accessing documentation resources . . . . . Troubleshooting . . . . . . . . . . . . Known problems and workarounds . . . . Registering at IBM . . . . . . . . . . Getting customer support. . . . . . . . Error, information, and warning messages . . . 27 . 27 . . . . . . . . . 28 29 30 30 31 31 32 32 33

. 33 . . . . . . . . . . . . . . . . . . . . . 33 34 35 36 37 37 37 38 38 38 39 39 42 43 44 44 45 45 46 47 47

Notices . . . . . . . . . . . . . . 77
Trademarks . . . . . . . . . . . . . . 78

Copyright IBM Corp. 2009, 2013

iii

iv

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

About this guide


This documentation is intended for system or network administrators of Power Systems servers who want to install Linux, update firmware, perform system recovery tasks, or install service and productivity tools on their systems. This edition applies to version 5.4.1 of the IBM Installation Toolkit for PowerLinux and to all subsequent releases and modifications until otherwise indicated in new editions.

Release Notes
IBM Installation Toolkit release notes can be found on the root directory of the DVD and at http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaan/ installationtoolkitreleasenotes.htm

Support
The IBM Installation Toolkit product is not officially supported by IBM Software Support, and is provided as-is. Customers are not entitled to IBM Software Support. However, you can find support information at: https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 or go to https://www.ibm.com/ developerworks/mydeveloperworks/ and search for the Think PowerLinux group.

Copyright IBM Corp. 2009, 2013

vi

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Installing Linux with the IBM Installation Toolkit for PowerLinux


The IBM Installation Toolkit for PowerLinux provides a set of tools and functions that allow you to quickly set up Linux on PowerLinux servers.

Introducing IBM Installation Toolkit


The IBM Installation Toolkit for PowerLinux speeds up the installation of Linux, and gives you access to the IBM value-added software necessary to fully use the capabilities of the Power platform. You can use the IBM Installation Toolkit for the following actions: v Install and configure Linux on a non-virtualized Power System server. v Install and configure Linux on servers with previously-configured logical partitions (LPARs, also known as virtualized servers). v Install IBM service and productivity tools on a new or previously installed Linux system. The IBM service and productivity tools include dynamic logical partition (DLPAR) utilities. v Upgrade system firmware level on Power Systems servers. v Perform diagnostics or maintenance operations on previously installed systems. v Access documentation resources included with IBM Installation Toolkit. v Migrate a LAMP server (software stack) and application data from a System x to a System p system. A LAMP server is a bundle of open source software. LAMP is an acronym for Linux, Apache HTTP Server, MySQL relational database, and PHP (Perl or Python) scripting language.

What's new in IBM Installation Toolkit 5.5


IBM Installation Toolkit for PowerLinux 5.5 introduces the following new features.

Support for Red Hat Enterprise Linux


IBM Installation Toolkit for PowerLinux 5.5 introduces support for Red Hat Enterprise Linux 5.10 and 6.5.

Optional Linux distribution update repositories


When installing a Linux distribution using IBM Installation Toolkit, you can now specify up to three network add-on repositories. This allows you to include additional distribution updates, if available. Learn more...

New value-add package included in IBM Installation Toolkit


The rssx-utils package is now included in the IBM Installation Toolkit media. Learn more...

Simplified Setup Tool


The IBM Installation Toolkit for PowerLinux provides the IBM Installation Toolkit Simplified Setup Tool, which helps you to quickly set up open source workloads on your system. After you install the IBM Installation Toolkit, you can access the Simplified Setup Tool. The Simplified Setup Tool guides you through the process of quickly and easily configuring one or more open source workloads on your system. The workloads include:
Copyright IBM Corp. 2009, 2013

v v v v

LAMP server Mail server File and print server Network infrastructure server

You can access the Simplified Setup Tool directly through a web browser. To open the Simplified Setup Tool, point your browser to https://server IP or hostname:6060, where server IP or hostname is the IP address or host name of your system. For documentation for the Simplified Setup Tool, see Getting started with PowerLinux servers (http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaay/vploverview.htm).

Supported Linux distributions


Use this information to determine which Linux distributions are supported by the IBM Installation Toolkit. The IBM Installation Toolkit supports installation of the following Linux distributions: v Red Hat Enterprise Linux 5.9 and 5.10 v Red Hat Enterprise Linux 6.4 and 6.5 v SUSE Linux Enterprise Server 11 SP2 and SP3 Note: Software that is contained in the product can be installed and used only on the described systems. Not following these restrictions might lead to unpredictable results.

Hardware and software requirements


Before you install the IBM Installation Toolkit for PowerLinux, verify that you have the necessary hardware and software.

Hardware requirements for using the IBM Installation Toolkit


The IBM Installation Toolkit is intended for IBM Power Systems servers and IBM BladeCenter blade servers using IBM POWER7 processors. Required hardware includes the following items: v CD or DVD-ROM reader, for CD- or DVD-based installations. v Network card, for installations over the network. v Minimum of 2 GB of RAM. v Additionally, refer to your Linux distribution documentation for minimum hardware requirements.

Requirements for installing Linux using the IBM Installation Toolkit


v Linux distribution installation media for ppc64 on a DVD or ISO image file

Requirements for running IBM Installation Toolkit on a previously installed Linux system
v IBM Installation Toolkit DVD or ISO image v Linux distribution installation media for ppc64

Additional requirements and restrictions


v IBM Installation Toolkit can be used only on a system that is managed with a Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM), or on an unmanaged system with a serial console. It cannot be used on an unmanaged system with a graphics card and monitor. v To use remote access with the IBM Installation Toolkit, you need a second system with Mozilla Firefox installed.

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v IBM Installation Toolkit does not support QLogic Fibre Channel cards on POWER processor-based blade servers.

IBM Installation Toolkit media contents


The IBM Installation Toolkit for PowerLinux media contains documentation, firmware images, and value-add IBM packages. The media contents includes the following packages: devices.chrp.base.ServiceRM Service Resource Manager is a Reliable, Scalable, Cluster Technology (RSCT) resource manager that creates the Serviceable Events from the output of the Error Log Analysis tool (diagela). ServiceRM then sends these events to the Service Focal Point on the Hardware Management Console (HMC). DynamicRM Dynamic Resource Manager is a Reliable, Scalable, Cluster Technology (RSCT) resource manager that allows a Hardware Management Console (HMC) to do tasks such as dynamically add or remove processors or I/O slots from a running partition, concurrently update system firmware, and perform certain shutdown operations on a partition. esagent.pLinux IBM Electronic Service Agent for PowerLinux is a no-charge software tool that automatically and continuously monitors, collects, and periodically submits hardware problem information to the IBM Electronic Support website. It also can collect hardware, software, performance, and system configuration information, which might help IBM Support assist in diagnosing problems. IBMinvscout The Inventory Scout tool surveys one or more systems for hardware and software information. The gathered data can be used by web services such as the Microcode Discovery Service, which generates a report indicating whether installed microcode needs to be updated. ibm-java-ppc64-sdk This SDK is the IBM 64-bit SDK for Linux on Power Systems architecture, Java Technology Edition, Version 7. ibm-java-ppc-sdk This SDK is the IBM 32-bit SDK for Linux on Power Systems architecture, Java Technology Edition, Version 7. ibmPMLinux The ibmPMLinux package contains a data collector for enabling IBM Performance Management for Power Systems. PM for Power Systems enables automated performance analysis and capacity planning for PowerLinux servers. With PM for Power Systems, non-proprietary utilization and growth information can be automatically collected from the servers with logical partitions (LPARs) that you elect to monitor. You have the choice of transmitting the daily collected data to IBM on a routine basis, using IBM Electronic Service Agent for PowerLinux. To activate PM for Power Systems, you install the collector and then follow more specific instructions at the PM for Power Systems Getting started page (http://www-03.ibm.com/systems/power/support/ perfmgmt/getstarted.html). See the PM for Power Systems Overview page ( http:// www.ibm.com/system/power/support/perfmgmt) for general information about PM for Power Systems. ibm-power-managed This package includes the recommended additional software packages for managed partitions on PowerLinux servers and blade servers. A managed server is a system that is managed by an HMC or by the Integrated Virtualization Manager (IVM).

Installing Linux with the IBM Installation Toolkit

ibm-power-nonmanaged This package includes the recommended additional software packages for non-virtualized, non-managed PowerLinux servers. A non-managed server is a stand-alone system that is not used with an HMC or IVM. ibm-power-repo This package configures the system to get software package updates from the IBM Tools Repository for PowerLinux servers. For more information, refer to http:// www14.software.ibm.com/webapp/set2/sas/f/lopdiags/yum.html. iprutils This package provides a suite of utilities to manage and configure SCSI devices supported by IBM Power RAID (IPR) device driver. librtas The librtas package contains a library that allows applications to access certain functionality provided by platform firmware. This functionality is required by many of the other higher-level service and productivity tools. libservicelog The libservicelog library provides the API which servicelog uses to store, retrieve, and modify system event and error notification details. libvpd The libvpd package contains the classes that are used to access a vpd database created by vpdupdate in the lsvpd package. lpa The Large Page Analysis tool includes two programs. One program records runtime memory usage information about an application. The other generates a translation lookaside buffer (TLB) miss rate report based on the recorded memory usage information. The LPA tool tracks TLB misses by memory region within an application (heap, data, stack, text). Then the tool generates a report that shows where use of larger page size might benefit application performance. The lsvpd package contains the lsvpd, lscfg, and lsmcode commands. These commands, along with a boot-time scanning script called update-lsvpd-db, constitute a hardware inventory system.

lsvpd

nmon This tool is the Performance Analyzer for PowerLinux servers. openmpi-sles11 Open MPI is a project combining technologies and resources from several other projects (FT-MPI, LA-MPI, LAM/MPI, and PACX-MPI) in order to build the best MPI library available. This package is not automatically installed by IBM Installation Toolkit. It is shipped for those interested in manually installing openmpi on a SUSE Linux Enterprise Server 11 system. powerpc-utils-python powerpc-utils-python contains python-based utilities for maintaining and servicing PowerPC systems. ppc64-diag The Error Log Analysis tool provides automatic analysis and notification of errors reported by the platform firmware on IBM System p systems. pseries-energy System p Energy Management daemon automatically manages Linux OS settings based on system power modes. rsct.core and rsct.core.utils The RSC packages provide the Resource Monitoring and Control (RMC) functions and infrastructure needed to monitor and manage one or more Linux systems. rssx-utils This package provides utility software for IBM Flash Adapter devices.

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

servicelog The servicelog package creates a database to store system-generated events that might require service. The package includes tools for querying the database. src sst SRC is a facility for managing daemons on a system. It provides a standard command interface for defining, undefining, starting, stopping, querying status and controlling trace for daemons. The sst package is the IBM Installation Toolkit Simplified Setup Tool. The Simplified Setup Tool guides you through the process of quickly and easily configuring one or more open source workloads on your system. The workloads include LAMP, mail, file and print, or network infrastructure servers.

Planning for IBM Installation Toolkit


Proper planning is essential to successfully install and use the IBM Installation Toolkit for PowerLinux. Before you begin, define your goals for using the IBM Installation Toolkit. v Are you planning to use IBM Installation Toolkit to install Linux? Will you be installing Linux on only one system? Will you be installing Linux on more than one system? v Is your system already running Linux and you plan to use the IBM Installation Toolkit to install service and productivity packages, update your firmware, or perform system recovery tasks? Knowing the answers to these and other similar questions allows you to choose the correct path for installing and running the IBM Installation Toolkit. The following figure shows the paths and general steps for installing and running the IBM Installation Toolkit.

Installing Linux with the IBM Installation Toolkit

Start the server

Yes

Linux installed?

No

Yes

IBM Installation Toolkit installed?

No

Download IBM Installation Toolkit

Done

Download IBM Installation Toolkit

Determine boot method

Install IBM Installation Toolkit

Boot server with IBM Installation Toolkit

Done Locate Linux distribution media

Install Linux

Done
Figure 1. Installing and using the IBM Installation Toolkit for PowerLinux

Either path for using the IBM Installation Toolkit begins with starting the server. Then, the paths diverge based on whether Linux is installed or to be installed.

Path for using IBM Installation Toolkit to install Linux


If Linux is not installed, use this path to install it with the IBM Installation Toolkit. 1. Download the IBM Installation Toolkit. To find out how to download the toolkit, see Downloading the IBM Installation Toolkit on page 9. 2. Determine a boot method for the IBM Installation Toolkit ISO image. You can choose from DVD device, virtual optical device, USB key, or network-based. For information, see Determining a boot method on page 9. After determining the boot method, configure it. For information, see Configuring the boot method to be used by the system on page 12. 3. Boot the server with the IBM Installation Toolkit using the method you previously determined and configured.

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

LIAAN501-2

4. Determine a location for your Linux distribution installation media. You can choose to install the Linux distribution from DVD disks, virtual optical device, or from a network repository. For information, see Determining the location for the distribution media on page 13. 5. Use the installation wizard to install Linux. For more information, see Installing a Linux distribution on page 15. This completes the path and general steps for using IBM Installation Toolkit to install Linux.

Path for preparing to use IBM Installation Toolkit to update a system when Linux is already installed
If Linux is already installed, either with the IBM Installation Toolkit or using another method, use this path to install the IBM Installation Toolkit. This allows you to then update the system, including managing repositories, installing service and productivity packages, and more. 1. Determine whether the IBM Installation Toolkit is installed. Run the following command:
rpm -q ibmit4linux

v If the command outputs a line similar to ibmit4linux-version, IBM Installation Toolkit is installed. You are ready to use the IBM Installation Toolkit to update your system. If you do not see a line similar to ibmit4linux-version, IBM Installation Toolkit is not installed. In this case, continue to the next item in the path. 2. Download the IBM Installation Toolkit. To find out how to download the IBM Installation Toolkit, see Downloading the IBM Installation Toolkit on page 9. 3. Install the IBM Installation Toolkit. To find out how to install the IBM Installation Toolkit, see Installing IBM Installation Toolkit on a system already running Linux on page 33. v This completes the path and general steps for preparing to use IBM Installation Toolkit to update a system when Linux is already installed. You are now ready to use the IBM Installation Toolkit to update your system, including the following tasks: v Managing software installation repositories on page 34. v Installing IBM packages on the system on page 35. v Migrating an x86 server running Linux to an IBM Power Systems server on page 38. v Installing open source workloads using the IBM Installation Toolkit Simplified Setup Tool. For documentation for the Simplified Setup Tool, see Getting started with PowerLinux servers (http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaay/vploverview.htm). The tasks that you can perform depend on which mode you are running in. Related concepts: IBM Installation Toolkit running modes You can run the IBM Installation Toolkit for PowerLinux in either live or installed mode. The tasks that you can perform depend on the mode that you are running in.

IBM Installation Toolkit running modes


You can run the IBM Installation Toolkit for PowerLinux in either live or installed mode. The tasks that you can perform depend on the mode that you are running in. You can switch back and forth between live mode and installed mode.

Live mode
The live mode for the IBM Installation Toolkit for PowerLinux allows you to perform the following tasks:

Installing Linux with the IBM Installation Toolkit

Install Linux See Installing a Linux distribution on page 15. Update firmware See Updating your firmware on page 36. Create a bootable USB key See Creating a bootable USB key on page 11. Configure the network See Configuring the network on page 32. Access documention See Accessing documentation resources on page 44. Register at IBM See Registering at IBM on page 46. Recover the system See Recovering your system on page 43. To use the IBM Installation Toolkit for PowerLinux in live mode, you must boot your system with the IBM Installation Toolkit for PowerLinux media using one of the methods: v DVD v ISO image v Network v USB key See Determining a boot method on page 9 for information about determining which method to choose. See Configuring the boot method to be used by the system on page 12 for configuring it. After you boot your system, the following options are available: Wizard mode (performs the installation) Choose this option to use the live mode with the text interface. You can install Linux or access any of the other tasks that are available when using live mode. See Opening the user interface on page 14. You can also use this option to remotely access the user interface. For more information, see Accessing the user interface remotely on page 15. Wizard mode graphical (performs the installation using X) Choose this option to use the live mode with the graphical interface. This option is only available on systems that have a graphics card. See Opening the user interface on page 14. Rescue mode (initiates a terminal) Choose this option to use the recovery console. You can access a Linux console to perform recovery tasks. See Recovering your system on page 43.

Installed mode
To use the IBM Installation Toolkit for PowerLinux in installed mode, you must install the IBM Installation Toolkit for PowerLinux packages on your Linux system. If you used the IBM Installation Toolkit for PowerLinux to install your system, the packages are already installed. To install the packages on a system that already has Linux installed, see Installing IBM Installation Toolkit on a system already running Linux on page 33. After you have installed the IBM Installation Toolkit for PowerLinux packages, you can perform the following tasks: Install IBM packages on the system See Installing IBM packages on the system on page 35.

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Migrate an x86 server running Linux to an IBMPower Systems server See Migrating an x86 server running Linux to an IBM Power Systems server on page 38. Manage Linux installation repositories available on the server See Managing Linux installation repositories available on the server on page 28. Configure the boot server See Configuring the boot server for IBM Installation Toolkit on page 21. Manage client systems for the boot server See Managing client systems for the boot server on page 23. Create a bootable USB key See Creating a bootable USB key on page 11. Manage software installation repositories See Managing software installation repositories on page 34. Access documention See Accessing documentation resources on page 44. Register at IBM See Registering at IBM on page 46. Monitor tasks See Monitoring IBM Installation Toolkit tasks on page 44. After you have installed the IBM Installation Toolkit for PowerLinux, you can access the user interface. See Accessing the user interface on page 13 and Opening the user interface on page 14.

Downloading the IBM Installation Toolkit


This section explains how to download the IBM Installation Toolkit for PowerLinux ISO image. The IBM Installation Toolkit is available for download from the IBM website at http:// www14.software.ibm.com/webapp/set2/sas/f/lopdiags/installtools/.

Determining a boot method


After you download the IBM Installation Toolkit, you must decide how you will boot the IBM Installation Toolkit ISO image. DVD device You can load the IBM Installation Toolkit ISO image onto DVD media and boot your system from the DVD device. To boot from a DVD disk, you need to perform these general steps: 1. Burn the IBM Installation Toolkit ISO image onto a DVD disk. 2. Ensure that the IBM Installation Toolkit disk is in the DVD drive of the system that you want to boot. 3. Restart the system or power it on. 4. Configure the system to boot from the DVD drive. For specific information about this task, see Creating a DVD on page 10. Virtual optical device You can boot the IBM Installation Toolkit directly from the ISO image if you have a system that has an LPAR with a virtual optical device. To boot directly from the IBM Installation Toolkit ISO image, you need to perform these general steps:

Installing Linux with the IBM Installation Toolkit

1. Create a virtual optical device and assign it to the LPAR you want to boot with the IBM Installation Toolkit. 2. Associate the IBM Installation Toolkit ISO image with that virtual optical device. 3. Restart the LPAR or power it on. 4. Configure the LPAR to boot from the virtual optical device. For specific information about this task, see Creating and assigning a virtual optical device. USB key You can create a USB key to use as a booting method. To boot IBM Installation Toolkit from a USB key, you need to perform these general steps: 1. Create an IBM Installation Toolkit bootable USB key. 2. Restart the system or power it on. 3. Configure the system to boot from the USB device. For specific information about this task, see Creating a bootable USB key on page 11. Network-based Booting from the network allows you to easily install Linux on more than one system that is connected to the network. To boot IBM Installation Toolkit from the network, you need to perform these general steps: 1. Configure a network boot server for IBM Installation Toolkit. 2. Configure the boot server for the system. 3. Restart the system or power it on. 4. Configure the system to boot from the network interface. For specific information about this task, see Creating a network installation server on page 21. To find out how to configure your chosen boot method, see Configuring the boot method to be used by the system on page 12.

Creating a DVD
You can create an IBM Installation Toolkit DVD to use either as a booting method or as an installation source for the IBM Installation Toolkit. You can use any method to create a DVD from an ISO image. However, whatever method you choose, use high-quality DVD-R media to ensure the best data transfer. Do not use DVD+R, DVD-RM, or DVD-RAM media.

Creating and assigning a virtual optical device


This topic explains how to create and assign a virtual optical device to a logical partition (LPAR). LPARs are also known as virtual servers. After a virtual optical device has been assigned to an LPAR, you can boot IBM Installation Toolkit for PowerLinux directly from the ISO image.

About this task


Note: This type of boot method is possible only with an LPAR that can have virtual optical devices assigned to it. To create and assign a virtual optical device to an LPAR, follow these steps:

Procedure
1. Access the web interface of the Integrated Virtualization Manager (IVM) of the system that contains the LPAR you want to set up.

10

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

2. On the left pane of the IVM main window, click View/Modify Partitions. 3. In the table of partitions (LPARs), select the partition where you want to create the new virtual optical device. 4. Ensure that the LPAR is shut down by clicking Shutdown. A window with shutdown options appears. Choose Immediate as the shutdown type and click OK. 5. On the IVM main window, select the name of the LPAR in the table of partitions. 6. Select Optical/Tape Devices to see the optical devices associated to the LPAR and then Virtual Optical Devices to expand the table of existing virtual devices. 7. Select Create Device. A new virtual device appears in the table. Click OK. 8. On the IVM main screen, select the LPAR in the table and click Activate to reactivate it. The new virtual optical device is now created and can be used at the LPAR. 9. On the IVM main screen, click View/Modify Virtual Storage. 10. On the tabs bar of the screen that appears, click Optical/Tape to see the table of ISO images available to be assigned. 11. Click Add Media to add the ISO image to be assigned. v To upload the ISO image file, click Upload media. v To use an ISO image file previously sent to the IVM system, click Add existing file. Click OK to add the ISO image file. 12. Select the ISO image file that you added and click Modify partition assignment to assign it to a virtual optical device of an LPAR. 13. Select the LPAR with the virtual optical device you want the ISO image file to be assigned to and click OK. The ISO image is assigned to the virtual optical device and can be accessed at the LPAR.

Creating a bootable USB key


You can create an IBM Installation Toolkit for PowerLinux bootable USB key to use either as a booting method or as an installation source for the IBM Installation Toolkit.

Before you begin


Note: Installing Red Hat Enterprise Linux 5 is not supported when you use an IBM Installation Toolkit USB key. Before you can create an IBM Installation Toolkit bootable USB, you must have the following items: v Blank USB key (or one that can be erased) v IBM Installation Toolkit DVD or ISO image file

About this task


To create a bootable USB key, follow these steps:

Procedure
1. From either live or installed mode, open the user interface. 2. Select Create an IBM Installation Toolkit bootable USB key. 3. On the Creation window, select the following information: v USB device: Select the USB device that you want to use to create the IBM Installation Toolkit USB key. If the USB device that you want to use is not in the list, verify that it is connected and click Refresh. Note: Your USB device will be formatted and any data contained in it will be lost.
Installing Linux with the IBM Installation Toolkit

11

v File system: Select the file system type to be used in the USB key. v IBMIT media source: Select where the IBM Installation Toolkit media is available to be read: CD/DVD-ROM drive or ISO image file. Files that are required to configure the boot server must be retrieved from the IBM Installation Toolkit media, so this field is required. v Extras: Select to include documentation, firmware files, and IBM packages in the USB key. Without any extras, the USB key is useful only to boot the system with IBM Installation Toolkit. If you chose ISO image as the IBM Installation Toolkit media source, browse your file system and select the ISO image file to be used. 4. Confirm your choices and click Next to create the IBM Installation Toolkit USB key.

Results
The process takes place in background and can be followed in the Task monitor at any time.

Configuring the boot method to be used by the system


This topic explains how to configure the boot method to be used by the system, as required to boot the IBM Installation Toolkit for PowerLinux live mode.

About this task


To configure the boot method to be used by the system, follow these steps:

Procedure
1. Power on or restart your system. 2. After the initial hardware tests, the firmware boot screen appears, line by line. At this window, select the SMS Menu option by entering 1. Note: You must enter 1 before the firmware boot screen is completely shown on the display, because it will disappear when complete.
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM 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 8 = Open Firmware Prompt Memory Keyboard Network SCSI

5 = Default Boot List 6 = Stored Boot List Speaker

Figure 2. Firmware boot screen

3. On the main SMS menu, select the Select Boot Options option by entering 5. 4. Enter 1 to select the boot device type selection menu.

12

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

5. Enter 7 to list all the available boot devices. 6. Enter the number corresponding the device you want to use. Tip: You can determine the device type based on its name: CD/DVD-ROM devices Names containing the word CD-ROM, such as SCSI CD-ROM and USB CD-ROM. This choice applies both for physical and virtual devices. Network devices Names containing the word Ethernet or LAN, such as Virtual Ethernet, IBM Host Ethernet adapter, and Interpartition Logical LAN. USB disk devices Names such as USB Disk. Note: Do not select USB CD-ROM, because booting from USB CD-ROM will result in an error. 7. Confirm the device type by entering 2. 8. Enter 1 to leave the SMS menu and start the boot process.

Determining the location for the distribution media


Before installing a Linux distribution, you must determine how and from what location you will be installing it. You can choose to install the Linux distribution from DVD media, a virtual optical device, or a network repository. DVD media If you have your Linux distribution installation media for ppc64 available on DVD media, you can use that media to install your Linux distribution. Use this option if you are planning to install Linux one time. Ensure that you have the disks available, or order them if necessary. Virtual optical device If you have your Linux distribution installation media for ppc64 available on an ISO image, you can use the ISO image to install your Linux distribution using a virtual optical device. Use this option if you are planning to install Linux on a logical partition (LPAR) with support for virtual optical devices and have the Linux distribution ISO images instead of physical DVD disks. Ensure that you have the ISO image available. Network installation repository If you have access to a network installation repository, you can use the repository to store your Linux distribution installation media for ppc64. Use this option if you are planning to install Linux multiple times. Ensure that you have the URL for the repository. If you need to create a network repository, see Managing Linux installation repositories available on the server on page 28 for information.

Accessing the user interface


After installing IBM Installation Toolkit for PowerLinux, you can use IBM Installation Toolkit from either the text interface or the graphical interface. You can access the graphical interface remotely. The first time that you access the user interface, you must accept the IBM Installation Toolkit licenses. If you do not accept the licenses, you cannot access the user interface.

Installing Linux with the IBM Installation Toolkit

13

Opening the user interface


When using live mode, the user interface is available after your system has booted the IBM Installation Toolkit media, by selecting either of the Wizard mode options. Alternatively, you can open the IBM Installation Toolkit user interface at any time from a command prompt. You can open the interface in text mode. Alternatively, if you have a system that has a graphics card, you can open the user interface in graphical mode from that system.

About this task


Open the user interface from a command prompt by completing these steps:

Procedure
1. At the command prompt, type the following command:
$ ibmit4linux

The user interface opens in the text interface. v If you want to use text mode, you are ready to begin. See Using the text interface. v If you want to use graphical mode, continue to the next step. 2. To start the graphical interface, complete the following steps: a. Open a Mozilla Firefox browser. You can use the browser either on the same system, or on another system. b. Enter the address http://system_IP:4233, where system_IP is the IP address or host name of the system. c. Accept the self-signed certificate.

Using the text interface


The text interface uses the installed text mode web browser on the system to access an equivalent interface to the graphical interface. Although equivalent, the text interface presents slight changes to enable the graphical features in the restricted area of the system. This section discusses these changes and provides general instructions for using the text interface.

About this task


The following tips explain how to navigate with the text interface:

Procedure
v After you start the user interface in text mode, it opens in the available text browser. To navigate, use the UP, DOWN, LEFT, RIGHT, and TAB keys on the keyboard. v When the cursor is over a link, press Enter to go to its destination. If the cursor is over a field, you can press Enter to change its status or edit. v If you select Access documentation resources from the main menu, the local and online resources are displayed. The steps to select the resources differ slightly based on whether the documentation is local (PDF format) or online (external web site). To select an online resource, navigate to the link and press Enter. The external web site opens in the current browser. However, to download one of the listed local documentation resources in PDF format, you must navigate to the resource and enter A or a. Simply pressing Enter will not select the PDF. After the PDF is selected, the PDF downloads, while a status window is displayed. v To close the text interface, enter Q or q. v When using the text interface, some of the instructions are folded due to space limitations. You must select Show Instructions to view. After you complete the view, select Hide Instructions.

14

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Accessing the user interface remotely


If you are using the IBM Installation Toolkit in live mode or installed mode, you can access it from a different system in the same network. Select one of the following options. v In live mode, to remotely access IBM Installation Toolkit, open Mozilla Firefox on the remote system in your network. Enter the address http://system_IP:4233 where system_IP is the system IP address of the system that you are accessing. v In installed mode, to remotely access IBM Installation Toolkit, open Mozilla Firefox on the remote system in your network. Enter the address https://system_IP:4234 where system_IP is the system IP address of the system that you are accessing.

Installing a Linux distribution


Use the IBM Installation Toolkit for PowerLinux to install a Linux distribution.

Before you begin


Before starting the installation, you must have the following items: v DVD disks or a network installation repository for the Linux distribution to be installed v DVD disk, virtual disk, USB key, or a network installation repository for IBM Installation Toolkit To learn about the supported Linux distributions, supported hardware and IBM Installation Toolkit software available, refer to the section Introducing IBM Installation Toolkit on page 1. You can install Linux only when using IBM Installation Toolkit in live mode. See IBM Installation Toolkit running modes on page 7.

About this task


To install Linux on your system, follow these steps:

Procedure
1. Open the user interface. 2. Select Install Linux. 3. Select the installation settings: v Linux distribution: Select one of the supported Linux distributions to install. v Installation profile: Select the set of packages to install. Click More info to see details about each of them. The available profiles are: Minimal Includes the smallest set of packages that allows the system to boot and to perform basic tasks. The disk usage is minimal. You can install additional packages in the future with the standard method provided by each Linux distribution. Minimal with X Includes all the packages included in Minimal but also includes the X Window System, a graphical environment that runs on Linux. This option is for servers that include a graphics card, but still have storage space restrictions. Default Includes the default package selection for the distribution and provides a balance between disk usage and functionality.

Installing Linux with the IBM Installation Toolkit

15

Includes all of the package sets provided by the distribution. Requires the most disk space, but includes all the available packages. v Disk partitioning: Select to install Linux on automatically partitioned disks or to use manual partitioning. N_Port ID Virtualization (NPIV) is not supported. For automatic partitioning, choose one of the following options: Full Automatic partitioning on a disk Installs Linux on the chosen disk, which will be conventionally partitioned. Any data contained in that specific disk will be lost. Automatic partitioning using LVM Creates an LVM-based partitioning scheme using all existing disks and installs Linux on the partitions according to the partitioning scheme scheme. Any data contained in all disks will be lost. Automatic partitioning using SW RAID Creates a software RAID-based partitioning scheme using all existing disks and installs Linux on the partitions according to the partitioning scheme. Any data contained in all disks will be lost. This option is available only if you have at least two disks on the system. v Use driver disk: Select whether a driver disk will be used for the Linux installation or not. Click Next. 4. Select the workloads to be installed on the target system. After the workloads are installed, these workloads can then be optimally configured by the IBM Installation Toolkit Simplified Setup Tool tool. Click Next. 5. If you selected to use driver disks for an installation setting, you must select a driver update disk. Click Choose driver update disk and browse for the file with the driver disk to use. Note: You can add only a single driver disk. If the driver disk displayed is not correct, you must remove it before you add another one. Click Next. 6. Select the installation sources. Click Refresh sources to update the list with a new network installation repository or an inserted USB key. v Linux distribution source: Select from the following installation sources for the Linux distribution. Select a Linux distribution source. Depending on your system, CD/DVD devices and network installation repositories might be available. Select Use custom network URL and specify a URL if you want to use a Linux distribution network installation repository that is not listed. v IBM Installation Toolkit media source: Select from the following installation sources for the IBM Installation Toolkit. Select an IBMIT source for the IBM packages. Depending on your system, CD/DVD devices, USB key devices, and network installation repositories might be available. Select Use custom network URL and specify a URL if you want to use an IBM packages network installation repository that is not listed. v Optional Linux distribution update repositories: Specify up to three network add-on repositories to include additional distribution updates, if available. Click Next. 7. If you chose manual partitioning, you must manually partition the disk. Refer to the section Manually partitioning disks on page 18 for details about accomplishing this task and then return to this step. Click Next.

16

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

8. Configure the network for the installed system. You must configure global network settings as well as a network interface. To configure your global settings, enter the following information: v Fully qualified hostname: The hostname to be used in the installed system. v DNS server: Optionally, the IP address of the DNS server to be used in the installed system. To configure your network interface, follow these steps: a. On the Network configuration main screen, select the interface you want to configure and click Configure. b. Enter the following information: v Configuration type: Choose the type of configuration by selecting Disabled, Automatic (DHCP), or Manual. v IP: For manual configuration, type the IP address to be used. v Netmask: For manual configuration, type the netmask to be used. v Gateway: Optionally, for manual configuration, type the IP address of the gateway to be used. c. Click Save to finish. You can check the configuration of a network interface by selecting it and clicking Details. Click OK to return to the Network setting window. When you are finished configuring your network settings, click Next. 9. Select the software repositories to be used in the installed system as sources to install new software or to get updates. For each of the selected repositories, the licenses must be accepted by checking I accept all the licenses above. Click See details to read the licenses for a repository and to get more information about it. 10. Choose the general settings for the installed system: v Keyboard: Language to be used for the keyboard. v Mouse: Mouse to be used. v Language: Language to be used on the installed system. v Timezone: Timezone to be used for the time and date settings on the installed system. Check Use UTC if you want to use UTC. v Root password: Root password for the installed system. v Confirm root password: Root password again to confirm it. Click Next. 11. Select the IBM software to be installed. You can see the packages that belong to a specific category by selecting it and clicking Apply. You can see details for a specific package by clicking See details. Packages that are unavailable for selection are automatically installed. Click Next. 12. Accept the licenses for the IBM software to be installed by checking I accept all the licenses above. You cannot proceed without accepting all of them. For each license, click Read license to learn more about it. Click Next. 13. Confirm the Linux installation settings, the workloads and IBM software to be installed, and the data that will be lost. If you are sure that this action is what you want, click Next to start the installation process. 14. If you chose to install the Linux distribution from CD/DVD-ROM, you are asked to insert the first disk to proceed. The installation process is displayed until the system reboots. After that, you can watch the terminal of the system to see the installation progress.

Installing Linux with the IBM Installation Toolkit

17

Note: The Red Hat Setup Utility may start during the first boot after you have installed Red Hat Enterprise Linux. For more information about this utility, see Red Hat Enterprise Linux documentation (http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/index.html). Note: If a partitioning or other installation preparation issue prevents Linux installation, see Known issues and workarounds.

What to do next
After you have installed Linux, you can use the IBM Installation Toolkit Simplified Setup Tool to configure one or more open source workloads. For documentation for the Simplified Setup Tool, see Getting started with PowerLinux servers (http://publib.boulder.ibm.com/infocenter/lnxinfo/v3r0m0/ topic/liaay/vploverview.htm).

Manually partitioning disks


This topic explains how to manually partition your disks to have Linux installed on them. The main window displays the available disks (physical and multipath), LVM volume groups, and software RAID arrays. To view the partitions of a disk, the logical volumes of an LVM volume group, or the software RAID arrays, select the disk, LVM volume group, or RAID array and click Change. Note: LVM logical partition or software RAID array might be referred to as partition, and LVM volume group might be referred to as disk. For each disk, the partitions are listed. For each partition, there are columns as follows: v Name: Indicates the partition name. Existing partitions have names that start with sd. New partitions start with new. For LVM volume groups, this value indicates the logical volume name. For RAID arrays, this value indicates the array name. Blank space slots start with blk. v Type: For disks, this value indicates the partition type. Valid types are Pri for primary, Log for logical, or Ext for extended. For software RAID arrays, this value indicates the RAID level. This field does not apply to LVM volume groups. v Size: Indicates the size of the partition. v Free: Indicates the amount of space that the partition has. v F.System: Indicates the file system that the partition uses. v M.Point: Indicates where the partition will be mounted in the installed system, for example / or /boot. v Format: Indicates whether the partition will be formatted and lose all data.

Working with partitions or LVM logical volumes


Use this information to add, edit, delete, and reset your partitions or LVM logical volumes.

Adding a partition
To add a partition: 1. On the Disk partitioning window, select an empty space in the current disk and click Add. 2. Enter the following partition settings: v File system: Specify the file system that the partition uses. If this partition is the first partition of the disk, the file system must be prep. v Size: Enter the size of the partition in MB, GB, or TB. Check All available to use all the space available. v Mount point: Specify where the partition is to be mounted, for example / or /boot. 3. Click Add to finish.

18

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Editing a partition
To edit a partition, follow these steps: 1. On the Disk partitioning window, select the partition you want to edit and click Edit. 2. Modify the partition settings you want. v File system: Specify the file system that the partition uses. If this partition is the first partition of the disk, the file system must be prep. v Format: Specify whether the partition is to be formatted. v Mount point: Specify where the partition is to be mounted, for example / or /boot. Note: You cannot change the size of an existing partition. 3. Click Apply to finish.

Deleting a partition
On the Disk partitioning window, select the partition you want to delete and click Delete. If you want to delete all partitions, click Delete all.

Resetting the partitioning scheme


On the Disk partitioning window, click Reset to discard all your modifications and reset the partitioning scheme.

Working with software RAID arrays


Use this information to add, edit, delete, and reset your software RAID arrays.

Adding an array
To add an array: 1. On the Disk partitioning window, select an empty space in the pseudo-disk RAID and click Add. 2. Enter the following partition settings: v Name: Select the name to be used for the array. v Level: Select the RAID level for the array. v Chunk size: Specify the chunk size to be used, in Kilobytes v Number of spares: Specify a number of spare devices for the array. v File system: Specify the file system for the array. v Mount point: Specify where the array is to be mounted, for example / or /boot. 3. Select the devices used to compose the array. Note: All physical partitions that have a file system set to raid are available to be used as devices to compose the array. To make a physical partition available to compose an array, edit an existing partition or add a partition and choose raid as the file system. See Working with partitions or LVM logical volumes on page 18 for instructions. 4. Click Add to finish.

Editing an array
To edit an array, follow these steps: 1. On the Disk partitioning window, select an empty space in the pseudo-disk RAID and click Edit. 2. Enter the following partition settings: v Name: Select the name to be used for the array.
Installing Linux with the IBM Installation Toolkit

19

v Number of spares: Specify the number of spare devices the array will have. v Format partition: Specify whether the array is to be formatted. v File system: Specify the file system that the array will use. v Mount point: Specify where the array is to be mounted, for example / or /boot. 3. Select the devices to be used to compose the array. Note: All physical partitions that have a file system set to raid are available to be used as devices to compose the array. To make a physical partition available to compose an array, edit an existing partition or add a partition and choose raid as the file system. See Working with partitions or LVM logical volumes on page 18 for instructions. 4. Click Apply to finish.

Deleting an array
On the Disk partitioning window, select the array you want to delete and click Delete. If you want to delete all arrays, click Delete all.

Resetting the partitioning scheme


On the Disk partitioning window, click Reset to discard all your modifications and reset the partitioning scheme.

Working with LVM volume groups


Use this information to add, edit, and delete an LVM volume group.

Adding an LVM volume group


To add an LVM volume group, follow these steps: 1. On the Disk partitioning window, click Manage VolGroups. 2. On the Volume groups management window, click Add. 3. Enter a name for the volume group. 4. Enter the extent size to be used. 5. Select the physical volumes to be used. Note: All physical partitions that have a file system set to lvm are available to be used as physical volumes. To make a physical partition available as a physical volume, edit an existing partition or add a partition and choose lvm as the file system. See Working with partitions or LVM logical volumes on page 18 for instructions. 6. When you are finished, click Add. 7. On the Volume groups management window, click Done.

Editing an LVM volume group


To edit an LVM volume group, follow these steps: 1. On the Disk partitioning window, click Manage VolGroups. 2. On the Volume groups management window, select the volume group that you want to change and click Edit. 3. Select the physical volumes to be used. You can add or remove physical volumes.

20

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Note: All physical partitions that have a file system set to lvm are available to be used as physical volumes. To make a physical partition available as a physical volume, edit an existing partition or add a partition and choose lvm as the file system. See Working with partitions or LVM logical volumes on page 18 for instructions. 4. When you are finished, click Apply. 5. On the Volume groups management window, click Done.

Deleting an LVM volume group


To delete an LVM volume group, follow these steps: 1. On the Disk partitioning window, click Manage VolGroups. 2. On the Volume groups management window, select the volume group that you want to remove and click Delete. 3. On the Volume groups management window, click Done.

Creating a network installation server


You can set up a network boot and installation server with an IBM Installation Toolkit for PowerLinux repository and one or more Linux distribution repositories. This server can then be used to boot multiple systems with the IBM Installation Toolkit through the network. The repositories can be used as network installation sources to install Linux on those systems. The following general steps are an overview of the steps to set up a network installation server: 1. Configure a network boot server for the IBM Installation Toolkit. 2. Configure the client systems. 3. Set up your IBM Installation Toolkit repository. 4. Set up your Linux distribution repositories. The network boot process works as follows. 1. The client system broadcasts a boot request to the network. 2. The IBM Installation Toolkit boot server receives the request. 3. If the DHCP server is configured to answer boot requests made by that client, it sends the client a file name. This file name is the boot image file the client needs to download. 4. The client receives that file name and downloads it from the TFTP server located at the boot server system. 5. Finally, the client loads the boot image in memory, runs it, and starts the boot process. During the process, the client downloads other boot images from the TFTP server as needed.

Configuring the boot server for IBM Installation Toolkit


You can configure your system to be a boot server for the IBM Installation Toolkit for PowerLinux, allowing client systems to boot the IBM Installation Toolkit from the network.

Before you begin


Before starting, you must have the following items: v A TFTP server installed and working on your system v An IBM Installation Toolkit DVD or ISO image file

Installing Linux with the IBM Installation Toolkit

21

Note: This tool currently works only on Power Systems servers. If you want to configure an IBM Installation Toolkit boot server in other type of system, you can manually configure the server. See the instructions in the Manually configuring the boot server for IBM Installation Toolkit topic. You can configure the boot server using this tool only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To configure the boot server, follow these steps:

Procedure
1. Open the user interface. 2. Select Configure the boot server for IBM Installation Toolkit. 3. Enter the following information: v TFTP export path: This directory is where the TFTP server hosts the files that are accessed through it. Files related to the network boot feature of IBM Installation Toolkit are copied to this location, so that they can be accessed by client systems. Make sure that your TFTP server software is correctly configured to use this directory by looking at its configuration file. Consult the documentation of your TFTP server software for details. v IBMIT media source: This field indicates where the IBM Installation Toolkit media is available to be read: CD/DVD-ROM drive or ISO image file. Files that are required to configure the boot server must be retrieved from the IBM Installation Toolkit media, so this field is required. 4. If you chose ISO image as the IBM Installation Toolkit media source, browse your file system and select the ISO image file to be used. 5. Confirm your choices and click Next to start the boot server configuration process. The process takes place in background and can be followed in the Task monitor at any time.

Manually configuring the boot server for IBM Installation Toolkit


You can manually configure your system to be a boot server for IBM Installation Toolkit for PowerLinux. If you are using a system other than a Power Systems server, manual configuration is your only configuration option.

Before you begin


Before manually configuring the boot server, you must have the following items: v A TFTP server installed and working on your system v An IBM Installation Toolkit DVD or ISO image file

About this task


Note: For these instructions, the following conventions apply: tftpdir The TFTP server chroot directory, usually /tftpboot. mountdir The directory where the IBM Installation Toolkit ISO image or DVD is mounted isofile The IBM Installation Toolkit ISO image file

To manually configure the boot server for IBM Installation Toolkit, follow these steps:

Procedure
1. Mount the IBM Installation Toolkit ISO image file or DVD.
mount -o loop -t iso9660 isofile mountdir

22

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

2. Copy the IBM Installation Toolkit boot images to the TFTP server:
mkdir -p tftpdir/ppc/ cp mountdir/boot/img1 tftpdir/ppc/ cp mountdir/boot/img2a tftpdir/ppc/ cp mountdir/boot/img3a tftpdir/ppc/ cp mountdir/boot/img4a tftpdir/ppc/

3. Copy the boot loader configuration files to the TFTP server:


cp mountdir/etc/yaboot_net.conf tftpdir/etc/yaboot.conf cp mountdir/etc/hardware.txt tftpdir/etc/hardware.txt

4. Unmount the IBM Installation Toolkit media.


umount mountdir

Managing client systems for the boot server


You can register client systems to use network booting. These client systems can then boot the IBM Installation Toolkit for PowerLinux by using the network from this boot server.

Before you begin


Before starting, you must have the following items: v Your system configured to act as an IBM Installation Toolkit boot server. See Configuring the boot server for IBM Installation Toolkit on page 21 for information. v DHCP server installed and working on your system. Note: This tool is intended for use on IBM Power Systems servers. If you want to use an IBM Installation Toolkit boot server configured in other type of system, you must manually configure the client. For instructions, see Manually configuring a client system for the IBM Installation Toolkit boot server on page 27. You can manage clients for the boot server only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


This procedure changes the DHCP server configuration file. It also restarts the DHCP server so that changes take effect and some configuration updates are completed in the TFTP boot server. The DHCP configuration file is updated only if the changes are applied. Complete the following steps:

Procedure
1. Open the user interface. 2. Open Manage client systems for the boot server. Clients that are in the DHCP configuration file but are not registered with the IBM Installation Toolkit are listed. You can import and automatically register them by selecting those clients and select Import. If you do not want to import clients, select Skip. The main screen displays all the registered clients. To view clients that belong to a subnet, select the subnet and click Filter. You can also add, edit, and delete clients or add, edit, or delete a subnet. Finally, you can edit DHCP headers. After performing any actions, you must click Apply changes for them to take effect. See Applying changes on page 27.

Adding a client
You can add a client for the boot server from the Manage client systems window.

Installing Linux with the IBM Installation Toolkit

23

Before you begin


You can manage clients for the boot server only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To add a client, follow these steps:

Procedure
1. 2. 3. 4. Open the user interface. Open Manage client systems for the boot server. On the Client Systems Management window, select Add. Enter the following client parameters: v Hostname: The client system host name, an identifier used to create this system entry into the dhcpd.conf file. This name is an arbitrary name, and not an Internet hostname, such as somename.ibm.com. v Subnet: Select the subnet of the new client. To manage the available subnets, select Manage subnets. Refer to Managing subnets for details. v IP address: The IP address that is assigned to the MAC (hardware) address of this system. This address is fixed and assigned to this system every time it connects to the local network. v MAC address: The client system MAC address of the network device being used to boot through network. v Comments: Additional comments used to identify this client system. This field is optional. 5. When you are finished entering the information, click Add. Note: You must click Apply changes for the changes to take effect. See Applying changes on page 27.

Editing a client
You can edit a client from the Manage client systems window.

Before you begin


You can manage clients for the boot server only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To edit a client, follow these steps:

Procedure
1. Open the user interface. 2. Open Manage client systems for the boot server. 3. On the Client Systems Management window, select the client that you want to edit and click Edit. 4. Modify the client parameters that you want to change. v Hostname: The client system host name, an identifier used to create this system entry into the dhcpd.conf file. This name is an arbitrary name, and not an Internet hostname, such as somename.ibm.com. v Subnet: Select the subnet of the new client. To manage the available subnets, select Manage subnets. Refer to Managing subnets for details.

24

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v IP address: The IP address that is assigned to the MAC (hardware) address of this system. This address is fixed and assigned to this system every time it connects to the local network. v MAC address: The client system MAC address of the network device being used to boot through network. v Comments: Additional comments used to identify this client system. This field is optional. 5. When you are finished, click OK. Note: You must click Apply changes for the changes to take effect. See Applying changes on page 27.

Deleting a client
You can delete a client from the Manage client systems window.

Before you begin


You can manage clients for the boot server only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To delete a client, follow these steps:

Procedure
1. Open the user interface. 2. Open Manage client systems for the boot server. 3. On the Client Systems Management window, select the client that you want to delete. 4. Select Delete. Note: You must click Apply changes for the changes to take effect. See Applying changes on page 27.

Adding a subnet
You can add a subnet from the Manage subnets window.

Before you begin


You can manage clients for the boot server only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To add a subnet, follow these steps:

Procedure
1. Open the user interface. 2. Open Manage client systems for the boot server > Manage subnets. Note: You can also select Manage subnets when adding a new client or editing an existing client. 3. Select Add. 4. Enter the following subnet parameters: v Subnet address: Enter the IP address of the subnet. v Network mask: Enter the netmask for the subnet. v Gateway: Optionally, enter the IP address for the gateway of the subnet.
Installing Linux with the IBM Installation Toolkit

25

v DNS server 1: Optionally, enter the address of the primary DNS server to be used. v DNS server 2: Optionally, enter the address of the secondary DNS server to be used. 5. Optionally, click Edit headers to specify DHCP configuration headers for the subnet. Refer to the section Editing DHCP headers on page 27 to learn about this topic. 6. Click Add to finish. Note: You must click Apply changes for the changes to take effect. See Applying changes on page 27.

Editing a subnet
You can edit a subnet from the Manage subnets window.

Before you begin


You can manage clients for the boot server only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To edit a subnet, follow these steps:

Procedure
1. Open the user interface. 2. Open Manage client systems for the boot server > Manage subnets. Note: You can also select Manage subnets when adding a new client or editing an existing client. 3. On the Subnets management menu, select the subnet that you want to edit and click Edit. 4. Modify the subnet parameters that you want to change. v Subnet address: Enter the IP address of the subnet. v Network mask: Enter the netmask for the subnet. v Gateway: Optionally, enter the IP address for the gateway of the subnet. v DNS server 1: Optionally, enter the address of the primary DNS server to be used. v DNS server 2: Optionally, enter the address of the secondary DNS server to be used. 5. Optionally, click Edit headers to specify DHCP configuration headers for the subnet. Refer to the section Editing DHCP headers on page 27 to learn about this topic. 6. When you are finished, click OK. Note: You must click Apply changes for the changes to take effect. See Applying changes on page 27.

Deleting a subnet
You can delete a subnet from the Manage subnets window.

Before you begin


You can manage clients for the boot server only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To delete a subnet, follow these steps:

26

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Procedure
1. Open the user interface. 2. Open Manage client systems for the boot server > Manage subnets. Note: You can also select Manage subnets when adding a new client or editing an existing client. 3. Select the subnet that you want to delete click Delete. Note: You must click Apply changes for the changes to take effect. See Applying changes.

Editing DHCP headers


You can specify DHCP configuration headers to be used. Both global and subnet specific headers can be specified.

Before you begin


You can manage clients for the boot server only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To edit headers, follow these steps:

Procedure
1. Open the user interface. 2. Open Manage client systems for the boot server > Manage subnets. Note: You can also select Manage subnets when adding a client or editing an existing client. 3. Select Edit DHCP headers from the Subnet management menu. 4. Enter each header separated by a semicolon. Consult the DHCP server documentation to learn about headers. 5. When you are finished, click OK. Note: You must click Apply changes for the changes to take effect. See Applying changes.

Applying changes
After you have made all the changes to Client management systems, you must apply changes or none of these actions take effect. Note: When you click Apply changes, the DHCP server is restarted and the new configuration file is in effect. This action is unavailable until after you have made a change. After you click Apply changes, the process begins and you can track its progress. After the process is finished, you can click View DHCP file to see the resulting DHCP configuration file that is now in effect. Click OK to return to the main window.

Manually configuring a client system for the IBM Installation Toolkit boot server
This topic explains how to manually configure the IBM Installation Toolkit for PowerLinux boot server in order to boot a client system.

Before you begin


Before starting, you must have the following items:

Installing Linux with the IBM Installation Toolkit

27

v Your system configured to act as an IBM Installation Toolkit boot server. To configure your system act as an IBM Installation Toolkit boot server, see Manually configuring the boot server for IBM Installation Toolkit on page 22. v DHCP server installed and working on your system. v Basic knowledge about DHCP server configuration files syntax. v The MAC address of the client system.

About this task


Note: For these instructions, the following conventions apply: tftpdir The TFTP server chroot directory, usually /tftpboot systemname An arbitrary name to identify the client system in the DHCP file. macaddress The MAC address of the client system. The letters must be in lowercase and components separated by hyphen. For example: ae-b3-c0-00-20-04. ipaddress The IP address to be assigned to the client system initscript The script that starts the DHCP server, usually /etc/init.d/dhcpd To configure the IBM Installation Toolkit boot server to have a client system booting from it, follow these steps:

Procedure
1. Set the boot loader configuration file for the client system by running the following command:
ln -sf etc/yaboot.conf tftpdir/yaboot.conf-macaddress

2. Configure the DHCP server to answer boot requests made by the client system by adding the following entry to the DHCP file:
host systemname { filename "ppc/img1"; hardware ethernet macaddress; fixed-address ipaddress; }

3. Restart the DHCP server for the configuration to take effect, by running the following command:
initscript restart

Managing Linux installation repositories available on the server


A repository is a directory that contains all of the files required to perform an installation. The repository is made accessible to the network through an HTTP, FTP, or NFS server. This function creates Linux and IBM Installation Toolkit network installation repositories. These repositories can be used to perform Linux installations from the network, rather than from CD/DVD-ROM or USB key.

Before you begin


Before creating any repository, you must have the following items: v ISO images or CD/DVD disks for ppc64 for the distributions that you want to create repositories for v An HTTP, FTP, or NFS server installed so that the repositories can be accessed

28

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Note: This tool is intended for use on IBM Power Systems servers. If you want to create a network installation repository on another type of system, you can manually create it, following the steps in the Manually creating a network installation repository on page 31 topic. You can manage Linux installation repositories only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To start the tool, follow these steps:

Procedure
1. Open the user interface. 2. Open Manage available Linux installation repositories. The main screen displays a list of the repositories currently available on the system. You can add and delete repositories. Repositories are accessible in the network through exported paths. You can also add and remove exported paths.

Adding a repository
You can use the Server management window to add a repository.

Before you begin


You can manage Linux installation repositories only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To add a repository, follow these steps:

Procedure
1. Open the user interface. 2. Open Manage available Linux installation repositories. 3. On the Setup Network Server window, click Add. 4. Enter the following information: v Exported Path: Location where the repository is available. To understand in details what an exported path is and to learn how to add a new one, see Adding an exported path on page 30. v Directory Name: Repository name. This name is also the name of the subdirectory, inside the exported path directory, where the repository is created. For example, if you type myrepo and choose the exported path at /srv/repositories/, accessible at http://192.168.1.54/repositories/, then your repository is created at /srv/repositories/myrepo/ and is accessible at http://192.168.1.54/repositories/myrepo/. v Distro: The distribution that is available from the repository. v Media Type: Type of media used as source to create the repository. Depending on the chosen distribution, CD or DVD is available. v Media Source: Source where the files are retrieved and copied to the repository. The source can be a CD/DVD-ROM device or ISO image. 5. If you chose ISO image, browse the file system and select the ISO image files for the distribution and media type (CD or DVD) you chose. 6. Confirm the options and click Next to start the repository creation process. The process takes place in background and can be followed in the Task monitor at any time.

Installing Linux with the IBM Installation Toolkit

29

Deleting a repository
You can use the Server management window to delete a repository.

Before you begin


You can manage Linux installation repositories only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To delete a repository, follow these steps:

Procedure
1. 2. 3. 4. Open the user interface. Open Manage available Linux installation repositories. In the Setup Network Server window, select the repository that you want to delete. Click Delete.

5. Click Yes to confirm. The repository is deleted from the list and also from the file system.

Adding an exported path


This topic explains how to add an exported path to provide network access to repositories. You can then use the exported path to install Linux from the network.

Before you begin


You can manage Linux installation repositories only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


An exported path is a directory that contains repositories and is accessible from the network through an HTTP, FTP, or NFS server. For example, the exported path /srv/repositories/ is accessible through an HTTP server at the URL http://192.168.1.54/repositories/ and contains a copy of SLES 10 SP3 in the repository /srv/repositories/sles10sp3/. The exported path is at the URL http://192.168.1.54/ repositories/sles10sp3/. To add an exported path, follow these steps:

Procedure
1. 2. 3. 4. Open the user interface. Open Manage available Linux installation repositories. On the Setup Network Server window, click Add to add a repository. On the Add a new repository window, select Add Exported Path.

5. Enter the following information: v Protocol: Select the network protocol used by the server. Possible values are HTTP, NFS, or FTP. v Path: Select the directory that contains the repositories. v URL path: Specify the path part of the URL. For example, if the directory is available at http://192.168.1.54/repositories/, then the URL path is /repositories. If the directory is available at http://192.168.1.54/my/url/path/, then the URL path would be /my/url/path. 6. Click Add to add the export path.

30

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Removing an exported path


You can use the Server management window to remove an export path.

Before you begin


You can manage Linux installation repositories only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To remove an exported path, follow these steps:

Procedure
1. 2. 3. 4. Open the user interface. Open Manage available Linux installation repositories. On the Setup Network Server window, click Add to add a repository. Select Remove exported paths.

5. Select the path in the list and click Delete.

Manually creating a network installation repository


This topic explains how to manually create a Linux or IBM Installation Toolkit for PowerLinux network installation repository. You can then use the repository to install Linux from the network.

Before you begin


Before starting this task, you must have the following items: v DVD ISO image for ppc64 for the distribution for which you want to create a repository v HTTP, FTP, or NFS server installed and working, so that the repository can be accessed

About this task


A network installation repository is a directory made accessible to the network through an HTTP, FTP, or NFS server. That directory must contain all the files required to perform an installation. After the repository is created, it is accessible at a URL that depends on the configuration of your server. For example: http://192.168.1.54/myrepo. One method of making the files available is to copy all the files of a distribution DVD media to a directory and then make that directory accessible to the network. However, you can also mount the ISO image file or the distribution DVD media. Note: For these instructions, the following conventions apply: isofile The DVD ISO image file for the distribution or IBM Installation Toolkit

mountdir The directory where the ISO image is mounted rootdir A directory that is accessible from an HTTP, FTP, or NFS server reponame The name of the subdirectory of rootdir that contains the repository To create a Linux or IBM Installation Toolkit network installation repository by mounting the ISO image file, follow these steps:

Installing Linux with the IBM Installation Toolkit

31

Procedure
1. Mount the ISO image file for the distribution DVD media file by running the following command:
mount -o loop -t iso9660 isofile mountdir

2. Copy all the files to the repository directory by running the following commands:
rm -rf rootdir/reponame cp -a mountdir rootdir/reponame

3. After the files are copied, unmount the ISO image by running this command:
umount mountdir

Mounting the DVD media: About this task Instead of copying files to the disk, you could directly mount the DVD media at a directory that is accessible by the server. To mount the DVD media, follow these steps: Procedure 1. Create a mount point on the server by running the following command:
mkdir -p rootdir/reponame

2. Mount the DVD media for the distribution DVD by running the following command:
mount -o loop -t iso9660 isofile rootdir/reponame

3. After you are finished using the repository, unmount it by running the following command:
umount rootdir/reponame

Configuring the network


You can set up your network configuration either automatically (through DHCP) or manually.

Before you begin


You can configure the network only when using IBM Installation Toolkit live mode. See IBM Installation Toolkit running modes on page 7.

About this task


Note: This action configures the network for the live mode and not for the target system environment. To configure the network, follow these steps:

Procedure
1. Open the user interface. 2. Select Configure network. 3. Select the network interface from the Network interfaces table and select the type of configuration you want (automatic or manual) from Configuration Type. Then click Next. v If you selected the automatic configuration, a confirmation window is displayed. Verify that your selection is correct and click Next to proceed. v If you select manual configuration, enter the following information: IP address: IP address number to be used by the system Network mask: Network mask of the IP address entered Gateway: IP address number of the system used as a gateway to access the external networks. This field is optional.

32

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

DNS server: DNS server to be used to resolve names. This field is optional. When you are finished, click Next. 4. Verify that the information is correct, click Next again to apply the configuration. Note: If you do not provide a valid gateway, you will not be able to access the external networks, such as the Internet.

Updating an installed system


You can use the IBM Installation Toolkit for PowerLinux to update your system. If you are running a system that was installed without the IBM Installation Toolkit, you need to install the IBM Installation Toolkit packages. For a system installed with the IBM Installation Toolkit, the packages are already available.

Installing IBM Installation Toolkit on a system already running Linux


Use this information to install the IBM Installation Toolkit for PowerLinux on a system already running Linux.

About this task


Note: For these instructions, the following conventions apply: isofile The DVD ISO image file for the IBM Installation Toolkit

mountdir The directory where the ISO image is mounted To install the IBM Installation Toolkit, follow these steps:

Procedure
1. Download the IBM Installation Toolkit ISO image. 2. Mount the ISO image file on the system using the following command:
mount -o loop -t iso9660 isofile mountdir

3. Start the installation script by running the following command:


mountdir/install

Manually installing IBM Installation Toolkit using a Yum repository


If you prefer, you can manually install IBM Installation Toolkit on a system already running Linux using a Yum repository, rather than running the installation script. This procedure is optional; the installation script automatically installs IBM Installation Toolkit and ensures that all dependencies are met.

About this task


Note: For these instructions, the following conventions apply: isofile The DVD ISO image file for the IBM Installation Toolkit

mountdir The directory where the ISO image is mounted To install the IBM Installation Toolkit, follow these steps:

Installing Linux with the IBM Installation Toolkit

33

Procedure
1. Download the IBM Installation Toolkit ISO image. 2. Mount the ISO image file on the system using the following command:
mount -o loop -t iso9660 isofile mountdir

3. Configure Yum to point to mountdir/repos/distro/, distro is the distribution. Possible choices for the distribution are rhel5, rhel6, sles10, and sles11. Note: You might also need to ensure that Yum has access to a distribution installation repository, to install dependencies required by IBM Installation Toolkit. 4. Install IBM Installation Toolkit by running the following command:
$ yum install ibmit4linux

Managing software installation repositories


You can configure and manage software installation repositories. These repositories are used to install software on the system. To manage software installation repositories, you must be running in installed mode. See IBM Installation Toolkit running modes on page 7. To start managing software installation repositories, follow these steps: 1. Open the user interface. 2. Select Manage repositories used by this system The main screen shows a list with the repositories currently configured. For each repository in the list, there are three columns: v Name: Displays the repository name. v Resource: Displays a URL with the repository location. v State: Indicates whether the repository is currently active or inactive. An inactive repository is not used by the system as a possible software source. If you select one of the repositories, you can activate, deactivate, or remove an existing repository or add a repository.

Activating or deactivating a repository


If you want to activate or deactivate a repository, select it from the list and click Activate/Inactivate.

Removing a repository
If you want to remove a currently configured repository, select it from the list and click Remove.

Adding a repository
If you want to add an existing repository or a new custom repository, follow these steps: 1. After clicking Add, the IBM Installation Toolkit searches for external repositories in the Internet. If you want to skip the search and add a custom repository, click Skip. 2. If you did not skip the previous step, a list with the external repositories available is displayed. To add any of those repositories, select it and click Add. To add a custom repository, click Add custom. 3. If you chose to add a custom repository enter the following information: v Repository name: The name you want to use for the new repository. v Repository type: The type of the repository you are adding. The available options depend on your system:

34

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Red Hat Enterprise Linux: Valid options include baseurl, metalink, mirrorlist, NFS, and CD/DVD media SLES: Valid types include URL and CD/DVD media v Location: Indicates where the repository can be found. This field depends on the repository type chosen: baseurl: Provide the URL where the repository can be found. The URL must be of the type file://, ftp://, or http://. For example, ftp://192.168.1.54/my/ftp/repo/. NFS: Similar to baseurl, but uses nfs:// URL type. For example, nfs://192.168.1.54/my/nfs/ repo/. metalink: Specify a location for a metalink file. mirrorlist: Specify a location for a mirror list. CD/DVD media (Red Hat Enterprise Linux): The repository is added by copying the content of a CD/DVD to a destination directory. Provide the path for that directory. URL: Provide the URL where the repository can be found. The URL must be of the type ftp://, nfs://, http:// or https://. For example, http://192.168.1.54/my/http/repo/. CD/DVD media (SLES): There is nothing to copy for SLES. Leave the field blank. v State: Defines whether the repository is initially active or inactive. Click Add to proceed. The repository is added.

Installing IBM packages on the system


This tool installs IBM packages on a previously installed Linux system.

Before you begin


Before starting this task, you must have the following items: v A software installation repository for IBM packages configured v A software installation repository for your Linux distribution configured You can configure software installation repositories with the tool Managing software installation repositories on page 34. Alternatively, you can use the package manager of your distribution to do it manually. To install IBM packages, you must be running in installed mode. See IBM Installation Toolkit running modes on page 7.

About this task


To install IBM packages on a previously installed Linux system, follow these steps:

Procedure
1. Open the user interface. 2. Select Install IBM packages on this system. A list of packages is displayed. 3. Choose the IBM packages to be installed. You can see details for a specific package by clicking See more. Choose a package by selecting the check box beside the package name. When finished selecting packages, click Next to continue. 4. Accept the licenses of the packages you selected. If you do not accept the licenses, the installation cannot proceed. To read a license, click the license name. Accept all licenses by selecting the I accept all the licenses above check box. Click Next to continue.

Installing Linux with the IBM Installation Toolkit

35

5. Confirm the packages to be installed and click Next to start the installation process. The process takes place in background and can be followed in the Task monitor at any time.

Updating your firmware


This tool updates the firmware of your system. The IBM Installation Toolkit for PowerLinux media comes with many firmware images that can be used for updating.

Before you begin


Before starting, you must have the firmware image file you want to be installed. Note: This tool is not intended to be a replacement for the Integrated Virtualization Manager (IVM) or Hardware Management Console (HMC) firmware update tools. Instead, use it as a recovery utility in cases where IVM or HMC is not working, but you are still able to boot the system with the IBM Installation Toolkit. If you have IVM or HMC properly working, you should use it to update the firmware. To update your firmware with the IBM Installation Toolkit, you must be running in live mode. See IBM Installation Toolkit running modes on page 7.

About this task


The firmware update process consists of the following steps: 1. Install a new firmware image in the temporary side. 2. Boot the system in the temporary side to verify that everything is working properly with this firmware image. 3. If the boot was successful, commit the firmware image from the temporary side to the permanent side. Otherwise, reject it. 4. Reboot the system in the permanent side.

Procedure
Open the user interface. Select Update the firmware of this system. Verify the system information and select Update firmware in temporary side and click Next. Browse the file system and select the firmware image file to be used. If you want to use a firmware image from the IBM Installation Toolkit DVD, click Load DVD to allow the system automatically look for the best firmware option for your system. 5. Confirm the list and start the operation by clicking Yes, I am sure - UPDATE FIRMWARE IN TEMPORARY SIDE. Do not try to restart or turn off the system during the process as this action may render the system inoperable. 1. 2. 3. 4. Your system reboots. v If your system successfully rebooted, with the firmware update on the temporary side, commit the firmware to the permanent side. v If the firmware was unsuccessful in the temporary side, you can reject it. 6. To commit the firmware to the permanent side, follow these steps: a. Return to the Firmware Updates window and select Commit firmware to permanent side. b. Click Next. c. You are warned that this operation cannot be undone. To proceed, click Yes, I am sure - COMMIT FIRMWARE TO PERMANENT SIDE. Your system reboots.

36

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

7. To a. b. c.

reject the firmware on the temporary side, follow these steps: Return to the Firmware Updates window and select Reject the firmware in the temporary side. Click Next. You are warned that this operation cannot be undone. To proceed, click Yes, I am sure - REJECT FIRMWARE IN THE TEMPORARY SIDE. Your system reboots.

Cloning your system


IBM Installation Toolkit for PowerLinux allows you to create a backup image of an existing system. You can then restore that image to the same system to restore it. Note: The cloning tool might not work if you attempt to restore to a different system.

Cloning devices
This task allows you to clone, or copy, an existing system.

Procedure
1. Open the user interface. 2. Select Clone and restore devices on this system. 3. Select Clone devices. A list of devices is displayed with their sizes. 4. Choose the devices to be cloned. Choose a device by selecting the check box beside the device name. When finished selecting devices, click Next to continue. 5. In the Server field, type the location where the cloned device images are to be stored as they are created. Only NFS servers can be used to store images. You must specify the storage location using standard URL notation. For example, this URL nfs://123.4.567.89/srv/www/images/ specifies to store the images on the NFS server 123.4.567.89 in the directory /srv/www/images/. Click Next to continue. A Compression field is shown, with None displayed as the only choice. The compression option is not available currently. 6. Confirm the cloning choices, and click Next to start the cloning process. The process takes place in background and can be followed in the Task monitor at any time.

Restoring devices
This task allows you to restore a backup image that you previously cloned from a system back to the same system.

Procedure
1. Open the user interface. 2. Select Clone and restore devices on this system. 3. Select Restore devices. 4. In the Server field, type the location where the previously cloned device images are stored. Only NFS servers can be used to store images. You must specify the storage location using standard URL notation. For example, this URL nfs://123.4.567.89/srv/www/images/ specifies to store the images on the NFS server 123.4.567.89 in the directory /srv/www/images/. Click Connect. A list of stored images is displayed with their sizes. 5. Choose the images to be restored. Choose an image by selecting the check box beside the image name. When finished selecting images, click Next to continue. The images that you selected are displayed with their sizes after decompression, and a destination field. 6. Specify the destination devices to which the images are to be restored. In the Destination field for each image, click the arrows to select a device. Click Next to continue.

Installing Linux with the IBM Installation Toolkit

37

7. Confirm the restoration choices, and click Next to start the restoration process. The process takes place in background and can be followed in the Task monitor at any time.

Migrating an x86 server running Linux to an IBM Power Systems server


You can use the IBM Installation Toolkit for PowerLinux Server Consolidation tool to replicate the software stack and to migrate application data from an x86 system to an IBM Power Systems server. The Server Consolidation tool allows you to migrate the LAMP or SAMBA software stack. A LAMP server is a bundle of open source software. LAMP is an acronym for Linux, Apache HTTP Server, MySQL relational database, and PHP (Perl or Python) scripting language. The tool retrieves the necessary information from a x86 system (source system) and installs a new IBM Power Systems server (target system) with the Linux distribution, users, groups, configuration files, and data of the source system.

Server Consolidation environment


The IBM Installation Toolkit for PowerLinux Server Consolidation tool works in a special environment provided by the IBM Installation Toolkit. The Server Consolidation tool includes three important elements: Source system The x86 (32-bit or 64-bit) system that is to be migrated. The Server Consolidation tool can migrate only x86 Linux systems, with or without Apache, MySQL, PHP, Perl, Python, and SAMBA applications. Target system The new system (IBM Power Systems server) that is installed with the IBM Installation Toolkit and receives all the data and configuration files from the source system. Network Server system The network boot and installation server system running the IBM Installation Toolkit. This system orchestrates all the migration steps between the source system and the target system. To perform a migration, you must connect remotely with a web browser to the network server system. This system retrieves information from the source system and creates a migration profile, which is later used to replicate the source in the target system. Next, the target system is booted from the network and is installed with a Linux distribution. Finally, the migration process runs and the target system becomes a replica of the source system. At a minimum, both the source and target systems must have network connectivity to the network server system. If you do not want to migrate data, the tool provides a clean installation of the LAMP and SAMBA stack on the target system. If you want to migrate data such as /home, HTML, CGI scripts, MySQL databases, and so on, you must have network connectivity between the source and target systems.

Server Consolidation tool considerations


Before starting a migration, you should understand some special characteristics of the tool. v If the target system has a disk that is not large enough to hold the Linux distribution installation plus all the data to be migrated from the source system, the migration will fail. v The Server Consolidation tool migrates only official packages from the Linux distributions of the source system. If there is any application that was installed manually, or that is not the official version of the application, the Server Consolidation tool either does not migrate the application or it installs the version distributed in the distribution. v The Server Consolidation tool does not migrate user passwords.

38

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v The root password of the target system is passw0rd. (Note the zero, instead of O.) After the first access, you should change this password. v The Server Consolidation tool migrates only the DocumentRoot data specified in the Apache configuration files. By default, Alias data directories are not migrated.

Supported Linux distributions for migration


Use this information to determine which Linux distributions are supported by the Server Consolidation tool. The Server Consolidation tool supports the following Linux distributions: v i386 and x86_64: Red Hat Enterprise Linux 5.0 through 5.9 Red Hat Enterprise Linux 6.0, 6.1, 6.2, 6.3, and 6.4 SUSE Linux Enterprise Server 11 (GA and Service Packs 1 and 2) v PowerPC or 64-bit PowerPC: Red Hat Enterprise Linux 5.9 and 5.10 Red Hat Enterprise Linux 6.4 and 6.5 SUSE Linux Enterprise Server 11 SP2 and SP3 You can migrate only between the same Linux distribution. For example, you can migrate from Red Hat Enterprise Linux 5 Update X to Red Hat Enterprise Linux 5 Update Y (where X and Y are minor release versions of Red Hat Enterprise Linux 5), but not from Red Hat Enterprise Linux 5 to Red Hat Enterprise Linux 6.

Using the migration wizard


These instructions describe how to use the migration wizard to migrate an existing source to a new target system.

Before you begin


To use the migration wizard, you must be running in installed mode. See IBM Installation Toolkit running modes on page 7. Before performing any migration, you must first have a network boot and installation server. For instructions about creating one, see the following topics: v Configuring the boot server for IBM Installation Toolkit on page 21 v Managing Linux installation repositories available on the server on page 28 You also must register the target system as a client system for the boot server. See Managing client systems for the boot server on page 23.

About this task


After the network boot server and installation server are set up and available and the target system has been registered as a client system, follow these steps:

Procedure
1. Use your browser to initiate a LAMP stack migration by entering the IP address or host name of the network server system plus the port 4234 to access the tool, and specifying the https protocol. For example, https://10.1.1.1:4234. 2. Open the user interface.
Installing Linux with the IBM Installation Toolkit

39

3. Select Migrate an x86 server to a Power Systems server. 4. Enter the IP address, the SSH port, and the root password for the source system. This information is required in order to remotely access the source system. The default port of SSH is 22, but if you have changed this information, use the correct port. Note: If you are running a firewall in the source system, make sure that it is not blocking the SSH port you set. After entering all the necessary information, click Next . 5. The system attempts to get a source profile with all the system information required to perform the migration. You can see the progress of the operation. After it is completed, click Next. If an error occurs, click Prev to go back to the source system connection parameters screen and try again. 6. Verify the system type of the source system and select the system type of the target system to be installed from a list of options provided. The available system type options for the target system are: v IBM POWER7 processor based server v IBM POWER7 processor based blade server Click Next. 7. Specify the disks that exist in the target system. To add a disk, follow these steps: a. On the target system disks screen, click Add. b. Enter the following information: v Device name: Enter the name of the device for the disk. v Disk size: Enter the size of the disk and choose the appropriate unit. c. Click Add to finish. To modify a previously added disk, follow these steps: a. On the target system disks screen, click Edit. b. Enter the new size of the disk and choose the appropriate unit. c. Click Apply to finish. To remove previously added disk, select it in the target system disks screen and click Delete. 8. Select the specific target system, the Linux distribution to install the target system, and the type of partitioning to be used. The options available for Linux distribution depend on the system type chosen in a previous step. If your target system is not listed, register it as a client system. See Managing client systems for the boot server on page 23. For partitioning type, you can choose between: v Automatic partitioning on a disk: Installs Linux on the chosen disk with automatic partitioning. Any data contained on that specific disk will be lost. v Manual partitioning: Allows you to manually partition the disks of the target system. You can also choose to create an LPAR to be used as target system. Click Create LPAR and follow the steps in Creating an LPAR on page 42. Click Next. 9. If you chose manual partitioning, you must manually partition the disk. Refer to the section Manually partitioning disks on page 18 for details about accomplishing this task. When you have finished, click Next. 10. Select the installation sources for both the Linux distribution and IBM packages. If a URL is not displayed, enter a custom URL that point to valid network installation repositories. Click Next. 11. Optionally, select the system profile options to install in the target system. The available options are:

40

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v v v v v v v v v

Web server (Apache) File server (Samba) Print server (Cups) Database server (PostgreSQL) Database server (MySQL) Directory server (Open LDAP) Mail server (Sendmail) Mail server (Postfix) DHCP and BOOTP server

Note: If the source system already has Apache and MySQL installed, these two options are not available in the list. They are migrated by default to the target system. When you are finished, click Next. 12. Optional: Optionally, select the options to migrate all users and groups, the home directories, and the LAMP data from the source system to the target system. The LAMP option is displayed only if there are Apache or MySQL server applications on the source system. If you select it, you must enter the MySQL root password if it is required by the source system. Also, you can specify that some additional data is migrated along with LAMP stack. To add a new file or directory, type the complete name in Path and click Add. The new chosen path is displayed in Additional directories to be migrated. You can remove directories from the list by selecting one or more and clicking Remove selected. You cannot migrate the following paths: v / v /bin v /dev v /lib v /sbin v v v v v /proc /usr /boot /etc initrd

v /opt v /selinux v /sys v /var Note: v To migrate the LAMP data, the server consolidation tool requires the root user password of the MySQL server and not the root password of the system. v Be sure that the MySQL Server is running or can be started in the source system before starting the migration, otherwise MySQL data cannot be migrated. v The Server Consolidation tool does not analyze or modify the LAMP configuration files during or after the migration. When you are finished, click Next. 13. Verify the information for migrating and click Next.
Installing Linux with the IBM Installation Toolkit

41

14. The migration is ready to run. Boot the target system from the network to start the migration Note: Record the task ID displayed so that you can monitor the progress.

What to do next
If you want to monitor the migration progress, click Go to task monitor. Then select the task ID that you recorded previously and click Details. After the first boot of the installed target system, all the data is migrated from the source to the target system. You can view messages reporting the progress of the migration.

Creating an LPAR
You can create an LPAR, or partition, when migrating an x86 system to an IBM Power Systems server.

About this task


To create an LPAR, follow these steps:

Procedure
1. From the migration wizard, when selecting the target system Linux distribution and system, click Create LPAR. 2. Enter the Power Systems management system information. v If you are using a system managed by the Integrated Virtualization Manager (IVM), provide the IVM IP address, user name, and password. Usually, padmin is the user name. v If you are using a system managed by the Hardware Management Console (HMC), provide the HMC IP address, user name, and password. Usually, hscroot is the user name. If your system uses an SSH port other than 22, then you can also set it here to the appropriate value. When you are finished, click Next . Note: If you are running a firewall on the management system, make sure that it is not blocking the SSH port you just provided. 3. If you are using a system managed by an HMC, select the Managed System to hold the new LPAR and enter the information for the Managed System VIOS. You must type the VIOS IP address, SSH port number, user name, and password. Usually, ppadmin is the user name. When you are finished, click Next. If you are using an IVM-managed system, this step is automatically skipped. 4. The next steps are the same for both IVM and HMC systems. Enter the new LPAR IP address; contact your network administrator if you are not sure about it. Also enter the host name and subnet to be used. The host name is used as the LPAR name as well. When you are finished, click Next. 5. On the LPAR Disk Configuration window, select to either create a storage pool or use an existing one for the LPAR virtual disk. If there is no space available for the new virtual disk, you can continue, but the LPAR creation will fail. Note: On HMC systems, an available virtual SCSI adapter (vhost) is required to create the LPAR. Click Next to proceed. 6. The LPAR creator wizard displays information about the new LPAR. If your management system cannot provide the same amount of resources as found in the source system being migrated, warning messages are displayed to report it. Note: By default each virtual processor in the created LPAR uses one processor unit. This value can be changed later through HMC or IVM directly.

42

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

If you agree with the warning message displayed, click Next . 7. Verify all the settings and click Next to create your LPAR. 8. Your LPAR has been created. Click OK to close the window. You are redirected back to the migration window and you can use the newly created LPAR as your migration target system.

Recovering your system


The IBM Installation Toolkit for PowerLinux bootable image loads a minimal Linux system to run Linux installation, firmware update, diagnostic and recovery tools, and other applications. To access the IBM Installation Toolkit recovery console, you must be running in live mode. See IBM Installation Toolkit running modes on page 7 for information about how to enter rescue mode, which allows you to use the recovery console. The minimal Linux system loaded with the recovery console comes with a wide range of system diagnostic and recovery applications. Besides sysdiag and many IBM service and productivity tools (lsvpd, ofpathname, bootlist, and so on), you can use over 1000 other Linux applications. These applications include the following: v System shells (bash, sh) v Line editing utilities (sed, awk) v Text editors v Linux partitioners (fdisk, sfdisk) v v v v mount and umount applications chroot Archivers (tar, gzip, gunzip) A python interpreter

For a complete list of applications available, you can either press the Tab key twice on system shell or check the following directories on a system booted with the IBM Installation Toolkit: v /sbin v /usr/sbin v v v v v /usr/local/sbin /root/bin /usr/local/bin /usr/bin /usr/X11R6/bin

v /bin You can find documentation for these applications at the website http://www.linuxmanpages.com/. Most of these applications have built-in help that serves as a quick reference for commonly used options. In general, this built-in help can be accessed by specifying a help argument with any command (for example: mount -help). However, the method for displaying help might vary from application to application. Note: While running the recovery console, you can access the IBM Installation Toolkit user interface at any time by entering welcomecenter. If you want to leave the user interface and return to the console, enter Q or q.

Installing Linux with the IBM Installation Toolkit

43

Monitoring IBM Installation Toolkit tasks


The Task monitor is a tool that allows you to monitor the progress of tasks that you are running in the background. You can monitor the state of all tasks in the Tasks overview window and the details of a specific task in the Task details window. You can monitor tasks only when using IBM Installation Toolkit in installed mode. See IBM Installation Toolkit running modes on page 7. To start the task monitor, open the user interface. Then select Monitor tasks. For each task in the list, there are four columns: Name, Description, State, and Duration. Name Displays the unique identifier for the task. You can use these identifiers to refer to the task whenever you need. Description Displays a short description for the task. State Displays the current state for that task. Possible states include: v Running: The task is running. v Interactive: The task is stopped waiting for user interaction. Move to the Task details window to determine what the task is requesting. v Paused: The task is in paused state. v Canceled: The task has been canceled. v Error: The task has finished with error. Move to the Task details window to determine what happened. v Completed: The task has finished with success. v N/A: The task state in unavailable. Duration Displays the length of time that the task has been running.

Canceling a task
You can cancel a task by selecting it and clicking Cancel.

Removing tasks that are no longer active from the list


If you click Clear not active tasks, all the tasks that are no longer active (Running, Interactive, or Paused) are removed from the list.

Task details
You can select a task in the list and then click Details to view a screen with details about it. The details screen is task-dependent: Each task implements its own details screen the way it prefers. For instructions about a specific task details screen, refer to the section which describes that task.

Accessing documentation resources


IBM Installation Toolkit for PowerLinux includes some additional documentation available with IBM Installation Toolkit. In addition, IBM Installation Toolkit provides links to other related documentation sites. You can select to browse documentation in either live or installed mode.

44

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

About this task


To browse documentation, follow these steps:

Procedure
1. From either live or installed mode, open the user interface. 2. Select Access documentation resources 3. Choose from the following options. v Select from the listed Local resources, which are PDFs that are available with IBM Installation Toolkit. Notes: If your browser does not support the PDF format, then the PDF is downloaded to your system. You can then use any PDF viewer to read it. If you are using the live system in text mode, the default download location for the local resources does not work. You must choose a location in the /tmp directory for the download to be successful. If you are using text mode and want to download local resources in PDF format, you must navigate to the resource and enter A or a. Simply pressing Enter will not select the PDF. After the PDF is selected, the PDF downloads, while a status window is displayed. v Select from the listed Online resources, which are links to related information centers and other web sites. Note: You must have an internet connection to view the web sites.

Troubleshooting
This section provides information about troubleshooting your system and IBM Installation Toolkit for PowerLinux.

Known problems and workarounds


The following list includes known issues and workarounds for installing and with the IBM Installation Toolkit for PowerLinux. v IBM Installation Toolkit can be used only on a system that is managed with a Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM), or on an unmanaged system with a serial console. It cannot be used on an unmanaged system with a graphics card and monitor. If a graphics card is installed in the system, when the IBM Installation Toolkit media is booting, a message such as init: networking main process (3258) terminated with status 1 might be displayed and the system might appear to hang. v In the authentication screen, only root is accepted as user. v Mozilla Firefox is the only supported web browser for graphical installations. v If a software repository is not accessible from the Linux installation wizard, ensure that your network is properly configured and working. Also, ensure that your system has a valid DNS server that is configured to be used in /etc/resolv.conf. v Remote installations with Windows HyperTerminal, Internet Explorer, and Web System Management PC Client are not fully supported. These installations might cause navigation issues, such as Home and End keys not working. v Matrox cards are the only fully supported graphics cards for starting in graphical mode. v QLogic Fibre Channel cards are not supported on POWER processor-based blade servers. v The IBM SAS RAID adapter CCIN 57B5 is not supported by the IBM Installation Toolkit.

Installing Linux with the IBM Installation Toolkit

45

v After a SUSE Linux Enterprise Server installation through the network, Yast might warn you that it cannot connect to the packages repository during system boot. You can safely click OK to try this operation again. v When you are manually partitioning on SUSE Linux Enterprise Server installations, if the disk contains all the four primary partitions (one of them being extended) and five or more logical partitions, Auto YaST might fail and cancel the installation. v When you are installing Red Hat Enterprise Linux 5, ensure that you do not have a USB key that is attached to the system as it might cause the Linux installer to fail. v When you are rebooting for the first time, Red Hat Enterprise Linux yaboot might not work automatically. You might have to press Enter at the prompt boot:. v Incomplete or incorrectly formed Linux startup messages can be safely ignored. v Serial terminals or serial-like terminals might not be the best for use because the terminal window refresh behavior is not adequate for this application. You might experience some window refresh problems when you are accessing your system with serial or serial-like terminals. Consider connecting with SSH sessions instead. v If the migration of user data fails when you are migrating a LAMP stack from System X to System P, the tool reports an error that states that mysql-server migration failed. v The System x to System p migration wizard automatically migrates only the data under the "DocumentRoot" of the web server. Custom directories with data that also must be migrated must be manually migrated through the manual data migration function of this tool. Directories such as users custom web server directories must be manually included into a migration plan. v SELinux must be disabled in a Red Hat Enterprise Linux source system for a migration to work. v Only virtual hardware is supported when you are creating LPARs with the Server Consolidation tool during LAMP stack migration. Make sure that the VIOS is configured to provide virtual disks and virtual Ethernet. v The cloning tool is limited to work only when you use it to clone from (back up) and restore to the same system. It might not work if you attempt to restore to a different system. v When you are using rescue mode to access the Linux recovery console, escape keys (Ctrl+C, Ctrl+Z, Ctrl+\) do not work. As a workaround, you can use SSH to connect. The keys can be used through an SSH connection. v Before you install a distribution in a Multipath storage system, you must ensure that none of the device partitions are part of LVM volume groups or RAID software arrays. v The Server Consolidation tool does not work for a target system with Multipath devices that are attached to it. v If a partitioning or other installation preparation issue prevents Linux installation, follow these steps: 1. Report the issue in the PowerLinux Community message board. 2. Reboot the system with the IBM Installation Toolkit. 3. Restart the installation process by selecting option "1 - Wizard mode (performs installation)".

Registering at IBM
You can register at the IBM website through the IBM Installation Toolkit for PowerLinux user interface.

Before you begin


To register, you must ensure that your system meets the following requirements: v The system has access to the external network (Internet). v The system is configured to use a DNS server. You can register manually, or, if you are running the IBM Installation Toolkit in live mode, you can use the network configuration tool.

46

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

About this task


After you register, you will have access to the IBM Installation Toolkit forum on the PowerLinux community site (https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32) as well as other content available at the IBM website. To register at the IBM website, follow these steps:

Procedure
1. From either live or installed mode, open the user interface. 2. Select Register at IBM 3. Select Click here to register. You will be redirected to the IBM registration page. Follow the instructions on that page. 4. Press uppercase B to return to IBM Installation Toolkit menus.

Getting customer support


IBM Installation Toolkit for PowerLinux is provided as is only. Customers are not entitled to IBM Software Support. However, you can get help from the PowerLinux community.

Getting product updates


The IBM Installation Toolkit for PowerLinux latest ISO image, documentation, and other related information can be found at the IBM Installation Toolkit for PowerLinux page (http://ibm.biz/BdxXsd).

Getting help from the PowerLinux community


You can submit questions and review technical information about the IBM Installation Toolkit for PowerLinux in the IBM developerWorks PowerLinux Community. You can go directly to the PowerLinux Community page (http://ibm.biz/BdxXrC), or go to IBM developerWorks (https://www.ibm.com/developerworks/mydeveloperworks/) and search for PowerLinux Community.

Error, information, and warning messages


The message codes are presented in alphabetic order to make them easy to find. Error and Warning messages are used to inform you of errors that could potentially compromise the system function or security. Information messages provide more information about items that could potentially cause problems. v BRLAU0001E: Authentication failure. The credentials entered were not accepted. Enter a different user name or password. v BRLAU0002E: No password provided. A password must be entered in the corresponding field. v BRLAU0003E: No user name provided. A user name must be entered in the corresponding field. v BRLAU0004E: Internal error. An internal error occurred. Verify whether the PAM installation is working correctly. v BRLAU0005E: Not a valid user name. The user name entered is invalid. Enter a different user name. v BRLAU0006E: No PAM module available to perform authentication. Verify whether your system has the python PAM module available and working. For SLES11 systems, ensure that the python-pam package is installed. v BRLAU0007E: Not able to identify installed Linux distribution. The tool could not determine which Linux distribution is installed. Verify that your file /etc/redhat-release (on RHEL systems) or /etc/SuSE-release (on SLES systems) is in the correct format.
Installing Linux with the IBM Installation Toolkit

47

v BRLAU0008E: The package pam-devel is not installed. Install it to perform authentication. Depending on the Linux distribution, the IBM Installation Toolkit might need the package pam-devel installed on the system to work properly. Install the package pam-devel provided by the distro in order to fix this problem. For RHEL systems, be sure to install the ppc version of the package. v BRLAU0009E: You must enable cookies to proceed. To authenticate, you must enable cookies in your web browser. v BRLAU0010I: Session expired due to inactivity. For security reasons, after some inactivity time you must sign in again. v BRLAU0011I: Your session has expired because a new user logged in. Your session has expired because a new user logged in. v BRLBE0001W: Unknown unit: %(error)s. The memory detector failed because an unrecognized memory size unit was found in /proc/meminfo. v BRLBE0005W: Cannot add files to a frozen %(name)s. The documentation search database is locked and can no longer have documents added to it. v BRLBE0006W: No levels specified for the search system. The number of indexing levels for the documentation search database has not been specified. Specify a number of indexing levels. v BRLBE0007W: No file specified for the search system index. No documents have been specified to be added to the documentation search database. Specify at least one document. v BRLBE0008I: Indexing: '%(name)s'.... The specified document is being added to the documentation search database. v BRLBE0009I: Search time: %(time)0.3fs. The documentation search database has had one document added to it in the specified number of seconds. v BRLBE0010I: Indexed %(doc)s documents in %(time)0.3fs. The documentation search database has been created in the specified number of seconds. v BRLBE0011I: Saved base: %(filename)s. The documentation search database has been created and written at the specified file. v BRLCS0001E: No host name specified. The hostname field was left blank. You must provide the host name of the client to proceed. v BRLCS0002E: Invalid host name. The host name entered in the hostname field is invalid. You must specify a valid host name for the client information. v BRLCS0003E: No IP address specified. The IP address field was left blank. You must provide the IP address for the client information. v BRLCS0004E: Invalid IP address. The provided IP address is either incomplete or in an invalid format. The IP address must follow the format [0-255].[0-255].[0-255].[0-255]. Examples of valid addresses are 10.2.0.1, 192.168.3.20. Examples of invalid addresses are 455.303.100.20 or 10.0.0. For more information, contact your network administrator. v BRLCS0005E: No MAC address specified. The MAC address field was left blank. You must provide the MAC address for the client information. v BRLCS0006E: Invalid MAC address. The provided MAC address is either incomplete or in an invalid format. The MAC address must follow the format [??]:[??]:[??]:[??]:[??:[??], where ? must be an integer from 0 to 9 or an uppercase character from A to F. Examples of valid addresses are 00:15:58:0B:5A:5F, 12:29:80:00:30:03 and 22:4C:90:00:30:03. For more information, contact your network administrator. v BRLCS0007E: No netmask specified. The network mask field was left blank. You must provide the network mask for the client information. v BRLCS0008E: Invalid netmask. The provided network mask is either incomplete or in an invalid format. The network mask must follow the format [0-255].[0-255].[0-255].[0-255]. Examples of valid netmasks are 255.255.255.0, 255.255.255.128.

48

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLCS0009E: Invalid gateway. The provided gateway is either incomplete or in an invalid format. The gateway must follow the format [0-255].[0-255].[0-255].[0-255]. Examples of valid gateways are 10.0.0.1 192.168.3.1. v BRLCS0010E: Invalid DNS server address. The provided DNS server address is either incomplete or in an invalid format. The DNS server address must follow the format [0-255].[0-255].[0255].[0-255]. Examples of valid DNS server addresses are 10.0.0.5 192.168.5.3. v BRLCS0011E: IP address already in use. The IP address entered is already in use by another device. Choose a different address and try again. v BRLCS0012E: Physical interface already in use by another subnet. You tried to configure a new subnet on a network interface that already has a subnet configured. Two subnets cannot use the same physical network interface. However, the DHCP server configuration allows this case if the subnets are enclosed in a shared-network declaration. The tool currently does not support adding such a statement, but you can do it manually and run the tool afterwards. Check the dhcpd.conf man page for further details on adding shared-network statements. v BRLCS0013E: DHCP configuration file not available. The wizard could not find the DHCP configuration file when trying to perform the operation. Ensure that the file is available and try again. v BRLCS0014E: Could not write DHCP file %s. Check the log for details. An unexpected error occurred while trying to write the DHCP configuration file to the file system. Check the application log for further details. v BRLCS0015E: Could not apply changes. Error restarting the DHCP service. Check the logs for details. The DHCP service failed to restart. Check the application log for the DHCP error message. v BRLCS0016E: Could not apply changes. Error performing backup of original DHCP file. Check the log for details. An unexpected error occurred when the tool tried to make a backup copy of the DHCP configuration file. Check the file system permissions and try again. v BRLCS0017E: Could not apply changes. Error writing the System Tools clients file. Check the log for details. An unexpected error occurred while trying to write the System Tools file to the file system. Check the application log for further details. v BRLCS0018W: Invalid clients found in DHCP configuration file. The tool encountered one or more hosts in the subnet that do not have a valid configuration. The hosts are missing a valid 'fixed-address' or 'hardware' header. You can manually edit the DHCP configuration file to fix the problem. v BRLCS0019E: No client selected. Select at least one client or click Skip to continue. If you choose to import clients, you must select at least one of them. Otherwise, click Skip to continue without importing any clients. v BRLCS0020E: Host name already in use. The host name entered is already in use. Try a different host name. v BRLCS0021E: MAC address already in use. The MAC address entered is already in use. The system you are trying to add is probably already registered. v BRLCS0022E: Could not read DHCP configuration file. Error at line %s, column %s. The DHCP configuration has a syntax error at the indicated location and the tool cannot read it. Check and correct the file syntax and try again. v BRLCS0023I: No clients registered. No clients are currently registered in the tool. v BRLCS0024E: No client selected. No client was selected to perform the operation. You must select a client for an action to be performed. v BRLCS0025E: Not able to find DHCP service template. The DHCP service template file /etc/init.d/dhcpd cannot be found. The DHCP server is probably not installed in the system. Verify that the DHCP server is properly installed and then run the tool again. v BRLCS0026E: Error when trying to read DHCP configuration file. Check the log for details. The System Tools application was not able to read the system DHCP configuration file due to an unexpected error. Consider creating a new empty file and then run the tool again.
Installing Linux with the IBM Installation Toolkit

49

v BRLCS0027E: Invalid headers entered. The configuration headers entered are in an invalid format. Check the syntax and try again. v BRLCS0028E: Invalid headers entered. Error at line %s, column %s. The configuration header entered at the specified location is in an invalid format. Check the syntax and try again. v BRLCS0029I: Debug: %s. This is a generic message used for debugging purposes only. v BRLCS0030W: DHCP configuration file not found. The System Tools application was not able to find the system DHCP configuration file. If you proceed, the tool will create a file at the standard location /etc/dhcpd.conf. v BRLCS0031E: Could not apply changes. Error performing backup of original System Tools file. Check the log for details. An unexpected error occurred when the tool tried to make a backup copy of the System Tools configuration file. Check the file system permissions and try again. v BRLCS0033W: Configuration has been changed. Click Apply changes to save your changes. Click Apply changes to save your changes before leaving the tool. If you quit the tool before clicking the button, all changes are lost. v BRLCS0034E: Unable to remove yaboot.conf file for the following clients: %s. The tool could not remove the yaboot files that became unused for the hosts listed. Try to remove them manually. v BRLCS0035E: Unable to create yaboot.conf file for the following clients: %s. The tool could not create the yaboot files for the hosts listed. Try to create them manually. v BRLCS0036E: No subnet selected. A subnet must be selected to proceed. v BRLCS0037E: Subnet entry not found. The subnet entry was not found by the tool. This might indicate an internal error. Try to restart the tool to fix the problem. v BRLCS0038W: Configuration has been changed. Remember to click Apply changes on the Client systems management window to save your changes. When the configuration is changed, it is not immediately saved. You must click Apply changes on the Client systems management window to save the changes to the system. v BRLCS0039I: No subnets registered. No subnets are currently registered in the tool. Therefore, there are no entries in the table. v BRLCS0040E: Could not write System Tools file %s. Check the log for details. An error occurred and the configuration file could not be saved. You can verify the application log for details on what might have caused the problem. v BRLCS0041I: No subnets registered. Register a subnet to proceed. No subnets are currently registered in the tool. To continue using the tool, you must register a new subnet. v BRLDB0001I: Debug: %s. This is a generic message used for debugging purposes only. v BRLDB0003E: Error when calling %(name)s%(args)s: %(msg)s, at %(file)s, line %(line)d. This is a generic message used for debugging purposes only. v BRLDP0001E: No partition selected. Select a partition from the displayed list. v BRLDP0002E: Invalid partition size. Type an integer number greater than zero in the 'Size' field to create the partition. v BRLDP0005E: Insufficient space to create a partition. The partition cannot be created because there is not enough available space on the disk. Enter a partition size for the new partition that does not exceed the available free space on the disk. v BRLDP0008E: Cannot edit a PReP boot partition. You cannot edit a PowerPC Reference Platform (PReP) boot partition. Instead, you can create a PReP boot partition by clicking 'Create PReP'. v BRLDP0011E: No disks selected. If there are two or more disks in the system, you must select one disk on which to create or delete partitions. v BRLDP0028E: No blank space selected. You must select an available or blank space to ensure that the new partition is created where no other partitions already exist.

50

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLDP0029E: Cannot edit a blank space. You selected to edit a blank space. A blank space cannot be edited, only selected to create a partition. v BRLDP0030E: Cannot edit an extended partition. You selected to edit an extended partition. An extended partition cannot be edited, only deleted. v BRLDP0031E: Cannot delete a blank space. You selected to delete a blank space. A blank space cannot be deleted, only selected to create a partition. v BRLDP0032E: The selected distribution cannot format a partition as %s. The file system type selected is not supported by the distribution. Format the partition as a different file system. v BRLDP0033E: The file system of a %s partition cannot be %s. The file system type selected is not compatible with the mount point for the partition. Select another file system or enter a different mount point. v BRLDP0035E: The selected distribution cannot have a %s partition. The mount point of the partition is invalid for the selected distribution. Enter a different mount point. v BRLDP0036E: The size of a %s partition must be exactly %d MB. For the specified partition type, you must enter the exact size given by the error message. v BRLDP0037E: The size of a %s partition must be at least %d MB. For the specified partition type, you must enter a size that is no less than the size given by the error message. v BRLDP0038E: The size of a %s partition must be at most %d MB. For the specified partition type, you must enter a size that is no more than the size given by the error message. v BRLDP0039E: The size of a %s partition must be between %d MB and %d MB. For the specified partition type, you must enter a size in the range given by the error message. v BRLDP0041E: Conflict found on partition %s when trying to fix %s. The same partition was selected for two or more fixes to be performed. Select a different partition for each fix. v BRLDP0042E: No fix selected. Select at least one fix. No fix was selected. You must select at least one fix to be performed. v BRLDP0043E: Partition size must be an integer. The size entered for the partition is invalid. Enter an integer number in the corresponding field. v BRLDP0044E: Partition size not specified. No size was entered for the partition. You must enter a size for the partition in the corresponding field. v BRLDP0045E: Mount point must be a path. The mount point entered is invalid. Enter a path as the mount point for the partition. v BRLDP0046E: Mount point not specified for partition to be formatted. For Red Hat Enterprise Linux installations, when you choose to format a partition as a file system other than swap or PReP, you must also specify a mount point for the partition. v BRLDP0047E: Primary partition %s has no file system or an unknown file system. For Red Hat Enterprise Linux installations, all primary partitions must be formatted as a valid file system. Edit and select a valid file system for the partition. v BRLDP0048E: Partition must have a mount point. For Red Hat Enterprise Linux installations, when creating a partition of type other than swap or PReP, you must also specify a mount point for the partition. v BRLDP0049E: Disk does not contain a valid MS-DOS partition table. The disk does not contain a valid MS-DOS partition table. To use the disk, you must create an MS-DOS partition table on the disk. v BRLDP0050W: Creating an MS-DOS partition table will cause any data contained in the disk %s to be lost. Are you sure you want to proceed? When an MS-DOS partition table is created, all data on the disk is lost. Therefore, you must confirm the operation. v BRLDP0051E: Partitions with file system "%s" cannot have a mount point. Do not specify a mount point. Partitions with the listed file system cannot have a mount point set. Leave the corresponding field blank.

Installing Linux with the IBM Installation Toolkit

51

v BRLDP0052E: The volume group name must contain only letters and underscores. The name of a volume group can contain only letters and underscores. Type a name that contains only those types of characters. v BRLDP0053E: Volume group name not specified. No volume group name was provided. Type a name for the volume group. v BRLDP0054E: The extent size must be an integer power of 2. The extent size for a volume group must be an integer number that is a power of 2, for example: 2, 4, 8, 16, and so on. Type a number that is a power of 2. v BRLDP0055E: Extent size for the volume group not specified. No extent size for the volume group name was provided. Type an extent size. v BRLDP0056E: No physical volumes available. Set a physical disk partition file system as "lvm" to create one. No physical volumes are available to create a volume group. Create a physical volume by setting the file system of a disk partition as 'lvm' and try again. v BRLDP0057E: Physical volume not specified. No physical volume was selected to be used. Select at least one physical volume to be used. v BRLDP0058E: Cannot remove %s. It does not exist. The specified physical volume cannot be removed because it does not exist. v BRLDP0059E: Cannot remove %s. It is used by the logical volumes: %s. The specified physical volume cannot be removed because it is used by the listed logical volumes. Remove some logical volumes first. v BRLDP0060E: Cannot remove %s. Insufficient space in the volume group. The specified physical volume cannot be removed because the volume group would not have space enough to contain all the logical volumes it currently contains. Remove some logical volumes first. v BRLDP0061E: Cannot remove %s. Unknown reason. The specified physical volume cannot be removed for an unknown reason. v BRLDP0062E: Cannot add %s. Unknown reason. The specified physical volume cannot be added for an unknown reason. v BRLDP0063E: No volume group selected for deletion. No volume group was selected. Select a volume group to delete. v BRLDP0064E: Cannot delete the volume group %s. Unknown reason. The specified volume group cannot be deleted for an unknown reason. v BRLDP0065E: No volume group selected for editing. No volume group was selected. Select a volume group to edit. v BRLDP0066E: Cannot edit the volume group %s. It does not exist. The specified volume group cannot be edited because it does not exist. v BRLDP0067E: Cannot delete /dev/%s. It is part of the LVM volume group %s. The specified partition cannot be deleted because it is a physical volume of the specified volume group. Remove it from the volume group first. v BRLDP0068E: Cannot edit /dev/%s. It is part of the LVM volume group %s. The specified partition cannot be edited because it is a physical volume of the specified volume group. Remove it from the volume group first. v BRLDP0069E: Cannot set /boot as the mount point for a non-physical disk partition. Only a physical disk partition can have the /boot directory set as the mount point. Set a physical disk partition instead. v BRLDP0070E: Volume group "%s" already exists. Type another name. A volume group with the specified name already exists. Enter a name that is not already used by another volume group. v BRLDP0071E: One or more partitions are part of an LVM volume group and cannot be deleted. At least one partition is used as a physical volume in an LVM volume group and cannot be deleted. Click [Manage VolGroups] to remove it from the volume group and try again. v BRLDP0072E: Partition name not specified. The partition name field was left blank. You must enter a name for the partition.

52

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLDP0073E: Partition "%s" already exists. Type another name. A partition with the specified name already exists. Enter a name that is not already used by another partition. v BRLDP0074W: The following partitions are missing: %s. The specified partitions are required by the chosen distribution but have not been provided yet. Create new partitions, or modify existing partitions for the chosen distribution. v BRLDP0075E: Disk %s contains more partitions (%d) than the maximum allowed (%d). The specified disk contains more partitions than the maximum number allowed. Remove some partitions before continuing. v BRLDP0076I: Disk %s contains the maximum number of partitions (%d). No more partitions can be added. The specified disk has reached the maximum number of partitions allowed. No more partitions can be added. v BRLDP0077E: The /boot mount point must be on a primary partition and next to the PReP partition. The /boot mount point must be on a primary partition and next to the PReP partition for the installation to work. v BRLDP0078E: Invalid partition name. The specified partition name is not valid. Type a different name. v BRLDP0079E: A logical volume name can contain only letters, digits, and the following characters: "+, -, _, and .". A logical volume name can contain only letters, digits, and the following characters: "+, -, _, and .". Type a different name. v BRLDP0080E: A logical volume name cannot start with "-". A logical volume name cannot start with "-". Type a different name. v BRLDP0081E: A logical volume name cannot be "%s". A logical volume name cannot be "%s". Type a different name. v BRLDP0082E: A logical volume name cannot contain "_mlog" or "_mimage". A logical volume name cannot contain "_mlog" or "_mimage". Type a different name. v BRLDP0083E: A volume group name can contain only letters, digits, and the following characters: "+, -, _, and .". A volume group name can contain only letters, digits, and the following characters: "+, -, _, and .". Type a different name. v BRLDP0084E: A volume group name cannot start with "-". A volume group name cannot start with "-". Type a different name. v BRLDP0085E: The specified name cannot be used because /dev/%s already exists. The chosen name cannot be used because /dev/%s already exists. Type a different name. v BRLDP0086E: Cannot delete /dev/%s. It is part of the RAID partition %s. /dev/%s cannot be deleted because it is part of the RAID partition %s. v BRLDP0087E: Cannot edit /dev/%s. It is part of the RAID partition %s. /dev/%s cannot be edited because it is part of the RAID partition %s. v BRLDP0088E: No RAID device was specified to be used. Select at least one RAID device to be used. v BRLDP0089E: No RAID devices available. Set a physical disk partition file system as "raid" to create one. No RAID devices are available. Set a physical disk partition file system as "raid" to create one. v BRLDP0090E: Invalid chunk size. The chunk size must be a number. v BRLDP0091E: No chunk size for the RAID partition specified. Type the chunk size for the RAID partition. v BRLDP0092E: Invalid number of spares for the RAID partition. The number of spares must be a number. v BRLDP0093E: No number of spares for the RAID partition was specified. Type the number of spares for the RAID partition. v BRLDP0094E: RAID 0 must have at least 2 RAID partitions and no spare partitions. RAID 0 requires at least 2 partitions and cannot have spare partitions. Modify your input to match these requirements.
Installing Linux with the IBM Installation Toolkit

53

v BRLDP0095E: RAID 1 must have at least 2 RAID partitions in addition to spare partitions. RAID 1 requires at least 2 partitions in addition to the spare partitions. Modify your input to match these requirements. v BRLDP0096E: RAID 5 must have at least 3 RAID partitions in addition to spare partitions. RAID 5 requires at least 3 partitions in addition to the spare partitions. Modify your input to match these requirements. v BRLDP0097E: RAID 1 and 5 must have 0 or more spare partitions. The number of spare partitions cannot be negative. Modify your input to match these requirements. v BRLDP0098E: RAID 1 on Red Hat Enterprise Linux 5 cannot have spare partitions. RAID 1 cannot contain spare partitions on Red Hat Enterprise Linux 5. Modify your input to match these requirements. v BRLDP0099E: PReP partition can not be set as a logical partition. Only a primary partition can be set as a PReP partition. Set a primary partition instead. v BRLDP0100W: The installation may not finish correctly due to a limitation on SUSE Linux Enterprise Server 11 installation using autoyast. Other mount points can be set on RAID devices except / to guarantee everything works fine. Do you want to proceed at your own risk? The installation may not finish correctly due to a limitation on SUSE Linux Enterprise Server 11 installation using autoyast. Other mount points can be set on RAID devices except / to guarantee everything works fine. v BRLDS0001E: Could not find search database. There is no documentation database installed. You must install the documentation to proceed. You can load it from DVD or from an ISO image. v BRLDS0002E: No file selected. No file was selected. You must select a file to view it. v BRLDS0003E: %s: Could not mount CD/DVD media. It was not possible to mount any media. Insert a CD/DVD in the drive and try again. v BRLDS0004E: Invalid media. The media is not the correct media for the IBM Installation Toolkit. Insert the IBM Installation Toolkit media and try again. v BRLDS0005E: Media does not contain documents. The media does not contain documents. Insert the IBM Installation Toolkit media with documents and try again. v BRLDS0006E: %s: Incorrect invocation or permissions. A mount error code 1 occurred. Refer to the mount manual for more information. v BRLDS0007E: %s: System error. Out of memory, cannot fork, or no more loop devices. A system error code 2 occurred. Refer to the mount manual for more information. v BRLDS0008E: %s: Internal mount error or missing NFS support. Ensure that you have Network File System properly installed and try the mount operation again. v BRLDS0009E: %s: User interrupt. The mount operation was interrupted by a user action. Try the mount operation again. v BRLDS0010E: %s: Error writing or locking /etc/mtab. It was not possible to write or lock /etc/mtab. Verify /etc/mtab permissions and ensure that the file system is not read-only. v BRLDS0011E: %s: Mount error. Some mount operations succeeded. A mount error code 64 occurred, but some mount operations succeeded. Refer to the mount manual for more information. v BRLHD0001I: Machine type: %(mtype)s. Your machine type has been detected as %(type)s. v BRLHD0002I: LPAR number: %(lpar)s. Your machine has been detected as an LPAR and its number is %(lpar)s. v BRLHD0003I: LPAR not detected. Your machine has not been detected as an LPAR. v BRLHD0004I: Video card: %(videoCard)s. Your machine has a video card and it was detected as %(videoCard)s. v BRLHD0005I: Net devices: %(device)s. Your machine has network devices and they have been detected as %(device)s. v BRLHS0001E: Unknown Content-type: %(type)s. The HTTP server has received a bad request. Data was sent in a unrecognized format.

54

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLHS0002E: 501 - Can POST only to CGI scripts. The HTTP server has received a POST request to get a static file. POST requests can only be made to invoke plugins. v BRLHS0004E: 503 - Script failed. The HTTP server detected that the execution of some script within IBM Installation Toolkit failed. Report this problem in the IBM Installation Toolkit Support Forum (https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32) for the development team to fix the problem. v BRLHS0005E: Exception while executing %(callable)s(%(url)s): %(error)s. The HTTP server detected that an error occurred inside a plugin and was not properly handled by it. v BRLHS0006E: Tried to access data outside root ('%(serverRoot)s'): '%(path)s'. The HTTP server detected an attempt to access a file in a restricted directory. v BRLHS0007E: No default specified for URL '%(path)s'. The HTTP server received a request for which no handler exists and a default handler has not been found to treat it. v BRLHS0008I: Server interrupted by keyboard. Exiting. The HTTP server has terminated because the user pressed CTRL+C. v BRLHS0010I: Starting watcher thread for TaskRunner %(pid)s. The HTTP server has started a watcher thread to look for a TaskRunner instance. v BRLHS0011W: TaskRunner %(pid)s is down. The HTTP server has not detected a working TaskRunner instance. v BRLHS0012W: Watcher thread did not find TaskRunner PID. The HTTP server watcher thread did not find a TaskRunner instance. v BRLIN0001E: Error setting locale: %(locale)s. This is a generic message used for debugging purposes only. v BRLIN0002E: Failed while setting locale %(lang)s %(error)s. This is a generic message used for debugging purposes only. v BRLIS0001E: No TFTP directory specified. The TFTP export directory field of the "Network Server Setup/Update" wizard was left blank. Specify the protocol export directory to continue. The IBM Installation Toolkit will copy all necessary files to set up the TFTP service into this directory. v BRLIS0003E: No ISO image file specified. The IBM Toolkit source field of the "Network Server Setup/Update" wizard was left blank. Specify the complete path of the ISO files to continue. The IBM Installation Toolkit will copy all necessary files to the repository directories. v BRLIS0005E: Invalid TFTP directory. The specified TFTP export directory is invalid. Specify a valid destination directory to continue. The directory entry must start with a forward slash (/) and cannot contain any empty spaces. v BRLIS0007E: Invalid DVD disk or ISO image file. The specified IBM Toolkit source information is invalid. Specify a valid destination directory to continue. The directory entry must start with a forward slash (/) and cannot contain any empty spaces. This information must include the ISO file name. v BRLIS0009E: Boot server software not running. A running DHCP server or TFTP server or both have not been found on the system. Ensure that you have both a DHCP and a TFTP server installed and running to continue. v BRLIW0013E: IBM Installation Toolkit media required to run installation wizard. The installation wizard can be run only from the IBM Installation Toolkit media. It cannot be run on a previously installed distribution. Start your system with the IBM Installation Toolkit media to install Linux. v BRLIW0017E: No IP address specified. The IP address field was left blank. Specify an IP address for the network card being configured. v BRLIW0022E: License terms must be accepted before continuing. To enter Welcome Center, you must accept the license terms. If you do not agree with the terms of the licenses, you can reject the license. However, rejecting the license makes it impossible to use Welcome Center.
Installing Linux with the IBM Installation Toolkit

55

v BRLIW0030E: No netmask specified. The netmask field was left blank. You must specify a network mask for the network card being configured. v BRLIW0032E: Invalid netmask. The specified netmask is invalid. You must specify a valid network mask for the network card being configured. v BRLIW0033E: Invalid gateway. The specified gateway is invalid. You must specify a valid gateway for the network card being configured. v BRLIW0034E: Invalid IP address. The specified IP address is invalid. You must specify a valid IP address for the network card being configured. v BRLIW0043W: Fingerprint check failed for %s. Do you want to proceed at your own risk? The IBM Installation Toolkit has found an inconsistency on either name, architecture, major version or minor version at media source. If you proceed, installation may not finish successfully. v BRLIW0044W: Could not find fingerprint for %s. Do you want to proceed at your own risk? The Welcome Center could not find the fingerprint on the specified source. This means that either the information to contact the server is incorrect or the specified repository was not set up with System Tools. Contact the source server administrator for more information. If you proceed with that source, installation may not finish successfully. v BRLIW0047E: No disks found on current system. No disks were found on current machine. In order to proceed with Linux installation, you must have one installed disk device on your system. v BRLIW0051E: Invalid DNS address. The DNS address entered is invalid. You must specify a valid DNS address for the network configuration. v BRLIW0054E: Invalid host name. The host name entered is invalid. You must specify a valid host name for the network configuration. v BRLIW0055E: No host name specified. The hostname field was left blank. You must specify a valid host name for the network configuration. v BRLIW0056E: Could not determine route to Install Server. Check the network setup. The wizard could not determine which network interface is being used to connect to the Install Server. Ensure that the system network is properly configured and try again. v BRLIW0058E: No valid Linux distribution CD/DVD found. No CD/DVD media containing a suitable Linux distribution was found. Ensure that you inserted the correct media and that it is not corrupted. v BRLIW0059I: Repository %s is not accessible. It was not possible to connect to external repositories. This problem might be caused by a firewall or an incorrectly configured network. Check your network configuration to ensure that the machine is able to connect to external sites. v BRLIW0060E: Could not mount USB device. The USB device is invalid. The device content might have been changed or the IBM Installation Toolkit image was not generated correctly. v BRLIW0061E: USB media cannot be used. Not able to retrieve UUID. Could not retrieve partition UUID (Universal Unique Identifier) information from the USB device. Try to generate a new IBM Installation Toolkit image for the device. v BRLIW1001I: No configured network interface found. The system network is not configured. You cannot perform network-based installations. Either configure the network or choose another installation type. v BRLIW1002I: No CD/DVD drive found. The system does not have a CD/DVD-ROM drive available. You cannot perform CD/DVD-based installations. Choose another installation type. v BRLIW1003E: No available installation media found. The IBM Installation Toolkit could not find any CD/DVD-ROM drive or network connection available on the system. At least one of these media are required in order to install the IBM Installation Toolkit.

56

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLIW1004E: No disks found on current system. The IBM Installation Toolkit could not find any disks available on the system. The system must have a disk to proceed with the installation. v BRLIW1005E: License terms must be accepted before continuing. The IBM Installation Toolkit cannot proceed until the license terms are accepted. v BRLIW1006E: Root password and confirmation password do not match. The root password and the confirmation entered are not the same. Be sure to type the same password in the root password and confirmation fields when you try again. v BRLIW1007E: Root password must be set. The root password field was left blank. A root password must be entered to continue the installation process. v BRLIW1008E: Selected distribution does not support Multipath. The selected distribution does not support Multipath devices. Either choose a device that is not Multipath, if available, or choose a distribution that supports Multipath devices. v BRLIW1009I: Selected disk %s is a Multipath device. Since the distro you've selected supports installation on Multipath, the path %s will be used instead. Selected disk %s is a Multipath device. Since the distro you've selected supports installation on Multipath, the path %s will be used instead. v BRLIW1100E: More than one source selected for driver update disk. You cannot select more than one source for driver update disk at a time. Select only one source for the driver update disk. v BRLIW1101E: No driver update disk file selected. No driver update disk was selected. You must select one to proceed. v BRLIW1102E: No distribution has been selected. The driver disk manager needs a distribution to be selected to work correctly. Start the wizard again and select a supported distribution. v BRLIW1103E: Could not mount media provided. The media provided is not valid. If you provided CD/DVD media, ensure that it is not corrupted. If you provided an image file, verify that it is valid. v BRLIW1104E: Cannot verify driver disk. Selected distribution is not supported. The driver disk needs a supported distribution selected to work correctly. Start the wizard again and select a supported distribution. v BRLIW1105E: Required file %s could not be found in driver disk. The driver disk provided is invalid because the indicated file is missing. Add the file to the driver disk or provide a different driver disk. v BRLIW1106E: Cannot verify driver disk. Selected distribution does not contain module vermagic information. The distribution selected for installation does not contain module vermagic information, which is necessary to make sure the modules provided by the driver disk can be safely loaded in the system for the distribution. Try to select a different distribution for installation. v BRLIW1107E: An error occurred while extracting the modules.cgz file contents. The contents of the indicated file could not be extracted due to an error. Try to start the process again or restart the system. v BRLIW1108E: File modules.cgz does not contain modules for kernel version of the selected distribution. The modules.cgz file contained in the driver disk does not have modules suitable for the kernel version of the distribution selected. Ensure that the driver disk provided is correct. v BRLIW1109E: Module vermagic information from driver disk does not match selected distribution. The vermagic information from the modules contained in the driver disk must match the distribution selected so that it can be safely loaded in the distribution's system. Ensure that the driver disk provided is correct. v BRLIW1110E: No modules could be found in driver disk. The driver disk provided does not contain any modules. Ensure that it is a valid driver disk and try again.

Installing Linux with the IBM Installation Toolkit

57

v BRLIW1111E: An error occurred while copying the driver disk contents to the system. An error occurred when copying the driver disk contents to the system. Try to begin the process again or restart the system. v BRLIW1112E: An error occurred when adding the driver disk. An error occurred when adding the driver disk. Try to begin the process again. v BRLIW1113E: A module that is not valid for Power Systems was found on the driver disk. The directory containing the modules to be used by the system contains a module that is not designed to work on Power Systems. Choose a valid driver disk. v BRLIW1114E: No more driver disks can be added. The maximum quantity of driver disks allowed at a time has been reached. You cannot add any more driver disks. v BRLIW1115I: The maximum quantity of driver disks has been reached. It's not possible to add more driver disks because the driver disk manager has reached the maximum quantity of driver disks allowed at a time. v BRLIW1116E: Driver disk content exceeds total size limit of %s. The total size of the driver disks cannot be greater than the size specified in the message. You can remove another driver disk to free some space or choose a smaller driver disk. v BRLIW1117E: No RPM package matching the selected distribution could be found in driver disk. The driver disk does not contain any RPM package that matches the selected distribution. Ensure that the driver disk provided is correct. v BRLIW1118E: Required file %s could not be read from driver disk. The file specified in the message could not be read. Ensure that the driver disk is accessible and try again. v BRLIW1119E: An error occurred while extracting the RPM package contents. The content of the RPM package from the driver disk could not be extracted. Ensure that the driver disk is not corrupted and try again. v BRLIW1120E: Protocol specified in URL not supported. You must specify a valid protocol for downloading the driver disk. Verify the instructions for the valid options. v BRLIW1121E: Specified URL is not accessible. The URL specified is not accessible. Verify the network connection and the address entered, then try again. v BRLIW1122E: Could not download file from specified URL. The wizard could not retrieve the file from the specified URL. Ensure that you entered a valid URL and that the file is accessible. Then try again. v BRLIW1123E: No URL specified. You must specify a URL from which to download the driver disk file. v BRLIW1124E: IBM Installation Toolkit must store files. Provide a formatted non-LVM partition with at least 100 MB of available space to continue. IBM Installation Toolkit requires some files to be stored on a physical disk partition to work. Provide a partition with at least 100 MB of available space that can be formatted. v BRLIW1125E: Required IBM packages not found. The IBM Installation Toolkit could not find all the required IBM packages in the repository. Check the repository and try again. v BRLIW1126E: Select one device to perform automatic partitioning. To do automatic partitioning, one device must be selected. Select one device and try again. v BRLIW1127E: Select one device without an LVM volume group partition activated, or use manual partitioning. The specified disk has at least one active LVM volume group. Choose another disk or try manual partitioning. v BRLIW1128E: Select one device without a RAID partition activated, or use manual partitioning. The specified disk has at least one active RAID partition. Choose another disk or try manual partitioning. v BRLIW1129E: Select a device on which to delete partitions. No device was specified. Select a device on which to delete partitions.

58

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLIW1130E: Detach LVM partition %(partition)s from volume group %(vg)s before deleting partition. A partition cannot be deleted if it belongs to an LVM volume group. Detach it from the volume group before deleting it. v BRLIW1131E: Detach RAID partition %(partition)s from RAID %(raid)s before deleting partition. A partition cannot be deleted if it belongs to a RAID array. Detach it from the RAID array before deleting it. v BRLIW1132W: The hostname for %s is invalid or not accessible. Do you want to proceed at your own risk? The specified hostname cannot be used. Ensure that it is a valid hostname and the network is correctly configured on your system. If you proceed, installation may not finish successfully. v BRLIW1133W: The disk %s is part of the LVM Volume Group(s) %s which will be destroyed if you continue. Are you sure you want to use that disk? The disk %s is part of the LVM Volume Group(s) %s, which will be destroyed if you decide to use the disk for automatic partitioning. Confirm you really want it to be done. v BRLIW1134W: The disk %s is part of the RAID array(s) %s which will be destroyed if you continue. Are you sure you want to use that disk? The disk %s is part of the RAID array(s) %s, which will be destroyed if you decide to use the disk for automatic partitioning. Confirm you really want it to be done. v BRLLC0001E: Error creating storage pool. An error occurred during the LPAR creation process when trying to create the storage pool. Check the log at /var/log/wui for details and verify that the HMC or IVM management system is properly configured. v BRLLC0002E: There is no MAC address information set up. A MAC address has not been passed to the DHCP module. v BRLLC0003E: There is no IP address information set up. An IP address has not been passed to the DHCP module. v BRLLC0004E: There is no host name information set up. A host name has not been passed to the DHCP module. v BRLLC0005E: There is an entry with same host name in DHCP configuration file. The passed host name is already used for another machine in the DHCP configuration file. v BRLLC0006E: There is an entry with same MAC address in DHCP configuration file. The passed MAC address is already used for another machine in the DHCP configuration file. v BRLLC0007E: Error while adding the new host to DHCP configuration file. There was a problem when trying to add a new host to DHCP configuration file. v BRLLC0008E: Error while updating or restarting DHCPD. There was an error when restarting the DHCP server. Verify that it is installed and properly configured. v BRLLC0010E: Unable to list available storage pools. The storage pools on the VIOS could not be listed. Check the log at /var/log/wui for details and verify that the HMC or IVM management system is properly configured. v BRLLC0011E: Target does not contains a management system. The information provided does not refer to a management system. Verify the information entered to ensure that it refers to an HMC or an IVM management system. v BRLLC0014E: Error creating virtual disk. An error occurred during the LPAR creation process when trying to create the virtual disk. Check the log file at /var/log/wui for details and verify that the HMC or IVM management system is properly configured. v BRLLC0015E: IP address already configured to another system. The IP address specified to be assigned to the LPAR is already assigned to another host in the DHCP configuration file. Specify another IP address. Consult your network administrator for available IP addresses. v BRLLC0016E: No available SCSI slots. No available SCSI slots were found in the HMC. An LPAR cannot be created without a SCSI slot. Create a SCSI slot in the HMC to proceed. v BRLLC0017E: LPAR name already in use. The name provided for the new LPAR is already in use by another LPAR in the HMC or IVM management system. Choose another name for the new LPAR.
Installing Linux with the IBM Installation Toolkit

59

v BRLLC0018E: No source system IP address specified. An IP address has not been specified to access the source system. Specify one to proceed. v BRLLC0019E: Source system IP address is not valid. An invalid IP address has been specified to access the source system. Specify a valid IP address to proceed. Example of a valid IP address: 192.168.1.54. v BRLLC0020E: No source system port number specified. A port number has not been specified to access the source system. Specify one to proceed. v BRLLC0021E: Source system port number is not valid. An invalid port number has been specified to access the source system. Specify a valid port number to proceed. A valid port number is an integer 0 - 65535. v BRLLC0022E: Source system root password not specified. A root password has not been specified to access the source system. Specify a root password to proceed. v BRLLC0023E: No management system IP address specified. An IP address has not been specified to access HMC or IVM management system. Specify an IP address to proceed. v BRLLC0024E: Management system IP address is not valid. An invalid IP address has been specified to access the HMC or IVM management system. Specify a valid IP address to proceed. Example of a valid IP address: 192.168.1.54. v BRLLC0025E: No management system port number specified. A port number has not been specified to access the HMC or IVM management system. Specify a port number to proceed. v BRLLC0026E: Management system port number is not valid. An invalid port number has been specified to access the HMC or IVM management system. Specify a valid port number to proceed. A valid port number is an integer 0 - 65535. v BRLLC0027E: Management system user not specified. A user name has not been specified to access the HMC or IVM management system. Specify a user name to proceed. v BRLLC0028E: Management system password not specified. A password has not been specified to access the HMC or IVM management system. Specify a password to proceed. v BRLLC0029E: No LPAR IP address specified. No IP address has been specified to be assigned to the LPAR. Specify an IP address to proceed. v BRLLC0030E: LPAR IP address is not valid. An invalid IP address has been specified to be assigned to the LPAR. Specify a valid IP address to proceed. Example of a valid IP address: 192.168.1.54. v BRLLC0032W: No profile was found for source system for the specified IP address. It was not possible to retrieve required information about the source system. The LPAR creation process cannot continue. Ensure that you specified the correct IP address. v BRLLC0033E: Insufficient storage resources available. No storage pools with space enough to perform an installation like the one present in the source system could be found to be assigned to the LPAR. The LPAR creation process cannot continue. v BRLLC0034E: Needed space could not be calculated. The disk space needed to perform an installation like the one present in the source system could not be determined. The LPAR creation process cannot continue. v BRLLC0035E: The specified host name is already assigned to another system. The specified host name is already used for another system in the DHCP configuration file. Choose another host name to proceed. v BRLLC0036E: No subnets found. No subnets have been found in the DHCP configuration file. Add a subnet to proceed, either manually or using the "Manage Client Systems" tool. v BRLLC0037E: No subnet specified. No subnet has been specified for the LPAR. Specify a subnet to proceed. v BRLMT0001E: No IP address specified. The IP address field was left blank. Specify an IP address for the source or target system to proceed.

60

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLMT0002E: IP address is not valid. The IP address given is not valid. Specify a valid IP address to proceed. The IP address must follow the format [0-255].[0-255].[0-255].[0-255]. Examples of valid addresses are 10.2.0.1 and 192.168.3.20. Examples of invalid addresses are 455.303.100.20 or 10.0.0. v BRLMT0003E: No port number specified. The SSH port number of the source system was not specified. The port number is necessary to upload the IBM Server Consolidation Tool public key to the source system. Provide the correct SSH port of the system. Contact the system administrator for more information. v BRLMT0004E: Port number is not valid. The given port number is not valid. Specify a valid port number. The port number must be an integer value in the range 0-65535. v BRLMT0005E: Root password not specified. The root password of the source system was not specified. Specify the correct password. v BRLMT0011E: Client sender error message: %s. An error occurred while starting the client consolidation application that retrieves the source profile. See the error message for more details. v BRLMT0012I: Sending the client consolidation application to %s. The client consolidation application is being sent to the given host. v BRLMT0013I: Transfer completed. The file transfer completed successfully. v BRLMT0014I: Client decompressed. The client consolidation application was decompressed successfully. v BRLMT0015I: Client consolidation application started. The client consolidation application is running. No problems reported. v BRLMT0016E: ERROR: The client consolidation application did not start. An error occurred while starting the client consolidation application. Check the logs for more information. v BRLMT0017E: ERROR: The upload of the client consolidation application to %s has failed. An error occurred while sending the client consolidation application to the given host. Check the logs for more information. v BRLMT0018E: Invalid IP address for Install Server. The provided IP address for the Install Server is either incomplete or in an invalid format. Specify a valid IP address to proceed. The IP address must follow the format [0-255].[0-255].[0-255].[0-255]. Examples of valid addresses are 10.2.0.1, 192.168.3.20. Examples of invalid addresses are 455.303.100.20 or 10.0.0. v BRLMT0019W: Could not connect to Install Server. The system tried to contact the Install Server at the specified IP address using the specified protocol but did not obtain any reply. This is probably caused by incorrect network configurations (incorrect IP address, incompatible protocol between the client and the server) or a temporary failure on the server. Check the network configuration and ensure that the IP address and network protocol used to access the server are correct. If the settings are correct, the server might be having problems. In this case, try again later or contact the server administrator for more information. v BRLMT0020E: The inserted Install Server directory is not valid. The specified directory for the Install Server is not in a valid format. Specify a valid directory to proceed. The directory entry must start with a slash ("/") and cannot contain any blank spaces. v BRLMT0021E: Invalid IP address for IBM Packages Server. The provided IP address for the IBM Packages Server is either incomplete or in an invalid format. Specify a valid IP address to proceed. The IP address must follow the format [0-255].[0-255].[0-255].[0-255]. Examples of valid addresses are 10.2.0.1, 192.168.3.20. Examples of invalid addresses are 455.303.100.20 or 10.0.0. v BRLMT0022E: Could not connect to the IBM Packages Server. The connection between the IBM Server Consolidation Tool system and the IBM Packages Server is not working. Verify the IP

Installing Linux with the IBM Installation Toolkit

61

address and protocol chosen for the IBM Packages Server communication. Most likely the IP address is not correct for the IBM Packages Server IP address, or the server is not set to work with the chosen protocol. v BRLMT0023E: Invalid directory for IBM Packages Server. The specified directory for the IBM Packages Server is not in a valid format. Specify a valid directory to proceed. The directory entry must start with a forward slash (/) and cannot contain any blank spaces. v BRLMT0024E: Fingerprint check failed on IBM Packages Server. The IBM Server Consolidation Tool could not check the fingerprint on the IBM Packages Server repository. Either the information to contact the server is incorrect, or the specified repository was not set up with System Tools. Contact the server administrator for more information. v BRLMT0025E: Fingerprint check failed on Install Server. The IBM Server Consolidation Tool could not check the fingerprint on the Install Server repository. Either the information to contact the server is incorrect, or the specified repository was not set up with System Tools. Contact the server administrator for more information. v BRLMT0026E: No protocol specified for Install Server. The protocol for the Install Server was left blank. Specify the protocol. The protocol is required for the IBM Installation Toolkit to retrieve the required packages. The available options are HTTP, FTP or NFS. v BRLMT0027E: No IP address specified for Install Server. The IP address field for the Install Server was left blank. Specify the IP address. The IP address is required for the IBM Installation Toolkit to retrieve the required packages for the Linux distributions. v BRLMT0028E: No directory specified for Install Server. The directory field for the Install Server was left blank. Specify the directory. The directory is required for the IBM Installation Toolkit to retrieve the required packages. v BRLMT0029E: No protocol specified for IBM Packages Server. The protocol for the IBM Packages Server was left blank. Specify a protocol. The protocol is required for the IBM Installation Toolkit to retrieve the required packages. v BRLMT0030E: No IP address specified for IBM Packages Server. The IP address field for the IBM Packages Server was left blank. Specify the IP address. The IP address is required for the IBM Installation Toolkit to retrieve the required packages. v BRLMT0031E: No directory specified for the IBM Packages Server. The directory field for the IBM Packages Server was left blank. Specify the directory. The directory is required for the IBM Installation Toolkit to retrieve the required packages. v BRLMT0032E: ERROR: Dependency error in client. The displayed information is a dependency of the Server Consolidation client application. Install the dependency and try again. v BRLMT0033E: Source architecture not supported. The architecture of the source system is not supported by the IBM Server Consolidation Tool. The source architectures supported are: x86 (i386, i486, i586, and i686) and x86_64. v BRLMT0034E: Source distribution not supported. The distribution of the source system is not supported by the IBM Server Consolidation Tool. The source distributions supported are: Red Hat Enterprise Linux 5 (and updates 1, 2, 3, 4, 5, 6, 7, 8 and 9), Red Hat Enterprise Linux 6 (6.0, 6.1, 6.2, 6.3, and 6.4), SLES 10 (and service packs 1, 1U1, 2, 3 and 4), and SLES 11 (and service packs 1 and 2). v BRLMT0035E: There is no possible target distribution for the current source. The IBM Server Consolidation Tool could not find a Linux distribution that matches the source system distribution and can be used for the target system. Verify that the source distribution is one of the supported distributions and try again. v BRLMT0036E: No hosts defined in System Tools. You must first define hosts in Server Management in the main menu. There is no target system candidate to migrate. Add at least one target candidate to complete a migration. To add a system as a target candidate, use the Server Management, Manage Client Systems option on the System Tools main menu. v BRLMT0037E: Target architecture not supported. The architecture of the target system is not supported by the IBM Server Consolidation Tool. The target architecture supported is POWER.

62

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLMT0038E: Target distribution not supported. The distribution of the target system is not supported by the IBM Server Consolidation Tool. The target distributions supported are: Red Hat Enterprise Linux 5 (Update 8 and 9), Red Hat Enterprise Linux 6 (6.3 and 6.4), SLES 10 (service pack 4), SLES 11 (service packs 1 and 2). v BRLMT0039E: Invalid MAC address for the target system. The MAC address of the target system is wrong or does not exist. Check the correct MAC address in the Server Management, Manage Client Systems option on the System Tools main menu. The MAC address must follow the format [??]:[??]:[??]:[??]:[??:[??], where ? must be an integer from 0 to 9 or an uppercase character from A to F. Examples of valid addresses are 00:15:58:0B:5A:5F, 12:29:80:00:30:03 and 22:4C:90:00:30:03. Contact your network administrator for more information. v BRLMT0040E: Error setting target system. An error occurred while the IBM Server Consolidation Tool was trying to set up the target system information. To recover, try restarting the migration process. v BRLMT0041I: Starting the migration process of the file %s. The given file is being migrated from the source system to the target system. v BRLMT0042E: ERROR: Could not connect to the RPC server %s:%s. An error occurred while trying to connect to the client consolidation application using RPC. Check the error message for more details. v BRLMT0043E: ERROR: Could not migrate the file %s. An error occurred while trying to migrate the given file from the source system to the target system. Check the log files for more information. v BRLMT0044E: Not able to load configuration file: "%s". Cannot load configuration file. Check the configuration file contents. v BRLMT0045I: Loaded "%s" from "%s". The client consolidation application module was loaded. v BRLMT0046E: Not able to load "%s" from module "%s". Error loading client consolidation application module. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0047E: No suitable interpreter for "%s". Could not find a valid interpreter for the given rule. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0048E: Error returned from code: -- START OF CODE -- %s -- EOF CODE --. Error returned while trying to retrieve information from the source system. Check the error message for mode details. v BRLMT0049I: Opening port "%s" on the firewall. Opening the required ports in the firewall so that the IBM Server Consolidation Tool can run properly. v BRLMT0050I: Closing port "%s" on the firewall. Closing the IBM Server Consolidation Tool and cleaning firewall rules. v BRLMT0051E: Program ended by signal "%s". Client consolidation application ended unexpectedly. Check the error message for details on the cause. v BRLMT0052I: Starting RPC Server on port "%s". Starting the client consolidation application RPC Server. v BRLMT0053E: Configuration file not found. Ending. Configuration file not found. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/ mydeveloperworks/groups/service/forum/topics?communityUuid=fe313521-2e95-46f2-817d44a4f27eba32 . v BRLMT0054I: Creating RPC connection: %s:%s. Creating RPC connection to the client consolidation application. v BRLMT0056E: ERROR: Could not create the FastStart file because the license agreement was not accepted. You must accept the IBM Installation Toolkit license agreement before the FastStart file can be created.
Installing Linux with the IBM Installation Toolkit

63

v BRLMT0058E: Home directories cannot be migrated unless users and groups are also migrated. To migrate the home directories from the source system to the target system, you must also migrate the users and groups. v BRLMT0059E: ERROR: Could not create the MySQL dump in client system. Could not dump the MySQL databases in the source system. Ensure that you entered the correct password and that your MySQL server is running in the client system. v BRLMT0061E: MySQL ERROR: %s - %s. Error accessing the MySQL server in the source system. Check the error message for more details. v BRLMT0062E: Not able to serialize profile. The profile could not be prepared for transfer using RPC. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0064W: Invalid source. Could not find a valid source profile for translation. Check the log files for more information. v BRLMT0065W: Invalid target. Could not translate the source profile to the target system. An error occurred while defining the target system. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/ forum/topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0066W: Error trying to run %s.translate(). An error occurred while translating the source profile to the target system. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0067E: Error translating from source system to target system. An error occurred while translating the source profile to the target system. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/ forum/topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0068E: Error writing installation file. An error occurred while writing the installation file. Ensure that the disk is not full. v BRLMT0069E: Error migrating group %s - %s. The given group could not be migrated from the source system to the target system. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0070E: Error while dumping GroupsInfo. Cannot migrate users. An error occurred while migrating the users from source system to target system. Could not interpret user group information. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0071E: Error migrating user %s - %s. The given user could not be migrated. Check the error message for more details. v BRLMT0072E: No host name specified. The host name of the target system is incorrect or does not exist. Check the correct host name in the Server Management Manage Client Systems icon of the System Tools main menu. v BRLMT0073E: Process already running with PID %s. Use --force to override. An instance of the run_client.py command with the same product ID is already running. You must use the --force switch to end the old process and open a new one. v BRLMT0074E: Terminating unregistered process %s. An instance of the run_client.py command is running but is not registered in /var/run/xmm.pid. This process is being terminated. v BRLMT0075E: The specified path does not exist in the source system. The path of the additional data does not exist in the source system. Verify the correct path and try again.

64

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLMT0076E: Error while connecting to source system to validate the specified path. The IBM Server Consolidation Tool could not connect to the source system to verify that the path of an additional file exists. Ensure that the network of the source system is up and running and try again. v BRLMT0077E: Cannot migrate the specified path. The specified path of the additional file is not a valid path for migration. The following paths are considered invalid for migration as additional files: /, /bin, /dev, /lib, /sbin, /proc, /usr, /boot, /etc, initrd, /opt, /selinux, /sys and /var. If this path were to be migrated, the target system would not work. v BRLMT0078E: Exception: %s. An exception occurred. Check the error message for more details. v BRLMT0079E: Error getting remote system information. The source system profile could not be created because the source system information could not be retrieved. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/ mydeveloperworks/groups/service/forum/topics?communityUuid=fe313521-2e95-46f2-817d44a4f27eba32 . v BRLMT0080E: Not able to read profile for source system. The profile from the source system could not be serialized. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0081E: SSH login failed. The IBM Server Consolidation Tool could not connect to a remote system using SSH. Ensure that the SSH server is up and running in the remote system and try again. v BRLMT0082E: No /root/.ssh directory in client system. The IBM Server Consolidation Tool found two possible problems. First, there is no /root/.ssh directory in the source system. Second, the source system public key has changed and the Network Server system (System Tools system) does not recognize it anymore. Create the directory and delete the old source system public key information from the root known_hosts file and try again. v BRLMT0083E: Invalid source. Could not get source system information. Unable to migrate data. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/ developerworks/mydeveloperworks/groups/service/forum/topics?communityUuid=fe313521-2e95-46f2817d-44a4f27eba32 . v BRLMT0084E: Invalid target. Could not get target system information. Unable to migrate data. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/ developerworks/mydeveloperworks/groups/service/forum/topics?communityUuid=fe313521-2e95-46f2817d-44a4f27eba32 . v BRLMT0085E: Target RPC server closed. Successfully closed the RPC connection with target system. v BRLMT0086E: Source RPC server closed. Successfully closed the RPC connection with source system. v BRLMT0088E: Cannot validate distribution repository. No distribution is available. The Install Server could not be validated. Verify that there is a compatible installation directory (repository) with the target system distribution value and try again. v BRLMT0089E: Cannot validate distribution repository. No repository information is available. The Install Server could not be validated. Verify that the installation directory (repository) is accessible through the network and try again. v BRLMT0090E: Protocol is not supported. The protocol chosen to install the distribution is not supported. The supported protocols are: HTTP, FTP, and NFS. v BRLMT0091E: Cannot validate IBM Installation Toolkit repository. No repository information. The IBM Packages Server could not be validated. Verify that the Packages directory (repository) is accessible through the network and try again. v BRLMT0092E: Registering '%s interpreter' for '%s' on '%s'[%s]. The given interpreter was registered in the client consolidation application.

Installing Linux with the IBM Installation Toolkit

65

v BRLMT0093E: Error while creating symbolic links. The IBM Server Consolidation Tool could not create the necessary symbolic links to run the client application. Verify that you are running the System Tools as root and that the /etc directory has the correct permissions to run the job. v BRLMT0094I: Public key transfer completed. Successfully transferred the IBM Server Consolidation Tool public key (SSH) to the source system. v BRLMT0095E: Error while transferring public key. The IBM Server Consolidation Tool public key could not be transferred to the source system. Verify that the SSH is up and running in the source system, and that the SSH port of the source system is open in the source system firewall. v BRLMT0096E: Error while adding public key into authorized_keys file. The IBM Server Consolidation Tool public key could not be inserted in the file that gives remote authorization to the source system. Verify that the /root/.ssh/authorized_keys file exists and that its permissions allow root to write to it. v BRLMT0097E: Not able to load rule (%s). Not able to load the given rule inside the client consolidation application. Check for a syntax error in the XML file where the rule is described. v BRLMT0098E: Not able to load configurations on %s. Ending. Not able to load configurations for the client consolidation application. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/groups/service/forum/ topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0099E: More than one mail profile selected. The IBM Server Consolidation Tool allows you to select only one mail profile (for example, Sendmail or Postfix) at the same time. Choose one profile to proceed. v BRLMT0113E: Not able to retrieve drc_name for %s. The tool could not retrieve the drc_name for the device during the LPAR creation process. Check the log at /var/log/wui for details and verify that the HMC or IVM system is properly configured. v BRLMT0114E: Error mapping virtual SCSI adapter (vhost) to physical devices. An error occurred during the LPAR creation process. Check the log at /var/log/wui for details and verify that the HMC or IVM system is properly configured. v BRLMT0117E: Not able to create LPAR: %s. An error occurred while creating the LPAR during the migration process. Check the error message for more details. v BRLMT0118E: Not able to bind LPAR '%s' to storage '%s'. The LPAR Creator tool could not bind the LPAR to the virtual disk during the LPAR creation process. Check the log at /var/log/wui for details and verify that the HMC or IVM system is properly configured. v BRLMT0119E: Not able to set up DHCP Server for the new LPAR. The LPAR Creator tool could not register the new LPAR in the DHCP server. Check the log at /var/log/wui for details on the cause of the error. v BRLMT0120E: Not able to create virtual ethernet adapter. The LPAR Creator tool could not create a virtual Ethernet adapter for the new LPAR during the creation process. Check the log at /var/log/wui for details and verify that the HMC or IVM system is properly configured. v BRLMT0122E: Unable to retrieve MAC address for virtual network interface. The LPAR Creator tool could not retrieve the MAC address of the LPAR network interface when registering it on the DHCP server. Check the log at /var/log/wui for details and verify that the HMC or IVM system is properly configured. v BRLMT0123E: Unable to remove LPAR. An error occurred during the LPAR creation process, and the LPAR Creator tool failed to issue a command to remove the LPAR. Check the log at /var/log/wui for details and verify that the HMC or IVM system is properly configured. v BRLMT0124E: Invalid MySQL root password. The MySQL root password supplied to the IBM Server Consolidation Tool is invalid. A valid password is needed in order to access the MySQL server on the source system. Check the password and try again.

66

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLMT0125E: Problem with MySQL installation on the source system. The IBM Server Consolidation Tool was not able to start the MySQL server on the source system. Verify that the MySQL server is correctly configured and can be started. v BRLMT0126E: Error: could not migrate path %s - code: %s - %s. An error occurred while migrating additional data from source system to target system. Check the IBM Installation Toolkit for PowerLinux Support Forum, https://www.ibm.com/developerworks/mydeveloperworks/ groups/service/forum/topics?communityUuid=fe313521-2e95-46f2-817d-44a4f27eba32 . v BRLMT0127E: Invalid path. The given path is not valid. Ensure that it exists in the source system and can be accessed by the root user. v BRLMT0128E: Invalid URL for distribution packages repository The URL provided as the distribution packages repository is invalid. Enter a valid URL to proceed. v BRLMT0129E: Invalid URL for IBM packages repository The URL provided as the IBM Installation Toolkit packages repository is invalid. Enter a valid URL to proceed. v BRLMT0130E: No target system selected. You must select a target system to proceed with this operation. v BRLMT0131E: No source system selected. You must select a source system to proceed with this operation. v BRLMT0132E: No disks specified. Specify at least one disk. No disks specified. Specify at least one disk to proceed. v BRLMT0133E: No disk selected. Select a disk to be removed. No disk selected. Select an existing disk in the table to remove it. v BRLMT0134E: No disk selected. Select a disk to be edited. No disk selected. Select an existing disk in the table to edit it. v BRLMT0135E: No disk size specified. No disk size provided. Type the size of the target machine disk, in the unit you choose (for example, MB, GB, or TB). v BRLMT0136E: Invalid disk size. The disk size must be an integer number. The specified disk size is not valid. Type an integer number for the disk size, in the unit you choosen (for example, MB, GB, or TB). v BRLMT0137E: No device name provided. No device name provided. Type the device name of the disk in the target machine (for example, sda or sdb). v BRLMT0138E: Invalid device name. The device name must contain only alphabetic characters. The specified device name is not valid. Type a device name containing only alphabetic characters (for example, sda or sdb). v BRLMT0139E: Disk '%s' already exists. Type another name. A disk with the specified name already exists. Type another name. v BRLMT0140E: Host name cannot be resolved. Ensure that it is correct and try again. The host name cannot be resolved. Ensure that it is correct and try again. If the host name is correct, ensure that the network is configured and working, and has a DNS server set up. v BRLMT0141I: In order to avoid rounding problems, only 90%% of the specified disk size will be used. In order to avoid rounding problems, only 90%% of the specified disk size will be used. This is to minimize the risk of insufficient disk space problems when the migration starts on the target machine. No further actions need to be taken. v BRLMT0142E: Disk '%s' does not exist. Please choose another disk to be edited. A disk with the specified name does not exist. Please choose another disk to be edited. v BRLMT0143E: Error connecting to source system to check MySQL password. Try again. Error connecting to source system to check MySQL password. Ensure that network is up and running on both server and source systems and try again. v BRLMU0001E: Firmware update not supported. IBM Installation Toolkit does not support firmware updates of an LPAR managed by Hardware Management Console (HMC) or Integrated Virtualization Manager (IVM). You must perform firmware updates through the HMC or IVM interface.
Installing Linux with the IBM Installation Toolkit

67

v BRLMU0002W: Could not determine architecture of system. The architecture of the system running the IBM Installation Toolkit could not be automatically determined. This problem probably means that you are running the system using an HMC. If so, you should use the HMC interface to perform the action. v BRLMU0003E: Error retrieving firmware information. The wizard was not able to determine the firmware data for the system. This might be caused by a missing or incorrectly installed lsvpd package. Verify that the package is running correctly on the system. v BRLMU0004E: Permanent firmware running. Firmware updates cannot be performed while the system is running with the firmware from the permanent side. Restart the system with the firmware from the temporary side and try again. v BRLMU0005E: Could not mount CD/DVD. The wizard was not able to create the mount point directory in order to mount the IBM Installation Toolkit media. Verify that the file system permissions are correctly set to allow the creation of the mount point directory specified in the error message issued by the wizard and try again. v BRLMU0006E: IBM Installation Toolkit media not found. The wizard could not find the IBM Installation Toolkit media in any of the optical devices. Check the media inserted and try again. v BRLMU0007E: No firmware available. The IBM Installation Toolkit media does not contain any suitable firmware image for the system. Consider downloading a firmware image file and select it at the file system menu in the wizard. v BRLMU0008I: No CD/DVD drive found. No CD/DVD drive was found in your system. Therefore, no option is available to load firmware images from the IBM Installation Toolkit DVD. If you have a CD/DVD drive, it might not be working. v BRLMU0009E: Could not validate file type. IBM Installation Toolkit media not found. A problem occurred while trying to access the media in the drive. Verify that the media is inserted in the drive and it is working correctly. v BRLMU0010E: The file %s is not a valid firmware image. The firmware file selected is not a valid RPM package or raw data file. Verify the file provided and try again. v BRLMU0011E: No firmware image file selected. You must select a firmware image file to proceed. v BRLMU0012E: Error installing firmware RPM package. An error occurred when installing the RPM package provided. Verify that the package file is valid. v BRLMU0013E: Error creating temporary directory /tmp/fwupdate. The wizard was not able to create the directory /tmp/fwupdate. Verify that the file system permissions allow the creation of this directory and try again. v BRLMU0014E: Error copying image file to temporary directory /tmp/fwupdate. The firmware file could not be copied to the directory /tmp/fwupdate. Verify that the file system permissions are set correctly to allow files to be copied to this directory and try again. v BRLNC0001E: No network card selected. You must select a network card to be configured from the network interfaces list. v BRLNC0002W: The interface link is currently down or cannot be determined. The network interface selected has no link or no cable connected, or its status cannot be determined. You can continue configuring it, but it might not work until the link is up. v BRLNC0003E: Invalid IP address specified. The IP address entered is not a valid address. Specify a valid IP address so that the IBM Installation Toolkit can set the IP address for the selected network interface. If you do not know this information, contact your network administrator. v BRLNC0004E: No IP address specified. The IP address field was left blank. Specify an IP address so that the IBM Installation Toolkit can set the IP address for the selected network interface. If you do not know this information, contact your network administrator.

68

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLNC0005E: Invalid network mask specified. The network mask inserted is not a valid mask. Specify a valid network mask so that the IBM Installation Toolkit can set the selected network interface. If you do not know this information, contact your network administrator. v BRLNC0006E: No network mask specified. The network mask field was left blank. Specify a network mask so that the IBM Installation Toolkit can set the network interface correctly. v BRLNC0007E: Invalid gateway specified. The gateway address entered is not a valid gateway. The gateway address field is an optional field. Specify a valid gateway address or leave the field blank so that the IBM Installation Toolkit can configure the selected network interface. v BRLNC0008E: Invalid DNS server specified. The DNS server address entered is not valid. The DNS server address field is an optional field. Specify a valid DNS address or leave the field blank so that the IBM Installation Toolkit can configure the selected network interface. v BRLRG0001E: Network not configured. The network is not properly configured. Configure the network so that the IBM Installation Toolkit can connect to the IBM registration website. v BRLRK0001E: Invalid or missing task. The application could not be launched because it was not specified or is invalid. v BRLRK0002E: Missing previous URL. The application could not be launched because the previous URL argument was not specified. v BRLRK0003E: Missing previous name. The application could not be launched because the previous name argument was not specified. v BRLRK0004E: Communication error with launcher: %(error)s. The listed error occurred when communicating with the TaskRunner. v BRLRK0005I: Running task at %(where)s with command %(cmd)s and arguments %(args)s. The listed application was launched at the specified location with the described arguments. v BRLRK0006E: Could not launch external application %(error)s. The listed error occurred when launching the application. v BRLRK0007I: Finished. Relaunching eLinks browser now. The application finished and the eLinks browser was relaunched. v BRLRK0008I: Finished. Relaunching w3m browser now. The application finished and the w3m browser was relaunched. v BRLRK0009E: Could not launch w3m browser. The application finished and the w3m browser was not relaunched. v BRLRM0001E: Not able to identify Linux distribution installed. Could not determine the running Linux distribution. This problem might be caused by a missing /etc/SuSE-release or /etc/redhat-release file on the system. Check the file availability and run the Repository Management wizard again. v BRLRM0002E: Error retrieving information from repository manager. It was not possible to retrieve information from the repository manager for the system. Ensure that the package manager for the system (Zypper on SUSE Linux Enterprise Server or YUM on Red Hat Enterprise Linux) is working properly. See the logs for details. v BRLRM0003I: No repositories available. No repositories are available in the system. You can add a new repository by clicking Add Custom. v BRLRM0004E: NFS repositories cannot be activated on Red Hat Enterprise Linux. Network File System (NFS) repositories cannot be activated manually on Red Hat Enterprise Linux systems. Choose another repository to activate. v BRLRM0005E: No repository selected. No repository was selected. Select a repository and try again. v BRLRM0006E: No repository name specified. The repository name field was left blank. You must specify a repository name to continue. v BRLRM0007E: No location specified. The location field was left blank. You must specify a location of the repository to continue.
Installing Linux with the IBM Installation Toolkit

69

v BRLRM0008E: Invalid location entered. The location entered is invalid. You must specify a valid location according to the chosen resource type to continue. v BRLRM0009E: No destination directory specified. The destination directory field was left blank. You must specify a destination directory to continue. v BRLRM0010E: Invalid directory entered. Cannot use a system directory. The directory location entered is invalid. The location cannot be a system directory. Specify a directory that is not a system directory. v BRLRM0011E: No media found. No media were found in any drive. Insert the media and try again. v BRLRM0012E: Error loading YUM-related libraries. The wizard failed to load a required Yellowdog Updater, Modified (YUM)-related library. Ensure that you have YUM and its dependencies correctly installed in the system and try again. Check the logs for details. v BRLRM0014E: Error loading wizard repository manager The wizard failed to load the repository manager and cannot proceed. Check the logs for details. v BRLRM0015E: Directory already exists. The directory entered already exists. You must specify a new directory to continue. v BRLRM0016E: Directory name cannot contain spaces. The directory name entered contains spaces. You must specify a name without spaces to continue. v BRLRM0017E: Linux distribution not supported. This tool does not support Red Hat Enterprise Linux 4 systems due to their lack of repository management support. If you still want to use Red Hat Enterprise Linux, consider installing a newer version of the distribution. v BRLRM0018E: Repository name %s already exists. The repository name entered already exists. Choose a different name to continue. v BRLRM0019E: Repository URL %s already installed. The repository location already exists. Choose a different location to continue. v BRLRT0001E: The IBM RAS Tools wizard cannot be used from the IBM Installation Toolkit live CD. The IBM RAS Tools wizard is disabled. This problem happens when trying to use the RAS Tools wizard from the IBM Installation Toolkit live CD. v BRLRT0002E: Not able to identify Linux distribution installed. The IBM RAS Tools wizard could not determine which Linux distribution is installed. Verify that your file /etc/redhat-release (on Red Hat Enterprise Linux systems) or /etc/SuSE-release (on SUSE Linux Enterprise Server systems) is in the correct format and try again. v BRLRT0007E: Package license terms must be accepted before continuing. To proceed with the IBM RAS Tools packages installation process, you must accept the license terms. If the licenses are not accepted, the IBM RAS Tools wizard cannot continue the packages installation. v BRLRT0008E: No packages selected for installation. You selected no IBM RAS Tools packages for installation. To continue with the IBM RAS Tools packages installation, select at least one package for installation. v BRLRT0009W: Another task is already running. Wait until it is finished and try again. Two installation tasks cannot run at the same time. If an installation process is running and a new installation is attempted, the new installation will not start and the output of the currently running installation will be displayed. v BRLRT0010E: Error initializing repository management subsystem. Check the log for details. The IBM RAS Tools wizard failed to initialize the package manager for the system (Zypper on SUSE Linux Enterprise Server or YUM on Red Hat Enterprise Linux). Check the application log for further details. v BRLRT0011E: Debug: %s. This is a generic message used for debugging purposes only. v BRLRT0012W: At least one external package cannot be displayed because the repository is not installed on system. An external package is available for installation. However, its repository is not installed in the system. Use the Repositories Management tool to add the external repositories that are available and try again.

70

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLRT0013W: IBM packages cannot be displayed. Add an IBM repository in order to display them. The IBM packages cannot be installed if the repository containing them is not installed in the system. Use the Repositories Management tool to add an IBM Installation Toolkit repository to the system and try again. v BRLRT0014E: No packages can be displayed. Add repositories in order to display them. The tool could not find any suitable repositories installed in the system. Use the Repositories Management tool to add the IBM Installation Toolkit repository and external repositories and try again. v BRLRT0015I: Some repositories could not be verified and were disabled temporarily. Some repositories may be offline or corrupted. Check the network configuration. v BRLSN0001E: No exported path is available. At least one exported path must be available to add a repository. Add an exported path to proceed. v BRLSN0002E: Directory name specified is invalid. The directory name entered is invalid. The directory name must contain only alphanumeric characters, dashes, and underscores. Specify a valid directory name to proceed. v BRLSN0003E: Directory name specified already exists in the export path. A directory with the specified name already exists. Enter the name of a directory that does not already exist in the file system to proceed. v BRLSN0004E: Directory name was not specified. No directory name was specified. A directory name must be specified to continue. v BRLSN0005E: The distribution does not support the selected media. The media type selected is not supported by the distribution. Choose an appropriate media type and try again. v BRLSN0008E: Not all required ISOs were provided. You have selected a number of ISOs that is less than the quantity needed. Select a number of ISOs that corresponds to the distribution and media type chosen. v BRLSN0010E: Insufficient disk space. The required space to create the repository is not available on the disk. Remove files to free the necessary disk space before proceeding. v BRLSN0011W: Other running tasks might use required available space. Other tasks are running that might consume the disk space available. Consider ending some of these tasks to ensure that they do not consume all required free space before proceeding. v BRLSN0100E: No path specified. No path was specified. Specify a path to proceed with this operation. v BRLSN0101E: No export URL path specified. No export URL path was specified. Specify an export URL path to proceed with this operation. v BRLSN0102E: Path does not exist. The path specified does not exist. Specify an existing path to proceed with this operation. v BRLSN0103E: Path already exported on protocol. The path specified is already exported for the chosen protocol. Specify a path not yet exported for the protocol to proceed. v BRLSN0104W: Export path to be deleted contains repositories. The export path to be deleted contains repositories. These repositories will no longer be available if you proceed with the operation. v BRLSN1000E: Repository creation canceled. The repository creation task has been canceled. v BRLSN1001E: The distribution is not supported. The distribution chosen for repository creation is not supported. v BRLSN1002E: The media source is not supported. The media source type is not supported. v BRLSN1003E: Media not found. Provided media has not been found. Verify that it is correct. v BRLSN1004E: The media type not determined. An internal error occurred and the media type could not be determined. Check the log at /tmp/log for details. v BRLSN1005E: Only the root user can create a repository. You must be logged on as the root user to create repositories.

Installing Linux with the IBM Installation Toolkit

71

v BRLSN1006E: The destination directory could not be created. The destination directory could not be created. Check the log at /tmp/log for details. v BRLSN1007E: The environment could not be set. The environment could not be set. Check the log at /tmp/log for details. v BRLSN1008E: Verification error. A verification error occurred. Check the log at /tmp/log for details. v BRLSN1009I: ISO image for %s could not be found. Enter the ISO image path and click OK. The given ISO image could not be found. Enter the correct path for the image to proceed with the operation. v BRLSN1010I: Insert the disk %s and click OK. Insert the given disk to proceed with the operation. v BRLSN1011I: A disk could not be found in the drive. Insert the disk into the drive and click Retry after the drive light stops blinking. No disk could be found in drive. Ensure that there is a disk inserted and that it is not corrupted. v BRLSN1012I: There was an error when copying this media. An error occurred while copying the given media. Try again, or replace the media, which might be corrupted. v BRLST0001E: Install IBM Installation Toolkit Simplified Setup Tool to proceed IBM Installation Toolkit Simplified Setup Tool is not installed. Install at least one of the described packages in order to proceed and use it. v BRLST0002E: Start IBM Installation Toolkit Simplified Setup Tool to proceed IBM Installation Toolkit Simplified Setup Tool is not running. You need to start it by running the command '/etc/init.d/sst start'. v BRLST0003W: Confirm you want to leave IBM Installation Toolkit for Linux If you go to IBM Installation Toolkit Simplified Setup Tool there will be no way to go back to IBM Installation Toolkit for Linux. Click [Yes] to confirm and go to IBM Installation Toolkit Simplified Setup Tool, or [No] to go back to the main menu of IBM Installation Toolkit for Linux. v BRLTM0001E: No task has been selected No task has been chosen. A task must be selected prior to accessing its details. v BRLTM0004E: The task is finished and cannot be canceled Once a task is finished, it cannot be canceled anymore. v BRLTP0001E: BRLTP0001E: Template error. '%(name)s' uses invalid key %(error)s. An internal error occurred caused by an invalid key used on a mapping or sequence. v BRLTP0002E: BRLTP0002E: Template error. '%(name)s', unknown exception %(error)s. An unknown internal error occurred. v BRLTP0003E: BRLTP0003E: Invalid key was required by %(error)s. An internal error occurred caused by an invalid key used on a mapping or sequence. v BRLTP0004E: BRLTP0004E: Unknown error %(error)r. An unknown internal error occurred. v BRLTP0005E: Template error: %(error)s %(template)s An error occurred when building the HTML content from the template. v BRLTR0001E: Problem while sending data %(error)s to server. An error occurred when sending data to the server. v BRLTR0002E: Problem packing data to send (%(error)s). An error occurred when packing data to send to the server. v BRLTR0003E: Problem receiving data %(error)s from server. An error occurred when receiving data from the server. v BRLTR0004E: Problem unpacking received data (%(error)s). An error occurred when unpacking the data received from the server. v BRLTR0005E: Could not connect to server (%(error)s). An error occurred when trying to connect to the TaskRunner server.

72

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLTR0006E: Problem closing connection (%(error)s). An error occurred when trying to close a socket. v BRLTR0007E: Operating system error: %(error)s. This is a generic message used for debugging purposes only. v BRLTR0008E: Invalid request: %(request)s. The TaskRunner received the described invalid request. v BRLTR0009E: Socket error: %(error)s. An error occurred when trying to create a socket. v BRLTR0010I: Running %(cmd)s with %(args)s arguments. The listed application has been started with the described arguments. v BRLTR0011E: Operating system error: %(error)s. An error occurred when trying to stop a running application. v BRLTR0012I: Key interruption or stop iteration occurred. The application has been stopped, possibly by a key interruption. v BRLTR0013E: Unsupported state: %(state)d This is a generic message used for debugging purposes only. v BRLTR0014I: Running %(cmd)s with arguments %(args)s. This is a generic message used for debugging purposes only. v BRLTR0015I: Running %(cmd)s command. This is a generic message used for debugging purposes only. v BRLTR0016I: Running %(cmd)s with arguments %(args)s This is a generic message used for debugging purposes only. v BRLTR0017I: TaskRunner: Beginning to listen for requisitions. The TaskRunner is listening for requisitions. v BRLTR0018W: Incorrect lock usage: %(msg)s. This is a generic message used for debugging purposes only. v BRLUC0001E: No USB key devices available. No USB key devices available. You must have a USB device to proceed. v BRLUC0002E: No file systems installed. No supported file systems are installed in the host system. Install ext3 or ext2 file system support. v BRLUC0003E: No image file selected. No image file was selected. You must select an image file to proceed. v BRLUC1000E: USB image creation canceled. USB image creation was canceled. v BRLUC1001E: An internal error occurred. The task cannot proceed. There was an internal error: distribution not supported. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1002E: Error loading libraries. The task cannot proceed. There was an internal error: libraries could not be loaded. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1003E: Provided media has not been found. The media was not been found in the drive. Ensure that the media is properly inserted into the drive. v BRLUC1004E: Media type is not defined. The media type is not defined. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1005E: Only the root user can perform this operation. You must be logged on as the root user to perform this operation. v BRLUC1006E: Destination directory could not be created. There was an internal error. The destination directory could not be created. Check the logs in /var/log/wui/ create_usb_image.log for details. v BRLUC1007E: Environment could not be set. There was an internal error. The environment could not be set. Check the logs in /var/log/wui/create_usb_image.log for details.

Installing Linux with the IBM Installation Toolkit

73

v BRLUC1008E: Task verification failed. There was an internal error. The task verification failed. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1009E: Error mounting destination partition. There was an internal error. The destination partition could not be mounted. Check the logs in /var/log/wui/ create_usb_image.log for details. v BRLUC1010E: Provided USB device has not been found. The USB device was not found. Ensure that a USB device is plugged in properly. v BRLUC1011E: Invalid USB device. The USB device file is not a block file. Check the path and USB device and try again. v BRLUC1012E: Invalid storage device. The provided device is not a USB device. Insert a USB device and try again. v BRLUC1013E: Insufficient space available on USB device. The provided USB device does not have enough available space. Insert a USB device with more space and try again. v BRLUC1014E: Error from sfdisk utility. Cannot continue. The sfdisk utility issued an error and cannot continue. Ensure that the USB device provided is not mounted or in use by any other process. v BRLUC1015E: Error from mkfs utility. Cannot continue. The mkfs utility issued an error and cannot continue. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1016E: Yaboot loader not available in source media. Could not find yaboot loader in source media. Verify that the source media has the yaboot loader installed. v BRLUC1017E: Error installing yaboot loader. An internal error occurred while installing yaboot loader. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1018E: Error passing parameters. An internal error occurred while passing parameters. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1019E: Error passing USB device parameter. An internal error occurred while passing the USB device parameter. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1020E: Error passing image source parameter. An internal error occurred while passing the image source parameter. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1021E: sfdisk utility not available on system. The sfdisk utility is not available on the system. Ensure that sfdisk is properly installed. v BRLUC1022E: File system not supported. The selected file system is not supported. Choose another file system. v BRLUC1023E: File system not supported. mkfs utility not available on system. The selected file system is not supported. Also, the mkfs utility is not available on the system. Choose another file system. v BRLUC1024E: Provided image source is not a block device file or a regular file. The image source must be either a block device file or a regular file. Check the logs in /var/log/wui/create_usb_image.log for details. v BRLUC1025I: ISO image provided is not valid. Enter the path for a valid %s ISO and click OK. The ISO image provided is not valid. Verify that you selected an ISO file, correct the path to the file if necessary, and try again. v BRLUC1026I: Insert the %s media into the drive and click OK. Insert the requested media into the drive to proceed. v BRLUC1027I: No media found in the drive. Insert the media into the drive and click OK. No media could be found in the drive. Insert the media and try again. v BRLWH0002E: BRLWH0002E: Empty HTTP referrer. Could not process its data. The data from the request could not be processed because it does not contain a valid HTTP referrer. v BRLWU0001I: Invalid port number. The port number specified is invalid. v BRLWU0002I: SystemExit: unrecognized option "%(option)s". The listed option was not recognized by the web server.

74

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

v BRLWU0003I: Server listening on %(host)s:%(port)d The server is running at the listed port.

Installing Linux with the IBM Installation Toolkit

75

76

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

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 in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only 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 is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made 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 this publication at any time without notice. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Dept. LRAS/Bldg. 903 11501 Burnet Road Austin, TX 78758-3400 U.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 provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Copyright IBM Corp. 2009, 2013

77

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the 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 illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first occurrence in this information with a trademark symbol ( and ), these symbols indicate U.S. registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Java and all Java-based trademarks and logos are registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. 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.

78

Linux: Installing Linux with the IBM Installation Toolkit for PowerLinux

Printed in USA

Vous aimerez peut-être aussi