Contents

Introduction..................................................................................................................................... 3
Objectives ....................................................................................................................................... 4
The Role of HMC ........................................................................................................................... 5
Access the HMC ............................................................................................................................. 6
Install and Configure WebSM Client Component.......................................................................... 7
Install and Configure WebSM Client Component.......................................................................... 8
Install and Configure WebSM Client Component (continued) ...................................................... 9
HMC Remote Access: WebSM PC-client Mode.......................................................................... 10
Managed System Power On: Partition Standby Mode ................................................................. 12
Select Partition Standby Mode...................................................................................................... 13
Partitions, Profiles, and Attributes ................................................................................................ 14
Create the First Logical Partition.................................................................................................. 16
Create the First Logical Partition.................................................................................................. 17
Create the First Logical Partition (continued) .............................................................................. 18
Assign System CPU and Memory Resources............................................................................... 19
LPAR Real Mode Memory Addressing Region Sizes.................................................................. 21
Real Mode Memory Addressing Region Size Summary.............................................................. 22
Rule of Thumb for Large Real Mode Memory ............................................................................. 23
Assign I/O Resources to the LPAR .............................................................................................. 24
Assign I/O Resources to an LPAR................................................................................................ 25
Assign I/O Resources to an LPAR................................................................................................ 26
Select Other LPAR Attributes ...................................................................................................... 27
Review the Partition Information: Inventory................................................................................ 29
Create the LPAR’s SMS Mode Profile......................................................................................... 30
HMC View of the Managed System............................................................................................. 31
Activate and Install the First Partition .......................................................................................... 32
Select the First Boot Device for the LPAR................................................................................... 33
Select the First Boot Device for the LPAR................................................................................... 34
Select and Commit the CD-ROM as the First Boot Device ......................................................... 35
Perform Overwrite of Base Operating System from CD .............................................................. 36
Modify Default AIX Installation Settings..................................................................................... 37
AIX Installation Settings: Select Disk(s)...................................................................................... 38
BOS Installation and Customization: Set Terminal Type............................................................. 39
Complete the BOS Installation and Customization ...................................................................... 40
Network Settings for the Partition ................................................................................................ 41
Activate the Partition Using Normal Profile................................................................................. 42
Miscellaneous: Login to LPAR and Issue AIX Commands ......................................................... 43
Miscellaneous: Enable Remote Command Execution for SSH.................................................... 44
Miscellaneous: Remote HMC Access Using SSH........................................................................ 45
Miscellaneous: PuTTY Configuration.......................................................................................... 46
Summary ....................................................................................................................................... 47
More Information.......................................................................................................................... 48
Trademarks ................................................................................................................................... 49
Author Biographical Information

Nam Keung, IBM

Nam Keung is a senior programmer for IBM in Austin, TX. He has worked in the area of
AIX ISDN communication, AIX SOM/DSOM development, AIX Multimedia development,
NT Clustering technology and Java performance. His current assignment involves
helping ISVs in porting, deploying applications, performance tuning, and education for
the pSeries platform.

Karim Haffad, instructor working with IBM ITS Education Services.

Kim Greene, President, Kim Greene Consulting, Inc.

Kim Greene is president of Kim Greene Consulting, Inc. specializing in Domino™ for
iSeries consulting, customized education, and resolving performance issues. Kim has
more than 20 years’ experience with IBM midrange server platforms and also does
technical writing for a number of different projects, recently including an IBM whitepaper
“Experiences with Lotus Domino and AIX Dynamic Logical Partitioning.” Kim is a
frequent writer for technology magazines and speaks at many conferences worldwide.
Prior to starting her own consulting business, she was employed at IBM in Rochester,
Minnesota, where among other responsibilities, she worked on several areas of
operating system performance in development laboratory.
 IBM eServer pSeries Logical Partitioning:
Installation and Configuration

Nam Keung, IBM Austin

Kim Greene, president, Kim Greene Consulting

© Copyright IBM Corporation, 2004. All Rights Reserverd.

This publication may refer to products that are not currently available in all countries.
IBM makes no commitment to make available any products referred to herein.

Introduction
Welcome to this online course, entitled “IBM eServer pSeries Logical Partitioning:
Installation and Configuration.” This course shows you how to set up your IBM®
eServer® pSeries® environment to be able to work with logical partitioning (LPAR). You
will learn how to install and configure the necessary components and also how to create
an LPAR.

[NOTE: This course is not intended to teach the fundamentals of logical partitioning.
The references at the end of the course provide this introductory information along with
details that help support the materials presented here.]
 Objectives
The role of HMC
Install and configure WebSM to remotely access HMC
Activate the Managed System in partition standby mode
Create a logical partition with a default normal profile
Create an alternate SMS partition profile
Install AIX on one LPAR using AIX 5.2 CD
Reactivate the LPAR
Install and configure OpenSecure Shell command on a
PC-based client

Objectives
In this course, you will learn the process for installation and configuration of LPAR on
the pSeries server. We start off by looking at the role of the Hardware Management
Console (HMC) when working with an LPAR environment. Next, we will show you how
to set up Web System Management (WebSM) to be able to remotely access HMC. You
will then learn how to activate the managed system in “partition standby” mode, to
prepare the system to be LPARed.

You will learn how to create a logical partition, and the different types of profiles that can
be used when creating the partition. You will also learn how to copy an existing partition
to create an alternate system management services (SMS) partition profile. Next, you
will see the steps involved in installing AIX® 5.2 onto a partition from CD-ROM.

You will next see how to reactivate the newly installed partition. We will wrap things up
by showing you a few tools and commands you will find helpful in working with your
LPARed pSeries server.
The Role of HMC
The Hardware Management Console is crucial to the pSeries LPAR environment. The
HMC is required for LPARing any pSeries server. It is also needed for the pSeries 630,
pSeries 650, pSeries 655, pSeries 670, and pSeries 690 servers, even if these servers
are not LPARed. HMC is used for creating partition profiles that define the processor,
memory, and I/O resources allocated to an individual partition; and it is also integral to
starting, stopping, and shutting down a partition.

You can use the HMC to open a virtual console for each partition, allowing you to issue
commands against a specific LPAR. HMC can also be used to display system
resources and status information. In essence, the HMC is a service focal point for
problem determination to find problems, report them, and store changes in the
hardware.

The HMC can be accessed remotely via the WebSM client. We will show you how to
setup the WebSM client in this course as well.
 Access the HMC

Configure LPARs using Java-based Web System Management (WebSM) interface on HMC.
HMC login window displays and prompts you to enter User ID/password. The login banner
looks similar to illustration below.

Default user ID/password

are as follows:

Login: hscroot
Password: abc123

Access the HMC

The HMC is the main interface for working with and configuring LPAR on an pSeries
server. LPARs are configured using the Java-based Web System Management
(WebSM) interface on the HMC. When you access the HMC, you will be presented with
a login window, as shown in the slide above. You will, however, need to provide a login
user ID and password.

The HMC ships with a predefined user ID and password. These are:
Login = hscroot
Password = abc123

In this example, we are not using the predefined user ID and password; rather we are
using a separately created ID, “hmcroot.”
 Install and Configure WebSM Client Component
Access the HMC remotely from either an AIX or a PC-based client
machine. Access to the HMC can occur through:
Graphical User Interface (GUI), i.e., WebSM
Command Line Interface (CLI) via rexec or ssh commands

Install PC Client WebSM component by:

Web browser to the HMC
http://10.31.209.51/remote_client.html

FTPing and executing the setup.exe file from an AIX machine

running AIX 5.1.C or AIX 5.2 or higher on your PC

Install and Configure WebSM Client Component

For remote access and to perform LPAR-related tasks from the HMC, you can use the
WebSM client component, which runs on either an AIX-based or PC-based client
machine. Alternatively, you can use the command line interface (CLI) to issue
commands to the LPAR. We will focus on using the WebSM client in this course.

There are two methods for installing the WebSM client. You can install it from the
browser. Or, you can use the File Transfer Protocol (FTP) to copy the setup.exe file
from the AIX server to your client and run the executable there.

To install the code from the browser, enter the URL shown in this slide (in red),
substituting either the name of your pSeries server (if you are using DNS), or the
TCP/IP address of your server (in place of 10.31.209.51). The next two slides take you
through installation steps for this option.

You can also use FTP to get the setup.exe file onto your local PC. The setup.exe file is
located in the /usr/websm/pc_client directory on the AIX server. Here are the commands
you will need in order to FTP the setup.exe file to your local PC for installation:
1. At a DOS prompt, type in ftp 10.31.209.71 and then hit “Enter”
2. Sign into the server with an appropriate user ID and password
3. At the prompt, type in bin and then hit “Enter”
4. Type in get /usr/websm/pc_client/setup.exe and then hit “Enter”
5. Type in quit and then hit “Enter”

In this example, we used the TCP/IP address of the AIX server when FTPing to the
server. You can also use the host name if you have DNS (Domain Name System) set
up in your environment.

Let’s continue to the next slide to see how to download and install the WebSM client
from the browser.
Install and Configure WebSM Client Component

Install and Configure WebSM Client Component

When you enter the URL http://hostname/remote_client.html, you will be brought to the
screen, Web-based System Manager. Here you can download the install image for
either the Microsoft® Windows® client or a Linux client. In this course, we will be
showing you how to install and download the Windows-based client. Instructions for
downloading and installing the Linux client are very similar. The Linux installation
requires either Red Hat Release 7.2 or 7.3. See the Redbook, “IBM Hardware
Management Console for pSeries Installation and Operations Guide,” SA38-0590, for
more details. (A hotlink to this Web site is listed in the “More Information” section of this
course.)

To download and start the installation process of the WebSM client for the Windows
platform, click on the ‘Windows NT/2000/XP’ link. This will download the setup.exe to
your PC. After the setup.exe file install image has been downloaded to your PC, invoke
the executable. This will bring you to the next screen, the Remote Client Installer
screen.
Install and Configure WebSM Client Component (continued)

Install and Configure WebSM Client Component (continued)

After launching the setup.exe, you will be brought to the Remote Client Installer shown
in this slide. This first screen is informational only; simply click ‘Next’ to continue.
 HMC Remote Access: WebSM PC-client Mode

Login as:hscroot
Password:abc123

HMC Remote Access: WebSM PC-client Mode

This is the first screen of consequence in the WebSM setup sequence—the “Loading
console…” dialog box display. The remote HMC console is being created.

Not every setup screen is shown in this course. For example, the following information
does not pertain to screens presented here, but does detail information you will be
required to fill out when installing the WebSM client.

You will be presented with a few installation setup screens that ask for additional
information. To install using the default location, click Next. Otherwise, type the
designed location and then click Next.

A confirmation panel opens, showing you the installation location, the package being
installed, and the approximate size of the installation package. Click Next to start the
installation. If any of the information shown is incorrect, click the Back button to make
any necessary corrections. Default values are recommended for most installations.

You will see a status panel while the WebSM client is being installed. Once the
installation has completed, a message in the status panel will tell you that the
installation completed successfully. Click Finish to close the status panel display.
The WebSM client is now installed on your PC, allowing you to work with the HMC
environment remotely.

Once the WebSM client is installed, you are ready to access the HMC remotely. To do
this, double click the Web-based System Manager Remote Client icon on the
desktop. You will see the Log On dialog box shown in the slide. Enter either the host
name or the TCP/IP address of the AIX server in the Host name field. You will also
need to provide a user ID and password to log in. The default user ID is hscroot and
the default password is abc123.

If you previously set up SSL for the WebSM client, you will be able to select the Enable
secure communication option. When all parameters are completed, click the Log On
button. Logging into the HMC remotely will take you to the next screen.
Managed System Power On: Partition Standby Mode

1
5 4
2
3

HMC's IP Address HMC host name

Managed System Power On: Partition Standby Mode

When the user ID and password you supplied on the previous slide is authenticated by
the HMC, a remote connection is established. You will now see the HMC graphical user
interface in the Web-based System Manager client application shown in this slide. Note
the HMC host name is displayed in the window title.

The first step to enable LPAR on a pSeries server is to verify system state information.
To do this, you must follow these steps:
1. Using the navigation area in the left pane, click the + symbol next to the HMC
hostname. The hostname in this example is 10.31.209.51.
2. Click on Server and Partition Application.
3. Next click on Server Management. This will bring up the server information
displayed in the content area in the right pane of the HMC.
4. Verify these values: State = No Power and “Operator Panel Value” = OK
5. Right click on the system serial number or system name. The serial number is
shown in this example as having a value of p690A.
6. Select Power On.

By selecting “Power On,” you will be able to select the power on mode shown in the
next slide.
 Select Partition Standby Mode

Select Partition
Standby and then
click OK button

Select Partition Standby Mode

To be able to logically partition a pSeries server, the Managed System must be in
standby mode. Partition standby mode is required to perform LPAR tasks such as
creating the LPAR, activating the LPAR, etc. When in partition standby mode, you can
run multiple, independent LPARs, with concurrent instances of AIX or Linux sessions on
a simple LPAR-capable pSeries server.

To put the Managed System in standby mode, select Partition Standby as shown in
this slide. When you have selected the standby power on mode, click OK to continue.
 Partitions, Profiles and Attributes
Minimum=1 CPU
Desired= 2 CPUs
CPU Maximum= 4 CPUs
Normal Minimum=1 GB
Memory Desired=3 GB
: Maximum=4GB
Partition1 :
Required=U1.9-P1-I1
SMS I/O
Partitions U1.9-P1/Z1
Partition2 Desired=U1.9-P1-I10

Partition3 Boot Mode=Normal

:
Partition Profiles
Partition4 Profile Attributes
:

Logical Partitions

Partitions, Profiles, and Attributes

Much upfront planning is required to properly set up and configure one or more LPAR
partitions. When planning for an LPAR, keep in mind that each LPAR must have:
• At least one processor
• A minimum of 256 megabytes of memory
• One boot disk to store the operating system (for AIX, this is the rootvg)
• One adapter or integrated adapter to access the disk
• One LAN adapter per partition to access the HMC
• An installation method, such as Network Installation Manager (NIM)
• A means of running diagnostics, such as network diagnostics

When creating logical partitions, you need to establish a minimum of one partition
profile. The partition profile defines the resources you want to assign to each partition.
Each partition can have one or more profiles. You activate a partition by selecting one of
its profiles. You can use alternate profiles to start a partition with a different number of
resources or to start partitions in different boot modes.

This slide shows that Partition 1 has two partition profiles: Normal and SMS. The
Normal partition profile has specific resource allocations for CPU, memory, and I/O. The
boot mode is also selected. These resource allocations are specified in the profile
attributes. For example, the profile attributes for CPU is a minimum of one CPU with a
maximum of four CPUs. The desired number of CPUs for this partition is two. You also
see a minimum, desired, and maximum specified for the memory to be allocated to this
partition. The I/O has both “required” and “desired” disk allocations. We will look at the
disk allocations in more detail in a few slides.

Once you have determined the number and types of partition profiles and associated
profile attributes for each profile, you are ready to create the partitions.
Create the First Logical Partition

Create the First Logical Partition

The first partition created will play the role of a Network Installation Manager (NIM)
master node. This is an AIX component that assists you in installing nodes over
communications networks. A NIM master is an AIX server that can install one or more
nodes.

A pSeries server must be defined as a NIM master before any NIM nodes are defined.
The NIM master manages the configuration database containing the information for the
NIM nodes. A NIM master must be at the latest AIX level with the NIM master file sets
installed.

To create the first partition as a NIM master, follow these steps:

1. Click on the + next to the system name or TCP/IP address. In this example, the
TCP/IP address of the system is 10.31.209.51.
2. Click on Server and Partition Application.
3. Next click on Server Management. This will bring up the server information in
the content area within the right pane of the HMC.
4. Right click on the system serial number or system name. The serial number is
shown in this example and it’s value is p690A.
5. Select Create -> Logical Partition.

This will take you to the next screen.

Create the First Logical Partition

Partition Name:
p690lpA1

Create the First Logical Partition

On the Create Logical Partition and Profile screen, enter a partition name. A partition
name of p690IpA1 has been provided. Click Next to continue.
Create the First Logical Partition (continued)

Profile Name:
Normal

Create the First Logical Partition (continued)

The next screen asks you to provide a profile name. Normal is the default profile name.
Remember, you can create multiple profiles for a given partition that specify different
resource allocations and boot modes. The profile name should reflect LPAR usage.

Press Next to continue.

Assign System CPU and Memory Resources

Assign System CPU and Memory Resources

These next two screens collect information on the processor and memory configurations
for the partition profile you are creating. The top screen shows you how many
processors are available in the system; in this case, there are eight. You need to specify
the desired, minimum, and maximum number of processors. The desired number of
processors is the number you would prefer to assign to the LPAR—if those resources
are available. The minimum is the absolute required resources that you would allocate
to the partition and if this required minimum is not met, then the partition would not start.
The maximum is the total number of processors that can be assigned to a dynamic
LPAR (DLPAR) environment. When you have finished providing the processor resource
profile attributes, click Next to continue.

You will now be asked to provide memory resource profile attributes, as shown in the
lower screen. We see this system has 16,384 megabytes of memory available. As with
the processor resources, you need to specify the desired, minimum, and maximum
memory for this LPAR.

You also have the option to specify if the small real mode address region is to be used.
If you do not select this option, the large real mode address region will be used. We
examine the differences between small and large real mode address regions on the
next slide. When finished making memory selections, press Next to continue.
 LPAR Real Mode Memory Addressing Region Sizes
LPAR logical Real Mode Addressing
memory range memory region size

[ 1 GB - 16 GB ] = 1GB
Pre-GA3

[ > 16 GB ] = 16 GB
AIX5.1 [ 0.25 GB - 4 GB ] = 0.25 GB
GA3 + APAR IY31961 and
Small Real Mode attribute in LPAR profile not [ 4.25 GB -16 GB ] = 1 GB
selected
[ > 16 GB ] = 16 GB
AIX 5L
[ 1 GB - 16 GB ] = 1 GB
Pre- GA3

[ > 16 GB ] = 16 GB

AIX5.2 [ 0.25 GB - 4 GB ] = 0.25 GB

GA3 and Small Real Mode attribute in LPAR profile
not selected [ 4.25 GB -16 GB ] = 1 GB
[ > 16 GB ] = 16 GB
GA3 and Small Real Mode attribute in LPAR
profile selected
for all LPAR logical
memory sizes* = 0.25 GB

GA3=October/2002 system firmware + HMCode R3.V1.0

DLPAR=GA3 + AIX5.2

LPAR Real Mode Memory Addressing Region Sizes

As stated on the previous slide, there are two options when selecting LPAR real mode
memory addressing region size: large and small. If you select small real mode memory
addressing, system memory will be managed more efficiently, avoiding some of the
memory-allocation constraints associated with large real mode memory addressing. To
use small real mode memory addressing, you must have either AIX 5.2 or later or Linux
installed in the partition.

If you did not select the Small Real Mode Address Region option on the previous slide
when you assigned your minimum, desired, and maximum memory amounts in the
partition profile, the partition will use large real mode addressing. Each large real mode
memory address range is associated with a scalable Real Mode Address Region of a
particular size (256 megabytes, one gigabyte, and 16 gigabytes).

The Real Mode Address Region size is determined by the maximum partition memory
size that you specify. Take the example shown in this slide as an example. If large real-
mode memory addressing regions are used, an LPAR logical memory range from one
gigabyte to 16 gigabytes will use a real-mode addressing memory region size of 16
gigabytes. Anything over 16 gigabytes will also use a real-mode addressing memory
region size of 16 gigabytes.
 Real Mode Memory Addressing Region Size Summary
Maximum memory size Real Mode Address Region
Size
0.15 GB - 4 GB 0.25 GB

4.25 GB - 16 GB 1 GB

> 16 GB 16 GB

Real Mode Memory Addressing Region Size Summary

When using small real mode memory addressing, the size of the real mode addressing
memory region size depends on the amount of LPAR logical memory allocated to the
partition. This table summarizes the real mode addressing memory region size used—
based on the amount of LPAR logical memory allocated—and illustrates the advantage
of using small real mode memory addressing.
 Rule of Thumb for Large Real Mode Memory

To prevent the "Not enough contiguous real mode memory" message, for Large Real
Mode Memory cases, start those partitions whose memory sizes are larger than 16 GB
first.

1 GB P2 16 GB P5
Memory Axis

P1 P3 P4

For "smal real mode memory" cases, LPAR order of startup is not an issue.

Rule of Thumb for Large Real Mode Memory

Because of their size, large real mode memory addressing regions have more limits
when being placed in memory. Here are some tips to use when starting partitions that
use large real mode memory addressing regions:
• Start all partitions that are greater than 16 gigabytes in size before starting all
partitions less than or equal to 16 gigabytes.
• If all partitions are greater than 16 gigabytes, start the largest partition last.

This last tip can help prevent the message “Not enough contiguous real mode memory”
from occurring. Using the Memory Axis in the slide shown in this chart, let’s look at an
example. Below are the partitions and the amount of memory they each have. Each
partition is labeled as partition 1 (P1), partition 2 (P2), etc.
• P1 = 2 gigabytes
• P2 = 10 gigabytes
• P3 = 16 gigabytes
• P4 = 20 gigabytes
• P5 = 24 gigabytes

With this configuration, you will want to start the partitions that are larger than 16
gigabytes first, and then start the smaller partitions. This will give a start order of:
• P4, P5, P1, P2, and finally, P3

Note that for small real mode memory address region sizes, the order of LPAR startup
is not an issue.
 Assign I/O Resources to the LPAR

The partition needs Disk

Drives assigned to it for
rootvg and other volume
groups.

I/O Subsystem: Front View

The physical location code of the disk drive highlighted in blue is: U1.9-P2/Z2-Aa

Assign I/O Resources to the LPAR

The next step in creating an LPAR is to assign I/O resources to it. The figure in this slide
shows the front view of the I/O subsystem for the pSeries server we are LPARing. Each
of the DASD drive positions are shown for the server’s I/O subsystem

In the current I/O subsystem, each I/O subsystem has four ultra 3 integrated SCSI
controllers. The SCSI IDs for the drives in each four pack are 1, 2, 3, 4 and 5, 6, 7, 8
and 9, 10, 11, 12 and 13, 14, 15, 16 from left to right.

To determine the physical location code of a particular disk drive, let’s look at drive
number 3, highlighted in blue.
ƒ This disk drive has a physical location code of: U1.9-P2/Z2-Aa.
ƒ This location code is derived from the formula: Ux.y-P2.72-Aa
(as shown in the rectangular box on this diagram).
ƒ “x” is equal to the rack number.
ƒ “y” is equal to the I/O subsystem EIA position in the rack.
ƒ If you look at the physical location code again, U1.9-P2/Z2-Aa, you can see it is
telling us that drive number 3 is located in rack number 1, and the I/O subsystem
EIA position in the rack is 9.

The partition you are creating will need disk drives assigned to it for rootvg and other
volume groups. The rootvg volume group holds the server code binaries. Additional
volume groups may be defined as necessary. An example is to create a second volume
group to hold the JFS (journaled file system) log for a Domino server’s file system.
 Assign I/O Resources to an LPAR
The partition needs PCI slots for network adapters and other
devices dedicated to user access and event reporting to the HMC.

U1.9-P1 U1.8-P2

I/O subsystem 1: Rear View

Assign I/O Resources to an LPAR

When assigning DASD units to a partition, you will need to know the PCI slots for
network adapters and other devices. The graphic shown in this slide provides a look at
the rear view of I/O subsystem 1 from the previous slide.

There are two planars shown here, planar P1 and planar P2. The PCI slots in each
planar are numbered from 1 to 10, counting from left to right. In this example, slot 10 in
U 1.9-P1 is associated with a SCSI PCI adapter dedicated to the CD-ROM media
device.

Slot 11/P1/Z1 in U 1.9-P1 is associated with a 4-pack disk bay enclosure in the I/O
planar board 1.

I/O adapters are physically installed in one of many drawers in a pSeries server.
However, with logical partitioning, any I/O adapter in any I/O drawer can be assigned to
any partition.

You will see that the information related to the front and rear view of the I/O subsystem
is important as we move to the next slide where we show the WebSM—which requires
you to select the I/O resources to be added to the LPAR.
Assign I/O Ressources to an LPAR

Assign I/O Resources to an LPAR

After making the appropriate memory resource allocations, the next screen you will see
in the WebSM client involves selecting I/O resources to be allocated to the newly
created LPAR. You must specify both the required I/O resources, as well as the desired
I/O resources you would like allocated if they are available at the time the LPAR is
activated.

Each of the I/O drawers is shown in the left navigation pane. Scroll up and down this
navigation area and select which I/O resources you want in the ‘required’ and ‘desired’
profile attributes of this partition profile. To add resources to either of these categories,
highlight the I/O resource in the left navigation pane and press the Add button.

When you have completed your selections, click the Next button to continue.
 Select other LPAR Attributes

Set the Service Authority attribute for this LPAR,

so that it can perform system firmware upgrade.
Only one LPAR can be active at a time with this
attribute set.

Select the LPAR Boot Mode

Select Other LPAR Attributes

The next screen allows you to select the service authority and boot mode settings for
the partition profile. If you want this partition to be used by service representatives to
perform system firmware updates and set other system policy parameters, select Set
Service Authority.

You can choose from multiple boot modes. Let’s examine each of the options in detail:
• Normal—This option boots the operating system as specified in the SMS settings.
• SMS—This option boots to the System Management Services (SMS) menus. The
SMS menus include:
ƒ Password utilities
ƒ Display error log
ƒ Remote initial program load setup
ƒ SCSI utilities
ƒ Select console
ƒ MultiBoot
ƒ Select language
ƒ OK prompt
• DIAG_DEFAULT—This power on option is similar to DIAG_STORED, except that
the system boots up using the default boot list that is stored in the system firmware.
• DIAG_STORED—This option causes the system to perform a service mode boot
using the service mode boot list saved on the managed system. If the system boots
AIX from the disk drive and AIX diagnostics are loaded on the disk drive, AIX boots
to the diagnostics menu. Using this profile to boot the system is the preferred way to
run online diagnostics.
• OPEN_FIRMWARE—This profile is used by service representatives to obtain further
debug information. When enabled, the system boots to the open firmware prompt.

We will select Normal for the boot mode for this first partition. After making your
selections for the service authority and boot mode settings, press Next to continue.
 Review the Partition Information: Inventory

Review the Partition Information: Inventory

The final screen you see in the WebSM client when creating a partition profile is a
summary screen allowing you to review all of your selections. If you see anything that
needs to be changed, press the Back button and make the necessary changes.

When you are satisfied with the configuration options you have chosen, click Finish and
the partition profile will be created.
Create the LPAR's SMS Mode Profile

To be able to initiate the LPAR installation, the Partition needs an alternate

profile whose Boot Mode is set to System Management Services (SMS).
The SMS profile inherits the same system resources (CPU, memory, I/O) as
that of the Normal partition profile, but the Boot Mode attribute is set to SMS
Copy the Normal profile to the new SMS profile and modify the Boot Mode
attribute.

Create the LPAR’s SMS Mode Profile

To be able to initiate the LPAR installation, the partition needs an alternate profile
whose boot mode is set to System Management Services (SMS). There is a copy profile
option available to make this step as efficient as possible. By copying the existing profile
we just created with a Normal boot mode, the SMS profile will inherit the same system
resources (CPU, memory, and I/O) of that profile. The only difference is that this second
profile will specify a different boot mode attribute of SMS.

To copy a system profile, follow these steps in the WebSM client interface:
1. In the left navigation pane, click the + next to the system name or TCP/IP address.
2. Click on Server and Partition Application.
3. Click on Server Management. This will bring up the server information in the
content area in the right pane of the HMC.
4. Highlight the name of the partition profile you just created.
5. From the WebSM menu, click Selected -> Copy.
6. In the Copy Profile window, type the new profile name. In this example, the profile
being copied is named ‘Normal,’ and we have chosen a profile name of ‘SMS.’
7. Click OK on the first Copy Profile screen.

This brings you to the next Copy Profile screen. On the second screen:
1. Click the Other tab and select the boot mode option of SMS.
2. Click OK to complete the profile copy operation.

To copy a partition profile, you must be a member of one of the following roles: System
Administration or Advanced Operator.
 HMC View of the Managed System

HMC View of the Managed System

This slide shows the Normal and SMS partition profiles that were created in the
previous steps. These profiles were created for the p690lpA1 LPAR. To create an
additional LPAR with one or more partition profiles, follow the same set of steps that
were used to create the partition profiles for the p690lpA1 LPAR.
Activate and Install the First Partition

Activate and Install the First Partition

Now that the partition profiles have been created, we are ready to activate and install
the first partition with the AIX operating system. Follow these steps for the newly
created partition:
1. Insert the AIX 5.2 volume 1 CD into the CD-ROM drive.
2. In the left navigation pane, click the + next to the system name or TCP/IP address.
3. Click on Server and Partition Application.
4. Next click Server Management. This will bring up the server information in the
content area in the right pane of the HMC.
5. Right click on the name of the partition profile you just created and select Activate.
The name of the partition profile we are activating in this example is p690lpA1.
6. Next, you will be asked to select the profile to activate. Select the SMS profile and
click OK to continue.
Select the First Boot Device for the LPAR

step 1. Press 7 for Boot Options

2
step 2. Press 2 for select boot device

Select the First Boot Device for the LPAR

A virtual terminal session will now be opened, and you need to select the first boot
device for the newly created and activated LPAR. On the first screen, select option 7.
Select Boot Options and press Enter.

On the next screen, you will need to select the boot device. Here select option 2.
Select Boot Devices. Press Enter to confirm your selection.

You will be taken to the set of screens on the next slide.

 Select the First Boot Device for the LPAR

step 3- select option 1 to configure

1st boot device

step 4, Press 3 to select CD/DVD

Select the First Boot Device for the LPAR

On the third screen, select option 1. Select 1st Boot Device and press Enter. The
fourth screen asks you to select the boot device type. Here, select option 3. CD/DVD
and press Enter.

These two selections will dictate the device used for first boot for the LPAR.
 Select and Commit the CD-ROM as the First Boot Device

select option 2 to set the Boot sequence

Select and Commit the CD-ROM as the First Boot Device

On this screen, you need to select the task to be performed by the CD/DVD device.
Select option 2 – Set Boot Sequence: Configure as 1st Boot Device. Press Enter
after making your selection.

Selecting this option will set the CD-ROM as the first boot device.
 Perform Overwrite of Base Operating System from CD

Next steps:
1. Boot from AIX product CD
2. Set BOS installation settings, including:
Perform new & complete overwrite install of AIX on hdisk0
Use English as primary language
Use default options in More Options menu
3. Start BOS installation & configure system

Perform Overwrite of Base Operating System from CD

After making the last selection in the previous slide, press the X key to exit the SMS
utilities menu. When you exit the SMS menu, the LPAR will boot from the CD-ROM.
You will now be installing the operating system from the CD.

The next set of slides will take you through these steps:
1. Boot from the CD which contains the AIX operating system code.
2. Set specific BOS (base operating system) installation settings.
3. Start the actual installation of the operating system, and thus, configure the LPAR.

Let’s continue to the next slide to start these steps.

 Modify Default AIX Installation Settings

Modify Default AIX Installation Settings

On the ‘Welcome to Base Operating System Installation and Maintenance’ screen:
• Select option 2. Change/Show Installation Settings and Install.
• Press Enter

On the next screen, ‘Installation and Settings,’ verify that the installation settings are
correct by checking:
ƒ The method of installation (new and complete overwrite)
ƒ The disk or disks you want to install
ƒ The primary language environment settings, and
ƒ The advanced options.

If the default choices are correct, type 0 and press Enter to begin the BOS installation.
To change any system settings, type 1 for System Settings and press Enter. You will
be able to select the method of installation and from which disks you want to install. In
this case, we need to change the installation method from ‘Preservation’ to ‘New and
Complete Overwrite.’ The next slide shows the screen you receive after selecting the
‘New and Complete Overwrite’ installation method.
 AIX Installation Settings: Select Disk(s)

AIX Installation Settings: Select Disk(s)

On the ‘Change Disk(s) Where You Want to Install’ screen, you see the available disk
volume groups from which you can select. Choose hdisk0 by typing option 1. Press
Enter to confirm your selection.

The final screen you will see is the ‘Overwrite Installation Summary’ screen. Here you
can verify the installation options you have specified. If you are satisfied with your
choices, select option 1. Continue with Install and press Enter to start the actual
installation process.
 BOS Installation and Customization: Set Terminal Type

BOS Installation and Customization: Set Terminal Type

Once the installation has started, you will need to select the terminal type. This screen
capture shows how to enter the terminal type. Simply type vt100 for your choice and
press Enter to continue with installation.
 Complete the BOS Installation and Customization
1. In the License Agreement menu, select Accept License Agreements.
2. Select yes to ACCEPT Installed License Agreements.
3. Press Esc+0 to exit the menu.
4. In Installation Assistant main menu, select Set Date and Time.
5. Set correct date, time, and time zone.
6. Press Esc+3 key to return to Installation Assistant main menu.
7. Set root password for the partition to: ibmaix.
8. Select Configure Network Communications: Select TCP/IP Startup.

Complete the BOS Installation and Customization

Some of the next steps you will encounter relate to the license agreement.
• On the ‘License Agreement’ menu, select yes to accept the license agreements
and continue with the installation process.
• Press Esc+0 to exit the License Agreement menu.

On the ‘Installation Assistant’ menu, select ‘Set Date and Time’ and complete the
following:
• Set the date and time to current values.
• Set the correct time zone.
• Press Esc+3 to return to the ‘Installation Assistant’ menu.

Back at the ‘Installation Assistant’ menu, set the root password for the partition to
ibmaix.

Next, select Configure Network Communications, and select TCP/IP Startup.

You will now be taken to the Minimum Configuration: Startup screen shown on the next
slide.
 Network Settings for the Partition

Network Settings for the Partition

The Minimum Configuration: Startup screen is shown in this slide. Here you can change
items such as the host name, Internet address, name server, default gateway, and
more. To change values in any of the highlighted fields, tab to the field and press Esc+7
to edit the field contents.

After making all necessary changes, press Enter.

When installation has completed, exit the ‘Installation Assistant’ menu. You will now
need to use the HMC or the WebSM to reactivate the partition based on its normal
profile. We will show you how to do this on the next slide.
Activate the Partition using Normal Profile

On the HMC select p690lpA1,

Right Click and Activate it using its Normal Profile.

Activate the Partition Using Normal Profile

Now that the partition has been installed with AIX, it will need to be reactivated. To do
this, right click on the partition name in the HMC or WebSM and select Activate.

This will bring up the ‘Activate Partition’ screen shown in this slide. Select the Normal
activation profile and press OK to start the partition. The newly configured and installed
partition is now ready for use.

The remainder of this course provides some additional hints and tips you may find
useful when creating and installing LPARs on your pSeries server.
Miscellaneous: Login to LPAR and Issue AIX Commands

Miscellaneous: Login to LPAR and Issue AIX Commands

Some additional commands you may find useful are uname and prtconf. The uname
command prints the system name. In this example, the system name is p6901pA2.

The prtconf command prints the system configuration information. Output includes:
• System model and serial number
• Processor type
• Number of processors
• processor clock speed
• CPU type
• Name of any associated LPARs
• Total memory
• Network information
• And more
Miscellaneous: Enable Remote Command Execution for SSH

Miscellaneous: Enable Remote Command Execution for SSH

In the WebSM client, you can specify system configuration information by clicking on
System Configuration in the navigation area. The system configuration tasks are
displayed in the contents pane on the right. One option you will most likely want to
enable is remote command execution via the virtual terminal (Secure Shell, or SSH). By
default, remote virtual terminal to the HMC from the remote WebSM client is disabled.

To enable this capability, do the following:

1. Expand the HMC Maintenance folder for the AIX server.
2. Select the System Configuration application in the Navigation area.
3. Select the Enable/Disable Remote Virtual Terminal task in the Contents area.
4. This opens the Enable Remote Virtual Terminal window (not shown in this slide).
5. On the Enable Remote Virtual Terminal window, select the check box next to
Enable remote virtual terminal connections.
6. Click OK.
 Miscellaneous: Remote HMC Access using SSH
PuTTY executable enables you to take advantage of the OpenSSH of the SSH
protocol; providing data encryption, data integrity and authentication.
The PuTTY executable can be downloaded from
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Miscellaneous: Remote HMC Access Using SSH

PuTTY is a free Secure Shell, Telnet, and Rlogin client for 32-bit Windows systems.
SSH, Telnet, and Rlogin are three ways of doing the same thing: logging into a multi-
user computer from another computer—over a network.

The PuTTY utility enables you to have secure, remote network connectivity to the HMC.
PuTTY provides data encryption, data integrity, and authentication. Using the PuTTY
interface, there is no need to be sitting at the same machine where you are typing
commands. The commands and responses can be securely sent over a network, so you
can sit at one computer and give commands to another one, or to more than one other
computer.

The PuTTY executable can be downloaded from the Web site shown in this chart.
 Miscellaneous: PuTTY Configuration

HMC IP address

Miscellaneous: PuTTY Configuration

Once you have downloaded the PuTTY executable, launch it to start the PuTTY
configuration. You will see the PuTTY configuration screen as shown in this slide. Click
on each of the categories to provide different configuration parameters.

The session information is shown here. For the Host Name (or IP address) field, enter
the host name or TCP/IP address of the system within which you want to use the
PuTTY utility. The protocol you will find most useful in executing remote commands to
an LPAR with PuTTY is the SSH protocol.

When you have specified the correct configuration parameters, press the Open button
to launch PuTTY over secure shell, SSH. You will be taken to the screen on the next
slide.
 The
End

Now you are ready to implement LPAR on your

pSeries server.

Summary
In this course, you learned how to configure HMC and also how to configure the
WebSM client to remotely access the HMC.

You also learned what steps are necessary in preparing your pSeries server to enable it
for logical partitioning.

This course also covered details showing you how to create and configure a logical
partition. You were shown how to copy that partition profile, creating an SMS partition
profile.

Additionally, you learned about some miscellaneous tools that you can use in your own
environment to install and configure LPAR on your own server.

We think you will now agree that the LPAR capability available on the pSeries servers
offers you a great deal of flexibility in configuring different environments for various
workloads.

Best of luck to you in your implementation of LPAR on the pSeries platform.

More Information
Here are some links that will provide you with some additional materials that will help as
you implement LPAR in your environment.

• Redbook: pSeries – LPAR Planning Redpiece (TIPS0119) can be found at…

ibm.com/redbooks Æ search for TIPS0119

• Redbook: Effective Management Using the IBM Hardware Management Console

for pSeries (SG24-7038-00) can be found at…
ibm.com/redbooks Æ search for SG24-7038

• Redbook: Complete Partitioning Guide for IBM eServer pSeries Servers (SG24-
7039) can be found at…
ibm.com/redbooks Æ search for SG24-7039

• The pSeries Information Center’s IBM Hardware Management Console for

pSeries Installation and Operations Guide, (SA38-0590), go to ..
http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/hardware_docs/p
df/380590.pdf

• The Logical Partitioning, Frequently Asked Questions web site which can be
found at …
ibm.com/eserver/pseries/lpar/faq_2.html

• LPAR resource management

http://publib16.boulder.ibm.com/pseries/en_US/infocenter/base/HowToAdmin.ht
m#CATEGORY_7
Trademarks
IBM, eServer, pSeries, and AIX are registered trademarks or trademarks of the IBM
Corporation in the United States or other countries or both.

Microsoft, Windows, and the Windows logo are trademarks or registered trademarks of
Microsoft Corporation.

All other trademarks and registered trademarks are the properties of their respective
companies.