AN11 Power Systems For AIX I LPAR Configuration and Planning Instructor Guide 2009 PDF

Power Systems for AIX I:
LPAR Configuration and

Planning
(Course code AN11)
Instructor Guide
ERC 1.0
Instructor Guide
Trademarks
The reader should recognize that the following terms, which appear in the content of this
training document, are official trademarks of IBM or other companies:
IBM is a registered trademark of International Business Machines Corporation.
The following are trademarks of International Business Machines Corporation in the United
States, or other countries, or both:
AIX AIX 5L AS/400
BladeCenter eServer EnergyScale
Express Focal Point GPFS
HACMP i5/OS IBM Systems Director Active
Energy Manager
Micro-Partitioning OpenPower OS/400
POWER POWER4 POWER5
POWER5+ POWER6 POWER Hypervisor
Power Systems PowerPC PowerVM
pSeries Redbooks Resource Link
RS/6000 System i System i5
System p System p5 System Storage
System z TotalStorage
Adobe is either a registered trademark or a trademark of Adobe Systems Incorporated in
the United States, and/or other countries.
Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the
United States and other countries.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc.
in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft, Windows and Windows NT are trademarks of Microsoft Corporation in the
United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
June 2009 edition

The information contained in this document has not been submitted to any formal IBM test and is distributed on an as is basis without
any warranty either express or implied. The use of this information or the implementation of any of these techniques is a customer
responsibility and depends on the customers ability to evaluate and integrate them into the customers operational environment. While
each item may have been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will
result elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk.
Copyright International Business Machines Corporation 2009. All rights reserved.

This document may not be reproduced in whole or in part without the prior written permission of IBM.
Note to U.S. Government Users Documentation related to restricted rights Use, duplication or disclosure is subject to restrictions
set forth in GSA ADP Schedule Contract with IBM Corp.
Instructor Guide
Other company, product, or service names may be trademarks or service marks of others.
iii PowerVM Virtualization I Copyright IBM Corp. 2009

Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Instructor Guide
iv PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
TOC Contents
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Instructor course overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Course description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Unit 1. Introduction to partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
What is a partition? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Physical partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Logical partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Partition characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Partition resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Logical partition resource example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
IBM POWER5+ LPAR-capable systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
IBM POWER6 LPAR-capable systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Benefits of using partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Software licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
POWER Hypervisor functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
The big picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
Advanced partition features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
Dynamic partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-41
How DLPAR works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-44
Processor concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
Micro-partitioning: Shared processor pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-50
Multiple shared processor pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52
Virtual I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55
Virtual I/O example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Integrated Virtual Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
Integrated Virtual Ethernet example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-63
Live partition mobility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65
Capacity on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-67
PowerVM editions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70
Partitioning concepts summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-73
Integrated Virtualization Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-76
LPAR configuration process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-79
Logical partition references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82
AN11 course content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-85
AN30 course content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-87
Checkpoint (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-89
Checkpoint (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91
Copyright IBM Corp. 2009 Contents v

Instructor Guide
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-93
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-95
Unit 2. Hardware system overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
IBM POWER5+ processor-based systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
IBM System p5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
IBM POWER6 processor-based systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9
IBM Power Systems: The new Power equation . . . . . . . . . . . . . . . . . . . . . . . . . . .2-13
POWER6 system example: IBM Power 550 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-17
Power System 550 I/O slots: Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20
I/O drawer options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-23
Location codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26
Physical location code convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29
AIX location codes (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-32
AIX location codes (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-34
Service processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-36
Advanced System Management Interface (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . .2-39
Advanced System Management Interface (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . .2-42
ASMI example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-44
Checkpoint (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-48
Checkpoint (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-50
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-52
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-54
Unit 3. Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
3.1. HMC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Topic 1 objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
HMC connection to the server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
HMC version 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14
Configuring a new HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17
Guided Setup Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20
HMC pre-login welcome screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
HMC login sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-24
Disconnect versus logoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26
Reconnecting to login session (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28
Reconnecting to login session (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30
HMC Welcome screen, after login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-32
HMC V7 user interface: Overall structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-35
Flexibility: Launching tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-38
Server table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-41
LPAR table view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-43
LPAR consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-45
HMC online help and documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-48
HMC V7 documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-50
Work area: Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-53
vi PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
TOC Toolbar features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55

Flexibility: Filtering columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
Flexibility: Sort options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Flexibility: Custom groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Status overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
SRC lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
HMC management: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
HMC network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Network settings: Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Network settings: LAN Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Network settings: LAN Adapter details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Network settings: LAN firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
Network Settings: Name Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Network settings: Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
Connecting HMC to managed system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90
Add managed system (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Managing the server or HMC connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
Check managed system status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-104
Check HMC software version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107
Lets review Topic 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109
3.2. HMC users, remote access, and security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-111
Topic 2: HMC users, remote access, and security . . . . . . . . . . . . . . . . . . . . . . . 3-112
HMC user management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-114
Add or manage HMC users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-117
Add an HMC user (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-120
Add an HMC user (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124
HMC users: Resources and task roles example . . . . . . . . . . . . . . . . . . . . . . . . . 3-126
Task roles management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-128
Add task role example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
Managed resource roles management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132
Add managed resource role example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-134
HMC remote access options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136
Enabling remote browser access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139
Remote HMC login: Browser requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-141
Enable or disable remote options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-144
Using HMC commands remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-147
HMC commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-149
SSH login environment on the HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151
HMC CLI: What is available then? (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153
HMC CLI: What is available then? (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-156
Remote access security overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-160
Browser access: SSL security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-163
HMC management: Manage certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-165
Integrated Virtualization Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-168
The IVM architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-171
The big picture with IVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-174
Copyright IBM Corp. 2009 Contents vii

Instructor Guide
IVM LPAR management: Common Web interface . . . . . . . . . . . . . . . . . . . . . . . .3-177

IVM administration from GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-179
Lets review Topic 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-181
Checkpoint (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-183
Checkpoint (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-185
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-187
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-189
Unit 4. System Planning Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
IBM System Planning Tool (SPT) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4
SP Tool and system plan deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-8
SPT: Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11
SPT: System attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13
SPT: DASD/Media backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-15
SPT: System Partitions definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17
SPT: Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-19
SPT: Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-21
SPT: System Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-23
SPT: Working with the Planned Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-25
SPT: Assigning Hardware devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-27
SPT: Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-29
SPT: Virtual Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32
SPT: LPARs operating system installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-35
SPT: Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-38
SPT: Configuration status (reports and output) . . . . . . . . . . . . . . . . . . . . . . . . . . .4-40
Import system plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42
Deploy system plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-44
Create a system plan using HMC version 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-46
Converting a system-plan file to SPT format . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-49
Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-51
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-53
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-55
Unit 5. HMC and managed system maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3
Backup critical console data (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5
Backup critical console data (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8
Backup critical console data (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11
Scheduling backups (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14
Scheduling backups (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-16
HMC corrective service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-19
Install corrective service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-22
HMC software upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-25
Prepare for HMC software upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-28
HMC reload procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-30
Managed system firmware update (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-33
Managed system firmware update (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-36
viii PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
TOC Examine current firmware level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39

Obtaining new firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Change LIC for current release (1 of 5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
Unit 6. System power management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Managed System Power States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Managed system power on and off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Managed system power on options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Partition standby . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
System profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
Partition auto start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
Hardware Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
System initialization (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-23
System initialization (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Power off managed system (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
Power off managed system (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34
Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41
Unit 7. Planning and configuring logical partitions . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Partition resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Dividing the system resources (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Dividing the system resources (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Creating partitions and profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Memory resources (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Memory resources (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Memory usage (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Memory usage (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Processor resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
I/O resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Virtual SCSI devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Virtual Ethernet options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Create a logical partition: System state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Create logical partition wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Partition ID and name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Profile name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Set processor type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51
Copyright IBM Corp. 2009 Contents ix

Instructor Guide
Configure dedicated processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-53

Configure shared processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-55
Configure memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-57
Configure I/O slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-59
Virtual I/O adapters setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-61
Logical Host Ethernet Adapter (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-64
Optional settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-71
Check logical partition profile summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-74
Editing a partitions configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-76
Additional configuration options (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-79
Additional configuration options (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-81
Checkpoint (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-84
Checkpoint (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-86
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-88
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-90
Unit 8. Partition operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-2
Web-based user interface: Systems management . . . . . . . . . . . . . . . . . . . . . . . . . .8-4
Activating partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-9
Activate partitions with a system profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11
Activating an individual partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-14
Activating with open terminal window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-18
Terminal window: Normal boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-21
Activating with advanced options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-24
Open or close a terminal window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-26
Stopping a partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-29
Partition shutdown options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-31
Restart partition options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-34
Create a system profile (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-37
Create a system profile (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-39
Validate allocations with a system profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-42
Change the default partition profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-44
Copy a partition profile (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-46
Copy a partition profile (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-48
Save configuration in a partition profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-50
Modify a partition profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-52
Delete a partition profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-55
Delete a partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-57
Partition availability priority (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-59
Partition availability priority (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-62
Backing up partition profile data (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-64
Backing up partition profile data (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-67
Restoring partition profile data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-69
Removing backup files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-72
Scheduling operations (1 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-74
x PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
TOC Scheduling operations (2 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-76

Scheduling operations (3 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-79
Scheduling operations (4 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-82
Troubleshooting activation failures (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-84
Managed system properties (1 of 9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-92
Managed system properties (5 of 9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-102
Checkpoint (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-118
Checkpoint (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-120
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-122
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-124
Unit 9. Dynamic resource allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Unit objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
9.1. Dynamic LPAR operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Topic 1: Dynamic LPAR operations objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Dynamic logical partitioning (DLPAR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
DLPAR operations overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
DLPAR operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Add/Remove dedicated processor operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Add/Remove shared processing units operation . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
DLPAR status (1 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
DLPAR status (2 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
DLPAR status (3 of 3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Move Memory operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-29
Add I/O slots operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
AIX commands for I/O operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
Removing I/O slots in AIX (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-37
Removing I/O slots in AIX (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
Move/Remove I/O slots operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
LHEA dynamic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45
Move/Remove an LHEA from the logical partition . . . . . . . . . . . . . . . . . . . . . . . . . 9-47
chhwres HMC command for DLPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
List resources with lshwres command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-52
Lets review Topic 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-57
9.2. DLPAR troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Topic 2: DLPAR troubleshooting objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
How DLPAR works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-62
Reliable Scalable Cluster Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-65
Copyright IBM Corp. 2009 Contents xi

Instructor Guide
Resource managers (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-67

Resource managers (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-70
HMC and LPAR initial communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-73
HMC and LPAR authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-76
Verifying HMC for DLPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-79
RMC management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-81
Viewing resource class information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-85
Reinitializing RMC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-87
DLPAR troubleshooting: Symptoms (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-89
DLPAR troubleshooting: Symptoms (2 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-92
DLPAR troubleshooting: Network setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-95
Lets review Topic 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-97
Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-99
Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-101
Unit summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-103
Appendix A. Checkpoint solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
xii PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
TMK Trademarks
The reader should recognize that the following terms, which appear in the content of this
training document, are official trademarks of IBM or other companies:
IBM is a registered trademark of International Business Machines Corporation.
The following are trademarks of International Business Machines Corporation in the United
States, or other countries, or both:
AIX AIX 5L AS/400
BladeCenter eServer EnergyScale
Express Focal Point GPFS
HACMP i5/OS IBM Systems Director Active
Energy Manager
Micro-Partitioning OpenPower OS/400
POWER POWER4 POWER5
POWER5+ POWER6 POWER Hypervisor
Power Systems PowerPC PowerVM
pSeries Redbooks Resource Link
RS/6000 System i System i5
System p System p5 System Storage
System z TotalStorage
Adobe is either a registered trademark or a trademark of Adobe Systems Incorporated in
the United States, and/or other countries.
Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the
United States and other countries.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc.
in the United States, other countries, or both.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or
both.
Microsoft, Windows and Windows NT are trademarks of Microsoft Corporation 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.
Copyright IBM Corp. 2009 Trademarks xiii

Instructor Guide
xiv PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
pref Instructor course overview

This course is an introduction to performing system administration in a
Power Systems p environment. It will provide the students with an
overview of basic LPAR terminology, planning and configuration tasks
associated with an IBM Power System. Additionally, the course covers
configuration rules for partitions running either AIX V5.2, AIX V5.3, AIX
V6.1, or Linux.
This is a 3-day course with checkpoint questions and hands-on
exercises at the end of each unit to check the students understanding
of the materials.
This course has been designed to support the Version 7.3 of the
Hardware Management Console (HMC) software.
Course strategy
The course purpose is to give new IBM customers the knowledge to
configure and manage partitions. For the students, no previous
knowledge of logical partitioning is expected.
The course design strategy is to define basic terms and concepts
related to logical partitioning, cover key configuration information for
the HMC, and explain how to configure the logical partitioning options.
Each unit contains a list of review questions on the last page. Use
these to review the material from the units that you covered on the
previous day each morning for the first 20-30 minutes.
Copyright IBM Corp. 2009 Instructor course overview xv

Instructor Guide
xvi PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
pref Course description

Power Systems for AIX I: LPAR Configuration and Planning
Duration: 3 days
Purpose
Learn how to perform system administration in a Power Systems p
environment. Learn the skills needed to become an effective
administrator on IBM's POWER6-based systems that support Logical
Partitioning (LPAR). Learn about the features of PowerVM Editions
(Advanced POWER Virtualization - APV) and how to configure and
manage LPARs running AIX V6.1 using the Hardware Management
Console (HMC).
Audience
This course is appropriate for system administrators, technical support
individuals, and IBM Business Partners who implement LPARs on IBM
System p systems.
Prerequisites
This introductory course does not require any logical partitioning
experience.
General TCP/IP knowledge is strongly recommended. This
prerequisite may be met by attending AIX 5L TCP/IP I: Configuration
(AU07).
Objectives
After completing this course, you should be able to:
Describe important concepts associated with managing POWER6
processor-based systems, such as logical partitioning, dynamic
partitioning, virtual devices, virtual processors, virtual consoles,
virtual Local Area Network (VLAN), and shared processors
Describe the features of the PowerVM editions
Use the System Planning Tool to plan an LPAR configuration
Describe the functions of the HMC
Copyright IBM Corp. 2009 Course description xvii

Instructor Guide
Configure and manage the HMC, including users and permissions,

software, startup and shutdown, remote access features, network
configuration, security features, HMC backup and restore options,
and the HMC reload procedure
Describe the rules associated with allocating resources, including
dedicated processors, processing units for Micro-Partitions,
memory, Logical Host Ethernet Adapter, and physical I/O for AIX
and Linux partitions
Configure and manage LPARs using the HMC Graphical User
Interface (GUI) and HMC commands
Interpret physical and AIX location codes and relate to the key
hardware components
Power on and power off the POWER6 system
Use the HMC to back up and restore partition data
xviii PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
pref Agenda
Day 1
(00:30) Welcome
(02:00) Unit 1: Introduction to partitioning
(00:30) Exercise 1
(01:00) Unit 2: Hardware system overview
(00:30) Exercise 2
(01:30) Unit 3: Hardware Management Console
Day 2
(01:00) Unit 3: Hardware Management Console (cont.)
(01:15) Exercise 3
(00:30) Unit 4: System Planning Tool
(00:30) Exercise 4
(00:45) Unit 5: HMC and managed system maintenance
(00:30) Exercise 5
(00:45) Unit 6: System power management
(00:45) Exercise 6
(01:00) Unit7: Planning and configuring logical partitions
Day 3
(00:30) Unit 7: Planning and configuring logical partitions (cont.)
(01:00) Exercise 7
(01:15) Unit 8: Partition operations
(01:00) Exercise 8
(01:15) Unit 9: Dynamic resource allocation
(01:15) Exercise 9
Copyright IBM Corp. 2009 Agenda xix

Instructor Guide
xx PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
Uempty Unit 1. Introduction to partitioning
Estimated time
02:00
What this unit is about

This unit introduces basic partitioning concepts and features on IBM
POWER5 and POWER6 processor-based servers.
What you should be able to do

After completing this unit, you should be able to:
Describe the following terms:
- Partition, logical partition, resource
Describe the following partition concepts:
- Dynamic logical partitioning
- Micro-partitioning
- Shared processor pool
- Virtual I/O
- Live partition mobility
- Capacity on Demand (CoD)
Describe the functions of the Hardware Management Console
(HMC)
Describe the functions performed by the POWER Hypervisor
Describe the overall process for configuring partitions
List references for IBM POWER5 and POWER6 processor-based
system partitioning
How you will check your progress

Accountability:
Checkpoint
Machine exercises
Copyright IBM Corp. 2009 Unit 1. Introduction to partitioning 1-1

Instructor Guide
References
IBM System p and AIX Information Center:
http://publib.boulder.ibm.com/infocenter/pseries/index.jsp
SG247940-03 PowerVM on IBM System p Introduction and
Configuration
1-2 PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
Uempty
Unit objectives
IBM Power Systems

Partition, logical partition resource
Describe the benefits of partitioning
Dynamic logical partitioning
Micro-partitioning
Virtual I/O
Live partition mobility
Capacity on Demand (CoD)
Describe the functions of the Hardware Management Console
(HMC)
List references for IBM POWER5 and POWER6 processor-based
system partitioning
Copyright IBM Corporation 2009
Figure 1-1. Unit objectives AN111.0
Notes:
Introduction
The objectives list what you should be able to do at the end of this unit.

Instructor Guide
Instructor notes:
Purpose Review the objectives for this unit.
Details Explain what we will cover and what the students should be able to do at the end
of the unit.
This unit introduces terms and concepts.
Because this is the students first unit, point out the references listed on the front page of
this unit. Each unit will have its own list of references.
Additional information
Transition statement We will start with the most basic term: partition.

V5.3
Instructor Guide
Uempty
What is a partition?
IBM Power Systems
Partition
Allocation of one systems resources to create logically separate systems
Each partition is an independent operating environment
From One to Many
Figure 1-2. What is a partition? AN111.0
Notes:
Partition
When a computer system is subdivided into multiple, independent operating system
images, those independent operating environments are called partitions. The resources
on the system are divided up among the partitions. Applications running on a partitioned
system do not have to be redesigned for the partitioned environment.
Independent operating environment

Each partition runs its own operating system that might or might not match operating
systems in other partitions on the same system. Each partition can be started and
stopped independently of other partitions.

Instructor Guide
Instructor notes:
Purpose Introduce the generic concept of a partition.
Details Define a partition as a configured set of resources running its own independent
operating system image.
From a security, network, application, and operational perspective, partitions are like
having separate physical systems, but with the benefit of having all resources in the same
system for maximum configuration flexibility.
Transition statement Next, we will define the concept of physical partitions.

V5.3
Instructor Guide
Uempty
Physical partition
IBM Power Systems
Physical partition (PPAR)

Resources are allocated in physical building blocks
Blocks contain groups of processors, memory and I/O slots
Interconnect
SMP building block SMP building block SMP building block
Operating System Operating

System
CPU, CPU, CPU,

Memory, and I/O Memory, and I/O Memory, and I/O
Physical Partition Physical Partition
Figure 1-3. Physical partition AN111.0
Notes:
Introduction
This page defines physical partitioning which we will contrast with logical partitioning on
the next visual. IBM Power Systems support logical partitions, not physical partitions.
PPARs
The visual shows an example of a system with three system building blocks, each made
up of a number of processors, an amount of memory, and several I/O slots. These three
building blocks can be configured into one, two, or three partitions each made up of one
or more entire building blocks. The size of the building blocks depends on the vendor
and system model.

Instructor Guide
Adding or removing resources

To add or remove resources in a PPAR environment, entire building blocks must be
added or removed. For example, if more memory is needed, you might have to add
more processors and I/O slots.

V5.3
Instructor Guide
Uempty Instructor notes:

Purpose This visual shows an example of a PPAR system.
Details Students might have heard the phrase physical partitions from the UNIX server
market. These are partitions based on physical system units, such as a system board,
which contain a certain amount of processing power and memory, and a number of I/O
slots. IBMs POWER5+ and POWER6 processor-based systems support logical partitions
and we mention physical partitions here so we can compare it with logical partitions.
Review the PPAR definition and use the visual to illustrate. Point out that the example in
the visual can be configured with only one, two, or three partitions because there are three
system building blocks.
The drawback is the lack of flexibility in configuring a system. If you just want to add a few
more processors or a bit more memory to get over an increase in workload (for example,
quarter end processing), you must add or remove an entire building block of resources,
which might be difficult to do.
Transition statement Now, lets look at LPAR more closely.

Instructor Guide
Logical partition
IBM Power Systems
A partition is the allocation of system resources to create logically

separate systems within the same physical footprint
A logical partition exists when the isolation is implemented with
firmware
Is not based on physical system building block
Provides configuration flexibility
SYS1 SYS2 SYS3 SYS4

1:00 10:00 11:00 12:00
Japan USA Brazil UK
RG RESS O
O
EP
ORDEM
AIX 5L Linux AIX 5L i5/OS
Figure 1-4. Logical partition AN111.0
Notes:
Logical partition
Logical partitioning is the ability to make a single system run as if it were two or more
systems. Each partition represents a division of resources in your computer system.
The partitions are logical because the division of resources is virtual and not along
physical boundaries. There are, however, configuration rules that must be followed.
For the rest of the course, logical partitions will be called simply LPARs or partitions for
brevity.
Implemented in firmware
The system uses firmware to allocate resources to partitions and manage the access to
those resources. Although there are configuration rules, the granularity of the units of
resources that can be allocated to partitions is very flexible. You can add just a small
amount of memory if that is all that is needed without a dependency on the size of the

V5.3
Instructor Guide
Uempty memory cards or without having to add more processors or I/O slots that are not
needed.
Firmware refers to underlying software running on a system independently from any
operating system. On IBM System p Systems and IBM Power Systems, this includes
the software used by the Flexible Service Processor (FSP) and the POWER Hypervisor.

Instructor Guide
Instructor notes:
Purpose Differentiate the generic term partition with the more specific term of logical
partition.
Details Describe what is meant by logical partitions.
The visual shows different time zones and country flags to show that because LPARs are
separate operating environments, system variables, such as the time zone, can be set in
each operating system of each LPAR. This topic is talked about more on the next visual.
Additional information Other vendors might also have LPARs, but each vendor
implements them differently. Some vendors refer to logical partitions as soft partitions and
physical partitions as hard partitions.
Transition statement Lets look at the characteristics of a partition that are independent
from other partitions on the same computer system.

V5.3
Instructor Guide
Uempty
Partition characteristics
IBM Power Systems
Each partition has its own:

Operating system
Licensed Internal Code (LIC) / Open Firmware
Console
Resources
And other things expected in a stand-alone operating system
environment:
Problem logs
Data (libraries, objects, file systems)
Performance characteristics
Network identity
Date and time
Figure 1-5. Partition characteristics AN111.0
Notes:
Characteristics of a partition
The visual illustrates how each partition is independent. As stated before, each partition
runs its own operating system. The version of the operating system can be any valid
version that is supported on the system. Other things you would expect on a physically
separate system are also separate for partitions; there are even independent virtual
consoles.
What is the same between partitions on the same system?

Each partition shares a few physical system attributes, such as the system serial
number, system model, and processor feature code with other partitions. In addition,
you can choose to share other hardware, such as SCSI devices among partitions.
The planar in an I/O drawer is also an example of a component that is used by all logical
partitions that use an adapter on that planar.

Instructor Guide
Instructor notes:
Purpose Describe characteristics of a partition that are independent from other
partitions.
Details List the things that are the same for LPARs on the same computer system.
Additional information Licensed Internal Code is a term used for i5/OS partitions and
Open Firmware is for AIX/Linux partitions.
Transition statement The term resource is used to specify the hardware can be
configured into a partition.

V5.3
Instructor Guide
Uempty
Partition resources
IBM Power Systems
Resources are allocated to partitions

Memory allocated in units as small as the LMB size
Dedicated whole processors or shared processing units
Individual I/O slots
Including virtual devices
Some resources can be shared

Virtual devices
Host Ethernet Adapter
Some core system components are inherently shared
AIX Linux AIX

PPPPP PP PPP
MMM MM MM
AAAAAA AAAA AAAA
A = Adapter
M = Memory
P = Processor
Figure 1-6. Partition resources AN111.0
Notes:
Resources
Resources are the system components that are configured into partitions.
The maximum number of partitions is related to the total amount of resources on the
system. For example, a system with eight processors can be configured with a total of
80 partitions (if there are sufficient resources). If a system has enough resources, the
upper limit of the number of partitions is 254.
Minimum amount of resources

Each partition must be configured with at least 128 MB of memory, one tenth of a
physical processor, and enough I/O devices to provide a boot disk and a connection to
a network.

Instructor Guide
Memory
Memory is allocated in units known as the Logical Memory Block (LMB). The default
LMB size is variable depending on the total amount of physical memory installed and
may be as small as 16 MB. A partition may be configured with as little as 128 MB of
memory or as much as all of the available memory.
Processors
A partition is configured with either dedicated whole processors or shared processors.
Shared processors are allocated in processing units. 1.0 processing units is equivalent
to the processing power of one processor. Partitions are configured with at least 0.1
processing units or with as much as the equivalent of all the available physical
processors. After the 0.1 minimum is satisfied, additional processing units can be
allocated in quantities of 0.01 processing units.
I/O slots
I/O resources are allocated to partitions at the slot level. At a minimum, you must
configure a partition with enough I/O resources to include the boot disk and a network
connection.
Shared devices
With software called the Virtual I/O Server installed in a special partition, Ethernet, and
storage devices can be configured to be shared between partitions.
Secure environments and shared I/O

Highly secure environments can choose not to take full advantage of the cross-partition
sharing of devices. Even very subtle visibility (for example, different response times
from a shared resource) can be considered a covert channel of communication. For this
reason, by design, all shared or virtual resources must be consciously enabled.
Shared core resources

Some devices can be shared because they are core resources to the entire system. For
example, even though you have allocated separate amounts of memory to different
partitions, that memory can be on the same memory card. Likewise, processors, I/O
drawers, and other core system components are shared. Because of this, a hardware
failure might bring down more than one partition, and potentially the entire system.
However, there are many fault containment, in-line recovery, and redundancy features
of the system to minimize unrecoverable failures.

V5.3
Instructor Guide

Purpose Define what is meant by the term resources and give examples of each type.
Details Describe that resources are what are allocated to partitions. Some resources
are dedicated and some can be shared.
Mention that even though processing power or an amount of memory is configured in a
partition, it does not mean that the underlying hardware is dedicated to that partition. For
example, memory allocated to several partitions can physically reside on the same memory
chip.
Transition statement Lets look at an example of how resources might be divided
between partitions.

Instructor Guide
Logical partition resource example

IBM Power Systems
Flexibility to allocate resources depending on need

With DLPAR operations, resources can be moved, removed, or
added without restarting the partition
LPAR 1 LPAR 2 LPAR 3 LPAR 4
Processors
Memory
I/O Slots
Figure 1-7. Logical partition resource example AN111.0
Notes:
Introduction
This visual shows how a systems resources might be divided between four partitions.
With logical partitions, resources can be allocated based on computing needs. You do
not need to allocate all resources to partitions; that is, some resources might remain
unallocated until they are needed.

With dynamic logical partitioning (DLPAR), resources can be added, removed, or
moved between partitions as computing needs change without restarting the partitions.

V5.3
Instructor Guide

Purpose Show an example of dividing system resources between multiple partitions.
Introduce the term DLPAR.
Details Show how resources are divided between partitions with little dependency on
underlying hardware architecture.
Transition statement Next we will see the POWER5+ processor-based servers that
support partitions.

Instructor Guide
IBM POWER5+ LPAR-capable systems

IBM Power Systems
IBM POWER5+ processor-based LPAR-capable systems

IBM System p5 Entry, mid-range, and high-end servers
Example models:
IBM System p5 505
IBM System p5 510
IBM System p5 520
IBM System p5 550
IBM System p5 560
IBM System p5 570
IBM System p5 575
IBM System p5 590
IBM System p5 595
Visit http://www.ibm.com for latest list of models.
Figure 1-8. IBM POWER5+ LPAR-capable systems AN111.0
Notes:
Introduction
The visual lists example IBM POWER5+ processor-based servers that support logical
partitioning. The list on the visual is not comprehensive; check www.ibm.com for the
current list.
IBM System p servers are IBM's previous generation of products for AIX and Linux
clients; subsequently replaced by the new IBM Power Systems.
System p models and resources remain available for AIX and Linux clients.

V5.3
Instructor Guide

Purpose List example models that support partitions.
Details This is a quick reference so that student see some of the models that are
available, and how they fit together in the product line. Because this list grows regularly,
point students to www.ibm.com for the most up-to-date information. There are also models
that end in Q, for Quad.
The pictures of systems in the visual are representative of some of the models.
Transition statement Next, we will see the POWER6 processor-based servers that
support partitions.

Instructor Guide
IBM POWER6 LPAR-capable systems

IBM Power Systems
IBM POWER6 processor-based LPAR-capable systems

Entry, mid-range, and high-end servers
IBM Power Systems
Example models:
IBM Power Blade Express servers
IBM Power 520
IBM Power 550
IBM Power 570
IBM Power 575
IBM Power 595
Visit http://www.ibm.com for latest list of models.
Figure 1-9. IBM POWER6 LPAR-capable systems AN111.0
Notes:
Introduction
The visual lists example IBM POWER6 processor-based servers that support logical
partitioning. The list on the visual is not comprehensive; check www.ibm.com for the
current list.
IBM Power Systems: a single, energy efficient and easy-to-deploy platform for all of
your UNIX, Linux, and IBM i applications.

V5.3
Instructor Guide

Purpose List example models that support partitions
Details
Transition statement Now that you know a bit about what a partition is, lets look at why
companies are using them.

Instructor Guide
Benefits of using partitions

IBM Power Systems
Capacity management
Flexibility to allocate resources
Consolidation
Consolidate hardware, floor space, software licenses, support contracts, in-house
support/operations
Efficient use of resources
Application isolation on a single frame
Separate workloads
Guaranteed resources
Data integrity
Merge production and test environments
Test on same hardware
The ability to have virtual Ethernet and virtual I/O devices is a

benefit to using POWER5 and POWER6 processor-based
partitions.
Figure 1-10. Benefits of using partitions AN111.0
Notes:
Introduction
Sometimes large symmetric multiprocessing systems are used to run several different
applications. This can be an efficient use of resources in some cases. In other cases,
separate physical computers are used to run individual applications. This page
describes reasons why it might be better to create separate partitions rather than run
everything in the same operating system image or use separate physical computers for
each application.
Capacity management
You might want to use partitions to dynamically reallocate resources when the system
workload changes. For example, if at the end of each month, one partition runs
CPU-intensive batch jobs, you can reconfigure the system monthly to take processors
from another lower priority partition and loan them to the partition with the batch
application.

V5.3
Instructor Guide
Uempty Consolidation
Using partitions gives you the ability to reallocate expensive resources and manage
them all with one interface (the Hardware Management Console). You can reallocate
processors, memory, or any I/O adapter (and thus device) by reconfiguring the
partitions or by using dynamic partition operations. All of the resources are located
within one server, potentially reducing the amount of floor space needed.
Application isolation
Partitioning isolates an application from others in different partitions. For example, two
applications on one SMP system could interfere with each other or compete for the
same resources. One decision support database query could bring a second,
interactive application to a frustrating snails pace. By separating the applications into
their own partitions, they cannot interfere with each other. Also, if one application were
to hang or crash the operating system, this would not have an effect on the other
partitions.
Also, with partitions, one server can support multiple applications that use different time
zones or that run on different operating system release levels.
Partitions can also be used to comply with application license requirements. For
example, a 4-processor partition could be created to comply with an application license
that only allows for a 4-processor server. Check the vendors application license
requirements carefully.
Merge production and test environments

Many customers utilize smaller development systems to develop, test, and migrate
applications. These smaller systems might not be the same hardware, or have the
same software, devices, or infrastructure as the real production system. These issues
can be largely avoided by utilizing a partition on the same system as the production
applications for development and testing. This also protects the production partition
from the activities on the test partition. When the testing is complete, the resources
used for the development partition can be reallocated to the production partition.
Partitions have an exclusive set of resources

The amount of resources allocated to a partition is generally fixed (although there are
some exceptions that can be configured). This could be a benefit or a disadvantage. On
a symmetric multiprocessor system running multiple applications within the same
operating system image, there might be greater sharing of resources than on a
partitioned system where the applications are isolated in their own partitions.

Instructor Guide
Virtual Ethernet and virtual I/O devices

On POWER6 processor-based servers, you can configure a virtual Ethernet connection
that acts like an Ethernet connection, but is really a memory-to-memory connection with
another partition. Virtual I/O devices allow partitions to use physical devices that are
owned by another partition. Also the Host Ethernet Adapter (or IVE), which is available
on all IBM Power Systems (except high-end servers), provides logical Ethernet
adapters, which communicate directly to logical partitions (LPARs). This reduces the
possible overall interaction with the POWER Hypervisor (PHYP).

V5.3
Instructor Guide

Purpose Describe the benefits of using partitions.
Details Discuss each benefit of using partitions.
Transition statement Next, we will talk about the software licensing models. As you
might expect, it is more complicated for partitioned systems.

Instructor Guide
Software licensing
IBM Power Systems
Licensing is per operating system and is based on processing

power
Partial processor and shared processor pool features affect licensing
Third-party application provider licenses will vary
Other Software
Operating Systems
IBM Hardware
Figure 1-11. Software licensing AN111.0
Notes:
Software licenses on a partitioned system

A partition runs its own separate copy of an operating system and programs. Language
feature codes, security, user data, most system values, and software release and fixes,
also known as program temporary fixes (PTFs), are unique for each partition.
For third-party software, you will have to discuss with the vendor how to license
packages on a partitioned system.
Effect of using sub-processors

Because operating systems and many other applications use numbers of processors as
the basis for licensing, if you use shared processors and take advantage of
sub-processor allocations, IBM rounds up to the nearest whole number in calculating
the appropriate software licenses and IBM will not charge you for more software
licenses than the number of physical processors on your server.

V5.3
Instructor Guide
Uempty If you plan to run different operating systems (that is, AIX 6 or Linux) on the same
server, then you need licenses for each individual operating system and the licenses
are based on processing power. For example, on an 8-processor system, you might
have licenses for seven processors for AIX 6 and one processor for Linux. If you
reconfigure your partitions so that, for example, you have 7.2 processors in the partition
running AIX 6 and your licenses only allow seven processors, you will receive out of
compliance messages. Either contact IBM to purchase more licenses or reconfigure the
partition to use less processing power to stop these messages.
Effect of using the Shared Processor Pool

For now, it is sufficient to understand that a software license must be purchased to
cover the maximum processing power that your partition might have at any point.
POWER5 and POWER6 advanced processing features allow partitions using the
Shared Processor Pool to optionally use excess processing power from other partitions.
This configuration feature is called uncapped processor allocation. Because a partition
that uses uncapped processor allocation could potentially use all of the processors in
the shared processing pool, the license for the software in that partition must take this
into account.
The POWER6 multiple shared processor feature can reduce the number of software
licenses by putting a limit on the amount of processors that an uncapped partition can
use.

Instructor Guide
Instructor notes:
Purpose Describe the licensing model for POWER5+ and POWER6 processor-based
LPAR-capable systems.
Details The new subprocessing and Shared Processor Pool features complicate
licensing on POWER5 and POWER6 systems. You must round up to the next whole
processor number for licenses, and licenses are affected by the use of uncapped shared
processors.
The Multiple Shared Processor Pools feature of POWER6 can affect licensing costs. This
will be covered later.
Transition statement The next page introduces the functions of the POWER
Hypervisor.

V5.3
Instructor Guide
Uempty
POWER Hypervisor functions

IBM Power Systems
The POWER Hypervisor is firmware that provides:

Virtual memory management
Controls page table and I/O access
Manages real memory addresses versus offset memory addresses
Virtual console support
Security and isolation between partitions
Partitions are allowed access only to resources that are allocated to them (enforced by
the POWER Hypervisor)
Shared processor pool management
POWER Hypervisor Security and

Isolation Barriers
System Hardware
(memory, processors, devices)
Figure 1-12. POWER Hypervisor functions AN111.0
Notes:
Introduction to the POWER Hypervisor

Partitions are isolated from each other by firmware (underlying software) called the
POWER Hypervisor. The names POWER Hypervisor and Hypervisor will be used
interchangeably in this course.
Virtual memory management by the Hypervisor

There is no program access permitted between partition memory and I/O memory.
Software exceptions and crashes are contained within a partition. The Hypervisor
controls the page tables used by partitions to ensure that a partition has access to only
its own physical memory segments. It uses a physical memory offset value for each
partition so that the operating system in each partition can continue to use memory
address zero as its starting point.

Instructor Guide
Virtual console support

The Hypervisor provides input/output streams for a virtual console device that can be
presented on the HMC.
Security and isolation between partitions

Besides managing virtual memory, the Hypervisor also ensures that a partition
accesses only devices allocated to it. It also clears memory, reinitializes processors,
resets processor registers, and resets I/O devices when devices are allocated to a
partition (statically or dynamically).
Shared Processor Pools

Always active on POWER5 and POWER6-based servers, the POWER Hypervisor is
responsible for dispatching the logical partition workload across the shared physical
processors. The Hypervisor creates a Shared Processor Pool from which it allocates
virtual processors to the logical partitions as needed.
Micro-Partitioning (or shared processing) allows logical partitions to share the
processors in Shared Processor Pools. Each logical partition that uses shared
processors is assigned a specific amount of processor power from its Shared Processor
Pool.
On POWER6-based systems there is support for Multiple Shared-Processor Pools.

V5.3
Instructor Guide

Purpose Describe the functions of the POWER Hypervisor.
Details Describe the purpose of the Hypervisor. You can use a traffic cop as an analogy.
The operating systems must go through the Hypervisor to access resources. The
Hypervisor controls access to these resources to make sure security is not compromised.
Transition statement The next page introduces the function of HMC.

Instructor Guide
Hardware Management Console

IBM Power Systems
The HMC provides:

Virtual console windows
LPAR configuration and operation management
Capacity on Demand (CoD) management
Service tools
Access to Live Partition Mobility function
PC-based console
Running custom Linux and Java application
Remotely accessible
Connects to Service Processor over private or open network
Desktop Rack-mount
Figure 1-13. Hardware Management Console AN111.0
Notes:
HMC description
The HMC is a PC-based console that is available in a desktop or a rack-mount model. It
runs a customized version of Linux with a Java-based management application. The
user can only access the management application and no additional applications can
be installed. A second HMC can be connected to a single managed system for
redundancy. Multiple managed systems can be managed by a single HMC.
There are desktop and rack-mount models of HMCs. Desktop models have the
machine type and model numbers such, as 7310-C0x. Rack-mount models have
machine type and model numbers such, as 7310-CRx.
The following new machine type HMC 7042-C0x and 7042-CRx
(desktop/rack-mounted) are shipped with POWER6 based-processor systems. 7042 is
pre-loaded with HMC version 7 code (and only V7 code is supported)
Older HMC model 7315 is not supported with POWER6/HMC V7.

V5.3
Instructor Guide
Uempty Check the IBM HMC support Web site for the latest information about the HMC
hardware and software:
https://www14.software.ibm.com/webapp/set2/sas/f/hmc/home.html
Remote access to the HMC functions

Remote access to the HMC Version 7 application is provided by using a Web browser
from a remote workstation. By default, remote browser access to the HMC is enabled.
In addition, there are extensive HMC command-line controls accessible through the use
of the Secure SHell (SSH).
HMC is independent from the managed system and its partitions

The managed system refers to the POWER5 or POWER6 system being managed by
the HMC. Although the HMC is necessary for some functions, such as configuring
LPARs, it will not affect the operation of any partitions if something goes wrong. The
partition configuration information is not only kept on the HMC but also kept in
Non-Volatile RAM (NVRAM) on the managed system; so if the HMC were to crash, the
partitions would continue to run. In fact, you can remove the HMC, replace it with
another, then download the partition data from the NVRAM on the managed system and
not affect the running of the partitions.
Service errors focal point

If a hardware error occurs, that error can be reported by multiple partitions. To prevent
confusion, the HMC is also used as a service focal point for error reporting. An
application on the HMC serves as a filter for errors to ensure IBM service calls are
placed only once per actual hardware error. Alternatively, a partition configured as the
service partition can collect system errors and report them to IBM.

Instructor Guide
Instructor notes:
Purpose Describe the basic functions of the HMC.
Details Describe when the HMC is required and the basic functions that the HMC
provides.
Point out the link to the IBM technical support Web site for more information about HMC
hardware and software.
Introduce the term managed system.
Additional information If asked, the screenshots and the HMC features in this entire
course are based on the HMC Version 7 Release 3.2 software.
Transition statement The next page shows an example screen from the HMC
application.

V5.3
Instructor Guide
Uempty
The big picture

IBM Power Systems
Managed System
AIX Linux Unassigned

resources
Partition 2
HMC
Partition 1
Hypervisor
Non-volatile RAM
Service
Processors
processor
Memory Ethernet
LPAR
I/O slots
allocation
tables
Figure 1-14. The big picture AN111.0
Notes:
Introduction
This picture brings together several concepts.
Partitions are independent operating environments and their resources are
managed by the Hypervisor.
NVRAM is used on the managed system to hold a copy of the partition
configuration so that if the HMC or the network were to fail, the partitions can
continue to run and even reboot if necessary.
Partitions are configured and managed on the HMC, which is a separate Linux
PC console. A copy of the partition configuration data is also kept on the HMC (in
addition to the primary copy in NVRAM).
The HMC is connected to the managed system through an Ethernet connection
to the service processor. The service processor is a separate, independent
processor that provides hardware initialization during system load, monitoring of
environmental and error events, and maintenance support.

Instructor Guide
Instructor notes:
Purpose Review the basics of how partitions, the POWER Hypervisor, and the HMC
relate to each other.
Details Describe how the LPAR configuration information is not only kept on the HMC
but also kept on the managed system.
The HMC connects to the managed system through an Ethernet connection to the service
processor.
Transition statement The first half of this unit covered the basics. The next half
introduces advanced partition features.

V5.3
Instructor Guide
Uempty
Advanced partition features

IBM Power Systems
Dynamic resource allocation

Advanced processor concepts
Virtual I/O
Integrated Virtual Ethernet
Live Partition Mobility
Capacity on Demand
Figure 1-15. Advanced partition features AN111.0
Notes:
Introduction
This page lists the advanced partition features covered in the rest of this unit.
The dynamic resource allocation, the advanced processor configuration options, the
virtual I/O and the capacity on demand are features available on POWER5 and
POWER6 processor-based servers.
Live Partition Mobility
Live partition mobility is a POWER6-based feature that enables you to migrate running
AIX and Linux partitions and their hosted applications from one physical server to
another without disrupting the infrastructure services. The migration operation, which
takes just a few seconds, maintains complete system transactional integrity. The
migration transfers the entire system environment, including processor state, memory,
attached virtual devices, and connected users.

Instructor Guide
Instructor notes:
Purpose Introduce the listed advanced partition features.
Details This page provides a transition from the first half of this unit, which covered
partition basics, and the second half, which talks about more advanced features.
Set expectations that this part of the unit will simply introduce terms and concepts.
Transition statement We will start with DLPAR.

V5.3
Instructor Guide
Uempty
Dynamic partitioning
IBM Power Systems
DLPAR is the ability to add, remove, or move resources

between partitions without restarting the partitions
Resources
Processors, memory, and I/O slots
Add/remove virtual devices
Security and isolation between LPARs is not compromised
A partition sees its own resources plus other available virtual
resources
Resources are reset when moved
Applications may or may not be DLPAR-aware
DLPAR allows you to react to

changing resource needs
Figure 1-16. Dynamic partitioning AN111.0
Notes:
Dynamic partitioning
Dynamic partitioning refers to the ability to move resources between partitions without
shutting down the partitions. The opposite of dynamic partitioning is static partitioning,
where new configurations are only used when a partition is reactivated.
DLPAR operations do not weaken the security or isolation between LPARs. A partition
sees only resources that have been explicitly allocated to the partition, along with any
potential connectors for additional virtual resources that may have been configured.
Resources are reset when moved from one partition to another. Processors are
reinitialized, memory regions are cleared, and adapter slots are reset.

Instructor Guide
DLPAR operations
You can add, remove, and move resources between partitions. The resources include
memory regions, processing units, and I/O slots. This can be accomplished from the
HMC application or using HMC command-line commands.
With virtual devices, you can add or remove them, but you cannot move them directly
from one partition to another. You can, however, dynamically change the configuration
that specifies what type of virtual adapter is in a virtual slot.
With the Integrated virtual ethernet, you can add or remove Logical Host Ethernet
Adapters. You can even move them from one partition to another dynamically.
Applications might not be DLPAR-aware

Most applications are unaware of the underlying resource specifics but some
applications and utilities, particularly monitoring tools, might inhibit some DLPAR
operations if they bind to processors or pin memory. Many resource-aware applications
have been rewritten in recent years to allow DLPAR. Check with your sales
representative about your applications.

V5.3
Instructor Guide

Purpose Describe the concept of dynamic partitioning.
Details List the operations and the resources involved with DLPAR.
Transition statement Lets look at how DLPAR works.

Instructor Guide
How DLPAR works

IBM Power Systems
1
HMC
HMC Command
2
3 3
Partition A Partition B
Hypervisor 4
Figure 1-17. How DLPAR works AN111.0
Notes:
Introduction
The visual illustrates how a dynamic move operation works.
1. The DLPAR request originates at the HMC.
2. The request is made over the network to the POWER Hypervisor.
3. Partition A and Partition B communicate with the HMC about the DLPAR operation
through a process running on both partitions.
4. The POWER Hypervisor makes the resource allocation change.
As you can see in the visual, DLPAR operations are dependent on a functioning network
between the HMC and the managed system, and between the HMC and the partitions. The
link between the HMC and the service processor is used to initiate the operation and
process the hardware add or remove operation. The link to the partition or partitions from
the HMC is used to notify the operating system of the hardware changes, enabling it to take
actions as required

V5.3
Instructor Guide
Uempty If the network is down, either between the HMC and the managed system or between the
partitions and the HMC, then DLPAR operations cannot occur.

Instructor Guide
Instructor notes:
Purpose Show what is involved in a DLPAR operation.
Details Review the components involved and what they do during a DLPAR operation.
The point to make on this slide is that there are two separate network connections that
must be fully functional to make DLPAR operations work. First, The link between the HMC
and the service processor is used to initiate the operation and process the hardware
add/remove operation. The link to the partition or partitions from the HMC is used to notify
the operating system of the hardware changes, enabling it to take actions as required
Transition statement The next topic is advanced processor concepts.

V5.3
Instructor Guide
Uempty
Processor concepts
IBM Power Systems
Logical
LPAR LPAR LPAR Virtual
Shared
Dedicated
Inactive
(CoD)
Deconfigured
Physical
(installed)
Shared processor pool
Figure 1-18. Processor concepts AN111.0
Notes:
Introduction
This visual summarizes the various concepts concerning POWER5 and POWER6
processors. Well see in the next slides that POWER6 based-processor systems
support other features, such as multiple virtual Shared Processor Pools. Along the
bottom are whole, physical processors installed in the computer system. These are
configured in various ways into the three partitions.
Processing units, partial processors, and logical processors

Partitions are allocated in dedicated whole processors or in processing units. A
processing unit is the equivalent of 1.0 of a physical processor. A partition can be
configured with as little as 0.1 processing units and after that minimum is satisfied,
processing units can be allocated in units of 0.01 processing units.

Instructor Guide
The terms Micro-Partitioning and partial processors refer to the ability to allocate less
than a whole physical processor to a partition.
Deconfigured
A physical processor can be automatically deconfigured from the system because of
detected errors or user deconfiguration.
Inactive, Capacity on Demand processors

Inactive processors can be added as a dedicated or shared processor through the
activation of a CoD license key. CoD is an option that can be purchased. There is more
on this in a few pages.
Shared versus dedicated processors

Dedicated processors are physical processors that are allocated to a partition and are
dedicated to that partition. Other partitions will not use any time slices on those
processors while that partition is active. Shared processors are put into a shared pool.
Partitions use processing units from the pools as needed within configuration
guidelines.
Virtual processors
If you were to allocate 2.0 processing units to a partition, the partition might get bits of
execution time on up to 20 physical processors. This concept is known as virtual
processors.
Virtual processors are the representation of the assigned processing units (defined as
processors) in the operating system. To run threads, the operating system dispatches
threads to the virtual processors. The Hypervisor takes the threads and dispatches
them to physical processors. The number of virtual processors in the operating system
limits the number of physical processors the Hypervisor can use for that partition during
each clock cycle. The processing units are spread across the virtual processors.
Logical processors
If simultaneous multi-threading is enabled for AIX 5L Version 5.3 or later, then each
virtual processor is utilized as if it were two processors.

V5.3
Instructor Guide

Purpose Review each of the processor concepts.
Details Try to touch each of these lightly, starting from the deconfigured and work your
way up to virtual. These will be covered in detail in later units. At this time, it is only
important to understand each term at a basic level.
Transition statement Lets talk about the term Micro-Partitioning.

Instructor Guide
Micro-partitioning: Shared processor pool

IBM Power Systems
Time-sliced sub-processor allocations are dispatched

according to demand and entitled capacity
This example shows one 10 ms timeslice, seven running
partitions, and four processors
Physical
processors
Partition 1
P P P P Partition 2
10ms
Partition 3
Partition 4
Partition 5
Partition 6
Partition 7
Shared processor pool

Figure 1-19. Micro-partitioning: Shared processor pool AN111.0
Notes:
Micro-Partitioning
Micro-Partitioning is defined as the ability to create a partition and allocate fractional
amounts of processing capacity to it.
Processing power can be allocated to partitions using dedicated processors or shared
processors. For shared processor partitions, processing power can be allocated in the
granularity of 0.01 processing units. A partition must have a minimum of 0.1 processing
units.
The visual shows seven partitions being run on a processing pool of four physical
processors. The diagram represents a single 10 millisecond (ms) interval. Each
partition gets a percentage of the execution dispatch time on the processors in the pool,
based on its capacity assignment. Do not worry; we will come back to this later. This
page is here to give you some basic terminology.

V5.3
Instructor Guide

Purpose Introduce the concept of virtual processors and time-slicing.
Details If students eyes cross when you get to this page, stick to the basics: now you
can allocate a partial processor to a partition and those partial processors are actually time
slices, which can be spread across multiple physical processors.
Transition statement Next, we will overview the multiple shared pools feature,
available on POWER6 based-processor systems.

Instructor Guide
Multiple shared processor pools

IBM Power Systems
Up to 64
Shared-Processor Pooln
Shared-Processor Pool1 Set of micro-partitions shared
Set of micro-partitions
Shared-Processor Pool0 processor
Set of micro-partitions
LPAR pools
LPAR1 LPAR3 LPAR
LPAR2 LPAR4
LPAR5
LPAR6
Shared
Dedicated
Physical
processors
Physical shared processor pool

Figure 1-20. Multiple shared processor pools AN111.0
Notes:
Introduction
By default, all physical processors that are not dedicated to specific logical partitions
are grouped together in a Shared Processor Pool. You can assign a specific amount of
the processing capacity in this Shared Processor Pool to each logical partition that uses
shared processors.
System p6 models enable you to use the HMC to configure multiple Shared Processor
Pools. Initially, there is a default Shared Processor Pool that contains all the processors
that do not belong to logical partitions that use dedicated processors or logical partitions
that use other Shared Processor Pools. The other Shared Processor Pools on these
models can be activated and configured with a maximum processing unit value and a
reserved processing unit value.

V5.3
Instructor Guide
Uempty Reserved and maximum processing unit values

The maximum processing unit value limits the total number of processing unit that can
be used by the set of logical partitions in the Shared Processor Pool. The reserved
processing unit value is the number of processing units that are reserved for the use of
uncapped logical partitions within the Shared Processor Pool.

Instructor Guide
Instructor notes:
Purpose
Details Introduce the concept of multiple Shared Processor Pools. Point out the default
shared pool ID 0. Also mention that 63 additional virtual shared pools can be activated.
Additional information Just give an overview of the multiple Shared Processor Pools
concept. Inform the students that this concept is detailed in the AN31 course: Power
Virtualization III: Advanced PowerVM, Partition Mobility and Performance.
Transition statement Next, we will describe what is meant by virtual I/O

V5.3
Instructor Guide
Uempty
Virtual I/O
IBM Power Systems
Each partition has virtual I/O slots

Configurable for each partition
Virtual slots can have a virtual adapter instance
Ethernet or SCSI
They can be dynamically added or removed just like physical
I/O slots
Cannot be dynamically moved to another partition
Figure 1-21. Virtual I/O AN111.0
Notes:
Virtual I/O basics

Each partition, by default, is configured to support 10 virtual I/O slots and each slot can
be populated with a virtual adapter instance, which allows partitions to share devices. It
also provides virtual Ethernet connections between partitions on the same system.
More virtual slots can be configured.
Virtual adapters interact with the operating system like any other adapter card, except
that they are not physically present. Virtual adapters are recorded in system inventory
and management utilities.
As with physical I/O adapters, a virtual I/O adapter must first be deconfigured from the
operating system to perform a DLPAR remove operation.

Instructor Guide
Virtual Ethernet
Virtual Ethernet provides the same function as using an Ethernet adapter and is
implemented through high-speed, inter-partition, in-memory communication. There are
two options with virtual Ethernet.
A virtual Ethernet connection can be configured between two LPARs on the
same managed system. There is no actual physical adapter. This provides a fast
network connection between the partitions.
A virtual Ethernet connection can be configured on one partition to connect to a
network using a Shared Ethernet adapter of another partition (called a hosting
partition or a Virtual I/O Server) on that managed system.
Virtual SCSI
The virtual SCSI option provides access to block storage devices in other partitions
(that is, device sharing). It uses the client/server model where the server exports disks,
logical volumes, files, or other SCSI-based devices, and the client sees the imported
device as a standard SCSI device.

V5.3
Instructor Guide

Purpose Describe what is meant by virtual I/O.
Details Describe the benefits of using virtual I/O devices.
Transition statement The next page shows how virtual Ethernet and virtual SCSI
devices are implemented.

Instructor Guide
Virtual I/O example

IBM Power Systems
Client Virtual I/O Server

Partition Partition
Physical
Virtual Virtual Virtual Layer 2
Bridge
Physical Network
Ethernet Ethernet Ethernet
Switch
Virtual
Ethernet Logical
Virtual Disk
Hypervisor Disk
Client Server Device

Adapter Adapter Mapping
SCSI RDMA Protocol
DMA
Buffer Device DM
A Transfer
SCSI, SSA, FC Physical

or Logical Disks
Figure 1-22. Virtual I/O example AN111.0
Notes:
Client/server relationship
Virtual I/O devices provide for sharing of physical resources, such as adapters and
SCSI devices, among partitions. Multiple partitions can share physical I/O resources
and each partition can simultaneously use virtual and physical (natively attached) I/O
devices. When sharing SCSI devices, the client/server model is used to designate
partitions as users or suppliers of resources. A server makes a virtual SCSI server
adapter available for use by a client partition. A client configures a virtual SCSI client
adapter that uses the resources provided by a virtual SCSI server adapter.
If a server partition providing I/O for a client partition fails, the client partition might
continue to function depending on the significance of the hardware it is using. For
example, if the server is providing the paging volume for another partition, a failure of
the server partition will be significant to the client.

V5.3
Instructor Guide
Uempty Virtual I/O Server

The IBM Virtual I/O Server software allows the creation of partitions that use the I/O
resources of another partition. In this way, it helps to maximize the utilization of physical
resources on POWER5 and POWER6 systems. Partitions can have dedicated I/O,
virtual I/O, or both.
Physical resources are assigned to the Virtual I/O Server partition in the same way
physical resources are assigned to other partitions.
Virtual I/O Server is a separate software product, and is included as part of the
PowerVM standard edition feature. It supports AIX V5.3, AIX V6.1, and Linux partitions
as virtual I/O clients.
Virtual SCSI adapters

Virtual SCSI adapters provide the ability for a partition to use SCSI devices that are
owned by another partition. For example, one partition can provide disk storage space
to other partitions.
See the Virtual I/O Server technical support Web site for specific devices that are
supported:
https://www14.software.ibm.com/webapp/set2/sas/f/vios/documentation/home.html
Virtual Ethernet
There are two main features to virtual Ethernet. One is the inter-partition virtual switch
to provide support for connecting up to 4,096 LANs. LAN IDs are used to configure
virtual Ethernet LANs and all partitions using a particular LAN ID can communicate with
each other.
The other feature is a function called Shared Ethernet adapter that bridges networks
together without using TCP/IP routing. This function allows the partition to appear to be
connected directly to an external network. The main benefit of using this feature is that
each partition need not have its own physical network adapter.

Instructor Guide
Instructor notes:
Purpose Describe the virtual I/O device types.
Details This visual shows that the virtual device traffic is managed by the Hypervisor
and the client/server model used for virtual I/O.
The Virtual I/O Server has the physical I/O devices that other partitions can use. The client
partition must then configure the devices it wants to use.
Transition statement The next slide is an IVE (Integrated Virtual Ethernet) introduction.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Also referred to Host Ethernet Adapter

Included in all POWER6 system configurations (except high-end)
Provides network connectivity for logical partitions without a
Virtual I/O Server
Integrated high-speed Ethernet ports with hardware-assisted
virtualization capabilities.
Offers virtualization support for Ethernet connections
Three types are available
Two port 1 Gbpsa (default)
Four port 1 Gbpsa
Two port 10 Gbpsb
Connected to the GX+ bus
A Logical Host Ethernet Adapter must be created on the logical

partition.
Figure 1-23. Integrated Virtual Ethernet AN111.0
Notes:
Host Ethernet Adapter
A Host Ethernet Adapter (HEA) is a physical Ethernet adapter that is integrated directly
into the GX+ bus on a managed system. HEAs offer high throughput, low latency, and
virtualization support for Ethernet connections. HEAs are also known as Integrated
Virtual Ethernet adapters (IVE adapters).
Unlike most other types of I/O devices, you can never assign the HEA itself to a logical
partition. Instead, multiple logical partitions can connect directly to the HEA and use the
HEA resources. This allows these logical partitions to access external networks through
the HEA without having to go through an Ethernet bridge on another logical partition.

Instructor Guide
Instructor notes:
Purpose
Details The Integrated Virtual Ethernet adapter is a standard feature of every POWER6
processor-based 570, 560, 550, and 520 server. You can select from different offerings
according to the specific IBM System p server.
The IVE consists of a physical Ethernet adapter that is connected directly to the GX+ bus of
a POWER6 processor-based server instead of being connected to a PCIe or PCI-X bus,
either as an optional or integrated PCI adapter. This provides IVE with the high throughput
and low latency of a bus imbedded in the I/O controller. IVE also includes special hardware
features that provide logical Ethernet adapters. These adapters can communicate directly
to logical partitions (LPARs), reducing the interaction with the POWER Hypervisor
(PHYP).
Transition statement The next slide introduces the Live partition mobility feature.

V5.3
Instructor Guide
Uempty
Integrated Virtual Ethernet example

IBM Power Systems
AIX Linux
LPAR LPAR
ent ent eth
Layer 2 switch Layer 2 switch
Physical Physical
port port
Physical Physical
network network
Figure 1-24. Integrated Virtual Ethernet example AN111.0
Notes:
Introduction
In this logical diagram, the AIX and Linux LPARs communicate directly to the Host
Ethernet adapter, reducing the interaction with the POWER Hypervisor.
IVE provides a way for a logical partition to communicate with other logical partitions or
with external networks without going through a Virtual I/O Server. After you create an
Logical host ethernet adapter (LHEA) for a logical partition, a network device is created
in the logical partition. This network device is named entX on AIX logical partitions, and
ethX on Linux logical partitions, where X represents sequentially assigned numbers.
The user can then set up TCP/IP configuration similar to a physical Ethernet device to
communicate with other logical partitions or to the external network.

Instructor Guide
Instructor notes:
Purpose
Details Tell the students that IVE is detailed in the AN30 course: Power Virtualization II:
Implementing Dual VIOS and IVE.
Transition statement The next slide introduces the Live partition mobility feature.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Migration or movement of a logical partition from one

physical server to another
Useful for:
Reducing the impact of planned outages and increasing application
availability
Workload balancing and consolidation
Relocation of workload to enable workload
Provision new technology with no disruption to service (migration to
newer systems)
Server 1 Server 2
Requirement
VIOS
VIOS
Logical partition must P1 P2 P3 P1 P5
only have virtual adapters
HMC
Network
Figure 1-25. Live partition mobility AN111.0
Notes:
For systems that are managed by an HMC, you can migrate a powered-off or
powered-on AIX or Linux logical partition to a different system that is managed by the
same or by a different HMC.
For systems that are managed by the Integrated Virtualization Manager, you can
migrate a powered off or powered on partition to a different system that is managed by
a different Integrated Virtualization Manager.
Live Partition Mobility is included in the PowerVM Enterprise Edition. Live Partition
Mobility is available on all POWER6 processor-based System p servers, the IBM
BladeCenter JS12 Express and JS22.
Active Partition Mobility refers to moving a running logical partition, including its
operating system and applications, from one system to another. The logical partition
and the applications running on the logical partition do not need to be shut down.
Inactive Partition Mobility refers to moving a powered off logical partition from one
system to another.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement The next topic is Capacity on Demand.

V5.3
Instructor Guide
Uempty
Capacity on Demand
IBM Power Systems
Capacity Upgrade on Demand (CUoD)

Permanent activation of processors or memory
Trial CoD
No charge 30-day activation of processors or memory resources
On/Off CoD
Ability to activate processor or memory resources temporarily
Utility CoD
Additional processor capacity on a temporary basis within the
shared processor pool.
Capacity Backup
Add Reserve
Processors and memory temporarily Resources
added to backup server
Prepaid for up to 90 days
Figure 1-26. Capacity on Demand AN111.0
Notes:
Introduction to Capacity on Demand

CoD is the name given to a collection of optional features available for purchase on
certain models of POWER5+ and POWER6 processor-based servers. The main bullets
in the visual list purchasing options. These options are managed from the HMC and
require a license key to activate.
Capacity Upgrade on Demand (CUoD) requires a purchase agreement. When
processors or memory are added, there is no ability to turn off the capacity. Processors
are added in units of one whole processor, and memory can be added in 1 GB
increments.
Trial CoD is available for up to 30 contiguous days at no additional cost to allow testing
and emergency relief while the customer processes the purchase of permanent CUoD
resources.

Instructor Guide
On/Off CoD provides temporary additional processor or memory resources. Activity is

reported to IBM monthly and there must be an On/Off Capacity agreement.
Utility CoD allows clients to use additional capacity in a minute-by-minute basis and
the service delivers a processor minute of capacity when and where you need it. Just
like electricity is accounted for as it is used, processor minutes are accounted for at the
time of actual use. Utility CoD allows you to assign inactive processors that are installed
on the system to the Shared Processor Pool where they can be used to satisfy the
variable workload demands of the business. The assigned processors will be treated as
utility processors that are available for use by uncapped partitions. When an uncapped
partition reaches 100% utilization and at least 10% of a utility processor is put into use
during a 1-minute interval, a utility processor minute will be considered consumed.
Capacity BackUp adds reserve processor and memory capacity to a backup server in
the event of an unforeseen loss of production server capability due to forces beyond
your control. You can divert entire workloads to backup servers for up to 90 days. There
is an upfront fee and an emergency-use fee, which include testing.
Reference
For more information, visit the IBM Web site (www.ibm.com) and search for CoD or
use this link: http://www-03.ibm.com/systems/p/advantages/cod/index.html.

V5.3
Instructor Guide

Purpose Introduce the concept of Capacity on Demand.
Details These are extra features that a customer can specify when configuring system
for purchase. Each option has a different license agreement and customers need to
purchase additional licenses to obtain license keys to activate the resources.
The Capacity on Demand options change over time. Point students to www.ibm.com or
their local IBM representative for specific information.
Transition statement Some of the product features discussed in this unit are part of the
PowerVM Editions, which are described on the next page.

Instructor Guide
PowerVM editions
IBM Power Systems
PowerVM editions hardware feature includes the following

components
PowerVM Editions
Express Standard Enterprise
1+2 /
Maximum LPARs 10 / Core 10 / Core
Server
Management IVM IVM, HMC IVM, HMC
Virtual I/O Server 9 9 9
Lx86 9 9 9
Shared Dedicated
9 9 9
Capacity*
Multiple Shared
9 9
Processor Pools
Live Partition
Mobility 9
Ordered as optional feature code for all but the largest systems
PowerVM Standard edition is standard on the IBM System p5 590 and 595
PowerVM Enterprise edition is standard on POWER6 595
Figure 1-27. PowerVM editions AN111.0
Notes:
PowerVM Express Edition
You can use the Express Edition in restricted environments at no cost. The Express
Edition is available on some POWER6 processor-based IBM System p servers. To use
the Express Edition, the system must be managed by the Integrated Virtualization
Manager.
With the Express Edition, you can create up to two client logical partitions that use
virtual Small Computer System Interface (SCSI) and shared processors, also called
Micro-Partitioning technology. If you want to create more than two client logical
partitions that use shared processors or virtual SCSI, then you must purchase either the
Standard or Enterprise Edition and enter the activation code. (Virtual Ethernet is
available to all client logical partitions.)
PowerVM Standard Edition
You can use the Standard Edition with POWER5 and POWER6 processor-based IBM
System p servers, IBM System i models, and some IBM BladeCenter blade servers.

V5.3
Instructor Guide
Uempty However, Partition Load Manager is available only on POWER5-processor based

systems.
For IBM System p servers and IBM System i models, the Standard Edition requires an
activation code to enable the PowerVM Editions hardware feature. When you specify
the PowerVM Editions hardware feature with the initial system order, the firmware is
activated to support the components of the feature. If you order the feature separately
from the server, you can enter the code using the HMC or the Integrated Virtualization
Manager. For IBM BladeCenter blade servers, the server includes the Standard Edition;
you do not need an activation code.
PowerVM Enterprise Edition
You can use the Enterprise Edition with POWER6 processor-based IBM System p
servers and some IBM BladeCenter blade servers. Like the Standard Edition, in HMC
environments, the Integrated Virtualization Manager is disabled because the system is
managed by the HMC. For some blade servers and IBM System p servers that are not
managed by an HMC, the Virtual I/O Server becomes the management partition and
provides the Integrated Virtualization Manager to help you manage the system. The
Enterprise Edition requires an activation code to enable the PowerVM Editions
hardware feature. When you specify the feature with the initial system order, the
firmware is activated to support the components of the feature. If you order the feature
separately from the server, you can enter the code using the HMC or the Integrated
Virtualization Manager. This is a different code from the Standard Edition. For example,
you might have previously purchased the Standard Edition and enabled the feature on
the system. Now you want the ability to migrate logical partitions from one system to
another. To do this, you must purchase the Enterprise Edition and enter the activation
code for the Enterprise Edition.
For more information about PowerVM editions, refer to:
http://www-03.ibm.com/systems/power/software/virtualization/editions/index.html

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Lets summarize the partitioning concepts.

V5.3
Instructor Guide
Uempty
Partitioning concepts summary

IBM Power Systems
Part#1 Part#2 Part#3 Part#4 Part#5 Part#6 Part#7-11

Use thisAIX
Virtual layout
V6 for all your
Linux drawing
i5/OS AIX V5needs
AIX V6 AIXV6 / LAN
I/O Server Linux
PPPPPP PPPP
PPPPPP PPP P PPPPPP
MMMMM MMMM MMM MMM M MM M M M M M
A A
AAAAAA AAAAA AAA AAAA AA AAA
Virtual LAN
Virtual I/O
OOO O
O O
O O
O
AIX 6 AIX 6 Linux i5/OS AIX 6 AIX 6 S S S S
S S S S
S
Kernel Kernel Kernel Kernel Kernel Kernel
Virtual Ethernet
POWER Hypervisor
HMC
Figure 1-28. Partitioning concepts summary AN111.0
Notes:
Introduction
This visual illustrates a system with 11 partitions running different operating systems. It
shows the basic components of a system running logical partitions, such as the HMC,
the POWER Hypervisor, a virtual LAN, virtual I/O, and both dedicated and shared
processor partitions.
In the visual, the P=processors, M=memory, and A=adapters in I/O slots.
Details shown in the example in the visual:
Partitions 1-3 are using dedicated processors.
Partitions 4-11 are using the Shared Processor Pool.
Partitions 4-11 are Micro-Partitions using less than a whole processor.
Partitions 1 and 6-11 have virtual Ethernet connections.

Instructor Guide
Partitions 7-11 are making use of virtual Ethernet and virtual I/O to share
Ethernet adapters and disks.
Partition 1 is a Virtual I/O Server and has the physical disks and Ethernet
adapters that the virtual clients are using.

V5.3
Instructor Guide

Purpose Use the visual to review some of the basic concepts from this unit and show
the big picture.
Details Review the bullet points in the student notes to show how a system might be
configured.
Transition statement There is one more major system configuration option with regard
to partition support. This is the Integrated Virtualization Manager.

Instructor Guide
Integrated Virtualization Manager

IBM Power Systems
Provides support for logical partitions without a physical HMC

Manages a single server
IVM software runs in Virtual I/O Server partition
Provides a subset of HMC functionality

Hypervisor has been modified to enable VIOS to manage the
partitioned system without an HMC
Implicit rule of configuration and setup

Requires that the server not be partitioned
First operating system installed VIOS AIX Linux Linux
must be the VIOS IVM V6.1 RHEL5 SLES10
Virtual I/O Server partition owns

all physical I/O
Client partitions can access
Virtual LAN
virtual optical, virtual disk,
virtual Ethernet, IVE, and console. POWER Hypervisor
Figure 1-29. Integrated Virtualization Manager AN111.0
Notes:
IVM description
IVM provides partition support without a physical HMC. The benefit is for low-end
systems to save the cost and space of a physical HMC.
The HMC functionality is provided by the IVM software running in the Virtual I/O Server
partition. The IVM can be accessed through a Web browser, or an HMC compatible
command line interface.
The client partition I/O used to be virtualized but with POWER6 based-processors
systems, you can assign dedicated I/O to logical partitions. Only one Virtual I/O Server
partition can be installed on a system using IVM. The maximum number of partitions is
10 times the number of processors.

V5.3
Instructor Guide
Uempty IVM and dynamic logical partition operations

Dynamic LPAR for the Virtual I/O Server partition is supported using the IVM interface.
As of the Virtual I/O Server release 1.3, CPU and memory DLPAR operations for client
partitions are supported. Prior to that release, DLPAR operations for client partitions are
not supported.
Reference
See the Virtual I/O Server Integrated Virtualization Manager and PowerVM
Virtualization on IBM System p: Introduction and Configuration Redbooks for
configuration details for IVM.

Instructor Guide
Instructor notes:
Purpose Introduce the IVM product.
Details IVM provides a subset of HMC functions and basic partition support for
lower-end systems. The benefit is that there is no physical HMC needed.
There are no IVM hands-on lab exercise steps in this class.
Transition statement Next, we will see the overall process to get a new server running
with partitions.

V5.3
Instructor Guide
Uempty
LPAR configuration process

IBM Power Systems
1 Create
Createplan
planfor
forusage
usagemodel
modeland
andapplications
applications
2 Plan
Planresources
resourcesfor
forpartitions
partitions
3 SetCreate
up HMCandand managed
configure system
partitions
4 Create
Createand
andconfigure
configurepartitions
partitions
5 Activate
Activatepartitions
partitionsand
andinstall
installoperating
operationsystems
systems
6 Configure
Configureand
andtest
testservice
serviceapplications
applications
Figure 1-30. LPAR configuration process AN111.0
Notes:
Introduction
These are the overall steps for configuring partitions on a managed system. The AN11
course is designed to follow this process from Step 2 to the end.
Step 1: Plan for usage model and applications

If you have already purchased a system, you have probably already completed Step 1
as part of the system sizing process.
As part of this step, you should have some idea about how to divide up the applications
into partitions. You should also plan for future needs, such as partitions for development
and testing.

Instructor Guide
Step 2: Plan resources for partitions

Planning the resource allocations for partitions is the most important step in the
configuration process because it will hopefully eliminate errors and multiple
reconfigurations later in the process.
Planning is crucial because as you will see, with multiple partitions, the configuration
information becomes quite complex very quickly. This is particularly true for the network
configuration of your partitions and the HMC. You should plan for the normal operation
of the application in a partition and for best case and worst case scenarios (that is, extra
resources and hardware failure).
It is important to document all configurations and keep the records up to date.
One useful tool to use during this step (and Step 1, if the Sales Representative uses it)
is the System Planning Tool available from IBM. You can use this tool to plan the
resources for the partitions on the system, and then import the partition configurations
from your plan. The use of this tool is covered in the AN11 course.
Step 3: Power on and set up managed system

The managed system is a term used to describe a single system with one or more
partitions.
For new managed systems and HMCs, the HMC must be configured to support the
managed system. Then, when you power on the managed system from the HMC,
choose the Partition Standby power on option. This option will allow you to configure
partitions.
Step 4: Create and configure partitions

You must plan, create, and configure each logical partition. Configuring a partition
consists of allocating resources and setting other configuration options.
Step 5: Activate partitions and install operating systems

At this point, you can activate each partition and install an operating system.
Step 6: Configure and test service applications

Because IBM cannot predict how a particular system might be divided into separate
operating system environments, you might need to alter the configuration of the service
applications, such as Service Agent and Service Focal Point.

V5.3
Instructor Guide

Purpose Describe the overall process to configure LPARs.
Details Describe each step in the visual.
Emphasize that it is extremely important to plan the resource allocations for partitions first
before starting the configuration step. It is much harder to catch mistakes after you begin
configuring than it is to plan the configuration correctly the first time.
Transition statement Lets see where to find more information about PowerVM and
logical partitioning.

Instructor Guide
Logical partition references

IBM Power Systems
Documentation
http://www.ibm.com/support/publications/us/library/
Software and hardware Information Centers available
LPAR and PowerVM information

http://www-03.ibm.com/systems/power/software/virtualization/index.html
IBM Redbooks
http://www.redbooks.ibm.com/
Technical support Web sites

http://www.ibm.com/servers/eserver/support/unixservers/
http://www14.software.ibm.com/webapp/set2/sas/f/hmc/
http://www14.software.ibm.com/webapp/set2/sas/f/vios
Linux Web site

http://www.ibm.com/systems/p/linux/
Web links might change over time.

Figure 1-31. Logical partition references AN111.0
Notes:
Introduction
This list is a starting point to obtain documentation for your system. There is
documentation for your specific system model, for the HMC, for the operating systems,
and for configuring partitions. The library link shown first in the visual is a good starting
point for information. Links are provided there for the Information Centers.
There are new IBM Redbooks released all the time, particularly as a product matures.
Check the www.redbooks.ibm.com Web site from time to time.
The Web locations shown in the visual might change over time; however, generally old
links are redirected to new ones.

V5.3
Instructor Guide
Uempty Linux adapter support

For customers installing SUSE Linux Enterprise Server for POWER, or Red Hat
Enterprise Linux AS for POWER, refer to the following Web site for information on
supported I/O adapters and storage devices:
http://www-03.ibm.com/systems/p/hardware/reports/factsfeatures.html

Instructor Guide
Instructor notes:
Purpose Describe references for partitioning.
Details Describe that the main place to go for information is the appropriate Information
Center. There are hardware and software Information Centers.
The World Wide Web links shown in the visual change over time, but users should be
redirected to the new ones if they try to use old ones.
Transition statement

V5.3
Instructor Guide
Uempty
AN11 course content

IBM Power Systems
System p hardware overview

System Planning Tool
HMC maintenance
System power management
Configuring logical partitions
Dynamic resource allocation
Figure 1-32. AN11 course content AN111.0
Notes:
The purpose of this slide is to overview the content and the different features that will be
covered in the AN11 class. Some of the advanced features that we just overviewed in
this introduction unit are not covered in that class.

Instructor Guide
Instructor notes:
Purpose Highlight the content of the AN11 course.
Details This unit introduced the virtualization features available on System p. Point out
to the students the content of this AN11 class and mention that some of the advanced
features that we overviewed, like the Micro-partitioning, the Virtual I/Os, the Integrated
Virtual Ethernet or the logical partition mobility are not part of this course.

V5.3
Instructor Guide
Uempty
AN30 course content

IBM Power Systems
Advanced processor concepts

Virtual I/O
Virtual network configurations
Virtual SCSI configurations
Service management
Figure 1-33. AN30 course content AN111.0
Notes:
The purpose of this slide is to overview the content and the different features that will be
covered in the AN30 course: Power Virtualization II: Implementing Dual VIO Servers
and IVE. Some of the advanced features that we just overviewed in this introduction unit
are not covered in that class.

Instructor Guide
Instructor notes:
Purpose Highlight the content of the AN30 course
Details This unit introduced the different features available on System p. Point out to the
students the content of this AN30 class and mention that the logical partition mobility
advanced feature is not covered in that course.
Transition statement Lets see if you have been paying attention.

V5.3
Instructor Guide
Uempty
Checkpoint (1 of 2)
IBM Power Systems
1. 1. True or False: A partition is an independent operating

environment.
2. What makes a partition logical?

a. Resource assignments are flexible.
b. Resources can be moved between partitions without a restart.
c. Partitioning is not dependent on physical system building blocks.
3. Which of the following are true for dynamic partition operations?

a. All AIX6 partitions on POWER6 processor-based systems are
capable of dynamic resource allocations.
b. Virtual I/O devices can be dynamically added or removed but not
moved between partitions.
c. Partitions do not need to be restarted to add, remove, or move
resources.
d. Applications might or might not be DLPAR-aware.
4. List the types of resources that are configured in partitions.
Figure 1-34. Checkpoint (1 of 2) AN111.0
Notes:

Instructor Guide
Instructor notes:
Purpose Check the students understanding of the material in this unit.
Details Checkpoint solutions:
Checkpoint solutions (1 of 2)
IBM Power Systems
1. 1. True or False: A partition is an independent operating environment.

3. Which of the following statements are true for dynamic partition operations?
resources.

Processors, memory, I/O slots (including the Host Ethernet Adapter)
Transition statement There is one more page of checkpoint questions.

V5.3
Instructor Guide
Uempty
Checkpoint (2 of 2)
IBM Power Systems
5. What system option provides the ability to order additional resources

that can be activated when you need them?
6. Which of the following are benefits of using partitions?

a. Better management of resources across operating environments
b. Isolate applications that were all running on one system
c. Better high availability solution
d. Manage operational costs by consolidating resources
7. What is the system component that performs the resource allocation to

partitions?
8. What is the system component needed to configure partitions,

configure CoD, and provide access to virtual consoles?
9. What is the term used for the concept of allocating sub-processors to

partitions?
Notes:

Instructor Guide
Instructor notes:
Purpose
Details Checkpoint solutions:
IBM Power Systems

that can be activated when you need them? Capacity on Demand
(CoD)


partitions? POWER Hypervisor

configure CoD, and provide access to virtual consoles? HMC or IVM

partitions? Micro-Partitioning
Transition statement Next, we will perform a hands-on exercise.

V5.3
Instructor Guide
Uempty
Exercise
IBM Power Systems
Unit
exerc
ise
Figure 1-36. Exercise AN111.0
Notes:

Instructor Guide
Instructor notes:
Purpose Practice the skills learned in this unit.
Details Have the students open to the exercise for this unit in the Exercise Guide.
Additional information Check the instructor notes in the exercise to see if you need to
provide any information such as logins, passwords, or IP addresses for the activities.
Transition statement Lets summarize what we learned in this unit.

V5.3
Instructor Guide
Uempty
Unit summary
IBM Power Systems
Having completed this unit, you should be able to:

Partition, logical partition resource
Describe the benefits of partitioning
Micro-partitioning
Virtual I/O
Capacity on Demand (CoD)
Describe the functions of the Hardware Management
Console (HMC)
List references for IBM POWER5 and POWER6 processor-
based system partitioning
Figure 1-37. Unit summary AN111.0
Notes:
More summary information:
Logical partitions are independent operating environments.
Resources are processors, memory, and I/O slots:
- Dedicated processors and shared processing units
- Physical and virtual I/O
The POWER Hypervisor is firmware that provides the isolation between partitions,
virtual console support, and virtual memory management.
The HMC is used to manage partition configurations, consoles, and service tools.
With dynamic logical partitioning, changes can be made to a partitions resource
allocation without a restart.
Virtual I/O Server software provides the ability to share SCSI devices and Ethernet
adapters.
The PowerVM editions features provide Micro-partitioning, Virtual I/O Server, Live
partition mobility.

Instructor Guide
Instructor notes:
Details
Additional information Review Questions: Review questions are used at the beginning
of each class day to review concepts learned during the previous day.
You can use the following questions as review for this unit:
1) What makes a logical partition logical?
Answer: The term logical refers to the fact that the partitioning of the independent operating
environments is done in firmware.
2) What is the benefit of dynamic partitioning?
Answer: With dynamic partitioning, you can reallocate memory, processors, and I/O slots
without having to restart a partition.
4) What are partition resources?
Answer: Partition resources are those things that can be allocated to a partition, such as
processors (or processor units), memory, and I/O slots.
5) What is included in the PowerVM Standard Edition feature on a POWER5 System?
Answer: The ability to create Micro-Partitions, the Virtual I/O Server software, and the
Partition Load Manager software.
Transition statement The next unit covers the system architecture of POWER5 and
POWER6 processor-based systems that support LPARs.

V5.3
Instructor Guide
Uempty Unit 2. Hardware system overview
Estimated time
01:00

This unit describes the system components and location code formats
for the LPAR-capable IBM POWER5+ and IBM POWER6
processor-based systems.

Identify basic architecture elements and hardware components of
the LPAR-capable IBM POWER5+ and POWER6 processor-based
systems
Describe the functions of the service processor
Describe physical location code conventions
Use AIX commands to view location codes

Accountability:
Checkpoint
Machine exercises
References
http://publib.boulder.ibm.com/infocenter/systems/index.jsp
Facts and features
Redpapers:
IBM System p 520 Technical Overview and Introduction
Copyright IBM Corp. 2009 Unit 2. Hardware system overview 2-1

Instructor Guide
Unit objectives
IBM Power Systems
Identify basic architecture elements and hardware

components of IBM POWER5+ and POWER6 processor-
based systems
Notes:

V5.3
Instructor Guide

of the unit. Point out to the students that we will cover the use of the SPT tool in this unit but
the hands on exercise is at the end of the class. The reason is that a lot of processor,
memory, and I/O material must be covered first before fully understanding the use of this
tool.
Transition statement We will start with an overview of the IBM POWER5+

Instructor Guide
IBM POWER5+ processor-based systems

IBM Power Systems
IBM System p5 and IBM System i5 hardware convergence at

POWER5
Both support mix of AIX V5.2, AIX V5.3, AIX V6.1, Linux, and IBM i operating systems
All support PowerVM Standard Edition
Entry systems: 1- to 4-way processor systems

Examples: IBM System p5 505, IBM System p5 505Q, IBM System p5 520, IBM System
p5 550
Mid-range systems: 2- to 16-way processor systems

Example: IBM System p5 560Q, IBM System p5 570
High-end systems: 8- to 64-way processor systems

Examples: IBM System p5 575, IBM System p5 590, IBM System p5 595
g
Scalin
-w a y
1- to 64
s
system
Figure 2-2. IBM POWER5+ processor-based systems AN111.0
Notes:
Introduction
With the introduction of POWER5, the IBM System p5 and IBM System i5
LPAR-capable hardware systems use the same basic hardware platform, with the
exception of the I/O subsystem. The same HMC can be used for both System i5 and
System p5 managed systems.
The machine type and model numbers shown in the visual are examples and are
specific to the IBM System p5 systems. There are differences between these System
p5 and System i5 systems in packaging and licensing. Check the http://www.ibm.com
Web site for the most up-to-date information.
Not all system models support all three operating systems.

V5.3
Instructor Guide
Uempty Hardware Management Console required for LPAR management and

CoD
An IBM HMC (or an IVM) is required to manage partitions or use Capacity on Demand
(CoD). Multiple partitions and multiple POWER5 processor-based servers can be
supported by one HMC. The HMC is not required for a partition to run, but is required to
create, define, and change the logical partition configuration.

Instructor Guide
Instructor notes:
Purpose List examples of IBM POWER5 processor-based systems available as of May
2008.
Details Give an overview of how the systems fit together. Mention that there are so
many systems, we will not cover all of them in this unit. Point them to http://www.ibm.com
for the latest models and specifications.
Except for the I/O subsystem, the architecture of the IBM System p5 hardware and the IBM
System i5 hardware is the same; however, the machine type and model numbers are
different. The firmware image and vital product data (VPD) chip are different too.
Transition statement The next visuals will give an overview of the IBM System p5
family.

V5.3
Instructor Guide
Uempty
IBM System p5
IBM Power Systems
Midrange Rack density High-end
p5-570
p5-560Q
p5-595
p5-575 p5-590
Rack / Entry
p5-550 Tower / Entry
550Q p5-520
520Q p5-550
550Q
p5-510 p5-520
510Q p5-505 520Q
505Q
POWER5+
Figure 2-3. IBM System p5 AN111.0
Notes:
IBM System p5 servers are IBM's previous generation of products for AIX and Linux
clients. Subsequently replaced by the new IBM Power Systems, System p5 models and
resources remain available for AIX and Linux clients.
IBM System p5 are using POWER5+ processors running at 1.9 GHz, 2.1 GHz, or 2.2
GHz depending on the System model. Q models (for example, p5-510Q p5-520Q, and
so on) are using IBMs latest Quad-Core Module (QCM) technology with four 1.65 GHz
or 1.8 GHz POWER5+ processor cores. For more informations refer to the System p
facts and features:

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement The next visual will give an overview of the POWER6

V5.3
Instructor Guide
Uempty
IBM POWER6 processor-based systems

IBM Power Systems
IBM System p and IBM System i unification.

Same hardware platform
Single product set
Servers, adapters and I/O components
Support AIX V5.3, AIX V6.1, IBM i 5.4, IBM i 6.1 and Linux (RHEL4, RHEL5,
SLES 9 and SLES10)
All support PowerVM Editions
Entry systems: 1- to 8-way processor systems

Examples: Power 520, Power 550, BladeCenter JS12, BladeCenter JS22
Mid-range systems: 2- to 16-way processor systems

Example: Power 570
High end systems: 8- to 64-way processor systems

Examples: Power 575, Power 595
g
Scalin
- to 6 4 -w a y
1
s
system
Figure 2-4. IBM POWER6 processor-based systems AN111.0
Notes:
BM Power Systems: A single, energy efficient and easy-to-deploy platform for all of
your UNIX, Linux, and IBM i applications.
Again with POWER6 we are breaking down barriers and pushing the envelope of where
the technology can go. POWER6 processors most visible feature is the speed with
ultra-high frequencies - breaking the 5 GHz barrier. Power Systems are shipped with
3.5 GHz, 4.2 GHz, 4.7 GHz, and 5.0 GHz dual-core chips.
One of the keys to our performance has always been balanced system design -- and
with POWER 6 we have doubled the memory bandwidth and 3X the SMP and I/O
bandwidth.
But POWER6 isn't just about performance. Substantial focus has been put on reliability
and availability as well. System z key reliability features have been brought to System p
such as the Processor Instruction Retry or the Storage keys
No more System i or System p, only Power Systems where you can select to run AIX
Linux or IBM i. All system models support all three operating systems.

Instructor Guide
All Power Systems servers can utilize logical partitioning (LPAR) technology
implemented via System p virtualization technologies, the operating system (OS), and a
hardware management console or IVM. Dynamic LPAR allows clients to dynamically
allocate many system resources to application partitions without rebooting.
PowerVM Editions
In addition to the base virtualization that is standard on every System p server, three
optional virtualization features are available on the server: PowerVM Express Edition,
PowerVM Standard Edition (formerly Advanced POWER Virtualization (APV)
Standard), and PowerVM Enterprise Edition (formerly APV Enterprise). These are
managed using built-in Integrated Virtualization Manager (IVM) software or optionally
through use of a hardware management console.
POWER6 integrated hardware accelerators
Introduced with the POWER6 processor design is hardware decimal floating-point
support improving the performance of the basic mathematical calculations of financial
transactions that occur regularly on todays business computers. This will improve the
performance of decimal calculations used by financial and retail companies up to seven
times whats done in software today. The POWER6 processor also includes an AltiVec
SIMD accelerator, which helps to improve the performance of multi-media and 3D
modeling algorithms used primarily in High performance computing.
POWER6 EnergyScale Technology
The IBM POWER6 architecture with EnergyScale technology provides features such as
power trending, power-saving, capping of maximum power, and thermal measurement.
These features are enabled using IBM Systems Director Active Energy Manager
software within the IBM Director console. They measure energy use and direct policies
toward the energy-efficient operation of the server, while the underlying hardware
automatically adjusts to deliver the desired operating solution. The POWER6 chip is
also designed to conserve power and reduce heat generated by the server. A feature
called nap mode enables processor clocks to be dynamically turned off when there is
no useful work to be done and turned back on when there are instructions to be
executed
Other features
Other features introduced with POWER6 processor-based technology include an
Integrated Virtual Ethernet adapter standard with every system, the Processor
Instruction Retry feature automatically monitoring the POWER6 processor and, if
needed, restarting the processor workload without disruption to the application, and a
new HMC (Hardware Management Console) graphical user interface offering enhanced
systems control.

V5.3
Instructor Guide
Uempty POWER6 processor characteristics

Ultra-high frequency dual-core chip: Up to 5.0 GHz
7-way superscalar, 2-way SMT core
Up to five instr. for one thread; up to two for other
Nine execution units
2LS, 2FP, 2FX, 1VMX, 1DP
790M transistors, 341 mm2 die
Up to 64-core SMP systems
2x4 MB on-chip L2 point of coherency
On-chip L3 directory and controller
Two memory controllers on-chip
CMOS 65nm lithography, SOI Cu
High-speed elastic bus interface at 2:1 freq
Full error checking and recovery
Dynamic power saving
Advanced Clock gating

Instructor Guide
Instructor notes:
Purpose
Details

V5.3
Instructor Guide
Uempty
IBM Power Systems: The new Power equation

IBM Power Systems
System i
i515 i525 i550 i570 i595
IBM BladeCenter IBM Power Servers

BladeCenter BladeCenter Power 520 Power 550 Power 570 Power 575 Power 595
JS22 JS12 Express Express 3.5 - 4.2 - 4.7 4.7 GHz 4.2 -5.0 GHz
Express Express 4.2 GHz 3.5 - 4.2 GHz GHz
3.8 - 4.0 GHz 3.8 - 4.0 GHz
System p
p5-520 p5-550 p5-570 p5-575 p5-595
Figure 2-5. IBM Power Systems: The new Power equation AN111.0
Notes:
Power System unification

One system for the future. The New Power Equation is more than just innovation of new
features on System i and System p platforms. There is more exciting news. Two
decades ago, IBM launched the AS/400 as a unification of two successful midrange
platforms and through numerous name changes, it has remained the central business
processing platform for many customers. Today, these platforms are combined into a
single line of systems: Power servers.
IBM System i and IBM System p can be upgraded to Power Systems.
Power System family characteristics

Refer to the following table for some characteristics of the Power System family. For
more information refer to the Facts & Features document available here:

Instructor Guide
Table 1: IBM Power Systems

Maximum number
System memory
of PCI-X slots
Models Processors (standard-Maximu
(without additional
m)
I/O drawer)
1, 2, or 4
2 PCI-X (64-bit), 3
IBM Power 520 processors per 1 GB - 64 GB
PCIe 8x
system
2, 4, 6, or 8
2 PCI-X (64-bit), 3
PCIe 8x
system
2, 4, 8, 12, or 16
8 PCI-X (64-bit);
16 PCIe 8x
system
32 processors per
IBM Power 575 32 GB - 256 GB 4 PCIe
system
8 - 64 processors 16 GB - 4 TB (5.0
IBM Power 595 20 (64bit)
per system GHz processor)
IBM BladeCenter 4 processors per
4 GB - 32 GB -
JS22 blade
IBM BladeCenter 2 processors per
2 GB - 64 GB -
JS12 blade
System p5 upgrade
IBM is committed to enhancing its customers investments in the IBM System p product
line. Based on this commitment, IBM provides an upgrade path from the System p
server to Power Systems.
Example: IBM System p5-570 server to POWER6 processor-based server upgrade
Two upgrade packages are available for POWER5+ to POWER6 upgrade consisting of
CPU card replacement and also other parts.
The POWER6 processor 5622 includes a 4.2 GHz chip, an 0/2 core POWER6, and 12
DDR-2 memory slots.
The POWER6 5621 upgrade is similar but includes eight DDR-2 memory slots. (Driver
for old DDR2 DIMMs is embedded on the board.)
DDR-1 memory won't migrate successfully; although DDR-2 memory will migrate for
5621 upgrades.
You can't mix 5621s and 5622s in a CEC enclosure.
The upgrade using 5622 is comprehensive because non-migratory parts include PCs,
some memory, the chassis, DASD and media, power regulators and PSUs.

V5.3
Instructor Guide
Uempty The 5621 processor migration is simple, the PSUs are good to go, as the DDR2
memory, the Power Backplane 7870, the operating panel and the PCI adaptors. The
P570 has 2 GX slots, but no integrated RIO ports, while it only supports SAS disks
internally.
It might be necessary to order for a RIO adapter to connect previous D20 drawers.
You must take in account that previous SCSI internal disks are not compatible with the
POWER6 CEC. So you might need to define a process to migrate from internal SCSI to
SAS drives.

Instructor Guide
Instructor notes:
Purpose
Details Currently, the same hardware is used in both System i and System p heritage
environments; but, for the time being, in the lower part of the product line there are still
separate machine types and designations for models intended for traditional System p
environments and i environments and differences in these models and environments.
Although p-oriented models support more processors (four on 520 and eight on 550),
they cannot currently run the i operating system. The i-oriented models support fewer
processors (two on 520; four on 550), but can run the i operating system as well as AIX and
Linux (as well as providing virtualization services to IBM Intel-based environments via
iSCSI).
Transition statement The next slide shows the IBM Power 550 features.

V5.3
Instructor Guide
Uempty
POWER6 system example: IBM Power 550

IBM Power Systems
p550 Rack & Tower

Architecture 2, 4, 6, or 8 cores @ 3.5 & 4.2 GHz
L3 Cache: 32MB per chip
DDR2 memory Up to 256GB (buffered )
Internal SAS disks 6 DASD ( 3.5) (Can be split)
PCIe: 3 Slots
Expansion PCI-X 266: 2 Slots
GX Bus: 2 Slots
Shared with PCIe 2 slots
Integrated SAS / SATA Yes Optional: RAID support
Integrated ports 3 USB, 2 Serial, 2 HMC

Optional: SAS port
Integrated Virtual Dual port 10/100/1000 Ethernet
Ethernet Optional: Quad 1Gbt or dual 10Gbt
Media bays 1 Slim-line DVD

1 Half High Tape
Remote IO drawers Yes / Max: 8

GX Bus connection: RIO2 / InfiniBand
Dynamic LPAR Up to 80 partitions
Redundant power Optional
Redundant cooling Yes
Figure 2-6. POWER6 system example: IBM Power 550 AN111.0
Notes:
The 550 Express is designed to continue the tradition of its predecessors, the IBM
POWER5+ processor-based System p5 550 and 550Q Express and System p5 560Q
midrange servers. It is available in either a 19-inch rack-mount or deskside packages
supporting up to four POWER6 processor cards each with two 64-bit 3.5 GHz or 4.2 GHz
processor cores. Each card has 8 MB of L2 cache, 32 MB of L3 cache and from 1 GB to 64
GB of DDR2 memory. A maximum configuration may have eight processor cores, 128 MB
of L3 cache and 256 GB of memory.
SAS Drives
Each system features one SAS DASD controller with six hot-swappable 3.5-inch SAS
disk bays and one hot-plug, slim-line media bay, and tape bay. There are two DASD
backplane options. Only SAS DASD hard disks are supported internally. SCSI DASD
hard drives can only be attached when located in a remote I/O drawer.

Instructor Guide
I/O slots
The 550 Express has five PCI slots (three PCIe 8x and two 64-bit DDR 2.0 PCI-X). A
maximum of five hot-swappable slots:
Two PCIe x8 slots, short card length:
One PCIe x8 slot, full card length
Two PCIX DDR slots, full card length
One GX+ slot (shares same space as PCIe x8 slot 2)
One GX+ slot (shares same space as PCIe x8 slot 1)
Two media bays (minimum configuration requires a DVD-ROM or DVD-RAM):
One slim bay for a DVD-ROM or DVD-RAM
One half-high bay for a tape drive (optional)
Each system includes the following native ports:
Choice of integrated (IVE) I/O options:
2-port 1 Gigabit Integrated Virtual Ethernet (single controller).
Three USB ports.
Two system (serial) ports. These ports are not active when an HMC is attached.
Two HMC ports.
Two remote I/O (RIO-2) ports
Two SPCN ports.
In addition, each system features one internal SAS controller, redundant
hot-swappable cooling fans, optional redundant power supplies, and
EnergyScale technology.
Integrated Virtual Ethernet Adapter
The IVE is a physical Ethernet adapter that is connected directly to the GX+ bus instead
of being connected to a PCIe or PCI-X bus, either as an optional or integrated PCI
adapter. This provides IVE high throughput, and low latency.
The Integrated Virtual Ethernet adapter is a 550 standard feature that is ordered with
different options. The IVE comes from a general market requirements for improved
performance and virtualization for Ethernet. It offers:
A single controller offering either 2- or 4- port configurations of one of the following:
Two 10 Gbps Ethernet ports
Four 1 Gbps ports
Two 1 Gbps integrated ports

V5.3
Instructor Guide

Purpose
Details
Transition statement Lets see the IBM Power 550 I/O slots.

Instructor Guide
Power System 550 I/O slots: Example

IBM Power Systems
T slots are integrated

Storage controller: SAS Raid Controller (internal SAS disks) and SATA drive
Universal Serial Bus: USB devices
C slots are PCI-X and PCI Express slots

I/O drawers, if connected, show up with their own unit type and serial number.
Figure 2-7. Power System 550 I/O slots: Example AN111.0
Notes:
When configuring partitions, you assign I/O slots to a specific partition. Systems have T
slots for integrated devices and C slots which represent PCI-X slots or PCI-Express
slots. When configuring partitions on a Power 550, the following slots correspond to the
following devices:
Integrated T slots:
Assign Slot T3 to allocate the USB ports.
Assign Slot T9 to allocate the internal SAS disks. Allocating this device to a
partition will include all internal disks (up to six SAS drives). Also the DVD ROM
is a SATA DVD-ROM Drive managed by the Controller SATA Protocol having the
SAS controller as parent. This means that the DVD drive cannot be moved to
another logical partition without the SAS drives devices.
Physical slots C1, C2 and C3 are PCI-Express slots. slots C4 and C5 are PCI-X slots.

V5.3
Instructor Guide
Uempty
SAS split backplane feature
The split backplane feature allows three SAS disk bays to be assigned to one partition
while the other three bays can be assigned to a second partition. This feature is
supported on Power Systems 520, 550 and 570.
For the Power System 550, the cable feature 3669 enables splitting the DASD
backplane, allocating a SAS controller for each half of the internal disks. The split
backplane capability is available with feature 8346 (back plane) or 8345 (and requires
one internal cable feature 3669 and one external cable feature 3679, which connects to
SAS controllers features 5900, 5912, or 5902, to drive half of the internal SAS disks).
DASD backplanes
The feature code 8341, 6 x 3.5-inch DASD backplane with no external SAS port, is the
default disk backplane option. It provides a single path from the SAS controller to each
internal disk drive. The feature code 8345, 6 x 3.5-inch DASD backplane with an
external SAS port, is an optional backplane providing dual paths from the SAS
controller to each internal disk drive via SAS expanders.
The IVE adapter itself cannot be assigned to a logical partition unlike most other types
of I/O devices. You can never assign the IVE (or HEA - Host Ethernet adapter) itself to a
logical partition. Instead, multiple logical partitions can connect directly to the HEA and
use the HEA resources. Thats why you cannot see the IVE in the I/O slots list. There is
a specific option in the HMC menus for managing IVE.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Lets see some I/O drawers options.

V5.3
Instructor Guide
Uempty
I/O drawer options

IBM Power Systems
7314 Model G30 for POWER6 system configurations (POWER

520, POWER 550, POWER 570)
6 PCI-X slots
7311 Model D20 (System p5-520, 520Q, 550, 550Q, 570, POWER
System 520, 550, 570)
12 disks and 7 PCI-X slots
7311 Model D11 (System p5 570)

6 PCI-X slots
Internal drawers for System p5 575, 590, 595 and POWER system
575, 595
Feature 5791 for 20 PCI-X slots and 16 disks
See the technical overview redpapers and http://www.ibm.com

for more information.
Figure 2-8. I/O drawer options AN111.0
Notes:
I/O drawers
For System p5, the I/O drawers listed are connected to the system planar using a RIO-2
loop configuration. They are connected to the systems using the Remote I/O (RIO)
ports on the systems. The PCI-X slots and disks in these drawers can be accessed
directly by the system processors. All these drawer types connected to the System p5
CEC use a RIO-2 adapter
For Power Systems, the supported I/O drawers can still be connected using RIO-2 I/O
hub except for the new G30 drawer that requires a GX 12 channel adapter
The 7314 Model G30 I/O drawer offers a modular growth path for selected POWER6
systems. It attaches to the host system using IBMs 12X Channel Interface technology.
The Dual-Port 12X Channel Attach Adapters (FC 5616) available for the Model G30
allow higher-speed data transfer rates for remote I/O drawers. A single 12X Channel I/O
loop can support up to four G30 I/O drawers.

Instructor Guide
New G30 drawer

The new G30 drawer offers better performance for I/O subsystem connection than the
D20. The G30 connection to the CEC uses a dual channel InfiniBand interface.
It has higher bandwidth to get the maximum throughput and to scale with the POWER6
CEC performance.
Modular growth is allowed for increasing I/O requirements, and up to four G30
expansion units can be attached in a loop using the GX dual port 12X channel attach
adapter.
Two loops for each CEC are supported.
No DASD slots are available in the G30 I/O drawer.
Other I/O options are available, which are connected through a fibre channel controller;
these devices are seen as external devices to the system.
For additional information about storage solutions, go to the IBM System Storage and
TotalStorage Web site (http://www.ibm.com/servers/storage).

V5.3
Instructor Guide

Purpose Describe the I/O drawer options for System p5 and Power Systems.
Details Describe each of the I/O drawers briefly and point the students to the
documentation for more details.
Point out the new G30 I/O drawer available and only supported by POWER6
based-processor systems
Transition statement Now, lets talk about location codes.

Instructor Guide
Location codes
IBM Power Systems
Types of location codes

Physical location codes refer to a specific component
A physical location code is a sequence of location labels that, when
followed in order, leads to the resource
Operating system location codes also refer to components and use a

different convention
Example hdisk0: 03-08-00-3,0 SCSI disk drive
Example hdisk0: 00-08-00 SAS disk drive
Virtual devices have codes as if they were on another

physical planar
Figure 2-9. Location codes AN111.0
Notes:
Physical location codes

A physical location code is a sequence of location labels that, when followed in order,
lead to the location. On a given system, a resource has only one physical location code.
It is necessary to interpret physical location codes in a variety of situations. Service
error logs, partition configuration screens, and inventory reports all report location
codes.
Operating system location codes

Operating systems also refer to devices by their own location codes. It is often
important to translate between the operating system location code and the physical
location code; for example, if you want to determine which physical disk to set as the
boot disk.

V5.3
Instructor Guide
Uempty Virtual cards and devices

Virtual card location codes are formed as though there were a virtual planar with card
slots.

Instructor Guide
Instructor notes:
Purpose Compare the two types of location codes.
Details This pages focuses on the definition of the two types of location codes.
Transition statement Lets look at an example physical location code.

V5.3
Instructor Guide
Uempty
Physical location code convention

IBM Power Systems
Physical location code format

Utttt.mmm.sssssss-additional device information
Unit type . Model . Serial number
Example physical location code

U78A0.001.DNWGCP5-P1-C1-T1
P1 specifies Planar 1
C1 specifies Card slot 1
After a card slot, a T followed by a number specifies a particular port
If no card slot, a T followed by a number specifies an integrated slot
An L followed by a number specifies a logical path identifier specific to
the protocol being used (for example, SCSI identifiers)
SAS adapter example

U78A0.001.DNWGCP5-P1-T9 PCI-X266 Planar 3Gb SAS adapter
Figure 2-10. Physical location code convention AN111.0
Notes:
Physical location code format

Servers (system unit and expansion units) use physical location codes to provide
mapping of replaceable units. Location codes are produced by the server's firmware,
which structures them so that they can be broken down to identify specific parts in a
system.
Physical location codes are formed by concatenating one or more location labels
together. Location labels start at the largest or most general resource (the unit) and
proceed to the most specific in order of containment. The location labels are separated
by dashes (-). Location codes are no more than 79 characters in length.
Drawers for which the system can obtain the machine type, model, and serial number
will have a unit location code composed of the machine type and serial number.

Instructor Guide
Unit numbers
These are the unit numbers that you will see in the location codes for the components in
the system drawer or the central electronics complex (CEC). For PCI-X slots in
attached I/O drawers, the unit number of the drawer will be used.
Example unit numbers:
Unit System Model
U787E System p5-510
U787A System p5-520
U787B System p5-550
U789 System p5-570
U787D System p5-575
U787C System p5-590 and System p5-595
U78A0 Power System 550
U789D Power System 570

V5.3
Instructor Guide

Purpose Describe the format of the POWER6 physical location code.
Details Describe each section of the physical location code. Show how it specifies from
the largest component to the most specific component as you move from left to right.
Transition statement Lets look at some AIX commands that display location codes.

Instructor Guide
AIX location codes (1 of 2)

IBM Power Systems
Use lscfg to see physical location codes

For hdisk0 (SCSI disk drive Drawer D20))
lscfg | grep hdisk0
hdisk0 U7311.D20.650441C-P1-C04-T2-L8-L0
For Ethernet adapter
lscfg | grep en
ent0 U78A0.001.DNWGCP5-P1-C4-T1
Use lsdev to see AIX location code

For SCSI disk drive
lsdev -Cc disk
hdisk0 Available 03-08-01-8,0 16 Bit LVD SCSI Disk
hdisk1 Available 05-08-01-9,0 16 Bit LVD SCSI Disk
For ethernet adapter

lsdev | grep ent
ent0 Available 01-08
Figure 2-11. AIX location codes (1 of 2) AN111.0
Notes:
Introduction
The AIX commands in the visual show how you can view both physical location codes
and the correlating AIX codes.

V5.3
Instructor Guide

Purpose Describe the AIX 6 commands that can be used to view both physical location
codes and the AIX 6 location codes.
Details Review each command, and show how each either shows the physical or AIX 6
location code. Students will have a chance to try various commands in the hands-on
exercise.
Transition statement Lets look at the SAS drive location codes.

Instructor Guide
AIX location codes (2 of 2)

IBM Power Systems
SAS disk drive physical location codes

For SAS disks devices
lscfg | grep hdisk
hdisk0 U78A0.001.DNWGCP5-P2-D5
hdisk1 U78A0.001.DNWGCP5-P2-D4
Use lsdev to see AIX SAS drive location code
lsdev -Cc disk

hdisk0 Available 00-08-00 SAS Disk drive
hdisk1 Available 00-08-00 SAS Disk Drive
Figure 2-12. AIX location codes (2 of 2) AN111.0
Notes:
Introduction
The AIX 6 commands in the visual show how you can view both physical location codes
and the correlating AIX 6 codes for the SAS drives on a Power System.

V5.3
Instructor Guide

Purpose
Details
Transition statement You will have a chance to try out these commands in the
exercise. Next, lets talk about the service processor functions.

Instructor Guide
Service processor
IBM Power Systems
Functions of the service processor

System initialization
Connection to the HMC
Web-based Advanced System Management Interface (ASMI) for setting system
flags
Hardware error detection
Connects to HMC over network
Server processors IP address set by HMC DHCP server
This can be changed through ASM interface
To find IP address of a service processor connected to an
HMC, use one of these HMC commands:
$ lssyscfg -r sys -F name,ipaddr,state
Server-name,192.168.255.254,Operating
$ lssysconn r all
resource_type=sys,type_model_serial_num=8204-E8A*65BF7E1,
sp=primary,sp_phys_loc=U78A0.001.DNWGD21-P1,
ipaddr=192.168.255.254,alt_ipaddr=unavailable,state=Connected
Figure 2-13. Service processor AN111.0
Notes:
Service processor
The service processor performs many vital Reliability, Availability, and Serviceability
(RAS) functions.
The service processor is an embedded controller that is based on a PowerPC 405GP
processor running the service processor internal operating system, which contains
programs and device drivers.
Service processor functions

The service processor gives the means to diagnose, check status, and sense
operational conditions of a remote system, even when the main processor is
inoperable. The service processor enables firmware and operating system surveillance,
several remote power controls, environmental monitoring (only critical errors are
supported under Linux), reset, and boot features, remote maintenance and diagnostic

V5.3
Instructor Guide
Uempty activities, including console mirroring. The service processor can place calls to report
surveillance failures, critical environmental faults, and critical processing faults.
SPCN ports
Two SPCN ports control the power of the attached I/O subsystem. The SPCN control
software is run on the service processor along with the service processor software.
Serial port access to the service processor

When an HMC is not connected to the service processor, two serial ports provide
terminal access to the service processor. Serial port 1 will give access to the Advanced
System Management Interface (ASMI) and port 2 will receive only boot sequence
information. When the HMC is connected, the serial ports are disabled.
Discovering managed system information with HMC commands

The two HMC commands shown in the visual will display which managed systems are
connected to the HMC. The lssyscfg command uses the -F (filter) option to show only
three pertinent items because the command output is extensive. The next unit in this
course will show you how to connect to the HMC to run HMC commands.

Instructor Guide
Instructor notes:
Purpose Describe the functions of the service processor.
Details With POWER5 and POWER6, the service processor is directly connected to the
network and is even running a Web server, which allows access to the ASMI.
The instructions on how to use HMC commands is covered in the next unit.
Transition statement Lets talk more about the ASMI.

V5.3
Instructor Guide
Uempty
Advanced System Management Interface (1 of 2)

IBM Power Systems
Or connect with ASMI using a Web browser:

https://<IP addr of service processor>
Figure 2-14. Advanced System Management Interface (1 of 2) AN111.0
Notes:
Introduction
With the system in power standby mode, or with an operating system in control of the
machine, or controlling the related partition, the service processor is working and
checking the system for errors, ensuring the connection to the HMC for manageability
purposes. With the system up and running, the service processor provides the
possibility to view and change the Power-On settings using the Advanced System
Management Interface. Also, the surveillance function of the service processor is
monitoring the operating system to check that it is still running and has not stalled.
Accessing ASMI
If the service processor is connected to an open network, you can access the Advanced
System Management Interface using a Web browser connection to the IP address of
the service processor. You must log in with the general or admin ID and password.

Instructor Guide
You can also access the ASMI from the physical HMC or from a browser through an
HTTPS connection to the HMC IP address. Select the server name in the Working area,
then from the Tasks menu, select Operations > Launch Advanced System
Management (ASM). Then in the window, choose the Service processor IP address to
connect and click OK. (If multiple service processors are detected, the primary and
secondary connections will be noted.)
Functions that can be accessed include:
Set flags that affect the auto-power restart
View information about the system, such as the error log and vital product data
(VPD)
Set up the network environment
Control system power
Start and shut down the system
Set the system boot speed (fast boot skips diagnostic tests and runs shorter
memory tests)
Set the firmware boot side for the next boot (you might have installed a firmware
update on the Temporary or Permanent side)
Set system operating mode to manual or normal (manual allows overrides of the
automatic power-on options)
If no HMC is connected, set the operating system partition boot mode
Set to boot system to server firmware

V5.3
Instructor Guide

Purpose Describe how to access the ASMI application running on the service
processor.
Details Describe how to access and log in to the ASMI application.
The student notes list the functions that can be performed in the ASMI. You cannot manage
partitions from the ASMI.
Transition statement Lets look at one example screen in the ASMI.

Instructor Guide
Advanced System Management Interface (2 of 2)

IBM Power Systems
Figure 2-15. Advanced System Management Interface (2 of 2) AN111.0
Notes:
This is the welcome menu of the Advanced System Management interface after login.
You must log in with the general or admin ID and password.

V5.3
Instructor Guide

Purpose
Details

Instructor Guide
ASMI example
IBM Power Systems
Figure 2-16. ASMI example AN111.0
Notes:
Introduction
The ASMI application is easy to navigate. The visual shows one example screen of the
network configuration for one of the Ethernet ports connected to the service processor.
All menus
If you were to expand all menus, you would see a list of options like this one. The exact
list that is available will depend on the managed system firmware version.
Power/Restart Control
Power On/Off System
Auto Power Restart
Immediate Power Off
System Reboot
Wake On LAN

V5.3
Instructor Guide
Uempty System Service Aids

Error/Event Logs
Serial Port Snoop
System Dump
Service Processor Dump
Partition Dump
Serial Port Setup
Modem Configuration
Call-Home/Call-In Setup
Call-Home Test
Reset Service Processor
Factory ConfigurationFactory Configuration
Deconfigured Resources
System Information
Vital Product Data
Power Control Network Trace
Previous Boot Progress Indicator
Progress Indicator History
Real-time Progress Indicator
System Configuration
System Name
Processing Unit Identifier
Configure I/O Enclosures
Time Of Day
Firmware Update Policy
PCI Error Injection Policy
Interposer Plug Count
I/O Adapter Enlarged Capacity
Hardware Management Consoles
Virtual Ethernet Switches
Hardware Deconfiguration
Deconfiguration Policies
Processor Deconfiguration
Memory Deconfiguration
Processing unit Deconfiguration
Program Vital Product Data
System Brand
System Keywords
System Enclosures
Service Indicators
System Attention Indicator
Enclosure Indicators
Indicators by Location code
Lamp Test

Instructor Guide
Network Services
Network Configuration
Network Access
Performance Setup
Logical Memory Block Size
System Memory Page Setup
On Demand Utilities
CoD Order Information
CoD Activation
CoD Recovery
CoD Command
CoD Processor Information
CoD Memory Information
CoD VET Information
CoD Capability Settings
Concurrent Maintenance
Control Panel
IDE Device Control
Login Profile
Change Password
Retrieve Login Audits
Change Default Language
Update Installed Languages
User Access Policy

V5.3
Instructor Guide

Purpose Show an example ASMI screen.
Details Describe that you navigate in the ASMI much like you would a Web page with
the links in a navigation bar on the left. The example in the visual shows the network
configuration for the Ethernet port for the service processor itself.
The list of available menu options, as shown in the student notes, might be different
depending on the level of firmware on the managed system.
The list of menu options is just to show the range of tasks that can be completed with
ASMI. You should not describe them line by line. Explain that many of the ASMI tasks are
there for systems that do not have an HMC to manage them.
Transition statement Next is a checkpoint.

Instructor Guide
Checkpoint (1 of 2)
IBM Power Systems
1. What is the maximum number of partitions per processor

that can be created on an IBM Power System 570 with four
activated processors if the PowerVM Standard or Enterprise
Edition feature is ordered?
a. 40
b. 20
c. 10
2. Which are features of the p5-550 system?

a. 1-, 2-, or 4-way processor cards
b. Supports up to eight I/O drawers
c. Must have an HMC (or IVM) for LPAR management
d. Can be cabled with other Power 550 to create 8-, 12-, or 16-way
SMP system
Notes:

V5.3
Instructor Guide

Purpose Review the concepts in this unit by answering Checkpoint questions.
Details This is page one of two pages of questions. Give the students about 2 minutes
to complete, then review the answers.
IBM Power Systems
1. What is the maximum number of partitions per processor that

can be created on an IBM Power System 570 with four
a. 40
b. 20
c. 10
2. Which are features of the Power 550 system?

d. Can be cabled with other Power 550s to create 8-, 12-, or 16-way SMP
system
Transition statement There is a second page of Checkpoint questions.

Instructor Guide
Checkpoint (2 of 2)
IBM Power Systems
3. List four major components you will find in the IBM Power Systems 520,
550, 570 system drawers.
4. How many partitions can a managed system support if the PowerVM

standard Edition feature has not been ordered?
5. When viewing I/O slots within the HMC applications, T slots are what kind
of slots?
6. When viewing physical location codes, what does the -T signify at the end
of a location code (if it is there)?
7. List at least three functions of the Service Processor.
Notes:

V5.3
Instructor Guide

Purpose Review the concepts in this unit by answering Checkpoint questions.
Details
IBM Power Systems
550, and 570 system drawers.
Processors, memory, PCI-X slots, disks
Standard Edition feature has not been ordered?
The maximum number of partitions is the same as activated physical
processors.
of slots?
T slots are integrated slots on the system planar and do not
correlate to the PCI-X or PCI Express slots on the system drawer.
At the end of a location code, a T followed by a number indicates a
specific port on an adapter.
7. List at least three functions of the Flexible Service Processor.
Provides system initialization, connects to the HMC, runs ASMI for
setting system flags, includes hardware error detection.
Transition statement Next, we will perform a hands-on exercise to reinforce the
concepts in this unit.

Instructor Guide
Exercise
IBM Power Systems
Unit
exerc
ise
Notes:

V5.3
Instructor Guide


Instructor Guide
Unit summary
IBM Power Systems
Identify basic architecture elements and hardware

components of IBM POWER5+ and POWER6 processor-
based systems
Notes:
IBM POWER5 and POWER6 processor-based systems have a wide range of
configuration options:
- Processors, memory, I/O, partitions
There are both physical and AIX location codes.
The service processor provides system initialization and hardware error detection
functions, and the connection to the HMC.
The ASM Interface tool can be used to alter the service processor configuration.

V5.3
Instructor Guide

Purpose Summarize what the students should have learned in this unit.
Details Answer any questions from the exercise before moving on to unit 3.
1) To what component does this location code refer?
Drawerlocationcode-P1-C1-T1 (where Drawerlocationcode represents any drawer
location code).
Answer: This is the first port on the adapter in PCI-X slot 1.
2) What are some commands that can be used to view location codes (physical or
AIX 6)?
Answer: lsdev and lscfg
2) How can you access the ASMI that runs on the service processor?
Answer: You can use a Web browser directly to the service processor or launch it from the
HMC Task Launch Advanced System Management (ASM).
Transition statement The next unit covers the features and configuration of the HMC.

Instructor Guide

V5.3
Instructor Guide
Uempty Unit 3. Hardware Management Console
Estimated time
01:30

This unit describes functions and configuration options for the
Hardware Management Console (HMC).

List the LPAR-related functions of the HMC
Describe how to connect the HMC to the managed system
Describe the new HMC version 7 Web-based management
console and the Web user interface (WUI) structure
Use the Guided Setup wizard to set configuration options
Add a managed system to the HMC application
Reboot the HMC
Configure the HMC network parameters
Create HMC users
Configure and assign task roles and managed resource roles
Configure HMC remote access options
Enable and disable remote virtual console support
Log in to the HMC command line and use HMC commands
Describe security options for HMC communication

Accountability:
Checkpoint
Machine exercises
Copyright IBM Corp. 2009 Unit 3. Hardware Management Console 3-1

Instructor Guide
References

V5.3
Instructor Guide
Uempty
Unit objectives
IBM Power Systems

Describe the new HMC V7 Web-based management console and
Web user interface (WUI) structure
Reboot the HMC
Create HMC users
Notes:
Introduction
You should be able to describe the HMCs functions and features and be able to
configure users and network options by the end of this unit.
The unit is separated into two topics. The first covers the HMC and its configuration.
The second covers creating HMC users, how to access the HMC remotely, and the
security issues associated with remote access.

Instructor Guide
Instructor notes:
of the unit.
Explain that there are two topics in this unit.
The hands-on exercise is also separated into two topics. The instructor can choose to do
the topic exercises directly after each topic or wait until the very end of the unit.
Transition statement Lets look at what is in Topic 1.

V5.3
Instructor Guide
Uempty 3.1. HMC configuration
Instructor topic introduction

What students will do The students will learn about the features of the HMC and how
to configure a new HMC, connect it to a managed system, and access the applications.
How students will do it The lecture materials, the Lets Review questions, and the
hands-on exercise will enable the students to meet the topics objectives.
What students will learn The students will learn how to configure a new HMC and
connect it to a managed system.
How this will help students on their job Understanding the features of the HMC and
how it communicates with the managed system is one of the most important skills an LPAR
system administrator must have.

Instructor Guide
Topic 1 objectives
IBM Power Systems
After completing this topic, you should be able to:

Describe the new HMC V7 Web-based management console
and Web User Interface (WUI) structure
Reboot the HMC
Figure 3-2. Topic 1 objectives AN111.0
Notes:
Introduction
The first topic in this unit covers the features of the HMC version 7 with the Web user
interface structure and how to configure a new HMC out of the box.

V5.3
Instructor Guide

Purpose Review the objectives for this topic.
of the topic.
Transition statement We will start with an overview of the HMC.

Instructor Guide

IBM Power Systems
HMC is a PC-based console used in the configuration and

management of partitions
Runs custom Linux and Java application
Is remotely accessible:
Command line and browser-based graphical user interfaces
Can be set up for redundancy
Supports multiple managed systems. Up to 48 entry and mid-range and 32 high-
end servers
It provides:
LPAR configuration and operation management
Virtual console windows for partitions
Capacity on Demand (CoD) management
Service tools Rack-mount
7310-CRx
Desktop
7342/7310 - C0x
Figure 3-3. Hardware Management Console AN111.0
Notes:
Introduction
The HMC is a PC-based console that is available in a deskside or a rack-mount model.
The user can only access the management application and no additional applications
can be installed. A second HMC can be connected to a single managed system for
redundancy. Multiple managed systems can be managed by a single HMC.
The Hardware Management Console is a dedicated system that provides a graphical
and command-line user interface for the configuration and management of logical
partitions on POWER processor-based servers. The HMC is packaged in a customized
Intel-based PC, running Linux with a Java-based management application. You cannot
load any other applications onto the HMC.
A managed system is what we call the POWER processor-based system running one
or more LPARs that the HMC manages.

V5.3
Instructor Guide
Uempty The HMC can support up to 48 managed systems as of Version 6 and version 7 of the
HMC software. The actual (May 2008) HMC version is V7 R3.3.0.
The HMC is available as either a deskside or rackmount model. Visit www.ibm.com for
information on the latest HMC models.
Check the IBM HMC support Web site for the latest information about the HMC
hardware and software:
System will continue to work if HMC fails

The managed system continues to operate in the absence of an HMC by using partition
configuration information stored in NVRAM. Individual partitions can be rebooted using
a shut down command in the partitions operating system. The managed system can be
powered off and on, and will restart predefined partitions automatically if the HMC is not
available. However, performing configuration changes to the partitions requires the
HMC.
HMC functions
The major functions of the HMC are for power on/off of the managed system, for LPAR
creation and operations, for access to the partitions consoles, for Capacity on Demand
resource management, and for serviceable events management and connection to the
IBM service organization.
HMC options
Whether you opt for a desktop or rack-mounted version is a personal choice.
Customers with space in their rack-mounted systems would probably opt for the
rack-mounted version with the slide-away keyboard and display. The following options
are available:
7042-C06 is a desktop HMC.
7042-CR4 is a rack-mounted HMC.

Instructor Guide
Instructor notes:
Purpose Introduce the HMC.
Details This page introduces the HMC. Emphasize that the HMC is an independent
system and is used for the management of POWER processor-based systems.
Transition statement The HMC is connected to the managed system via the servers
service processor.

V5.3
Instructor Guide
Uempty
HMC connection to the server

IBM Power Systems
POWER processor-based
managed system
AIX Linux Unassigned

resources HMC
Partition 1 Partition 2
Hypervisor
Non-Volatile RAM
Service
Processors
processor
Memory Ethernet
LPAR
I/O Slots Partition
allocation
configuration
tables
information is kept
both on HMC(s) and
in servers NVRAM
Figure 3-4. HMC connection to the server AN111.0
Notes:
Introduction
This visual brings together several concepts.
Partitions are independent operating environments and their resources are
managed by the Hypervisor. The Hypervisor manages the resources for the
partitions.
NVRAM is used on the managed system to hold a copy of the partition
configuration so that if the HMC or the network were to fail, the partitions can
continue to run and even reboot if necessary.
Partitions are configured and managed on the HMC which is a separate system.
A copy of the partition configuration data is also kept on the HMC (in addition to
NVRAM).
The HMC is connected to the managed system via an Ethernet connection to the
service processor. The service processor is a separate, independent processor

Instructor Guide
that provides hardware initialization during system load, monitoring of

environmental and error events, and maintenance support.
Two HMCs can be connected to a managed system to provided HMC
redundancy. Either HMC can be used for operations and they remain
synchronized.
An HMC (or pair of HMCs) can managed multiple managed systems.

V5.3
Instructor Guide

Purpose Review the basics of how partitions, the POWER Hypervisor, and the HMC
relate to each other.
Details Describe how the LPAR configuration information is not only kept on the HMC
but also kept on the managed system.
The HMC connects to the managed system via an Ethernet connection to the service
processor. Keep this discussion brief. The HMC and Service Processor are connected via
an Ethernet connection which can be on a public network or a private network.
The notes also mention that two HMCs can manage the same managed system for HMC
redundancy.
Although the HMC code is based on Linux, you cannot just use any Intel PC because the
HMC product media only includes a specific set of device drivers.
Additional information Try to keep the discussion away from the fact that customers
do not have full access to Linux on the HMC. Should a student comment on this, discuss
the stability of Linux on the HMC, and that to assure this stability, IBM decided to make it a
blackbox appliance.
Transition statement This course covers HMC Version 7.

Instructor Guide
HMC version 7
IBM Power Systems
Supports POWER6 and POWER5 processor-based server

systems
Customers can add POWER6 servers to their POWER5 data
center and use their existing HMC hardware (after software
upgrade to V7).
HMC V6.1 or earlier will not manage POWER6 processor-based
servers.
POWER5 systems should have minimum firmware level (SF240-
299).
One HMC V7 can manage a mix of p5 and p6 servers and a mix
of System p and System i machines.
Supports and enables significant new features and

functionality on POWER6
Figure 3-5. HMC version 7 AN111.0
Notes:
HMC versions
POWER5 processor-based servers can be managed by either HMC V5, V6, or V7.
POWER6 processor-based servers can be managed only by HMC V7. HMC V7 can
manage a mix of POWER5 and POWER6 processor-based servers at the same time
and these can be a mix of System p and System i servers.
HMC upgrades
Machine type 7310 (POWER5 HMCs) can be upgraded to run HMC Version 7. There
might be older HMC machines that have been upgraded over the years that might not
be upgradeable to run HMC V7, such as the machine type 7315, which was originally
used to manage POWER4 processor-based servers.
You can find detailed information about HMC versions at:
http://www14.software.ibm.com/webapp/set2/sas/f/hmc/home.html

V5.3
Instructor Guide
Uempty New POWER6 features

Utility Capacity on Demand
Partition availability priority
Dedicated processor sharing
Virtual Shared Processing Pools (VSPP)
Redundant FSP
Dual HMC support
Partition mobility
Power saver mode (moving towards greener computing)

Instructor Guide
Instructor notes:
Purpose Describe some basics about the new HMC V7 and what it will support.
Details
Transition statement What are the steps needed to configure a new HMC?

V5.3
Instructor Guide
Uempty
Configuring a new HMC

IBM Power Systems
Checklist to set a new HMC

Power on the HMC
Do not plug in the managed system yet!
Log in locally as hscroot
Use Guided Setup Wizard to configure HMC.
Date/time, hscroot and root passwords, add users, configure networking,
configure service provider, connection monitoring.
Reboot HMC
Check HMC software version.

Upgrade HMC software if necessary.
Connect network cables to HMC and service processor.
HMC1 port on service processor connects to first Ethernet port on HMC.
Apply power to managed systems.

Set access passwords.
Apply any activation codes.
Figure 3-6. Configuring a new HMC AN111.0
Notes:
Hardware connections
Connect the HMC to the network and Power it on. If you plan to use the HMCs modem
to dial up IBM service to transmit service errors, then connect a phone line to the
modem.
Access the HMC and check the configuration

Power on the HMC by pressing the power button. You will see the Linux initialization
messages and then will be prompted to log in. The default login account and password
for the HMC is hscroot and abc123. Because this is the same on all HMCs, you should
change the password immediately. New passwords must be at least 7 characters.
If this is a new HMC, you will automatically be prompted to run the Guided Setup wizard
which will help you set up a few critical options. You can re-run this wizard at any time,
or access the individual configuration options separately.

Instructor Guide
One configuration check that the Guided Setup wizard does not do is check to be sure
the software version is up to date. How to check the version and upgrade the software
will be covered in a later unit in this course.
Log out, shut down, or restart HMC

If you change the network configuration, you will need to restart the HMC. You can log
out by selecting on the top right of the Web-based user interface the logout option. To
shut down, or restart the HMC, click the HMC Management tab in the navigation area
and then click the Shut Down or Restart option in the HMC management working area,
and pick an option (restart or shutdown) in the window that opens.
Connect the managed system to the HMC

Connect the HMC1 port on the managed system to the first integrated Ethernet port on
the HMC.
For desktop HMC models: Connect the cable to the HMCs integrated Ethernet
port.
For rack-mounted HMC models: Connect the cable to the HMCs bottom
integrated Ethernet port if the two integrated Ethernet ports are stacked
vertically. If the integrated ports are next to each other horizontally, use the port
on the left labeled port 1.
When the HMC networking is fully configured and the Ethernet cable between the HMC
and the managed system is connected, then you can plug in the managed system to
the power source.
The previous instructions assume that you have a direct connection between a
managed system and its HMC. You might have a private network with multiple
managed systems and HMCs connected with a hub or switch. You might also have just
one open network for all of the HMCs, managed systems, and partitions.
For redundant HMCs, the second HMC connects to the HMC2 port on the managed
system. Never connect the same HMC to both ports.
Special note for IBM System p5-590 and p5-595 systems

There are several service processors on the p5-590 and p5-595 systems. There are
two system service processors plus a service processor in each Bulk Power Controller
(BPC). The HMC is connected to the ports on the BPCs.
The first, or primary, HMC is connected to BPCA in the system and expansion rack. The
second HMC is connected to BPCB in the system and expansion rack.

V5.3
Instructor Guide

Purpose Describe how to configure a new HMC.
Details This page gives the big picture of the process to configure a new HMC. All of
these tasks will be covered in this unit or future units.
One of the first tasks is to turn on the HMC and log in. You can do this even before
connecting the Ethernet cable from the HMC to the managed system. At this point you will
be on the physical HMC. Press the power button and wait. After the Linux startup
information, you will be presented with a login screen. When you log in, the Guided Setup
Wizard displays.
The managed system must not be plugged into a power source until the networking on the
HMC is fully configured.
Transition statement Lets look in more detail at the Guided Setup Wizard.

Instructor Guide
Guided Setup Wizard

IBM Power Systems
Guided Setup wizard will display when you start a new HMC for
the first time and log in
You can run it at any time later
Reboot HMC when complete
Figure 3-7. Guided Setup Wizard AN111.0
Notes:
Introduction
This application is an easy way to configure your HMC for the first time. All of the
options available in the wizard can be accessed separately in the HMC applications.
More configuration options are available, which do not appear in the Guided Setup
Wizard.

V5.3
Instructor Guide

Purpose Show the options available in the Guided Setup wizard.
Details Quickly show the options available in the Guided Setup wizard.
The rest of the screenshots in this unit will not be from the Guided Setup wizard, but
instead will show the actual configuration screens for these items through the HMC
applications. Many of the screens in the wizard and in the actual application will be the
same, but there are more options if you use the applications directly.
Transition statement Now, lets look at the HMC pre-login screen.

Instructor Guide
HMC pre-login welcome screen

IBM Power Systems
Connect using the local console or via

https://<hostname or IP address of HMC>
Launch HMC Web

application
Figure 3-8. HMC pre-login welcome screen AN111.0
Notes:
Introduction
This HMC uses a Web-based user interface. This interface uses a tree-style navigation
model providing hierarchical views of system resources and tasks using drill-down and
launch-in-context techniques to enable direct access to hardware resources and task
management capabilities. It provides views of system resources and provides tasks for
system administration.
The Welcome window contains the link to log in to the HMC application, the ability to
view the online help information, and the summarized status information for the HMC.
Pre-login screen
Click the Log on and launch link to get to the login screen. Notice that you can access
online help and see system status before logging in.

V5.3
Instructor Guide

Purpose Describe the contents of the pre-login screen.
Details
Additional information Introduce the different connection type either using the local
console or a web browser for a remote access. Dont spend too much time explaining
remote access as this is detailed in topic 2.
Transition statement Lets look at specifics about logging in.

Instructor Guide
HMC login sessions

IBM Power Systems
Default root login is hscroot w/ default password of abc123

Concept of multiple login sessions per user:
Important reason for creating unique logins for different users
When logging out, choose:
Disconnect and your session ends, but tasks continue running:
You can reconnect to this session later
Log off and your session ends, ending all tasks
Reconnect and choose to continue a session or start a new one.
Default account.
Other accounts can
be created.
Figure 3-9. HMC login sessions AN111.0
Notes:
HMC login sessions

The default administrator login for the HMC is hscroot. You cannot log directly into the
HMC with the Linux root password. Additional accounts can be created and these can
have the same hscroot access to objects and tasks, or a particular account can have a
specific subset of objects and tasks that it can use.
When you log out of the HMC, you use either the Log off option or the Disconnect
option. A disconnect will leave any running tasks running and allow you to reconnect to
that session later. Log off will stop any running tasks and log you out completely.

V5.3
Instructor Guide

Purpose Describe login and logout specifics.
Details Describe the new concept of reconnecting to a running session.
Transition statement The next visual shows the Log off and Disconnect options.

Instructor Guide
Disconnect versus logoff

IBM Power Systems
Logoff
command
Choose Log off

or Disconnect
Figure 3-10. Disconnect versus logoff AN111.0
Notes:
Logging off
Click the Logoff command in the upper right corner of the HMC interface to log off or
disconnect.

V5.3
Instructor Guide

Purpose Show how to logoff or disconnect from the HMC.
Details
Transition statement The next visual shows how to reconnect to a previous session.

Instructor Guide
Reconnecting to login session (1 of 2)

IBM Power Systems
Number of tasks
still running
Reconnect to
the selected
session
Figure 3-11. Reconnecting to login session (1 of 2) AN111.0
Notes:
Create unique users

The reconnect function shows why it is a good idea now to create separate users for the
HMC if there will be multiple people logging into the HMC. If everyone logs in as
hscroot, then when you reconnect, you might reconnect to someone elses session.

V5.3
Instructor Guide

Purpose Show how to reconnect to a previous session.
Details
Transition statement The next visual shows that when you reconnect, any running
tasks will still be running.

Instructor Guide
Reconnecting to login session (2 of 2)

IBM Power Systems
Tasks continued
running
Figure 3-12. Reconnecting to login session (2 of 2) AN111.0
Notes:
Example of reconnecting to a login session

The visual shows that when you reconnect, any running tasks are still active.

V5.3
Instructor Guide

Purpose Show how tasks are still running if you reconnect to a previous session.
Details
Transition statement When youve logged in, you will be at the HMCs Welcome
screen.

Instructor Guide
HMC Welcome screen, after login

IBM Power Systems
Task bar
Navigation Work
area
Status bar
See also : https://www14.software.ibm.com/webapp/set2/sas/f/hmc/v7310notice.html - Basic Usage Guidance

Figure 3-13. HMC Welcome screen, after login AN111.0
Notes:
Welcome screen structure

When you successfully log in to the HMC GUI, you will see the Welcome screen. From
here you can view the clickable major applications in the navigation bar, and you will
see a summary of the current status of servers that this HMC manages in the status bar.
The work area will provide more information about the applications in the navigation
bar, and the banner and task bar area will be along the top of the window. The task bar
will show any running tasks.
In the example in the visual, there are no current running tasks and the status bar
shows that there is at least one attention LED on an object. The status bar icons are
clickable to drill-down to get more information.
The banner, across the top of the workplace window, identifies the product and logo. It
is optionally displayed and is set by using the Change User Interface Settings task.

V5.3
Instructor Guide
Uempty The Navigation pane, in the left portion of the window, contains the primary navigation
links for managing your system resources and the Hardware Management Console.
The items are referred to as nodes.
The Work pane, in the right portion of the window, displays information based on the
current selection from the Navigation pane. For example, when Welcome is selected in
the Navigation pane, the Welcome window content is displayed in the Work pane, as
shown in the figure.
The Status bar, in the bottom left portion of the window, provides visual indicators of
current overall system status. It also contains a status overview icon, which can be
selected to display more detailed status information in the Work pane.
You can resize the panes of the Hardware Management Console workplace by moving
the mouse pointer over the border that separates the Navigation pane from the Work
pane until the mouse pointer changes to a double-pointed arrow. When the pointer
changes shape, press and hold the left mouse button while dragging the mouse pointer
to the left or right. Release the button and your Navigation pane or Work pane is now
larger or smaller in size. You can also do this within the Work pane border that
separates the resources table from the Tasks pad.

Instructor Guide
Instructor notes:
Purpose Show main welcome screen. Show overall user interface areas.
Details The visual is an eye chart to show the major structure of the HMC Welcome
window.
Transition statement Lets look at the overall structure of the HMC V7 Web interface.

V5.3
Instructor Guide
Uempty
HMC V7 user interface: Overall structure

IBM Power Systems
Task bar
Logoff
Work
Navigation area
area
Status
bar
Task
pad
Note: The Task bar shows that several other tasks are running.
Figure 3-14. HMC V7 user interface: Overall structure AN111.0
Notes:
Navigation Area
The Navigation Area, as shown in the visual, contains the primary navigation links for
managing your system resources and the Hardware Management Console.
Access the different applications listed in the navigation bar by clicking their names.
The work area part of the window will change depending on the application. The
Servers application will show a list of all servers being managed by this HMC. If you
click a specific servers name, it will show a table of all of its LPARs. Well look at these
two table views more closely.
The rest of the applications will help you configure a server using system plans,
configure and monitor the HMC, manage any serviceable events that have been logged
by any of the partitions, and manage software updates to both the HMC itself and to the
firmware of the servers.

Instructor Guide
Task bar
The Task bar provides the capability of an active task switcher. The Task bar can be
used as a navigation aid to move between tasks that were launched and have not yet
been closed. The task switcher does not pause or resume existing tasks. Clicking a task
in the Task bar brings that task's window forward and gives it focus. The right end of the
Task bar also contains the following information as shown in the visual:
User ID that you are logged in as. By clicking the user ID, you launch the Change
User Interface Settings task.
Help displays information about all the tasks on the Hardware Management
Console and how to use the Web-based user interface on the Hardware
Management Console.
Logoff launches the Logoff or Disconnect task.
Tasks pad
The Tasks pad displays below the Work Area when you have selected Systems
Management or System Plans in the Navigation Area. This view contains available
tasks for selected managed objects. The content of the Tasks pad changes when
different objects are selected in the Work Area.
The Tasks pad is resizeable by moving the mouse pointer over the border that
separates the Work pane from the Tasks pad.
Status bar
The Status bar in the bottom left pane provides an at a glance view of overall system
status, including managed system resources and the Hardware Management Console.
A status-sensitive title, background color, and icons are part of the Status bar. The
status indicators (icons) appear in color when one or more objects go into unacceptable
status, have attention LEDs, or have open serviceable events; otherwise, the status
icon is greyed out.

V5.3
Instructor Guide

Purpose Discuss the overall structure of the HMC V7 user interface. Show how to
navigate to the major applications using the navigation bar.
Details Describe each item in the navigation bar and how to access the system table
view and the LPAR views.
Transition statement Lets look at how to run specific tasks.

Instructor Guide
Flexibility: Launching tasks

IBM Power Systems
Tasks menu
Context
menu
button
Selected
object
Tasks grouped
into standard
Task pad
categories
Figure 3-15. Flexibility: Launching tasks AN111.0
Notes:
Accessing tasks
You can access tasks from the task pad, the tasks menu, or the selected menu next to
the object. Also, if the task is running, you can click the task in the task bar.
Running tasks
The task bar not only shows running tasks, it also provides the capability to switch the
active task. The task bar can be used as a navigation aid to move between tasks that
were launched and have not yet been closed. Switching tasks does not pause or
resume existing tasks. Clicking a task in the task bar brings that tasks window forward
and gives it focus.

V5.3
Instructor Guide
Uempty Tasks menu

The Tasks menu displays on the table toolbar. The Tasks menu is only available for
table selections. For example, in the Select column of the Servers Work pane table,
select the object with which you want to work. (A check mark displays.) Click Tasks for
the list of the applicable task groups for the selected objects in the table. Select a task
group; then select a task to launch for the object. If more than one object is selected,
the tasks that display in the menu apply to all selections.
Not all tasks can be performed on more than one selected object as the same time. If
you attempt one of these tasks, a window opens requiring you to select the one system
on which to perform the task.
Context menus
The context menu lists the task groups appropriate for the selected object. Context
menus are available for table selections only. For example, in the Select column of the
Servers Work pane table, select the object with which you want to work. (A check mark
displays.) The context menu button (double right arrows) appears next to the object
name you have selected. Click the button and the task groups menu displays for that
particular object. Then select a task to launch for the object. If more than one object is
selected, the tasks that appear in the context menus apply to all selections.
Not all tasks can be performed on more than one selected object as the same time. If
you attempt one of these tasks, a window opens display requiring you to select the one
system on which to perform the task.
Task bar
The Task bar provides the capability of an active task switcher. The Task bar can be
used as a navigation aid to move between tasks that were launched and have not yet
been closed. The task switcher does not pause or resume existing tasks. Clicking a task
in the Task bar brings that task's window forward and gives it focus.

Instructor Guide
Instructor notes:
Purpose Describe the different ways to access tasks.
Details Point out the three ways to access the task list. Mention that if an object (like an
LPAR) is selected, then the task list changes to be specific for that object. If more than one
object is selected, usually a window will appear and ask which object you want to use.
Transition statement The server table view lists all the servers being managed by the
HMC.

V5.3
Instructor Guide
Uempty
Server table view

IBM Power Systems
Default server table view shows status, available (free) CPU and
memory resources and any current reference codes
Select a server to access tasks available for that server
Click Servers to
see a list of
servers.
Then select the
check box to
see tasks
available for that
server.
Figure 3-16. Server table view AN111.0
Notes:
List attached servers (managed systems)

To list all servers being managed by the HMC, click the Servers link in the Navigation
bar. In the example in the visual, there is just one server named rand and it is currently
selected. To select a server, select the check box in the Select column.
The default server table view shows available memory and processing resources and
the status. If there was a current reference code, then it would show as well. Example
tasks to run for a selected server are to view its properties or to power it off.

Instructor Guide
Instructor notes:
Purpose Describe information shown in the default server table view.
Details Point out the basics so that students will be able to navigate to the server table
view and understand the default data shown.
Transition statement The LPAR table view shows a list of LPARs.

V5.3
Instructor Guide
Uempty
LPAR table view

IBM Power Systems
Default LPAR table view includes status, configured CPU and

memory resources, and current reference code
Select a partition to access tasks available for that partition
Figure 3-17. LPAR table view AN111.0
Notes:
List partitions
In the example shown in the visual, the rand managed system has been selected under
Servers in the navigation bar. This will show all LPARs configured on the rand system,
whether they are running or not.
This view will show basic configuration information for the partitions plus their status. In
the example in the visual, no partitions are selected. The list of tasks when no partitions
are selected is different than when a partition or partitions are selected (by selecting the
check box in the Select column).

Instructor Guide
Instructor notes:
Purpose Describe information shown in the default LPAR table view.
Details Point out the basics so that students will be able to navigate to the LPAR table
view and understand the default data shown.
You can mention that when no partitions are selected, often you get the same tasks as
when youre at the server table view and the server is selected. For example, if you run the
Properties task with no LPARs selected in the LPAR table view, you see the servers
properties.
Transition statement One common task for selected LPARs is to open up the
partitions console window.

V5.3
Instructor Guide
Uempty
LPAR consoles
IBM Power Systems
The HMC provides the ability to access a partitions console:

Only one permitted for each LPAR at a time
To access from the GUI, select a running partition and use the
Console Window > Open Terminal Window task
If the window wont open because there is one already open, you
can use Close Terminal Connection first
Figure 3-18. LPAR consoles AN111.0
Notes:
Introduction
From the LPAR table view, you can select partitions and run tasks specific to that
partition. One common task is to open a partitions console window.
Open a virtual (console) terminal window for a running partition

If there is not an open virtual terminal window for an active partition, you can select the
partition and run the Console Window -> Open Terminal Window task.

Instructor Guide
Close a (console) terminal window

There are two ways to close a virtual terminal.
1. The preferred, usual method of closing a terminal window on a Windows PC is to
click the X in the upper right corner of the terminal window. This removes the
window from the desktop and closes the connection.
2. You might need to force a virtual terminal window to close by selecting the partition
name in the Server Management area of the HMC, right-clicking, and choosing
Close Terminal Connection. Use this procedure when the virtual terminal window
is open on another HMC (or remotely from a browser) and you want to turn off that
session or as a recovery in case you cant close the window for some reason.

V5.3
Instructor Guide

Purpose Cover how to manually open and close a terminal window.
Details Describe the procedure to open and close the terminal windows.
Emphasize that even though the menu option says terminal window, were only
discussing the partition console.
Transition statement Lets look at the HMC online Help and documentation.

Instructor Guide
HMC online help and documentation

IBM Power Systems
The HMC has online help:

The Help link is always available in the upper right part of the task bar:
Help buttons on task windows give context sensitive help

You can search for topics from the help screen
Main HMC documentation:

Operations Guide for the HMC and Managed Systems (SA76-0085)
Available from the Resource Link site:
http://www.ibm.com/servers/resourcelink
HMC V7 Handbook (SG24-7491)

An IBM Redbooks document available from www.redbooks.ibm.com
Figure 3-19. HMC online help and documentation AN111.0
Notes:
HMC usage information

To get more information about how to use the HMC, you can access the online help
facility from the HMC itself, or access the operations guide available on the Internet.
Theres also a link to the online HMC help screens from the prelogin screen.
In addition, when we discuss the HMC command-line interface later in this course, youll
see that HMC commands have man pages accessible from the command line.

V5.3
Instructor Guide

Purpose Discuss the major resources for HMC information.
Details Mention that theres also an online help link right from the HMC pre-login
welcome screen. You do not have to log in to the HMC to access the help information.
Transition statement Lets see how to access the online documentation.

Instructor Guide
HMC V7 documentation
IBM Power Systems
Follow the links on the HMC welcome screen for support

information, tutorials, and documentation:
Link to POWER6 and

HMC V7 documentation
(Follow Publications link)
Internet documentation location:

//www.ibm.com/servers/resourcelink
Look for Library and then System p POWER6 hardware links.
Figure 3-20. HMC V7 documentation AN111.0
Notes:
Access to documentation
Online links are available from the HMC Welcome screen. An HMC tutorial and
documentation are available from Resource Link. Resource Link requires a unique login
account and password.
HMC Support web site

The HMC support Web site has the latest information and downloads for the HMC:

V5.3
Instructor Guide
Uempty HMC V7 Readme document

See the detailed list of changes between HMC V7 and previous releases with the
Cumulative history and Readme for use with HMC Version 7 document:
http://www14.software.ibm.com/webapp/set2/sas/f/hmc/power6/install/v7.Readme.html

Instructor Guide
Instructor notes:
Purpose Describe how to get to the documentation.
Details An HMC tutorial available is online in addition to an HMC operations guide.
Resource Link is on the Internet and requires you to set up a login and password.
Transition statement In the next section of this unit, youll see several screens where
you can customize display options in the HMC. Lets see a few.

V5.3
Instructor Guide
Uempty
Work area: Tables

IBM Power Systems
Toolbar features: Select/Deselect all, filtering, sorting, column display and ordering
Note: Toolbar details are shown on the next chart.
Item
selection
Toolbar Column
sizing
Click to
sort
Scrolling
Summary
Note: Shift-select to select a range
Figure 3-21. Work area: Tables AN111.0
Notes:
When you click a managed server in the Navigation area, the Work pane displays the
list of partitions defined on the server.
If you click the Column configuration icon on the table toolbar, optional attributes
display. This function enables you to select additional attributes that you want displayed
as columns in the table. It also allows you to reorder the columns.
Displaying server and partition details

To display details (properties) about a server or partition, you can select the server (or
partition) by clicking in the Select column in the Work pane table. Then you can either
click Properties from the Tasks pad or click the double-arrow icon next to the server (or
partition) name and click Properties from the context menu. In both cases, the
Properties window opens.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Introduce the toolbar options.

V5.3
Instructor Guide
Uempty
Toolbar features
IBM Power Systems
Select all Select all of the items which are shown in the current table view
Deselect all
Show filter row Filter according to specified text

Contains; Does Not contain; Starts with; Ends with; Matches; Is empty; Is not empty
Clear all filters
Edit sort Up to three sort fields can be specified. Sort by Ascending/Descending

Name, ID, Status, Processing Units, Memory, Active Profile, Type, Reference Code,
Processor, Service partition, Configured, Default Profile
Clear all sorts
Configure columns Select which columns to display

Name, ID, Status, Processing Units, Memory, Active Profile, Type, Reference Code,
Processor, Service partition, Configured, Default Profile
Reset columns Reset Column Order / Visibility / Width
Note: These settings (for each user ID) are preserved between sessions.
Figure 3-22. Toolbar features AN111.0
Notes:
The toolbar is extremely useful and flexible for adjusting the information on display.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Lets see how to filter columns.

V5.3
Instructor Guide
Uempty
Flexibility: Filtering columns

IBM Power Systems
Filters
Filter indicator Tick-box: Filter can

be toggled on or off
Filter
options
Filter text
Filter
results
Figure 3-23. Flexibility: Filtering columns AN111.0
Notes:
The display area can be easily changed by using filters. This greatly improves flexibility.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Lets see sort options.

V5.3
Instructor Guide
Uempty
Flexibility: Sort options

IBM Power Systems
Sort
Sort indicators
Sort
Sort on fields
multiple
columns
Figure 3-24. Flexibility: Sort options AN111.0
Notes:
The work area data can be displayed in a particular sort order.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Custom groups let us group objects of different classes together.

V5.3
Instructor Guide
Uempty
Flexibility: Custom groups

IBM Power Systems
(above example shows LPARs from two servers)
Create groups of objects (for example, servers and LPARs)

Group by location, or business function, or department
Add LPARs from one or more servers
Add LPARs from one or more servers

Default groups (showing all partitions or all objects)
Figure 3-25. Flexibility: Custom groups AN111.0
Notes:
Custom groups
Groups are comprised of logical collections of objects. You can report status on a group
basis, allowing you to monitor your system in a way that you prefer.
You can also nest groups (a group contained within a group) to provide hierarchical or
topology views.
One or more user-defined groups might already be defined on your HMC. There are
default groups listed under the Custom Groups node under Server Management. The
default groups are All Partitions and All Objects. You can create others, delete the
ones that were created, add to created groups, or delete from created groups by using
the Manage Custom Groups task.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Now, lets go through the status overview information.

V5.3
Instructor Guide
Uempty
Status overview
IBM Power Systems
Figure 3-26. Status overview AN111.0
Notes:
Status Overview icon

When you click the Status Overview icon, it displays a highly visible and detailed
summary of system status in the Work pane, as shown in the figure. It displays details
about any errors (objects with unacceptable state), attention LEDs active, or open
serviceable events found for the HMC or managed objects. It also summarizes the total
number of errors, attention LEDs, and open serviceable events by object type. Object
types include the server, partition, frames, and the HMC. When any of these conditions
are present, links are available to drill down and display all objects with the particular
state in the Work pane.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement No more searching on Google for reasons why the machine
wont initial program load (IPL). Now code explanations are available.

V5.3
Instructor Guide
Uempty
SRC lookup
IBM Power Systems
This is the ability to look up the 8-digit reference codes (SRCs).

The majority of codes are listed in the initial release.
Later, many 4-digit codes are converted to 8 digits.
Figure 3-27. SRC lookup AN111.0
Notes:
You can now look up SRC codes from the HMC as shown in the visual.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Quickly go through the HMC management options.

V5.3
Instructor Guide
Uempty
HMC management: Overview

IBM Power Systems
HMC
operations
HMC network
configuration
HMC users HMC

management administration
Figure 3-28. HMC management: Overview AN111.0
Notes:
HMC Management
HMC Management contains a categorized or alphabetical view of Hardware
Management Console management tasks and their descriptions. These tasks are used
for setting up the Hardware Management Console, maintaining its internal code, and
securing the Hardware Management Console.
To display the tasks in the Work pane:
Select the HMC Management node in the Navigation pane.
From the Work pane, click the task you want to perform.
By default, a categorized listing of the tasks displays. The categories include:
- Operations
- Administration

Instructor Guide
If you want to see what level of the HMC you are currently working with, move
your mouse over HMC Version found at the top of the Work pane.
If you want an alphabetical listing of the tasks, click Alphabetical List in the
upper right corner of the Work pane. Click Categorized List to go back to the
task categories.

V5.3
Instructor Guide

Purpose
Details Show some examples or feel free to demo instead.
Transition statement In the next section of this unit, youll see several screens where
you must supply information about your HMC and its network.

Instructor Guide
HMC network configuration

IBM Power Systems
Needed for configuring HMC network options:
9 Private or open network for HMC to service processor

9 HMC host name
9 IP addresses LAN to partitions
9 Domain name Open and other hosts
9 DNS server IP address network
9 DHCP setting
9 Default gateway IP address
9 Additional routes
9 Firewall configuration
Private
HMC network
LAN to service
processor
Figure 3-29. HMC network configuration AN111.0
Notes:
Introduction
In the next section of this unit, youll see several screens where you must supply
information about your HMC and its network. This visual lists the options that you must
decide whether to enable, and the information that you will need to enter. Plan ahead
and document all of this information before you attempt to configure the HMC. You will
need some knowledge of basic TCP/IP configuration information or help in this area.
Some of the acronyms used in the visual are explained here:
Domain Name System (DNS): The HMC needs to know which DNS server to
use.
Internet Protocol (IP): The HMC needs an IP address configured for one or two
Ethernet interfaces.
Dynamic Host Configuration Protocol (DHCP): The HMC can be configured as a
DHCP server for its managed systems.

V5.3
Instructor Guide
Uempty Private versus open network for HMC to the service processor
One of the decisions you have is whether to connect the HMC to the service processor
over a private network or over an open network. A private network is one that is
restricted to HMC and service processor connections. An open network has other
network hosts connected to it. The visual shows a graphic with a private network
connecting the HMC to the service processor and an open network connecting the
HMC to the partitions. This is a typical configuration and the easiest to configure.
The HMC and the service processor use the Secure Sockets Layer (SSL) protocol for
communications.

Instructor Guide
Instructor notes:
Purpose Describe information needed before attempting to configure the HMCs
network settings.
Details Define an open network and a private network. Explain you can have the service
processor connected to the open network and not have a private network.
The next set of visuals will show the screenshots where you enter in the network
information that is listed on this visual.
The basic network configuration can be set in the Guided Setup wizard; so many of the
screens shown in the following visuals are similar to those used in the wizard. The
difference is that there are more options to configure when you go through the HMC
Configuration application.
Transition statement Next, we will see the first window that opens when you choose
Change Network Settings in the HMC Management Work pane.

V5.3
Instructor Guide
Uempty
Network settings: Identification

IBM Power Systems
Figure 3-30. Network settings: Identification AN111.0
Notes:
Introduction
This visual shows the first window you will see after choosing Customize Network
Settings from the HMC Management Work pane. Notice there are four tabs along the
top.
Changing the network options in these windows will require a restart of the HMC for the
changed values to be used.
Identification tab
The Console name field is the HMCs host name. Enter the HMCs host name.
The Domain name field is the Domain Name System (DNS) domain name in use for
this HMC. It might be something like companyname.com, engineering.acme.com, or
mopssc.com as shown in the visual.

Instructor Guide
The Console description field is where you can put a description that uniquely
describes this HMC. Some HMCs are described by the managed systems they manage
or by their location.

V5.3
Instructor Guide

Purpose Describe the first network configuration window.
Details Describe each field and mention that you click the tabs at the top to change to
those windows. Click OK when you are done.
On this window, enter the HMCs host name and network domain name that will be used by
other hosts on the network to access this HMC.
Transition statement Next is the LAN Adapters tab.

Instructor Guide
Network settings: LAN Adapters

IBM Power Systems
Select interface and

click Details button.
Figure 3-31. Network settings: LAN Adapters AN111.0
Notes:
Choose a network interface to configure

Choose which interface you want to configure and click the Details button. The screen
that appears is shown on the next visual.
Private network configuration

If the managed system and the HMC will communicate over a private network,
configure eth0 as the private connection to the service processor. Configure eth1 on an
open network to the partitions on the managed system.
Open network configuration

If the managed system and the HMC will communicate over an open network, configure
eth0 for the open network. Important: Do not connect both Ethernet connections from
one HMC to the two service processor HMC connections.

V5.3
Instructor Guide

Purpose Describe how to configure a network interface.
Details This visual shows how to choose which interface to configure.
Transition statement The next page shows the Details window.

Instructor Guide
Network settings: LAN Adapter details

IBM Power Systems
Figure 3-32. Network settings: LAN Adapter details AN111.0
Notes:
Introduction
The window opens after you choose an interface and click the Details button as shown
on the previous visual.
LAN information
The first option allows you to choose a private or an open network for the HMC.
A private network means that the HMC connects to the managed systems over a
separate network which is not shared by other network traffic. The term open refers to
any general network that contains elements other than HMCs and service processors,
and that is not isolated for only HMC network traffic to its managed system.
It is recommended that you implement service network communications through a
private network, because of the additional security and ease of setup that it provides.
However, in some environments, this is not feasible because of physical wiring, floor

V5.3
Instructor Guide
Uempty planning, or control center considerations. The same functionality is available on both
types of networks, although the initial setup and configuration on an open network
requires more manual steps.
Partition communication check box

The partition communication check box, if selected, configures this interface for
communications between the HMC and partitions. Select this check box for the
interface that connects to the partitions.
Media speed
The default of automatic detection for the Ethernet adapter media speed is
recommended for the initial setup. However, in some situations, you might want to
reduce the speed of the adapter to decrease the amount of processing power it uses for
large amounts of data, if, for instance, an Ethernet hub or switch is used and needs a
lower media speed.
Dynamic Host Configuration Protocol server

If you click Private, you have the option of configuring this HMC as a DHCP server.
Dynamic Host Configuration Protocol (DHCP) servers provide an automated method for
dynamic client configuration. The clients in this case are the service processors on the
managed systems that the HMC is managing. Clients that are DHCP-enabled
automatically obtain their own IP address and configuration parameters from the DHCP
server. In a private network, configure your first or only HMC as a DHCP server.
If you click Open, the Enable DHCP server option is not available.
A DHCP server has a range of IP addresses that it assigns to systems. If you configure
the HMC as a DHCP server, select one of the following standard nonroutable IP
address ranges for your private network. These ranges are shown in the visual.
It is recommended that you use the non-routable 192.168.128.2 - 192.168.255.254
address range when setting up the connection between the HMC and the managed
system.
If DHCP is not set up or the managed system cannot access the DHCP server, it will
use the default IP address of 169.254.2.147 for the first Ethernet interface and
169.254.3.147 for the second Ethernet interface. Note that these default IP addresses
are different if you use a POWER5 based-processor system. The default IP addresses
on the FSps are 192.168.2.147 and 192.168.3.147
The DHCP server in the HMC uses automatic allocation, which means that each unique
service processor Ethernet interface will be reassigned exactly the same IP address
each time it is started. Each Ethernet interface has a unique identifier based upon a
built-in Media Access Control (MAC) address, which allows the DHCP server to
reassign the same IP parameters.

Instructor Guide
DHCP client/IP address

In the last part of the Basic Settings tab, you can choose whether this HMC will be a
DHCP client or whether a specific IP address will be assigned. In the example shown in
the visual, this HMC is using a fixed IP address and a network mask.

V5.3
Instructor Guide

Purpose Describe the LAN adapter configuration settings.
Details Describe the difference between an open network and a private network.
Emphasize that the private network is only for HMC to service processor communications.
The HMC still needs to connect to a public network so that it can communicate with the
daemons running in the partitions for DLPAR operations and the service tools
communications.
Describe when to set up as a DHCP server versus a client.
Describe how to use static addresses rather than setting up as a DHCP client. Be sure the
students understand the difference between setting up the HMC as a DHCP client and a
DHCP server.
Transition statement Another option to set up for the LAN adapter is whether you want
to open the firewall for remote access. This is covered next.

Instructor Guide
Network settings: LAN firewall

IBM Power Systems
Add Secure Remote

Web access and
SSH to permit remote
access to HMC
Figure 3-33. Network settings: LAN firewall AN111.0
Notes:
Firewall configuration
In an open network, there is usually a firewall that controls outside access to your
company network. The HMC also has a firewall on each of its Ethernet adapters. If you
want to remotely administer a managed system, then you must modify the firewall
settings of the Ethernet adapter on the HMC that is connected to your open network to
allow remote Web and SSH access.
The bottom panel shows what is currently configured for this interface. SSH and remote
Web access are not permitted by default. Select the ports in the top panel that you want
to configure, then click either the Allow Incoming (from any IP address) button or the
Allow Incoming by IP Address (to only allow a specific address or addresses) button.
These procedures are explained as follows.

V5.3
Instructor Guide
Uempty Allow specific applications from any IP address

To allow any IP address using a particular application through the firewall:
1) In the Available Applications panels, highlight the application.
2) Click Allow Incoming. The name of the application displays in the bottom
box to signify that it has been configured.
Allow specific applications from a specific IP address

To allow applications from specific IP addresses through the firewall:
1) In the Available Applications panel, highlight an application.
2) Click Allow Incoming by IP Address.
3) In the Allowed Hosts panel, enter the clients IP address and network mask.
4) Click Add and OK.
A few recommended settings

By default, remote Web connection and SSH traffic are not allowed through the firewall.
To allow the use of the remote Web connection, add Secure Remote Web Access. To
allow access to the HMC using ssh, add Secure Shell.
The remote operation task available in the HMC Management pane controls whether
the Hardware Management Console can be operated using a Web browser from a
remote workstation. When you enable remote operations, the firewall settings are
automatically modified (the Secure Remote Web Access entry is added for allowing
access for network traffic through the firewall).

Instructor Guide
Instructor notes:
Purpose Describe how to configure the HMC firewall.
Details The firewall application allows you to control remote access to the HMC. The
firewall prevents outside unauthorized access to the private network between the HMC and
its managed systems service processor. If you want to use the HMC remotely, you must
open up the firewall to allow some applications like Secure Remote Web Access and SSH
access to the HMC.
Describe the difference between the Allow Incoming and the Allow Incoming by IP
Address buttons.
Remind the students that this window opened when the Details button was clicked on the
LAN Adapters tab. Now when you click the OK button on the window shown in this visual,
the Details window closes and you are returned to the Customize Network Settings
window, which is shown in the next visual.
Transition statement The next page shows how to configure name services on the
HMC.

V5.3
Instructor Guide
Uempty
Network Settings: Name Services

IBM Power Systems
Figure 3-34. Network Settings: Name Services AN111.0
Notes:
Name Services configuration

This tab configures the Domain Name Services (DNS) settings for the HMC. Name
services provide IP to host name (and vice versa) mappings.
If the network where the HMC resides uses DNS services, select the DNS enabled
check box. This will configure the HMC to use DNS as a client. Enter the DNS server
search order. List DNS servers in the order that they will be checked. As specified by
the DNS protocol, the second and third servers are only used if the ones above it on the
list are not available.
In the bottom portion of the screen, enter the domain suffix search order for your
network. For example, the HMC host name might be sys03hmc.moppssc.com; so
with the search orders specified in the visual, every host name will first be looked up in
the moppssc.com domain.

Instructor Guide
Instructor notes:
Purpose Describe how to configure DNS services.
Details This tab configures the HMC to be a DNS client.
If the students are familiar with setting up the UNIX /etc/resolv.conf file, then the items on
this visual look familiar.
If asked, there is no way to set up an /etc/hosts file on the HMC. If the HMC is in a
non-DNS environment, simply do not select the DNS enabled check box. From the HMC,
you will not be able to ping host names with the Test Network Connectivity tool; however,
everything else will work and you can ping IP addresses. HMCs do not need to have host
name lookup services to communicate to partitions for DLPAR operations and service tool
operations.
Transition statement An HMC might also need to have network routes configured.

V5.3
Instructor Guide
Uempty
Network settings: Routing

IBM Power Systems
Figure 3-35. Network settings: Routing AN111.0
Notes:
Network routes
You might have a complex network structure where additional network routes might
need to be configured. There are a few reasons you might need to configure routes and
these reasons are not unique to an LPAR environment. An HMC needs to be able to
reach its partitions and those partitions might be on a remote network. A default
gateway might be all that you need to configure as the default gateway might be able to
route all IP packets to the correct network. Or, you might know of a more direct route to
get to partitions than the default gateway. You can add this route on this tab. Another
reason is that you might not have a complex network at all and are not using dynamic
routing, in which case, a few static routes might be all that you need.
Adding a route
To add a route, click the New button in the middle of the screen. The window that opens
is shown in the visual. Enter the destination network address, the gateway network

Instructor Guide
address, and the subnet mask in use, and choose which adapter to use. Click OK to
enter the route.
Enable routed daemon

You might want to run the dynamic routed daemon. This daemon communicates with
other routed daemons to learn new, closer routes to remote networks.
Default gateway information

For many installations, the HMC simply needs to know the IP address of a gateway
system. The HMC then relies on this gateway for all routing services. Make sure that
the adapter you choose is on the same subnet as the gateway system. For the
recommended setup, this would be eth1, the interface on the open network.

V5.3
Instructor Guide

Purpose Describe how to configure routing on the HMC.
Details Describe when to create routes and how to create them.
That is the end of the network configuration section. The HMC should be restarted and
then the administrator should use the ping command (HMC command line or from a remote
system) and the Test Network Connectivity HMC task to test the network configuration.
For the last few screens, the configuration data that must be entered is standard for TCP/IP
networks. Students installing an HMC should work with their network administrator to enter
the correct TCP/IP configuration information. This is not a TCP/IP administration class, so
avoid going into a lot of detail on how DNS, DHCP, or routing functions.
Transition statement That is it for the HMCs network configuration. Now that the HMC
is on the network, you need to connect it to its managed systems.

Instructor Guide
Connecting HMC to managed system

IBM Power Systems
HMC is connected to open LAN to Partitions

network and configured
Connect Ethernet cable
between HMC and service
processor
Private or open network Network
Direct or through hub/switch
Apply power to managed
system
HMC will find it
Or, use Add Managed System
menu option
Private
HMC Network
Default service processor IP addresses without DHCP LAN to service
POWER5 based-processor systems: processors
192.168.2.147 and 192.168.3.147
POWER6 based-processor systems:
169.254.2.147 and 169.254.3.147
Figure 3-36. Connecting HMC to managed system AN111.0
Notes:
Introduction
Now that you have powered on your new HMC and configured the basic network
options, lets see how to get the HMC communicating with the managed system. Both
the HMC and the managed system must be connected to the same network. The visual
shows the HMC and the service processor connected to a private network.
Connecting the Ethernet cables

Connect the HMC1 port on the managed system to the Ethernet port on the HMC. For
desktop HMC models, connect the cable to the integrated Ethernet port. For
rack-mounted HMC models, connect the cable to the bottom port (for vertically stacked
ports) or the one labeled port 1 of the two Ethernet ports. For direct connections, you
can use either a straight or cross-over Ethernet cable.

V5.3
Instructor Guide
Uempty You can also use a hub or switch between your HMCs and the service processors or
connect them all on an open network with the partitions and other network hosts.
Connecting the managed system

If the managed system is on the same private network, the HMC will automatically find
the managed system as soon as you apply power to the managed system.
Important: Do not connect the managed system to power until the HMC is fully
configured and the Ethernet cable between the HMC and the service processor is
connected.
At first, the System Management application will be empty. After a short time, you will
see a system appear with the state of No Connection. After a short time, this will
disappear and another entry will appear with a state of Pending Authorization. At this
point, select the managed system name and a window will open with three tabs. Enter a
password on each of these tabs. These passwords are used with the general and
admin accounts in ASMI and the third is for HMC to managed system communication.
It is recommended for ease of configuration to use a private network between the HMC
and the service processor. If you have multiple systems on an open network, you might
need to use the Add Managed System task on the System Management so that you
can connect to a specific service processor.
IP addresses
If the HMC is running DHCP, the IP address of the HMC will be depend on the range of
DHCP addresses that are configured. For example, if the range of 192.168.128.2 -
192.168.255.254 is configured, the HMC will receive 192.168.128.1 and the first service
processor will be 192.168.255.254.
On POWER5 based-processor systems: If the service processor powers on and cannot
find a DHCP server it will use 192.168.2.147 for its first Ethernet port and 192.168.3.147
for the second Ethernet port by default. You can configure the service processor to use
any static IP address by using the ASMI application.
On POWER6 based-processor systems: If the service processor powers on and cannot
find a DHCP server it will use 169.254.2.147 for its first Ethernet port and 169.254.3.147
for the second Ethernet port by default. You can configure the service processor to use
any static IP address by using the ASMI application.
If you have multiple HMCs on the same network, only the first should be configured as a
DHCP server and the IP addresses shown above are for the first HMC and service
processor.

Instructor Guide
Add the managed system

If necessary, you can use the Add Managed System task from the HMC Management
Work pane to add a new managed system. The next few visuals will walk through this
procedure.
Redundant HMCs
All of the POWER5 and POWER6 processor-based managed systems support
redundant HMCs. This is a highly recommended configuration for the enterprise-level
servers.
Secure connection using SSL

The HMC to service processor connection uses SSL for secure communications. For
SSL, we need userids and passwords on the service processor and there are default
userids admin and general already set up, and an additional HMC userid when HMC is
connected. This HMC account is used for authentication between the HMC and the
service processor on the managed system.
The service processor issues the SSL certificate and this SSL connection is established
when the managed Server is added to the HMC. When you connect the HMC to the
managed system and apply power, the state of the managed system is Pending
Authentication - Password Updates Required. Click the managed system name and
you will be prompted to set up the three passwords. Be sure to document these in a
safe place.
If another HMC subsequently needs access to this managed system, upon attempting
to access this HMC the user is presented with the Update Password Failed
Authentication window, which will prompt for the HMC access password you entered.
In the scenario where the HMC access password changes while you are logged in to
the managed system, your HMC will discover that it can no longer authenticate when it
attempts to reconnect to that managed system. This will result in a state of Failed
Authentication for that managed system. You will be required to enter the new
password before any actions can be performed.

V5.3
Instructor Guide

Purpose Describe how to add a managed system to the HMC.
Details Describe a simple private network setup, where the HMC and managed system
are both on the same subnet.
Describe how the HMC will automatically discover the service processor and the DHCP
server on the HMC will assign it an IP address. The state of the managed system will at first
be No Connection, then change to Pending Authorization. If it stays on No Connection
and never changes to Pending Authorization, then there is a problem. Try the Add
Managed System task from the HMC Management Work pane.
When the state is Pending Authorization, click the managed system name and you will be
prompted to enter three passwords to set up the SSL connection between the HMC and
the managed system: HMC access, and the admin and general accounts for accessing
ASMI.
The next visual shows the menu option to begin the process of adding the managed
system manually to the HMCs Server Management application.
Transition statement Now, lets see how to add the managed system in the HMC
interface.

Instructor Guide
Add managed system (1 of 3)

IBM Power Systems
Add the managed system to the Server Management

application
Managed system must be on the same network as HMC
Figure 3-37. Add managed system (1 of 3) AN111.0
Notes:
Introduction
If the HMC is on a private network with the service processor, then the HMC should find
the service processor automatically, and add it to the Server Management application.
If the HMC and service processor are on a network with other systems, or if the service
processor is using static IP addresses, then you must use the Add Managed System
task from the HMC Management Work pane to add the managed system to the list of
Servers of the Systems Management pane.
If this is a new managed system, and there is no DHCP server available, the default
service processor IP address will be 192.168.2.147 or 169.254.2.147 depending on
your system type for the first Ethernet port on the service processor card and
192.168.3.147 or 169.254.3.147 for the second Ethernet port.

V5.3
Instructor Guide

Purpose Describe how to add a managed system to the HMC.
Details Illustrate how you access the Add Managed System option.
Transition statement The next visual shows the window that opens when you choose
the Add Managed System task from the HMC Management Work pane.

Instructor Guide

IBM Power Systems
Notes:
Add and Find managed system options

If you know the IP address of the managed system and the HMC access password,
then you can use the first option on this screen, Add a managed system and type the
IP address in the IP Address/Host name field. The password you enter is the HMC
access password, which must have already been set during a previous HMC to service
processor setup.
If you do not know the IP address, or the HMC access password has not been set up,
then type the range of IP addresses that it could be as shown in the example in the
visual. The range of addresses cannot exceed 256 total addresses. The next visual
shows what happens when this operation finds the managed system.
If you need to set or see the IP address of the service processor, you can connect a
terminal to the serial port of the service processor to access ASMI. This interface can
be used to configure the IP address that will be used by the service processor. You can
then connect the service processor to the network, and enter the IP address in the Find

V5.3
Instructor Guide
Uempty managed systems option. This procedure is particularly useful if the service processor
is connected to an open network.

Instructor Guide
Instructor notes:
Purpose Describe the two options when adding the managed system to the HMC.
Details Compare the two options and when they might be used.
When setting up the HMC to service processor connection for the first time, you should
know the default IP address of the service processor and then search for it using the Find
managed systems option. Because you need to know the HMC to managed system
access password for the Add managed system option, you cannot use this option the first
time you set up the HMC and service processor connection.
Transition statement The next page shows the window that opens when the managed
system in the specified IP range has been found.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Notes:
Find managed systems

The visual shows the result of the find operation specified on the last visual. Select the
managed system and click the Next button to add this managed system to the HMC
Systems Management pane.

Instructor Guide
Instructor notes:
Purpose Describe the final step to add the managed system to the HMC.
Details This procedure shows how to add a managed system if you are not sure of its IP
address but you know its approximate IP address because you know what the DHCP IP
address range is. You would also use the Add managed system task when the service
processor is configured with a static IP address.
Transition statement The next page shows how to remove or reset a connection
between the HMC and a managed system.

V5.3
Instructor Guide
Uempty
Managing the server or HMC connection

IBM Power Systems
Menu options to:

Reset or remove connection
Disconnect another HMC
Add a managed system
Check service processor status
Figure 3-40. Managing the server or HMC connection AN111.0
Notes:
Introduction
The visual points out some other important tasks that you might need to do to manage
the communications between the HMC and its managed systems.
Reset or remove a connection

We have already seen that Add Managed System task on the HMC Management
Work pane is how you can seek managed systems on the network and add them to the
HMC Systems Management. The visual shows an example where a second
management system was added to the System Management.
The opposite to Add Managed System is Reset or Remove Connection. This will
allow you to reset or remove a managed system from the Systems Management. If
you choose this menu option, another window will open asking if you want to reset or
remove the managed system. If you choose remove it, the managed system disappears

Instructor Guide
from the Systems Management. Choosing to reset the managed system will
disconnect then reconnect the managed system.
If you suspect a problem with the managed system connection to the HMC, you can
perform a reset. If there is no connection between the managed system and the HMC,
try a reset to see if it fixes the issue. If a reset does not help, investigate the physical
connection between the HMC and the managed system and the network configurations.
Update managed system password

You can use the Change Password task to change the managed system's HMC
access password. This is the one used for communications between the HMC and the
managed systems service processors. If you change this password, you must change
the password for any other HMCs that connect to this managed system.

V5.3
Instructor Guide

Purpose Describe menu options for managing HMC/managed server connections.
Details This visual shows some additional HMC menu options to keep communications
between the HMC and its managed systems working correctly.
Transition statement As of HMC software version 7, a Service Processor Status
menu option can be used to check the status of the connection between the HMC and the
managed system.

Instructor Guide
Check managed system status

IBM Power Systems
Figure 3-41. Check managed system status AN111.0
Notes:
Connection status
The Status menu option displays information about the status of the HMC connection
to the bulk power assemblies on the frame or to the service processors on the managed
system. You must select the managed system name first before accessing this option.
If you are viewing the connection status for a frame, you can see the state of the
connection from the HMC to side A and side B of the bulk power assembly. The HMC
will operate normally with a connection to either side A or side B. However, for code
update operations and some concurrent maintenance operations, the HMC needs
connections to both sides.
If you are viewing the connection status for a managed system, you can see the state of
the connection from the HMC to the primary and secondary service processors. The
HMC will operate normally with a connection to only the primary service processor.
However, for code update operations and some concurrent maintenance operations on
the managed system, the HMC needs connections to both the primary and secondary

V5.3
Instructor Guide
Uempty service processors. If no secondary service processor is installed, only one connection
to the primary service processor is required.
HMC lssysconn command

The following command displays the connection status from the HMC command line:
lssysconn -r all
Example output from this command:
resource_type=sys,type_model_serial_num=8204-E8A*65BF7E1,sp=primary,sp_p
hys_loc=U78A0.001.DNWGD21-P1,ipaddr=192.168.255.254,alt_ipaddr=unavailab
le,state=Connected

Instructor Guide
Instructor notes:
Purpose Show the Status menu options output.
Details You can see the status of the HMC connection to the managed system with the
Status menu option. This option is new with HMC version 6.1.
Transition statement The FSP connection status can also be viewed using the HMC
Management task View Network Topology.

V5.3
Instructor Guide
Uempty
Check HMC software version

IBM Power Systems
Check in HMC management

HMC version
Or, check from HMC command line:

$ lshmc V
"version= Version: 7
Release: 3.3.0
Service pack: 0
HMC Build level 20080421.1
MH01102: Required fix for V7R3.3.0 (04-21-2008)
","base_version=V7R3.3.0
"
Check against Web site for latest version and fixes:
Figure 3-42. Check HMC software version AN111.0
Notes:
Introduction
Another step in the configuration and maintenance of your HMC is to ensure that its
software is kept up to date. Check the HMC technical support Web site to make sure
there are no additional fixes for the HMC.
The visual shows two places where the HMC software version can be checked. Notice
that when you use the lshmc -V command from the command line, the fix packs that
have been loaded are displayed. The procedure for loading fixes will be covered later in
this course.

Instructor Guide
Instructor notes:
Purpose Describe how to check the HMC software version.
Details It is important to keep your HMC software version up to date. Administrators
should check the HMC technical support site as soon as a new HMC is configured to see if
it needs to be updated. We will cover how to apply fixes to the HMC later in this course.
Transition statement Thats the end of Topic 1. Next is a Lets Review.

V5.3
Instructor Guide
Uempty
Lets review Topic 1

IBM Power Systems
1. Circle all of the following that are functions of the HMC.

a. Monitor TCP/IP network objects
b. Capacity on Demand activation
c. Partition configuration
d. Activate partitions
2. When might an HMC need to be configured as a DHCP

server?
3. How is the HMC connected to its managed system?
4. True or False: One HMC can manage multiple managed

systems.
Figure 3-43. Lets review Topic 1 AN111.0
Notes:

Instructor Guide
Instructor notes:
Purpose Check the students understanding of the material in this topic.
Details Lets Review solution:
Additional information There is a Topic 1 hands-on exercise in the exercise book. You
may choose to do this hands-on exercise now to break up this long unit, or you can do both
Topic 1 and Topic 2 exercises at the end of the unit.
Lets review Topic 1 solutions

IBM Power Systems


server? When it is on a private network and there is no
other DHCP server.

The connection uses Ethernet.

systems.
Transition statement The next topic in this unit covers HMC users, remote access, and
security.

V5.3
Instructor Guide
Uempty 3.2. HMC users, remote access, and security

What students will do The students will learn how to create custom user accounts,
access the HMC remotely, and describe some additional security features on the HMC.
How students will do it The lecture materials, the Lets Review questions, and the
hands-on exercise will allow the students to meet the topics objectives.
What students will learn The students will learn how to configure user accounts, task
roles, and managed resource roles. They will learn how to connect to the HMC remotely
and how to make these connections more secure.
How this will help students on their job It is common to need to access the HMC
remotely and this topic shows not only how to do that, but how to make this more secure by
adding custom users and increasing the security.

Instructor Guide
Topic 2: HMC users, remote access, and security

IBM Power Systems

Create HMC users
Configure and assign task roles and managed resource
roles
Describe security options, such as:
Controlling remote connection, virtual consoles, and SSH access
Managing certificates from the HMC
Overview of Integrated Virtualization Manager (IVM): The
HMC alternative
Figure 3-44. Topic 2: HMC users, remote access, and security AN111.0
Notes:

V5.3
Instructor Guide

of the topic.
Transition statement We will start this topic with more information on how to create and
manage custom HMC users.

Instructor Guide
HMC user management

IBM Power Systems
HMC users and roles are

specific to that HMC
Passwords must be at least 7
characters
Password expiration
Configurable roles by task and
by resource
Figure 3-45. HMC user management AN111.0
Notes:
HMC users management

Under the HMC Management Work pane, a task is available for creating, managing
custom user accounts. As stated earlier in this unit, these HMC users are unique on this
HMC.
The first task in the visual, Change User Password, allows you to change the
password for the account that you used to log in to the current HMC session. If you are
logged in as a different account than hscroot, you might find the options Manage User
Profiles and Access and Manage Tasks and Resource Roles unavailable and only
the Change User Password option available for you to change your own password.
The second task shown in the visual is Manage User Profiles and Access. This is
where you create new users, and modify other aspects of a user account.
The third task is Manage Task and Resource Roles. A task is a specific procedure
that a user might do, such as activate a partition, or create a user. A managed resource

V5.3
Instructor Guide
Uempty is a thing that a user might perform a procedure on, such as a managed system, or a
partition. When you create a user account, you assign a task role, which has assigned
to it one or more tasks, and a managed resource role, which has one or more managed
resources assigned to it.

Instructor Guide
Instructor notes:
Purpose Describe the options available on the HMC Users application.
Details Define the terms task and managed resource. Describe the basic functions of
the options available in this Work pane.
Transition statement The next page will show how to add or modify HMC users.

V5.3
Instructor Guide
Uempty
Add or manage HMC users

IBM Power Systems
To add or manage users, choose HMC Management and then

Manage User Profiles and Access
Access the User menu to add, modify, remove, or copy a user
List of current
user accounts
Figure 3-46. Add or manage HMC users AN111.0
Notes:
Default accounts
There are three default user accounts on new HMCs. hscroot is used to log in to the
HMC with all permissions to all applications. The root user is the actual Linux root user.
You should change the default passwords for the default users as soon as possible.
The default password for hscroot is abc123 and the default password for root is
passw0rd (where the 0 is a zero). Note that you cannot su to root from the HMC
command line.
Managing accounts
To add an account, use the User > Add menu option. To change an account, use the
User > Modify option. To change the accounts password, use the User > Modify
menu option.

Instructor Guide
The hscpe user

This user is created with the Service Representative authority for software fixes and
updates from your software support personnel. Support might need to log on to your
HMC using this username when analyzing a problem. Generally, this user is created
after the installation and setup of the HMC.

V5.3
Instructor Guide

Purpose Describe how accounts are created and maintained.
Details Describe how to add accounts and change passwords. When you add an
account you choose which predefined task role to use.
Additional information The HMC super user is hscroot rather than hmcroot because
the original name for the HMC was the Hardware System Console (HSC) but it was
changed before the product was first released.
Transition statement The next visual shows the window that opens when you click
User > Add on the menu.

Instructor Guide
Add an HMC user (1 of 2)

IBM Power Systems
Password cannot
be less than
Select type of seven characters
authentication
Select Managed Resource

Roles and one Task Role
Custom roles appear in these
lists
Figure 3-47. Add an HMC user (1 of 2) AN111.0
Notes:
Adding a user
This visual shows what happens when you click User > Add from the menu shown on
the previous visual. From here you can type in the user name, a password, and a short
description. You must also select one of the task roles and at least one resource role to
assign to the user account. The resource roles define which resources (such as which
partitions) that a user can perform tasks on, and task roles define the groups of tasks
that the user can perform. By default, there is only one resource role that includes all of
the resources. More than one Managed Resource Role can be selected but only one
Task Role can be selected. The default task roles are listed as follows.
Also you need to select the type authentication between local authentication, LDAP
authentication, or Kerberos authentication.

V5.3
Instructor Guide
Uempty Modifying a user

If you were modifying a user rather than adding a new user, this screen would show you
the current settings for this user by highlighting the task role and the managed resource
roles assigned to the user.
Task role descriptions

Following is a general description of the default task roles. New roles can be created if
the default roles do not meet your requirements. A user can have only one task role.
Service Representative (hmcservicerep)
A Service Representative is an IBM service representative who is at your location to
install or repair the machine.
It is strongly recommended that you create a user named hscpe with the Service
Representative authority for software fixes and updates from your software support
personnel. Support might need to log on to your HMC using this username when
analyzing a problem.
Viewer (hmcviewer)
A Viewer can view HMC information, but cannot change any configuration information.
Operator (hmcoperator)
An Operator is a user who is responsible for daily system operations. Tasks that an
operator cannot do include adding new users and changing the definitions of task roles.
Product Engineer (hmcpe)
A Product Engineer is someone who assists in support operations. The differences
between the Service Representative task role and the Product Engineer task role are
slight. For example, the Product Engineer can shut down the HMC and close virtual
terminal windows, whereas the Service Representative cannot.
Super Administrator (hmcsuperadmin)
The Super Administrator acts as the root user, or manager of the HMC system. The
Super Administrator has unrestricted authority to access and modify most of the HMC
system. The hscroot login account is set to have the hmcsuperadmin task role.
Default task roles definitions

To find out exactly what the default task roles are allowed to do, copy one of the task
roles and then modify the copy. In this way, you can list out the exact operations that a
user with this task role can perform. You must first make a copy because you cannot
modify a default task role. You can then delete the copy.
The default task role operations are also listed in the Information Center. Do a search
for HMC tasks to find this information.

Instructor Guide
Authentication methods
Users who remotely authenticate through Kerberos or LDAP must have their profiles set
appropriately. You must set the user profile of each remotely authenticated Kerberos or
LDAP user to use that type of authentication instead of local authentication. A user that
is set to use Kerberos or LDAP remote authentication will always use that type of
authentication, even when the user logs in to the HMC locally.
The use of Kerberos authentication requires configuration of a KDC server using the
KDC Configuration task. Use of LDAP authentication requires configuration of an
LDAP server using the LDAP Configuration task. You do not need to set all users to
use Kerberos or LDAP remote authentication.
If you select Local Authentication, type a password and a password confirmation in
the field provided. If you select Kerberos Authentication, type a Kerberos remote
userid. If you select LDAP Authentication, no additional information is required.

V5.3
Instructor Guide

Purpose Describe how to add accounts and change passwords.
Details When you add an account, you choose which predefined roles to associate with
that user account.
Review the default roles. Describe how to view the exact operations that each of these
default roles can perform. This is described in the student notes.
Transition statement The next page talks about the User properties window and the
remote access option.

Instructor Guide
Add an HMC user (2 of 2)

IBM Power Systems
Specify
timeout
values if
needed
Select Allow remote access

or youll get this message
Figure 3-48. Add an HMC user (2 of 2) AN111.0
Notes:
When you click User Properties from the previous visual, you reach this window where
you can specify special properties for the user you are managing. If you want to enable
remote Web server access for the user you are managing, select Allow remote access
via the Web or you will encounter the message Remote Access is Prohibited
when trying a remote login using this user.

V5.3
Instructor Guide

Purpose Show how to enable remote access via the Web for a specific user.
Details
Transition statement The next page is an overview of Resources and task roles
improvement with HMC V7.

Instructor Guide
HMC users: Resources and task roles example

IBM Power Systems
Resource role:
Selected resources Add user ID with
selected roles
Select the
Resource role
Task role:
Selected tasks Select the
Task role
User sees only the selected LPARs

and selected tasks for those LPARs
Figure 3-49. HMC users: Resources and task roles example AN111.0
Notes:
HMC version 7 offers improved Task, Resource, and User assignment configuration.
HMC version 7 can be configured so that users see only LPARs and Tasks that have
been allocated to them.

V5.3
Instructor Guide

Purpose
Details Quickly describe the different steps shown in that visual. Point out that the user
can only see the selected LPAR and associated tasks in the HMC when logged in.
Transition statement The next page talks about how to customize the task roles.

Instructor Guide
Task roles management

IBM Power Systems
Task roles define what tasks that an account can perform.

One role is assigned to each user account when the user account is
created.
Add new task roles to create custom task roles.
You can use the copy feature to copy a role, and then alter.
From HMC Management work pane, click Manage Task and
Resource Roles
Figure 3-50. Task roles management AN111.0
Notes:
Introduction
Each HMC user account must be assigned a task role when it is created. Each of these
roles allows the user to access different parts of the HMC or perform tasks on different
partitions.
You might want to add new user roles or to customize existing user-created roles. If you
do, remember that the changes occur only on the HMC where you did the
customization. If you want to customize the default roles, you will need to copy them
first, and then perform the customization on the copy.

V5.3
Instructor Guide

Purpose Discuss customizing the task roles.
Details Be sure to explain that we are talking about roles and not actual users on this
visual. When you create a user, for example called Fred, you pick one of these roles for
the user. You might never need to add new roles, but you can customize the list of
applications and commands a user account has access to by creating a custom role.
Transition statement Lets look at an example of adding a new task.

Instructor Guide
Add task role example

IBM Power Systems
Then create an HMC user

and associate with it this
task role: DLPAROperator
Figure 3-51. Add task role example AN111.0
Notes:
Introduction
The visual shows how to add a new custom task role. After clicking Add from the menu,
the Add Role window opens. Select one or more tasks in the Web User interface
permission menu from left side window and click the Add button to add them to the right
side window, which is what will be configured for this task role.
Users created with task roles that only allow them to do certain tasks will have only
those tasks presented to them in the menus when they are logged in. For example, if
the user is not allowed to shut down a partition, then that option does not display on the
HMC menus.

V5.3
Instructor Guide

Purpose Describe how to create a list of tasks when adding a new task role.
Details Show how to add a list of task roles
Point out that if you select a task role, then click Modify on the menu from the Customize
User Controls task, you can alter an existing user-defined task role. You cannot alter one
of the default predefined roles, but you can copy them and customize the copy.
Transition statement That was task roles. Now, lets look at managed resource roles.

Instructor Guide
Managed resource roles management

IBM Power Systems
Managed resource roles define the resources on which a user can

perform a task
For example, a user might only be allowed to perform tasks on a particular
managed system or partition
Unlike tasks roles, more than one managed resource role can be associated
with a user.
Add new managed resource roles to create custom roles
You can use the copy feature to copy a role, and then alter
From HMC Management work pane, click Manage Task and Resource
Roles
Example
custom
role
Figure 3-52. Managed resource roles management AN111.0
Notes:
Introduction
In the visual the Managed Resource Roles option has been selected; so the list of
current managed resource roles is listed.
A managed resource is a resource on which an action can be performed, such as a
partition or a managed system. In the visual above, you can see the one default
resource role is AllSystemResources. As an example, a custom resource role was
added called sys034_v2_T4.
You can create a managed resource role with multiple resources, and then add just one
named managed resource role to a user, or you can create separate, specific managed
resource roles, such as one per partition and managed system.
One HMC can be connected to up to 48 managed systems. You might want to create
users that can only perform operations on one or more managed systems. You will
need to create managed resource roles for the managed systems to accomplish this.

V5.3
Instructor Guide

Purpose Describe what a managed resource role is and that there is just one default
managed resource, which includes all resources available to this HMC.
Details Mention that one HMC can be connected to multiple managed systems. So you
might want to restrict operations on one or more managed systems to particular users.
Transition statement Lets see how to create a custom managed resource role.

Instructor Guide
Add managed resource role example

IBM Power Systems
Select a
managed system,
and then a
logical partition
Figure 3-53. Add managed resource role example AN111.0
Notes:
Introduction
Users created with managed resource roles that only allow them to have access to
certain resources will only have those resources available to them when they are
logged in. For example, if the user is only allowed to perform tasks on the LPAR
sys034_v2_T4, then the user will only be able to see sys034_v2_T4 when they log in
and select the Systems Management in the navigation pane.
The procedure for creating a managed resource role is similar to a task role. Click Add
on the Customize User Controls menu, type a new name, choose available objects
from the window on the left, then click the Add button to add them to the list of current
objects for this managed resource role.

V5.3
Instructor Guide

Purpose Describe how to create a managed resource role.
Details The procedure is similar to adding a task role.
Transition statement That is enough about users. You will be able to practice creating
roles in the hands-on exercise. Next, lets discuss ways to remotely access the HMC.

Instructor Guide
HMC remote access options

IBM Power Systems
2
SSH access
to HMC
HMC commands
Network
1
Windows,
Linux, or AIX
browser
Figure 3-54. HMC remote access options AN111.0
Notes:
Introduction
There are two options for accessing HMC functions remotely as listed in the visual
above.
Remote interface (1)

To access remotely an HMC running HMC Version 4, 5, or 6, a special client program
(WebSM) was required. WebSM is no longer required with HMC Version 7. Remote
access to an HMC running Version 7 requires only a standard (and supported) Web
browser.
HMC Version 7 is migrated to a new framework, the System z HMC framework. All
existing management functions and commands remain unchanged. However, there are
new user interface improvements and changes because of the new framework.

V5.3
Instructor Guide
Uempty A major change is the Web browser-based user interface. With this interface, you do
not have to install an application to access the HMC remotely, and you can connect to
the HMC using your browser. Firefox and Internet Explorer are supported.
SSH connection (2)

You can use a Secure Shell (SSH) connection directly to the HMC. When you log in,
you are given a restricted shell. Most partition management commands can be
executed using this restricted shell command line. There are also a limited number of
Linux commands available. Use the shell command echo $PATH after you log in to see
which directories are available. A listing of these directories will show the commands
available. To see usage information, run the commands with the --help option.
The SSH access feature is disabled by default. You can enable this from the HMC.
SSH installation options

On Windows PCs, you must have an SSH application loaded. Here is an example of a
Web page that has a free SSH application:
http://www.chiark.greenend.org.uk/~sgtatham/putty/
On AIX, you need both OpenSSL and OpenSSH. Install OpenSSL first from the AIX
Toolbox for Linux Applications for POWER Systems CD-ROM. Then install the
OpenSSH package, which is on the AIX Expansion Pack CD-ROM. Both of these
CD-ROMs are shipped with the AIX product media. For more information about how to
install and use the OpenSSH package, please refer to the Managing AIX Server Farms
IBM Redbook available from http://www.redbooks.ibm.com.
On Linux, SSH is generally installed by default in the Linux distribution.

Instructor Guide
Instructor notes:
Purpose Describe the HMC remote access options.
Details Describe each of the three options for accessing an HMC remotely. Notice the
two bubbles with the numbers 1 and 2 in them. These will be used on upcoming pages to
show that they refer back to one of the options introduced on this page.
The network cloud in the middle of the visual is an oversimplification of whatever the
network configuration might be.
Transition statement Lets look how to enable remote browser access from the HMC
Management Work pane tasks.

V5.3
Instructor Guide
Uempty
Enabling remote browser access

IBM Power Systems
Needs to be enabled using the physical HMC interface 1

HMC firewall port 443 enabled (secure remote Web access)
Note: There is no line-mode command to enable remote browser access.
Figure 3-55. Enabling remote browser access AN111.0
Notes:
To enable the HMC remote access:

Open the Remote Operation task from the HMC Management Work pane.
Select Enabled from the Remote Operation drop-down list, and then click OK.
The HMC can be accessed from a remote workstation using a Web browser.
All remote browser access to Version 7 of the Hardware Management Console must
use Secure Sockets Layer (SSL) encryption. With SSL encryption required for all
remote access to the Hardware Management Console, a certificate is required to
provide the keys for this encryption. Version 7 of the Hardware Management Console
provides a self-signed certificate that allows this encryption to occur.

Instructor Guide
Instructor notes:
Purpose
Details Mention to the students that we have seen in a previous slide the firewall
settings needed to allow remote Web connection. When enabling the remote Web
connection using the HMC Management task, the firewall settings are modified
accordingly.
Transition statement Lets see the browser requirements.

V5.3
Instructor Guide
Uempty
Remote HMC login: Browser requirements

IBM Power Systems
Connect via
https://<HMC hostname> or <HMC IPaddress>
The following browsers have been tested:
Mozilla Firefox 1.5.0.6 and later
Microsoft IE 6.0 and later
HTTP 1.1 settings

Must be enabled
If using a proxy server, HTTP 1.1 through proxy connect setting must also be enabled
In addition, HTML 2.0, JavaScript 1.0, Java (JVM), cookie support and
pop-ups must be enabled for all HMCs addressed in the browser
Session cookies need to be enabled for ASMI to work when connected to

HMC remotely
Figure 3-56. Remote HMC login: Browser requirements AN111.0
Notes:
Web browser requirements

Hardware Management Console Web browser support requires HTML 2.0, JavaScript
1.0, Java Virtual Machine (JVM), and cookie support in browsers that will connect to it.
Contact your support personnel to assist you in determining if your browser is
configured with a Java Virtual Machine. It is required that the Web browser uses the
HTTP 1.1 protocol and if you are using a proxy server, the HTTP 1.1 protocol is enabled
for the proxy connections. Additionally, pop-ups must be enabled for all Hardware
Management Consoles addressed in the browser if running with pop-ups disabled. The
following browsers have been tested:
Microsoft Internet Explorer 6.0 or later

If this browser is configured to use an internet proxy, then local intranet addresses
should be included in the exception list, consult your network administrator for more
information. If you still need to use the proxy to get to the Hardware Management

Instructor Guide
Console, enable Use HTTP 1.1 through proxy connections under the Advanced tab
in your Internet Options window.
Firefox 1.5.0.6 or later

For Firefox 2.0 make sure the JavaScript option to raise or lower windows and move or
resize existing windows is enabled. To enable this option, go to the Content tab in the
browsers Options dialog, click Advanced next to the Enable JavaScript option, then
select Raise or lower windows and Move or resize existing windows options, and
then click OK to enable. These features allow you to switch easily between HMC tasks
and to resize the task window.

V5.3
Instructor Guide

Purpose
Details
Transition statement Next, we will see how to execute HMC command-line commands
remotely. The first step is to enable the SSH login feature from the HMC. This is shown on
the next page.

Instructor Guide
Enable or disable remote options

IBM Power Systems
SSH to the HMC to perform management tasks remotely 2

HMC Management > Remote Command Execution
Must also open the HMC firewall for SSH access
Remote access to LPAR virtual terminals (consoles)

HMC Management > Remote Virtual Terminal
Figure 3-57. Enable or disable remote options AN111.0
Notes:
Enabling remote HMC commands (SSH)

Recall that the remote HMC commands allow you to perform many partition
management operations from a remote command line. From this secure shell, you can
execute remote HMC commands to do things like activate a partition or query its status.
By default, the HMC does not allow SSH sessions so you must enable this function
using the Remote Command Execution task from the HMC Management Work pane.
Select the check box labeled Enable remote command execution using the ssh
facility in the Remote Command Execution window.
Enabling remote virtual terminals

Another remote option available from the HMC Management Work pane is a tool that
allows you to enable or disable the ability to use remote virtual terminal windows to the

V5.3
Instructor Guide
Uempty partitions (that is, remote console windows). Simply click the Remote Virtual Terminal
task in the work area and select the Enable remote virtual terminal connections.
HMC command to see current remote settings

The lshmc -r HMC command will show the current remote settings on the HMC. For
example:
hscroot@sys046-hmc:~> lshmc -r
ssh=enable,sshprotocol=all,remotewebui=enable,xntp=disable,xn
tpserver=127.127.1.0,netboot=disable,altdiskboot=disable,ldap
=disable,kerberos=disable,kerberos_default_realm=,kerberos_re
alm_kdc=,kerberos_clockskew=,kerberos_ticket_lifetime=,kerber
os_keyfile_present=
There is a corresponding chhmc command to change options if you want to do this
from the command line. See the man pages on the HMC for details.

Instructor Guide
Instructor notes:
Purpose Describe how to enable or disable SSH access to the HMC and the ability to
bring up virtual console windows remotely.
Details The visual shows how to enable the SSH remote command function of the HMC
and enable remote virtual terminals. By default both of these are disabled.
Remind the students that they need to open the HMC firewall ports for SSH if they want to
use remote command execution using the ssh facility.
The bubble with the 2 at the top right of the visual shows that this refers to the second of
the two HMC Remote Access Options described on Figure 3-54. For SSH to the HMC
work, you must enable it here (and open up the port in the HMCs firewall).
Transition statement That is how you enable SSH access for command line access to
the HMC. Lets look at some HMC command examples.

V5.3
Instructor Guide
Uempty
Using HMC commands remotely

IBM Power Systems
Install SSH if necessary on client 2

Multiple ways to run commands using SSH
Single HMC command (you will be prompted for password)
$ ssh -l hscroot hmchost hmccommand
Alternative single HMC command syntax:
$ ssh hscroot@hmchost hmccommand
Log in to the HMC and execute commands in a shell
$ ssh -l hscroot hmchost
hscroot@hmchost's password:
Last login: Thu May 5 12:03:12 2008 from console
hscroot@hmcname:~> date
Thu May 5 12:04:21 PDT 2008
Figure 3-58. Using HMC commands remotely AN111.0
Notes:
HMC command line options

The visual shows how to use SSH from a remote command line, such as a Linux or AIX
shell. To run HMC commands remotely, you can either send one command to the HMC
as shown in the first example, or log in to the restricted shell using SSH and run any
number of commands. Exit out of the SSH shell when you are done. SSH encrypts
network communications for security.
On Microsoft Windows computers, there might be an application, such as the open
source PuTTY program, which provides SSH operations. PuTTY can be downloaded
from the http://www.chiark.greenend.org.uk/~sgtatham/putty/ Web site. When using
PuTTY for SSH communications, be sure to click the SSH button on the login screen
because telnet to the HMC is not allowed.

Instructor Guide
Instructor notes:
Purpose Describe how to use SSH.
Details The students will use the HMC commands extensively in the exercise for this
unit and in future exercises.
The date command is simply used here as an example to show that commands would be
typed at the HMC shell prompt.
This visual shows how to log in using SSH from a Linux or an AIX shell. On a Microsoft
Windows computer, it is likely that there is an application, such as PuTTY, which allows
SSH access.
The bubble with the 2 at the top right of the visual shows that this refers to the second of
the two HMC Remote Access Options described on Figure 3-54.
Transition statement Lets see some more HMC commands.

V5.3
Instructor Guide
Uempty
HMC commands
IBM Power Systems
Commands have --help option and man pages

Example commands:
Show processor usage by partition
$ lshwres -m msname -r proc --level lpar \
F lpar_name,run_procs --header
lpar_name,run_procs
LPAR1,0
LPAR2,1
LPAR3,0
Reboot the HMC immediately

$ hmcshutdown t now -r
Figure 3-59. HMC commands AN111.0
Notes:
HMC commands
When you have logged in you can execute the echo $PATH command to see which
directories are available to you in the HMCs restricted shell. You can only run the
commands in these directories and the shell commands are restricted as well.
List each of the directories listed in the echo $PATH output to see a listing of the
commands that are available. For usage information, run the commands with the --help
option or access the man pages. For example, man hmcshutdown will display the
manual page for that command. The man pages show more information than the --help
information.

Instructor Guide
Instructor notes:
Purpose Introduce HMC commands.
Details HMC commands will be mentioned as appropriate throughout this course. This
page illustrates how commands are executed.
Mention that if you leave the -r off of the hmcshutdown command that is shown on the
visual that the HMC will shut down without rebooting.
Ask the students: What would happen if you did the hmcshutdown command remotely
without the -r option? Answer: The HMC would shut down and because you are remote
you will not be able to boot it again. Someone local to the HMC will have to boot it. This is
an important point if the students are using lab equipment remote to the classroom.
Transition statement Lets look at some more details on the HMC shell environment.

V5.3
Instructor Guide
Uempty
SSH login environment on the HMC

IBM Power Systems
HMC provides restricted shell

SSH is a secure shell program.
It is the only remote login method to access HMC command line
Passwords and public key authentication in use
No way to escape from restrictions without contacting IBM technical
support for temporary root access
Example operations that are not allowed:
cd, redirection, su
Figure 3-60. SSH login environment on the HMC AN111.0
Notes:
Restricted shell environment

As SSH is the only remote login method, and the default shell startup files are copied at
each login, you get a restricted shell. This is true even if you bring up a shell on the
physical HMC. Users, even hscroot, cannot run the su command.
The only way to escape from the restrictions is to obtain access to the root shell. If
necessary, IBM Technical Support can supply a password that allows you to access a
shell where you can su to root. This is covered on the next visual.
Warning
The restricted shell controls are for the protection of the HMC environment. The
configuration of the HMC is much more complex than just a Linux system and if you
were able to alter system files, your HMC might become unusable and you will need to
reload the software.

Instructor Guide
Instructor notes:
Purpose Describe the restricted shell environment for users on the HMC.
Details SSH is the only way to remotely log in to the HMC. The physical HMC has a way
to bring out to a shell as well. Both are restricted shell environments. There is no way to
escape without contacting IBM technical support and obtaining temporary root access; this
is mentioned on the next page.
Transition statement Now that we know what we cannot do on the HMC, lets see
some of the things we can do.

V5.3
Instructor Guide
Uempty
HMC CLI: What is available then? (1 of 2)

IBM Power Systems
sed and scp are available

Can list out directories and cat files outside of $PATH
HMC commands allow you to manually run commands that
are in the Web browser user interface
You can write scripts
Commands have man pages
Temporary (1 day) root access can be obtained with IBM

approval
It requires a good reason and opening a call
You will need to create a service user named hscpe and retrieve HMC serial
number (lshmc v)
Figure 3-61. HMC CLI: What is available then? (1 of 2) AN111.0
Notes:
Introduction
You can edit files with sed and remotely copy files with scp. You can list the contents of
directories and cat files. You can list out directories if you know their names. Because
you cannot use the cd command, you need to provide full pathnames to explore the
system.
You can enable vi command line editing with the set -o vi command.
rnvi command
rnvi - HMC restricted-nvi text editor: rnvi enables users to edit a text file in a
restricted mode. The rnvi command invokes the nvi command in a chroot environment.
The rnvi command must be issued from the user's home directory and only one file can
be specified on the command line.

Instructor Guide
HMC commands
To list the commands that are available, use echo $PATH to see which directories are
available, then list the contents of each directory in turn. For example:
hscroot@sys046-hmc:~> echo $PATH
/hmcrbin/:/usr/hmcrbin
hscroot@sys046-hmc:~> ls /hmcrbin
cat cp date ls mount netstat ping sleep sort umount uname
The /usr/hmcrbin directory has many more commands specific to the HMC operations.
If you have to administer several managed systems, you can achieve consistent results
by using the command-line interface. The command sequence can be stored in scripts
and run remotely.
After you have developed a consistent way to manage the managed systems, you can
automate the operations by invoking the scripts from batch-processing applications,
such as the cron daemon, from other systems.
More information on commands in the Information Center

If you search for HMC tasks in the Information Center search window, you will see not
only the list of tasks each default task role can perform, but it also lists out the HMC
command that corresponds to each task. This is a nice reference.
Scripts with HMC commands

You can write scripts that contain ssh commands that run HMC commands. When you
run this script on a system, the ssh commands in the script run the HMC commands
remotely on the HMC. You will need to configure SSH between the remote system and
the HMC to allow for remote HMC commands without requiring the hscroot password.
An example line in a script might look like the following where lssyscfg is an HMC
command, hmcname is the HMCs hostname, and msname is the managed system
name:
ssh -l hscroot hmcname lssyscfg -r lpar -m msname -F state,lpar_id

V5.3
Instructor Guide

Purpose Describe some of the things that you can do from the HMC command line.
Details Describe how to see what HMC commands are available and that there are man
pages for them to provide syntax information and examples.
If asked about more details on creating scripts with HMC commands:
The student notes mention writing scripts to be run on the HMC and that you would
need to set up SSH so that there is no need to enter a password. This is in the student
notes in this course on page 3-159. A summary of the procedure is: An SSH key is
generated on the remote system, you copy the key list file from the HMC, append the
key, then you copy the key list file back to the HMC. When this is set up, you can run a
script from the remote system that contains ssh commands that run HMC commands
on the HMC.
Transition statement Lets see a few more options available from the HMC command
line.

Instructor Guide
HMC CLI: What is available then? (2 of 2)

IBM Power Systems
Can shut down or reboot HMC remotely from Web browser or

use command line.
Can open remote virtual terminals to partitions
Use mkvterm or vtmenu
mkvterm example:
Enter at mkvterm m managedsystem --id lparID

HMC shell
prompt
AIX Version 6
(C) Copyrights by IBM and by others 1982, 2007.
Console login:
Enter ~. to # ~.
end Terminate session? [y/n]
(can log out
first)
Figure 3-62. HMC CLI: What is available then? (2 of 2) AN111.0
Notes:
Remote HMC reboot

You can use the command line if you want to reboot the HMC remotely. We saw this
command earlier in this unit:
hmcshutdown -t now -r
With HMC version 7 you can also shutdown or restart it using Shut Down or Restart
task from the HMC Management Work pane.
Remote virtual terminals (partition consoles) with mkvterm command

You can open a remote virtual terminal to a partition with the mkvterm command. You
will be in a shell to the partition. When you are done, log out, and type ~. to end the
session and return to the HMC shell.

V5.3
Instructor Guide
Uempty An alternate syntax for the mkvterm command shown in the visual is as follows, where
managedsystem is replaced with the actual managed system name and lparname is
replaced with the partition name:
mkvterm -m managedsystem -p lparname
Closing a remote terminal

If a remote terminal to a partition is already open, you will receive an error. Use the
rmvterm command to remove that other connection so that you can make one.
Hopefully, someone is not actively using that other remote terminal.
Remote virtual terminals with vtmenu command

The vtmenu HMC command will list a menu of partitions for you to choose. After you
choose one, it opens a remove virtual terminal to that partition. Following is an example
command and its output where the user access the managed system sys034, the typed
in a 7 to open a terminal to sys034_v1_T2:
hscroot@sys03hmc:~> vtmenu
Retrieving name of managed system(s) . . .

----------------------------------------------------
Managed Systems:
---------------------------------------------------
1) sys036
2) sys034
Enter Number of Managed System. (q to quit): 2
----------------------------------------------------------
Partitions On Managed System: sys034
OS/400 Partitions not listed
----------------------------------------------------------
1) abelpar Not Activated
2) testg Not Activated
3) sys034_nfsserver Not Activated
4) sys034_v2_T4 Not Activated
6) sys034_v2 Not Activated
7) sys034_v1_T2 Running
8) sys034_v1_T1 Open Firmware
9) sys034_v1 Running
Enter Number of Running Partition (q to quit): 7

Instructor Guide
Opening Virtual Terminal On Partition sys034_v1_T2 . . .
Open in progress..
Open in progress
Open Completed.
AIX Version 6
Console login:
login: root
root's Password:
(Note that the user can type ~. at the password prompt or at the shell prompt. In this
case the user typed it at the password prompt.)
Terminate session? [y/n]
Hit <Enter> To Continue, q to quit:

----------------------------------------------------------
Partitions On Managed System: sys034
OS/400 Partitions not listed
----------------------------------------------------------
1) abelpar Not Activated
2) testg Not Activated
3) sys034_nfsserver Not Activated
6) sys034_v2 Not Activated
7) sys034_v1_T2 Running
8) sys034_v1_T1 Open Firmware
9) sys034_v1 Running
Enter Number of Running Partition (q to quit): q
Bye.
hscroot@sys03hmc:~>

V5.3
Instructor Guide

Purpose Describe how to reboot the HMC remotely and how to create a virtual terminal
to a partition from the command line.
Details The student notes also mention the rmvterm command to remove other remote
virtual terminals. Make sure students do not confuse this with using the ~. to close the
current virtual terminal session.
Transition statement That is the HMC command line environment. You will have lots of
practice with the HMC commands in the lab. Next, lets talk about security issues.

Instructor Guide
Remote access security overview

IBM Power Systems
Review:
HMC and service processor use SSL for secure communications
HMC users and tasks are unique to each HMC
HMC firewall options on the Ethernet interface
Restricted SSH for HMC command line access
SSH and remote console access can be disabled or enabled
Secure remote web access can be disabled or enabled
Additional security topics:
Virtual console communications
SSL encrypted when using remote Web connection
Uses SSL also when using the physical HMC
Can configure HMC access without a password
Web browser to HMC communications
SSL encrypted by default
Certificate authority is issued by the HMC (self signed certificate)
Can create a new self-signed certificate or a certificate signed by a trusted
third party
Figure 3-63. Remote access security overview AN111.0
Notes:
HMC and managed system use SSL

The HMC to service processor private network uses SSL for a secure connection. For
SSL, we need userids and passwords on the service processor and there are default
userids admin and general already set up, and an additional HMC userid when HMC is
connected.
The service processor issues the SSL certificate and this SSL connection is established
when the managed server is added to the HMC. When you connect the HMC to the
managed system and apply power, and the state of the managed system is Pending
Authorization, click the managed system name and you will be prompted to set up the
three passwords. Be sure to document these in a safe place.

V5.3
Instructor Guide
Uempty HMC login without passwords

If you create scripts that must log in to the HMC, then you might need to set up SSH
access to the HMC without a password. The remote system must have SSH installed.
An SSH key must then be generated and exchanged with the HMC. Here is an example
set of commands.
1) On the remote system, run this command (as root) to generate the SSH key.
Use all the defaults for the questions.
# ssh-keygen -t rsa
2) Next, exchange the SSH keys with the HMC. Run these commands from the
remote system:
# scp hscroot@hmchostname:.ssh/authorized_keys2 \
~/.ssh/tmp_authorized_keys2
# cat ~/.ssh/id_rsa.pub >> ~/.ssh/tmp_authorized_keys2
# scp ~/.ssh/tmp_authorized_keys2 \
hscroot@hmchostname:.ssh/authorized_keys2
3) Test the SSH access to the HMC. You should not be asked for a password if
it is configured correctly; however, the first time you try this, you might be
prompted to allow the key exchange and you should answer yes.
# ssh hscroot@hmchostname lssyscfg -r sys

Instructor Guide
Instructor notes:
Purpose Review HMC security issues.
Details The review list at the top are items we have discussed already in this course.
They are listed here to provide a quick review and to put all security items in one list for
reference.
The last two are discussed in more detail in the following pages.
Transition statement Lets see the SSL certificate when connecting to the HMC from a
remote Web browser.

V5.3
Instructor Guide
Uempty
Browser access: SSL security

IBM Power Systems
By default, the SSL

certificate is issued by
the HMC.
Administrator can
import certificates
from a CA.
Logon button is
disabled until
certificate is loaded.
Figure 3-64. Browser access: SSL security AN111.0
Notes:
SSL Certificate
When you first connect to the HMC, an SSL certificate is issued, which must be
accepted. Additional certificates can be imported from a Certification Authority (CA).
Security certificates ensure that the HMC can operate securely in the client-server
mode. The managed machines are servers and the managed users are clients. Servers
and clients communicate over the Secure Sockets Layer (SSL) protocol, which provides
server authentication, data encryption, and data integrity.
When a user wants remote access the HMC user interface through a Web browser, the
user requests the secure page by https://hmc_hostname. The HMC then presents its
certificate to the remote client (Web browser) when establishing connection with the
HMC. The browser verifies that the certificate was issued by a trusted party, check that
the dates are still valid, as well as making sure that the certificate was created for that
specific HMC.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Lets see how to secure HMC remote connections by managing
certificates.

V5.3
Instructor Guide
Uempty
HMC management: Manage certificates

IBM Power Systems
To secure HMC remote connections

Manage certificates under the Administration tab of the HMC
management
HMC needs to be
Create a new self-signed certificate
rebooted for the new
. certificate to take effect
Figure 3-65. HMC management: Manage certificates AN111.0
Notes:
HMC security management has changed from earlier versions of the HMC. Most
options under System Manager Security are no longer needed in Version 7.3. Object
Manager and Server Security are now gone. The new option for securing HMC remote
connections is Manage Certificates under the Administration tab of HMC
Management.
Certificates management
The available options in Manage Certificates allow you to create, modify, import, and
remove certificates. There are a couple of notable changes from earlier HMC versions
in HMC V7R3. Remote access is now available through a Web browser. Previous
versions used WebSM remote client. Another notable change in certificate
management is that HMC V7 does not allow a public or private key ring file to be
created.
The Hardware Management Console provides the capability of getting information on
the certificates used on the console. This task allows you to create a new certificate for

Instructor Guide
the console, change the property values of the certificate, and work with existing and
archived certificates or signing certificates.
To manage your certificates, open the Manage Certificates task from the HMC
Management Work pane. Use the menu bar from the Certificate Management window
for the actions you want to take with the certificates.
To create a new certificate for the console, click Create, then select New Certificate.
Determine whether your certificate will be self-signed or signed by a Certificate
Authority, and then click OK.
To modify the property values of the self-signed certificate, click Selected, then select
Modify. Make the appropriate changes, and then click OK.
To work with existing and archived certificates or signing certificates, click Advanced.
Then you can choose the following options:
Delete existing certificates.
Work with archived certificates.
Import certificates.
View issuer certificates.
Click Apply for all changes to take effect.

V5.3
Instructor Guide

Purpose
Details
Additional information HMC security management has changed from earlier versions
of the HMC. Most options under System Manager Security are no longer needed in Version
7.3. Object Manager and Server Security are now gone. The new option for securing HMC
remote connections is Manage Certificates under the Administration tab of HMC
Management.
Transition statement Lets have a quick overview of IVM.

Instructor Guide
Integrated Virtualization Manager

IBM Power Systems
What does IVM do?

IVM is a simplified HMC within a partition
It was developed to provide a simple environment
A single control program has the ownership of the physical
hardware
Other LPARs use it to access resources
IVM uses a predefined default partition

The Virtual I/O Server manages the system partitioning:
VIOS is installed using standard AIX installation methods
Dynamic CPU and memory reconfiguration is allowed when
installation is complete
Auto started at system power-on
VIOS can update the system firmware
Figure 3-66. Integrated Virtualization Manager AN111.0
Notes:
Introduction
IVM is a simplified hardware management solution that inherits most of the HMC
features. It manages a single server, avoiding the need of an independent personal
computer. It is designed to provide a solution that enables the administrator to reduce
system setup time and to make hardware management easier, at a lower cost.
IVM provides a management model for a single system. (If we want to manage multiple
systems from a unique point of control, the HMC will be needed.) Although it does not
offer all of the HMC capabilities, it enables the exploitation of IBM Virtualization Engine
technology. IVM targets the small and medium systems that are best suited for this
product.
IVM is an enhancement of the Virtual I/O Server (VIOS), the product that enables I/O
virtualization in System p processor-based systems.
So, the first operating system to be installed must be the VIOS.

V5.3
Instructor Guide
Uempty The VIOS is automatically configured to own all of the I/O resources and it can be
configured to provide service to other LPARs through its virtualization capabilities.
Therefore, all other logical partitions (LPARs) do not own any physical adapters and
they must access disk, network, and optical devices only through the VIOS as virtual
devices.

Instructor Guide
Instructor notes:
Purpose Introduce IVM
Details IVM provides an interface to many of the partitioning and virtualization functions
that previously have required an HMC. For clients planning to consolidate their workloads
onto a POWER5 or POWER6 processor-based server, an HMC may be cost prohibitive,
particularly for smaller to mid-sized companies or larger businesses with distributed
environments.
It is a good time to recall that IVM has been an enhancement to the VIOS since version 1.2.
At time of writing, the current version of the Virtual I/O Server 1.5, comes with several IVM
improvements, such as dynamic LPAR-capability of the client LPARs, security
improvements (firewall, vio secure), usability additions (TCP/IP GUI configuration,
hyperlinks, simple LPAR creation, task monitor, and so on), and other improvements.
Additional information Because the IVM and HMC both provide management
capabilities, they cannot be used in conjunction with one another to manage the same
server.
Transition statement Lets have a look now at the IVM architecture.

V5.3
Instructor Guide
Uempty
The IVM architecture

IBM Power Systems
IVM manages power, partitions, and virtualization using Hypervisor

IVM does not interact with the systems service processor
IVM requires management access to the Hypervisor through a specific virtual
I/O device called Virtual Management Channel (VMC)
Figure 3-67. The IVM architecture AN111.0
Notes:
Introduction
To set up LPARs, the IVM requires management access to the Hypervisor. It has no
service processor connection and it relies on a new virtual I/O device type called Virtual
Management Channel (VMC). This device is activated only when VIOS installation
detects that the environment has to be managed by IVM.
VMC is present on VIOS only when the following conditions are true:
The virtualization feature has been enabled.
The system has not been managed by an HMC.
The system is in Manufacturing Default Configuration.
On a VIOS partition with IVM activated, a new ibmvmc0 virtual device is present and a
management Web server is started listening to HTTP port 80 and to HTTPS port 443.
(The presence of the virtual device can be detected using the lsdev -virtual command
from the VIOS partition.)

Instructor Guide
Because IVM relies on VMC to set up logical partitioning, it can manage only the
system on which it is installed. The primary user interface is a Web browser that
connects to port 80 of the VIOS.
IVM can use only one VIOS to manage the system. This is in contrast with the
HMC-managed mode where two (or multiple) VIOSs can be created and installed,
adding security and redundancy to the LPARs activities.

V5.3
Instructor Guide

Purpose Describe IVM architecture
Details Do not spend a lot of time explaining the architecture. This is just an overview.
The HMC uses the flexible service processor (FSP) to interact with the Hypervisor; there is
no link between the IVM and the FSP.
Transition statement IVM and the managed system: the big picture

Instructor Guide
The big picture with IVM

IBM Power Systems
Public Ethernet
LAN
LAN/ /WAN
WAN
Managed system
VIO server
AIX Linux IVM WEB browser: IVM GUI

Web server
VMC
Hypervisor
Non-Volatile RAM
Service
Processors processor
Memory
LPAR
I/O Slots
allocation
tables
Figure 3-68. The big picture with IVM AN111.0
Notes:
Introduction
The tight relationship between the Virtual I/O Server and IVM enables the administrator
to manage a partitioned system without the HMC. The software that is normally running
on the HMC has been reworked to fit inside the Virtual I/O Server, reducing its functions
to those required by the IVM configuration model.
The VIOS partition owns all of the physical I/O resources; all I/Os are virtualized
through the VIOS. VIOS provides virtual SCSI, virtual optical, and Shared
Ethernet Adapter support to the client partitions, which enables a client partition
to run with no physical I/O devices. Other partitions are configured to use only
virtual devices.
The VIOS partition owns only a portion of the memory and processing resources.
Client partitions can be created using the IVM Graphical User Interface, or using
the Command Line Interface. Those two user interfaces are running on the
Virtual I/O Server partition. Processing and memory resources allocated to a

V5.3
Instructor Guide
Uempty client partition are assigned directly by the POWER Hypervisor to these client
partitions.
User interfaces
The IVM provides both a browser-based graphical interface and a command line
interface.
The graphical interface provides an intuitive, easy-to-use method to configure
and manage the system. Because it is browser-based, the only client
requirement is a computer with a Web browser that has network access to the
VIOS partition. This Web interface is built on top of the command line interface
and provides access to all commonly used partitioning, virtual I/O, and service
commands.
The command line interface has a similar syntax to the HMC command line
interface. It requires an interactive console, Telnet, or SSH session be
established with the VIOS partition.

Instructor Guide
Instructor notes:
Purpose
Details The HMC uses the flexible service processor to interact with the Hypervisor;
there is no link between the IVM and the FSP.
Transition statement Lets see the IVM Web interface.

V5.3
Instructor Guide
Uempty
IVM LPAR management: Common Web interface

IBM Power Systems
The IVM Web server provides a simple GUI

From any Web browser: http://<IVM address>
Figure 3-69. IVM LPAR management: Common Web interface AN111.0
Notes:
On a VIOS partition with IVM activated, a management Web server is started listening
to HTTP port 80 and to HTTPS port 443.
So, the IVM GUI is accessible from a Web browser connected to the VIOS.
At the installation time, the default user ID is padmin. The default password is padmin,
but we recommend that you change it.

Instructor Guide
Instructor notes:
Purpose Describe the IVM login GUI
Details At installation time, a TCP/IP interface is not automatically configured on VIOS.
The configuration should be done from the VIOS console to allow access to the IVM GUI
through the assigned HTTP/HTTTPS ports.
Details
Transition statement Lets see the Welcome screen when logged in.

V5.3
Instructor Guide
Uempty
IVM administration from GUI

IBM Power Systems
IVM welcome panel
Work
area
Navigation
area
Figure 3-70. IVM administration from GUI AN111.0
Notes:
After the authentication process, log in and the default IVM console window opens. The
IVM GUI is composed of several elements:
Work area: The work area contains information related to the management tasks
that you perform using the IVM and to the objects on which you can perform
management tasks.
Navigation area: The navigation area displays the tasks that you can access in
the work area.
Task area: The task area lists the tasks that you can perform for items displayed
in the work area. (The tasks listed in the task area can change depending on the
page that is displayed in the work area, or even depending on the tab that is
clicked in the work area.)
The main task area enables Partition management, Virtual Ethernet management, IVM
management, and Services management.

Instructor Guide
Instructor notes:
Purpose Point out that the IVM GUI provides the same features that are provided by the
HMC.
Details When using the IVM GUI, it is easy to create and manage a partitioned system,
because most of the complexity of the LPAR setup is hidden. A new user can quickly learn
an effective methodology to manage the system. However, it is important to understand
how configurations are applied and can be changed. The VIOS is the only LPAR that is
capable of management interaction with the Hypervisor and is able to react to hardware
configuration changes. Its configuration can be changed dynamically while it is running.
The other LPARs do not have access to the Hypervisor and have no interaction with IVM to
be aware of possible system changes.
Transition statement Lets review the topic.

V5.3
Instructor Guide
Uempty
Lets review Topic 2

IBM Power Systems
1. Which of these statements about HMC users are true?

a. When you create an HMC user, it exists only on that HMC.
b. Task roles describe the procedures that users can perform.
c. You can set multiple task roles and multiple managed resource roles for a user.
d. A user with a custom task role can be created, which allows the user to access
only the HMC command line and not the Web browser user interface.
2. List HMC remote access options.
3. What must be configured to provide SSH access to the HMC command

line?
4. True or False: The communication between a remote Web browser and

the HMC is SSL encrypted by default.
Notes:

Instructor Guide
Instructor notes:
Purpose Check the students understanding of the material in this topic.
Details Lets Review solution:

IBM Power Systems

c. You can set multiple task roles and multiple managed resource roles
for a user.
d. A user with a custom task role can be created, which allows the
user to access only the HMC command line and not the Web
browser user interface.

Remote Web connection, SSH login

line?
Open firewall, enable SSH access from HMC Management Work
pane, install SSH on client
4. True or False: The communication between a remote Web browser and the
HMC is SSL encrypted by default.
Transition statement Now, lets answer some Checkpoint questions about the entire
unit.

V5.3
Instructor Guide
Uempty
Checkpoint (1 of 2)
IBM Power Systems
1. Which of the following statements are true?

a. When you apply power to the managed system, the service processor
searches for a DHCP server for its IP address.
b. If it does not find a DHCP server, it waits for one to contact it.
c. The IP address for the service processor can be set to any valid IP address.
d. The network configuration for the service processor can be changed in the
ASMI application.
2. True or False: An important part of setting up the managed system

connection to the HMC is to not apply power to the managed system
until the HMC is configured.
3. True or False: The virtual console communications are encrypted.
4. How do you reboot the HMC remotely?
Notes:

Instructor Guide
Instructor notes:
Purpose Review the concepts in this unit.
IBM Power Systems

c. The IP address for the service processor can be set to any valid IP
address.
d. The network configuration for the service processor can be changed in
the ASMI application.


Use the Shutdown or Restart task from the HMC Management
work pane or log in with SSH to the HMC command line and type
hmcshutdown r t now
Transition statement There is one more page of Checkpoint questions.

V5.3
Instructor Guide
Uempty
Checkpoint (2 of 2)
IBM Power Systems
5. What is the difference between a user account and a task role?
6. Besides the firewall options, what are the remote access options that
can be enabled or disabled on the HMC version 7?
7. True or False: The HMC can be used as a fully functional Linux

system.
Notes:

Instructor Guide
Instructor notes:
Purpose Review the concepts in this unit.
IBM Power Systems

A user account is used to log in. A task role is a predefined set
of access rights.
Remote virtual console, SSH access, remote Web connection

system. The HMC allows only restricted shell access to a
reduced set of Linux commands.

V5.3
Instructor Guide
Uempty
Exercise
IBM Power Systems
Unit
exerc
ise
Notes:

Instructor Guide
Instructor notes:
Details Review the major activities in the exercise for this unit.

V5.3
Instructor Guide
Uempty
Unit summary
IBM Power Systems

Describe the new HMC V7 Web-based management console
and Web user interface (WUI) structure
Reboot the HMC
Create HMC users
Notes:
The HMC is a separate system that is required to create and manage partitions
The HMC is connected to one or more managed systems with an Ethernet connection
The Guided Setup wizard can be used to set up a new HMC
- Including users, date/time, and the network configuration
HMC menus allow you to configure the HMC and manage partitions and managed
systems
- Including access to the partitions consoles and service tools
Remote access options allow you to use the HMC from the network
- Web connection and command line options
- Communications are SSL encrypted by default

Instructor Guide
Instructor notes:
Purpose Review the objectives of the unit.
Details Ask the students if they felt they met these objectives and ask if there are any
more questions.
1) What actions must you take to allow SSH traffic to the HMC?
Answer: You must enable the Remote Command Execution option. You must also open the
firewall to allow SSH on the HMCs network adapter.
2) What options are available to access the HMC remotely?
Answer: SSH and a remote Web browser connection
3) Which interface on the HMC should have the Partition communications check
box selected if the HMC is connected on a private network with its first Ethernet port
and an open network on its second Ethernet port?
Answer: Assuming the partitions are on the open network, the second Ethernet port on the
open network should have the check box selected.
4) If the HMC is connected on a private network with its first Ethernet port and an
open network on its second Ethernet port, on which interface do you enable the
DHCP server?
Answer: Enable the DHCP server on the interface on the private network.
5) How do you reboot the HMC?
Answer: There are two ways. Using the HMC Management Work pane and by selecting
Shut Down or Restart task or you can also use SSH to log in remotely and type the
hmcshutdown -t now command.
Transition statement Unit 4 will cover the power on and off procedures for the
managed system.

V5.3
Instructor Guide
Uempty Unit 4. System Planning Tool
Estimated time
00:30

This unit describes the procedures for performing maintenance tasks
on the HMC and the managed system.

Use the System Planning Tool (SPT) to plan resource
configurations

Accountability:
Checkpoint
Hands-on lab exercise
References
IBM PowerVM Web portal:
http://www-03.ibm.com/systems/power/software/virtualization/index.html
IBM Technical Support Web sites:
http://www-304.ibm.com/systems/support/
Copyright IBM Corp. 2009 Unit 4. System Planning Tool 4-1

Instructor Guide
Unit objectives
IBM Power Systems

configurations
Import and deploy a system plan on the HMC
Generate a system plan from the HMC
Convert a system plan file to the SPT format for

modification
Notes:
Introduction
This unit discusses the System Planning Tool, how to create a system configuration,
and how to import and deploy a system plan on the HMC. It also describes how to
generate a system plan from the HMC as well.

V5.3
Instructor Guide

Details Explain what we will cover and what they should be able to do by the end of the
unit.
Transition statement We will start this unit by discussing the System planning tool.

Instructor Guide
IBM System Planning Tool overview

IBM Power Systems
SPT is a PC-browser based application used for the system

planning and configuration
Obtain SPT from:
https://www-304.ibm.com/systems/support/tools/systemplanningtool/
Download and install to your PC
Output from SPT:

The sysplan file can be used by the HMC to configure partitions
The cfr file can be used by eConfig to order a system
Figure 4-2. IBM System Planning Tool (SPT) overview AN111.0
Notes:
Introduction
The IBM System Planning Tool is the next generation of the IBM LPAR Validation Tool
(LVT) and replaced LVT in October 2006. It contains all of the function from the LVT and
is integrated with the IBM Systems Workload Estimator (WLE). System plans generated
by the SPT can be deployed on the system by the Hardware Management Console.
The SPT is available to assist the user in system planning, designing, documenting,
and providing a system validation report that reflects the users system requirements
while not exceeding system recommendations.
The SPT is a PC-based browser application designed to be run in a stand-alone
environment. Complete information, documentation, release notes, self-paced
education, and the tool source can be found on the Web site mentioned in the visual.
With SPT version 3.0 and later, you can include configuration specifications for the
following components of a Virtual I/O Server logical partition in your system plan:

V5.3
Instructor Guide
Uempty Backup virtual Ethernet adapters

EtherChannel or Link aggregation devices
Shared Ethernet adapter failover
Shared Ethernet adapters
Virtual Ethernet adapter mappings between the Virtual I/O Server and its client
logical partitions
Virtual Ethernet adapters
Virtual LANs
Mirroring
Multi-path I/O
SAN volumes
Storage pools (Volume groups)
Virtual SCSI adapter mappings between the Virtual I/O Server and its client
logical partitions
Virtual SCSI adapters
With SPT version 3.0 and later, you can include AIX and Linux installation information
for client logical partitions in the system plan.
Installing and running

Download the installation files from the Web site shown in the visual. Execute the
downloaded file to install the SPT tool. Updates to the software might be on this site.
After installation you will have an icon on your desktop named IBM System Planning
Tool. Simply double-click the icon to start the SPT application.
The following set of visuals will show and describe the features of version 3.08.095 of
the tool, which was released in April 2008.
Functions
The System Planning Tool helps you design a system to fit your needs. You can use the
SPT to design a logically partitioned system or you can use the SPT to design an
unpartitioned system. You can create an entirely new system configuration, or you can
create a system configuration based upon any of the following items:
Performance data from an existing system that the new system is to replace
Performance estimates that anticipates future workloads that you must support
Sample systems that you can customize to fit your needs

Instructor Guide
Integration between the SPT and both the Workload Estimator and IBM Performance
Management (PM) allows you to create a system that is based upon performance and
capacity data from an existing system or that is based on new workloads that you
specify.

V5.3
Instructor Guide

Purpose Explain the benefits of the SPT tool and how to load and run it.
Details The SPT is better than flat-worksheets because it gives you error messages
along the way and prints out a list of feature codes needed for the configuration.
Transition statement Lets overview the LPAR planning process.

Instructor Guide
SPT and system plan deployment

IBM Power Systems
Requirements
Requirements
Requirements eConfig
SPT version 3
system delivery
sysplan file
System
operator
system plan
deployment
Define OS
resource for
LPAR installation
during sysplan
deployment
Figure 4-3. SP Tool and system plan deployment AN111.0
Notes:
The process involved in planning for a system with logical partitions can get quite
involved. If the system has not been ordered, there should be steps that collect
requirements for the new system as well as steps to select hardware, software, and
which partitions will be created with what resources. Then the plan should be ordered
and, after the hardware arrives, the plan should be deployed. The whole process is
shown in the figure.
e-Config
You can export the system-plan file from the System Planning tool as a configuration file
with the extension .cfr. Then, you can import this file into the IBM marketing tool for
hardware and software ordering (also referred as e-Config). The SPT can create a
configuration file (.cfr) that can be imported to the IBM sales configurator tool.

V5.3
Instructor Guide
Uempty System plan

System plan deployment leverages the output of the System Planning Tool to automate
initial partition configuration upon system setup. Utilization of both system planning and
deployment capabilities can improve productivity and help assure a workable
configuration. System Planning Tool V3 and HMC V7 support of configuration and
deployment of IBM System p AIX, Virtual I/O Server, and Integrated Virtualization
Manager partitions.

Instructor Guide
Instructor notes:
Purpose Explain the LPAR planning process.
Details
Transition statement Lets look at starting SPT and beginning a sample configuration
example.

V5.3
Instructor Guide
Uempty
SPT: Launch
IBM Power Systems
Start SPT from the desktop
Figure 4-4. SPT: Launch AN111.0
Notes:
Starting a new configuration

The first window that displays when you run the SPT tool allows you to work with an
existing plan or create a new one. Choose the circled options on the visual to create a
new plan.
Choose a plan name, description and use the menus to pick the platform and the
system machine type and model. Click the Next button to proceed.
Self-paced training and demo

A self-paced training session with complete details on the usage of the SPT is on the
Web site mentioned in the previous visual.

Instructor Guide
Instructor notes:
Purpose Describe how to start a new configuration with SPT and enter the system-wide
information.
Details Enter the machine type model and system information for this system.
Transition statement On the next page, enter the processor specifics and more details
on the configuration.

V5.3
Instructor Guide
Uempty
SPT: System attributes

IBM Power Systems
Processor
Features
Figure 4-5. SPT: System attributes AN111.0
Notes:
System attributes
On this page, shown in the visual, enter the processor feature. This feature gives you
the number of processors and the minimum and maximum memory you can configure
on your system.
Click the Next button to proceed.

Instructor Guide
Instructor notes:
Purpose Describe how to enter the rest of the information about the planned system.
Details Describe how to select the processor features.
Transition statement Lets look disk and backplane configuration.

V5.3
Instructor Guide
Uempty
SPT: DASD/Media backplane

IBM Power Systems
Figure 4-6. SPT: DASD/Media backplane AN111.0
Notes:
Backplane
The system we selected comes with a choice of Backplanes; we need to specify the
Backplane we want our system to use.
After you select a Backplane in the System Wizard, that Backplane is set for this plan. If
you have to change the Backplane after the Wizard completes, you will need to create a
new plan.
Choosing either the 8345 or 8346 backplane allows for a split backplane on the Power
520 and Power 550. In addition, a cable is required to tie two of the SAS disks to a PCI
card. That cable is FC 3669 on the 550 and 3670 on the 520. For more information,
refer to TechDoc TD104556.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Lets look the system partition and operating system
configuration page.

V5.3
Instructor Guide
Uempty
SPT: System Partitions definition

IBM Power Systems
Figure 4-7. SPT: System Partitions definitions AN111.0
Notes:
Enter partition configurations

On this page, add the required logical partition and adjust the partition names, ID,
operating system types, and other partition configuration, such as Availability Priority
values.
Click the Next button to continue.

Instructor Guide
Instructor notes:
Purpose Describe how to enter partition information for the planned system.
Details Each row represents a partition. When added each can be adjusted to meet the
needs.
Transition statement Now lets look at the processors configuration for each logical
partition.

V5.3
Instructor Guide
Uempty
SPT: Processors
IBM Power Systems
AIX licenses
required
Activate additional
shared pools
Figure 4-8. SPT: Processors AN111.0
Notes:
Enter Processors distribution among partitions

On this screen, specify for each partition, the processor type (Shared or Dedicated), the
processing units values, the Sharing Mode (Idle sharing, Uncapped and the weight) and
the virtual processors configuration. The number of AIX licenses needed for the
partition processors configuration is displayed. The number of AIX licenses required
can also be recalculated after any configuration value modification.
You can also specify to activate one or more Shared Processor Pools and assign logical
partitions to them.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Now lets look at the memory page.

V5.3
Instructor Guide
Uempty
SPT: Memory
IBM Power Systems
Hypervisor
memory is
computed
Figure 4-9. SPT: Memory AN111.0
Notes:
System memory
This page is where the minimum, desired, and maximum memory values are set for
each partition. Notice the unassigned memory information. The Hypervisor memory
will be recalculated based on partition configurations.

Instructor Guide
Instructor notes:
Purpose Describe how to fill in memory requirements.
Details Describe the fields to be filled in on the screen shown.
In previously released versions of the SPT, the Memory tab focused on the number of
virtual I/O slots for which you want to reserve system memory. You no longer need to work
with virtual adapters and slots configuration during this step. In the new version of the SPT
slots are automatically mapped and created as you configure your network (virtual
Ethernet), storage (virtual SCSI), and Consoles (virtual serial).
The Hypervisor memory (MB) field displays an estimate of the memory that is to be used by
the system firmware (in megabytes). This estimate is calculated based upon the current
system configuration, and assumes that all I/O connections to the system are to be used.
Transition statement This next page shows a summary of the System configuration.

V5.3
Instructor Guide
Uempty
SPT: System Summary

IBM Power Systems
Figure 4-10. SPT: System Summary AN111.0
Notes:
Planned system information

This page summarizes the information you have entered so far. It displays the
Type-model you have specified, the number of processors, the amount of memory and
the different logical partitions. Click Finish to move to the next phase where you define
the hardware devices, the network, the virtual storage configurations you want for each
logical partition.

Instructor Guide
Instructor notes:
Purpose Show the summary screen with planned system information.
Details Check the summary information and click Finish to work with your planned
system and specify logical partitions adapters configuration.
Transition statement The next window is used to finalize the planning configuration by
assigning hardware to the various adapters in the system.

V5.3
Instructor Guide
Uempty
SPT: Working with the Planned Systems

IBM Power Systems
When the system is defined, edit it to assign physical

devices, network, virtual storage, and so on
Figure 4-11. SPT: Working with the Planned Systems AN111.0
Notes:
Placing hardware
This visual shows that the system is not complete. Note the Additional
configuration is required message in the status column. This indicates that
further configuration is required before this is a valid system configuration.
Click Edit to move to the final screens where hardware devices, disks, network virtual
storage, and operating system informations can be specified.

Instructor Guide
Instructor notes:
Purpose This is the end of the basic system creation section and the beginning of the
device configuration section.
Details Point out and describe the Additional configuration is required
message and the Edit option.
Transition statement The next screen displayed allows the assignment of the rest of
the system devices.

V5.3
Instructor Guide
Uempty
SPT: Assigning hardware devices

IBM Power Systems
Assigned to the
Click Add
Select partition when
the added
physical
adapter
Figure 4-12. SPT: Assigning Hardware devices AN111.0
Notes:
Final configuration
In this window, you can work with the various system components and expansion units.
In the first list near the top of the screen, select the unit to be worked with and assign
the various devices, such as storage devices, physical disk, CD or DVD devices, and
network devices. Then move on to the rest of the units in the list by clicking Actions >
Work with system/expansion units.
When the hardware configuration is defined, click the Networking tab.

Instructor Guide
Instructor notes:
Purpose Describe the configuration where the devices are added to the system.
Details The complete details of adding devices can be found in a short Web-based
class found on the SPT Web site.
http://www.ibm.com/servers/eserver/support/tools/systemplanningtool
Transition statement Lets move to the Networking tab.

V5.3
Instructor Guide
Uempty
SPT: Networking
IBM Power Systems
Click Add to Select

add VLAN physical
adapter
Shared Ethernet
Adapter
Configuration
Figure 4-13. SPT: Networking AN111.0
Notes:
Use this page to map your logical partitions to a virtual Ethernet. When you associate a
logical partition with a corresponding Virtual Local Area Network (VLAN), the System
Planning Tool automatically creates a Virtual Ethernet Adapter and maps a connection
to the partition.
To create a new VLAN column, click the Add link in the upper right-hand corner of the
column header.
Each VLAN column contains a selectable check box at every intersection with a
partition row. By selecting a check box, you are indicating that you want the logical
partition in the intersecting row to participate in this VLAN. When you select or clear a
check box, a Virtual Ethernet Adapter is added or removed from the Virtual Ethernet
Adapters tab in the Details view below.

Instructor Guide
By clicking a partition name, this tab displays the Shared Ethernet adapters
associated with the selected partition.
Click Create Adapter to create a new Shared Ethernet adapter for the selected
partition.

V5.3
Instructor Guide

Purpose
Details
Transition statement Next is Virtual Storage configuration.

Instructor Guide
SPT: Virtual Storage

IBM Power Systems
Add VSCSI
connections
Physical volume
assigned as virtual
disk to partition
Figure 4-14. SPT: Virtual Storage AN111.0
Notes:
Use this screen to define virtual storage, virtual SCSI connections between the Virtual
I/O Server and the client logical partition, assign physical volume to partitions, create
SAN volumes, storage pools, and so on. The example displays the SCSI connections
between server and client partitions and how to add a new virtual SCSI connection
between your server and client partition.
SCSI Connections tab

Use the SCSI Connections tab to view, add, edit, and remove virtual SCSI
connections.
Server partition
This column displays the names of your server partitions. Click a partition name to
display the virtual SCSI connection details of this partition. The Connection Details view
displays connections to client partitions and the slot ID associated with this connection
on both the server and the client. Each time you click a different server partition name,

V5.3
Instructor Guide
Uempty the Connection Details view is updated with the virtual SCSI connection information
associated with the selected partition name.
Virtual SCSI connections
This column displays the total number of virtual SCSI connections that currently exist
between the corresponding server and client partitions displayed in each row. Click
Remove Connections to modify the slot IDs on both the server and client partitions.
Click Edit Virtual Slots to modify the slot IDs on both the server and client partitions.
Client partition
This column displays the name of the client partition sharing a virtual SCSI connection
with the server partition
Physical Volumes tab

This panel displays all of the physical disks and SAN volumes on the selected system
owned by Virtual I/O Server partitions. Click Create SAN Volume to create a new SAN
volume. To modify an existing SAN volume, click the name of the SAN volume you want
to work with to display the details of this volume. Click Edit on the Disk/Volume details
tab to modify the volume, or click Delete to delete the volume.
Assignment column
Specify the client partition you want to assign the selected disk or volume to.
Storage Pools (Volumes Groups) tab

This panel allows you to create storage pools, create virtual disks to assign or unassign
storage pools to, delete storage pools, and view the details for a storage pool.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Lets see the Installation tab.

V5.3
Instructor Guide
Uempty
SPT: LPARs operating system installation

IBM Power Systems
Define install source and target for the virtual I/O Server, AIX,
or Linux partition
Operating system will be installed with sysplan deployment
Physical Ethernet Physical hdisk

Adapter for for VIO server
network
installation installation
Virtual SCSI
disk for
Virtual Ethernet
for network installation
installation
Figure 4-15. SPT: LPARs operating system installation AN111.0
Notes:
This Installation tab enables to create or modify the AIX, Virtual I/O Server, or Linux
install image location and install target location.
Installing operating environments on the HMC

You can use HMC version 7 to install an operating environment on a logical partition
when you deploy a system plan. For HMCs prior to HMC V7R3.3.0, you can deploy a
system plan to install only the Virtual I/O Server operating environment. Beginning with
HMC V7R3.3.0, you also can deploy a system plan to install AIX or Linux operating
environments on logical partitions in a system plan.
Note: You can create a system plan with installation information for an AIX or Linux
operating environment only in the System Planning Tool. If a system plan has
installation information for an AIX or Linux operating environment, you still can deploy
the system plan to systems that are managed by an earlier version of the HMC. Earlier
versions of the HMC Deploy System Plan wizard can deploy the logical partitions in the
system plan and ignore any operating environment installation information in the

Instructor Guide
system plan. The earlier versions of the HMC can deploy all other aspects of the system
plan successfully, as long as the other items in the system plan are validated
successfully. System plans that contain AIX or Linux installation information can be
deployed only to new logical partitions or to logical partitions that do not already have
an operating environment installed on them. If the logical partition already has an
operating environment installed, the HMC does not deploy the operating environment
that the system plan specifies for that logical partition.

V5.3
Instructor Guide

Purpose
Details
Transition statement Lets see the Summary.

Instructor Guide
SPT: Summary
IBM Power Systems
Validation
messages
Figure 4-16. SPT: Summary AN111.0
Notes:
In this step, you will review the settings for this system. When you are ready to create
the system, click Finish to create the system.
Some informational or error messages can be displayed in the System plan summary
panel. The visual shows two messages:
A dedicated DVD is required in slot P2-D2 of he 8204_E8A
system tower:
The Validate For New Order Warning icon displays when the plan is valid as a
new order for import into eConfig, but the warning message contains additional
information about a situation that might affect your order in an undesirable way.
You might want to fix this situation before you export your plan for initial order.
If Network Install is being used for software install, no
optical device is required:
The Validate For New Order Informational icon displays when the plan is valid
as a new order for import into eConfig, but there is some additional information
that might be relevant to your order.

V5.3
Instructor Guide

Purpose
Details
Transition statement Lets see the SPT outputs.

Instructor Guide
SPT: Configuration status (report and output)

IBM Power Systems
Figure 4-17. SPT: Configuration status (reports and output) AN111.0
Notes:
SPT outputs
You can print a detailed report from SPT on the system configuration with the Report
option. And, with the Save and Export options, you can extract .sysplan and .cfr files
that can be used as input to planning and configuration tools.
Deploying system plans

After you have designed your system, you can save your system plan (.sysplan) and
import it into a Hardware Management Console. You can then deploy the system plan
to one or more systems.

V5.3
Instructor Guide

Purpose Describe the final steps in system planning: saving the plan, exporting the plan
files.
Details These exported files can be used as input to create the HMC configuration for
the system.
Transition statement The last step is to load the plan onto your HMC and deploy the
configuration.

Instructor Guide
Import system plan

IBM Power Systems
Figure 4-18. Import system plan AN111.0
Notes:
Implementing the plan

The final step after creating the system plan is to load and deploy the plan onto an HMC
to create and configure a managed systems partitions. In the visual, you can reach the
screens to work with the system plan by selecting System Plans in the navigation area.
From there you can load and deploy the plan in the HMC. The visual shows how to
import a system plan from a local computer to the HMC.
The .sysplan file might also be sent to the HMC using scp, CD-R, USB drive or diskette.
Supported HMC versions

This import function is currently supported on version 5.2.0 or later of the HMC
software; however, it is recommended that you use HMC version 7.3.3 or later for full
functionality.

V5.3
Instructor Guide

Purpose Describe the process of loading the plan on the HMC.
Details Show the process of using the HMC to import the system plan.
Transition statement Lets see the HMC option to deploy a system plan.

Instructor Guide
Deploy system plan

IBM Power Systems
Figure 4-19. Deploy system plan AN111.0
Notes:
Select the system plan you want to deploy in the System Plans working pane. Use the
Tasks pad or the context menu to select Deploy System Plan. The Deploy System
Plan wizard displays to select the managed system on which to deploy the system plan.

V5.3
Instructor Guide

Purpose Show how to deploy a system plan from the HMC GUI
Details
Transition statement A system plan can also be created from the HMC GUI

Instructor Guide
Create a system plan using HMC version 7

IBM Power Systems
From the navigation area, select System Plans. The System

Plans page opens.
From the Tasks area, select Create System Plan Start SPT from the
desktop
Specify a system
plan name
Figure 4-20. Create a system plan using HMC version 7 AN111.0
Notes:
Creating a system plan using HMC Version 7

To create a system plan from Version 7 of the Hardware Management Console,
complete the following steps:
1. From the navigation area, select System Plans. The System
Plans page opens.
2. From the Tasks area, select Create System Plan. The Create
System Plan window opens. Select the managed system that you
want to use as the basis for the new system plan.
3. Enter a name and description for the new system plan.
Optional: Select whether you want to retrieve inactive and unallocated hardware
resources. This option appears only if the managed system is capable of hardware
discovery; the option is selected by default.

V5.3
Instructor Guide
Uempty Note: If you do not select the Retrieve inactive and unallocated hardware resources
option, the HMC does not perform hardware discovery. The HMC still performs
inventory gathering and retrieves hardware information for any active partitions on the
managed server. The resulting system plan contains hardware information from the
inventory-gathering process, as well as hardware information from the hardware
inventory cache on the system.
Optional: Select whether you want to view the system plan immediately after the HMC
creates it.
1. Click Create.

Instructor Guide
Instructor notes:
Purpose
Details Show how to create a system plan from the HMC GUI.
Transition statement Lets see how to convert a sysplan generated by the HMC to the
SPT format.

V5.3
Instructor Guide
Uempty
Converting a system-plan file to SPT format

IBM Power Systems
System-plan files generated from the HMC can be imported

in SPT for modification.
Click
Convert
Figure 4-21. Converting a system-plan file to SPT format AN111.0
Notes:
After you create your system plan, you have to export it from the HMC or Integrated
Virtualization Manager so that you can work with it using the System Planning Tool. You
can export the sysplan-file to the computer on which you remotely access the HMC.
After you have exported a system plan from the HMC or from Integrated Virtualization
Manager, you are ready to convert that system plan into System Planning Tool format.
There are two parts to this process.
1. First, you convert the system-plan file to SPT format using the
Conversion Wizard in the SPT.
2. Second, you complete the conversion by addressing any
messages or warnings you receive in the System Planning Tool.

Instructor Guide
Instructor notes:
Purpose
Details Show how to export and convert a sysplan file to the SPT format.
Transition statement Lets see if you were paying attention by answering the unit
Checkpoint questions.

V5.3
Instructor Guide
Uempty
Checkpoint
IBM Power Systems
1. True or False: After you have designed your system in

SPT, you can save your system-plan file (.sysplan) and
import it into a Hardware Management Console.
2. True or False: The system plan can contain the information

about the Virtual I/O Server deployment, operating system
installation, and provisioning.
3. True or False: System plan generated from the HMC can

be import in the SPT for modifications
Figure 4-22. Checkpoint AN111.0
Notes:

Instructor Guide
Instructor notes:
Purpose Check the students comprehension of the material from the entire unit.
Details Give the students 10 minutes to complete these questions and then review the
answers.
Checkpoint solutions
IBM Power Systems




V5.3
Instructor Guide
Uempty
Exercise
IBM Power Systems
Unit
exerc
ise
Notes:

Instructor Guide
Instructor notes:

V5.3
Instructor Guide
Uempty
Unit summary
IBM Power Systems

configurations
Import and deploy a system plan on the HMC
Generate a system plan from the HMC
Convert a system plan file to the SPT format for

modification
Notes:

Instructor Guide
Instructor notes:
Details Touch on each objective and remind the students of the key points on each.
Additional information Review questions are not provided because this unit is the last
one.

V5.3
Instructor Guide
Uempty Unit 5. HMC and managed system maintenance
Estimated time
00:45

This unit describes the procedures for performing maintenance tasks
on the HMC and the managed system.

Back up critical console data
Schedule regular critical console data backups
Describe the following procedures:
- Install corrective service code on the HMC
- Prepare for an HMC upgrade
- Perform an HMC upgrade
- Perform an HMC reload
- Install managed system firmware updates.

Accountability:
Checkpoint
References
IBM PowerVM Web portal:
http://www-03.ibm.com/systems/power/software/virtualization/index.ht
ml
Copyright IBM Corp. 2009 Unit 5. HMC and managed system maintenance 5-1
Instructor Guide
IBM Technical Support Web sites:

http://www-304.ibm.com/systems/support/

V5.3
Instructor Guide
Uempty
Unit objectives
IBM Power Systems

Schedule regular critical console backups
Install corrective service code on the HMC
Prepare for an HMC upgrade
Perform an HMC upgrade
Perform an HMC reload
Install managed system firmware updates
Notes:
Introduction
This unit discusses the maintenance of the software and configuration information on
the HMC. It also describes how to perform firmware updates for the managed system.
Instructor Guide
Instructor notes:
unit.
Transition statement We will start this unit by discussing backing up the HMC critical
console data.

V5.3
Instructor Guide
Uempty
Backup critical console data (1 of 3)

IBM Power Systems
Back up critical console data to DVD-RAM or to a remote

system
Used for restoring HMC data during HMC recovery
Backup data includes

User configuration
HMC configuration
HMC log entries
Any partition profile data backup files
Backup does not include

List of scheduled operations
Remote command execution setting
Can schedule backup operations for a specific time or schedule

them to repeat
Figure 5-2. Backup critical console data (1 of 3) AN111.0
Notes:
Introduction
You can back up critical HMC console data to the HMC's DVD-RAM drive or to a remote
system. Back up the HMC after you have made changes to the HMC configuration or to
the information associated with partitions. You can set up an automated backup of
critical console data through the HMC Management > Schedule Operations task from
the HMC workplace window.
If you leave a DVD in the DVD-RAM drive, subsequent backups will continue to write
over the backups on the DVD. That is, you will only ever have the last backup on the
DVD.
The critical console data backup can only be restored in conjunction with a
re-installation of the HMC from the HMC product media.
Instructor Guide
Backup critical console data

The visual lists the types of items that are backed up as part of a critical console data
backup. Basically, it is every configurable item on the HMC with the exceptions of the
scheduled operations and enable/disable settings for remote access to the HMC. Be
sure to document these items manually and remember to reconfigure them if you need
to re-install the HMC software. The HMC software itself is not backed up as part of this
procedure.
When you back up critical console data, you cannot choose which pieces of the
software you want to save. The HMC saves all pertinent configuration.
Partition profile data

Recall that when you perform a backup of profile data for all the partitions using this
option, select Configuration > Manage Partition Data > Backup. Backup files of the
profile data are created on the HMC hard drive. These backup files are saved in the
Back up Critical Console Data operation.
Even if you have neglected to perform a backup operation of profile data, a backup file,
named backupFile, is written whenever you make a profile configuration change so this
backup will be saved as part of the critical console backup.

V5.3
Instructor Guide

Purpose Describe the Back up Critical Console Data feature on the HMC.
Details This page describes what a critical console data backup is. The next page will
show what application is used to perform this procedure.
Emphasize that this feature backs up HMC configuration data in case of complete failure of
the HMC. Its purpose is not to restore individual items in case they are accidently removed
or changed. It also does not back up the HMC software itself.
This backup is used only during the recovery process if the HMC must be re-installed for
any reason. There is no control over what exactly is backed up or what is restored.
Transition statement Lets look at the HMC screen where you can perform this backup.
Instructor Guide

IBM Power Systems
Backup options
Notes:
Backing up critical console data

Step 1: Click HMC Management in the navigation area on the HMC.
Step 2: If the backup of critical console data will be to DVD-RAM, first you must format
the DVD in the DVD-RAM format before you can save data to the DVD. To format a
DVD, click HMC Management > Format Media from the HMC workplace window.
Step 3: Next choose the Backup HMC Data task in the HMC workplace window.
Step 4: A window will ask you to select an archive option. You can back up to DVD on
the HMC, back up to a remote system mounted to the HMC file system (such as NFS),
or a remote site through FTP. Choose an option and click Next. For the remote site or
mounted remote system options, another window will open and ask you for the remote
site information. The next few pages show these windows.

V5.3
Instructor Guide
Uempty The visual shows the window that opens after you click the Backup HMC Data task
shown on the last visual. You can choose to back up to DVD, to an NFS mounted
system, or to a remote site.
Backup size requirements

For NFS and FTP backup options, ensure that the remote destination has sufficient
space for the backup image. You will need a minimum of 100 MB of space for simple
HMC configurations. But you might want to allow around 1 GB of space, or potentially
more, if you have a large number of partitions and profiles, or if the HMC controls
multiple managed systems.
NFS considerations
For the NFS choice, the backup file will be placed in the file system of the NFS server
directory which is specified. You cannot specify the subdirectory of the NFS filesystem.
You must ensure that the NFS export provides permission for this client with root
access allowed.
Remote site considerations

In the case of the third option, sending the backup to a remote site with FTP, the backup
file will be stored in the default home directory of the user ID you specify.
If you pick the remote site option, another window opens where you can provide
information about the remote site. This window is shown in the next visual.
Restoring critical console data

Critical console data can be restored on any HMC. The restore process is part of a
recovery process of an HMC and you cannot restore just one piece of data, such as a
particular partition profile.
If the critical console data has been archived on a DVD-RAM, the re-installation of the
HMC from the product media will prompt the user to insert the DVD-RAM containing the
archived console data at installation end. On first boot of the newly installed HMC, a
check will be made to see if the DVD-RAM is inserted. The data will then be
automatically restored.
If the critical console data has been archived remotely, the network settings must be
re-configured manually to enable access to the remote system after the HMC is newly
installed. Then launch the Restore HMC Data task in the HMC workplace window.
Format removable media

You have to format DVD-RAM disks, before you write to them.
Instructor Guide
Instructor notes:
Purpose Describe the procedure to make a backup of critical console data.
Details Describe each step of the backup and restore procedures.
Describe the two ways to perform restores (from DVD and from a remote system). We will
get to the recovery process for an HMC later in this unit. Describe the differences between
the Critical data archive options on this visual.
Transition statement The next page shows the window when you pick the remote site
option.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Back up to a remote system
Notes:
Introduction
This window opens for the remote site information where the critical console data
backup file will be sent with FTP. Enter the server address, user ID and password and
click OK to perform the backup.
The actual backup file is in a compressed UNIX tape archive (tar) format. The remote
site option performs the backup to the tar file then will FTP it to the site that you list in
the box shown in the visual.
For restores, you will be given the option to choose DVD or remote site to retrieve your
backup file.
Remote site information

Enter the host name of the remote system where you wish the backup file to be stored.
This host must be accessible on the network.
Instructor Guide
The User ID and password are for the account on the remote site and will be used in the
FTP process to log in to the remote system. The backup file will be placed in that user
IDs default home directory. Make sure there is enough room for the backup on the file
system.
If you choose to save the backup file to a remote site, you will need to configure the
HMC network configuration information manually before restoring the rest of the HMCs
configuration from the backup file. Be sure to document this configuration.

V5.3
Instructor Guide

Purpose Describe the procedure to make a backup of critical console data.
Details Describe that this is the information for the system where the backup file will be
kept. The User ID and password must be valid on the remote system and have permissions
such that a successful FTP can be performed.
Transition statement You can also schedule backups to happen at a particular time.
Instructor Guide
Scheduling backups (1 of 2)
IBM Power Systems
The only HMC operation that can be scheduled is Backup

Critical Console Data
You can schedule one operation or schedule them to repeat
Figure 5-5. Scheduling backups (1 of 2) AN111.0
Notes:
Introduction
You can schedule critical console data backups to occur at sometime in the future and
you can schedule backups to happen regularly. To get to this feature, Select HMC
Management > Schedule Operations from the HMC workplace window. Then in the
Customized Scheduled Operations window, click Options > New. Then Add an
Operation window opens, then click the only option available Backup Critical Console
Data, then click OK to continue.

V5.3
Instructor Guide
Uempty lInstructor notes:

Purpose Describe how backups can be automated.
Details You can schedule critical console data backups. Make sure the students are not
confusing this with the Systems Management partition profile data backup option.
The scheduling window mentioned in the procedure in the student notes allows you to set
the date, time, and repeat information for the scheduled backup. This screen is shown in
the next visual.
Transition statement After you click OK on the window shown in this visual, another
window will pop up which will allow you to set the date and time.
Instructor Guide
Scheduling backups (2 of 2)
IBM Power Systems
Figure 5-6. Scheduling backups (2 of 2) AN111.0
Notes:
Schedule date and time

This option enables you to schedule the date and time for backing up critical console
information. You must provide the time and date that you want the operation to occur.
You can schedule a backup to occur once, or you can set up a repeated schedule. For a
repeated schedule, click the Repeat tab.
Schedule single or repeat operations

Specify either a single or repeated operation. Refer to Unit 8, Dynamic resource
Allocation for more information about scheduling operations.
The interval specifies the time between operations and the example in the visual above
shows that this operation will happen every other week (that is, 2 weeks between each
operation). Repetitions is how long you want the operations to continue. In the example,

V5.3
Instructor Guide
Uempty this operation that happens every two weeks will run for 26 repetitions which means for
one year.
Click Save to save the new operation.
Instructor Guide
Instructor notes:
Purpose Describe how backups can be automated.
Details You can schedule backups to occur automatically. Note that these scheduled
backups perform the Back up Critical Console Data task.
The scheduling window mentioned in the procedure in the student notes allows you to set
the date and time for the operation. Click the Repeat tab if the scheduled operation should
repeat over time.
Describe the options for scheduling a repeated operation.
Transition statement That is it for backups. Lets look at how to update the HMC
software.

V5.3
Instructor Guide
Uempty
Install corrective service

IBM Power Systems
Choose how
to install
For network
installation, enter
file location and
login information
After update, reboot HMC and check version level

Figure 5-7. HMC corrective service AN111.0
Notes:
Introduction
A corrective fix updates the minor version level of code on the HMC. Corrective fixes
may be obtained by ordering them on a CD-ROM or by downloading them either to the
HMC itself or to a remote system that the HMC is able to connect to using FTP or
mountable file system. Monitor the IBM HMC Corrective Fixes Web site to find out
about corrective fix information and obtain downloads. The URL is shown on the visual.
The procedure to install corrective fixes is detailed on the IBM HMC Corrective Service
Web site and discussed on the next visual.
Before installing corrective service on the HMC you should perform a backup of the
critical console data and locate the recovery CD media for the current HMC code level,
to ensure your current HMC is recoverable in the event of a problem. You should also
determine what level of code exists on your HMC.
Instructor Guide
HMC Technical Support Web site

The main HMC Technical Support Web site is:
There is a subscription service with which you can register and have notices sent to you
when there are HMC updates and security fixes available. This can be found at
http://www.ibm.com/systems/power/support, look for the link to Subscription Service.
Find the current level of HMC code

The current levels of the HMC version, release, and build are listed at the top of the
Updates application. Look under the heading HMC Code Level. When you know what
level of HMC software you have, check the IBM Web site to see whether fixes are
available for your software release.

V5.3
Instructor Guide

Purpose Define what is meant by a corrective service update or fix and the overall
process of how to obtain information about fixes.
Details All products get updated from time to time and the HMC is no different.
Occasionally, patches or fixes to the HMC code must be installed. This is part of the normal
cycle of improvement.
Customers can access the IBM HMC Corrective Service Web site to see the latest
information about what fixes are available and download them if necessary. Customers
without network access between the Internet and the HMC can move the compressed file
with the fix from one network to another using media or can contact IBM if the fix is
available on CD-ROM. The Web page will state whether a CD-ROM is available.
Transition statement The next visual shows how to install the fix.
Instructor Guide
HMC corrective service

IBM Power Systems
A corrective service is a minor software update or "fix"

Typically changes the minor version level
HMC corrective service information and downloads can be

obtained from:
http://www14.software.ibm.com/webapp/set2/sas/f/hmc/
Procedure
1. Perform a critical console data backup (just in case)
2. Download zipped file from Internet (or obtain a CD-ROM with the fix)
3. From the HMC Install Corrective Service application, install the fix
Updates > Update HMC (button)
4. Reboot HMC
5. Check that the version level is what you expect
Figure 5-8. Install corrective service AN111.0
Notes:
Introduction
You can download the corrective fix file from the Internet directly to the HMC or to
another system that is accessible to the HMC from the network. One of the partitions on
the managed system works well for this.
Install corrective service

1. In the HMC workplace window, click Updates > Update HMC, the Install Corrective
Service window opens. This is the window shown in the visual.
2. Select the appropriate installation option, whether from media or from the network. The
rest of the steps shown below assume you chose the second option Download the
corrective service file from a remote system.
3. Enter the specified information in the following fields:

V5.3
Instructor Guide
Uempty Remote Site

Enter the fully qualified name of the host where the compressed file is stored.
If you are downloading the corrective service file directly from the Internet, refer to
the FTP link for the host name of the FTP server. Enter only the host name as shown
in the visual above.
Patch File
Enter the FTP directory and .zip file name (that is, the absolute pathname to the .zip
file).
If you are downloading the corrective service file directly from the Internet, refer to
the FTP link for the absolute path to enter. Enter the path starting with the / character
that immediately follows the host name.
User ID
Enter the FTP userid. For direct Internet download, use anonymous.
Password
Enter the FTP password for the userid. For direct Internet download, use your e-mail
address.
The HMC interface retrieves the update package from the remote FTP server and
begins the install process.
1) Reboot the HMC after the installation of the update has completed.
Rebooting ensures that all changes are available immediately.
2) Verify a successful update. Check the HMC release level from the Updates
workplace window.
Instructor Guide
Instructor notes:
Purpose Describe how to install a corrective fix from the IBM site or from another
network computer.
Details Go over the procedure listed in the student notes for downloading and installing
the corrective fix.
Transition statement Occasionally, the HMC software needs to be upgraded to a new
release. The next page shows this procedure.

V5.3
Instructor Guide
Uempty
HMC software upgrades

IBM Power Systems
HMC upgrade procedure

1. Back up critical console data to DVD (just in case)
Do not make any configuration changes between this step and the next
2. Save upgrade data

Saves data to special area on HMC disk
3. Put new HMC product media in drive

4. Reboot HMC
5. Select upgrade when asked
Youll be prompted to insert second CD
Figure 5-9. HMC software upgrades AN111.0
Notes:
Introduction
A software upgrade is different from a corrective service in that it is more than just a fix
of the current functionality. Look for new features, enhancements, and new applications
when you install a software upgrade.
When you are upgrading the HMC software at the same time that you will be updating
the firmware on the managed system, upgrade the HMC first so that it will recognize the
new version of firmware.
Save upgrade data

The HMC Save Upgrade Data task saves all of the HMC configuration information to a
special area on the HMCs hard disk drive. When you boot the HMC from the product
media and choose Upgrade (rather than Install/Recovery), it will load the HMC
Instructor Guide
configuration information from the special area. It will not ask you for a critical console
data backup.
In the procedure in the visual, the Back up Critical Console Data step is included just
in case something goes wrong during the software upgrade and you need to perform a
full install of the HMC at the existing software level. See the HMC reload process in this
unit for more information about that procedure.
You should only save upgrade data immediately prior to upgrading your HMC software
to a new release. This allows you to restore previous levels if you need to recover the
HMC. Be aware that only one level of upgrade data is allowed. Each time you save
upgrade data, the previous level is overwritten.
If the Save Upgrade Data step fails

If the Save Upgrade Data task fails, contact software support before proceeding.
Do not continue the upgrade process if the Save Upgrade Data task fails.

V5.3
Instructor Guide

Purpose Describe the HMC software upgrade process.
Details Point out that you must Save Upgrade Data first to save all of the HMC
configuration information before performing the upgrade. Where you save the upgrade
data is shown on the next window.
Transition statement Lets see how to perform Step 2, saving the HMC configuration
data before performing the upgrade.
Instructor Guide
Prepare for HMC software upgrades

IBM Power Systems
This tool saves the HMC configuration information in a special

area on the HMC disk
The HMC upgrade program will find this data and restore it
Figure 5-10. Prepare for HMC software upgrades AN111.0
Notes:
Save Upgrade Data

In the HMC workplace window, select HMC Management. Then in the tasks list, select
Save Upgrade Data. Select Hard Drive and click Next. Perform this task to store
system information in preparation for an HMC upgrade. When you complete this
process, the HMC saves configuration data, such as:
System preferences
Profile information
Service applications files
You can save this information to the hard disk. Only Support Personnel can save this
data to a DVD-RAM disk.
Note: Only perform this task immediately prior to upgrading your HMC software from
one release to another. Any configuration changes made after performing this task will
not be migrated to the new HMC software release.

V5.3
Instructor Guide

Purpose Show how to save the HMC configuration data before an upgrade.
Details Emphasize to those sleeping in the audience that this is different from backing
up the critical console data. Even if you have that backup disk, it will not help you when you
perform the software update.
If you performed the HMC software upgrade, but forgot to do this Save Upgrade Data task,
and you do have a backup DVD, you could reinstall your existing HMC product software
using the HMC reload procedure listed on the next page. This would bring your HMC back
to a known release level and restore your configuration data. Presumably, your HMC
product software CDs will not be the latest version, so you will have to perform the software
upgrade step again. Remember the Save Upgrade Data step this time.
Transition statement Next, we will see how a full recovery of the HMC is performed.
Instructor Guide
HMC reload procedure

IBM Power Systems
What if you need to rebuild the entire HMC?

Example: HMC boot disk is replaced
Reinstalling the HMC interface

1. Insert the HMC product media into DVD-RAM drive
2. Reboot the HMC
3. Select the Install/Recovery process (not Upgrade)
4. When prompted, insert your backup DVD-RAM, if you have one
5. HMC will need to reboot, and install will continue
6. When install is finished, verify the HMC level
7. If necessary, restore remote critical console data backup (not on DVD)
a) Set up HMC network parameters
b) Use Restore HMC Data task under HMC Management to restore the Critical
Console Data backup.
Figure 5-11. HMC reload procedure AN111.0
Notes:
Introduction
If you replace the HMC, its hard drive, or for some reason need to perform a completely
new installation, you must reinstall the HMC product software and your configuration
data.
Reinstalling the HMC

1. With the HMC powered off, place the HMC software product media in the DVD-RAM
drive. Power on your HMC.
2. When the HMC boots, a window opens with the following options:
a. Install/Recovery
b. Upgrade
3. Select the Install/Recovery option by pressing F8. Press F1 to confirm.

V5.3
Instructor Guide
Uempty 4. When the installation is complete, the DVD ejects from the drive. Remove the HMC
product media from the drive and close the DVD-RAM drive. Press Enter to reboot
HMC. You will be prompted to insert your backup DVD-RAM disk.
Note: If there is a modem connected, ensure that it is powered on.
Additional steps
There are a few additional steps that may need to occur:
If the HMC needs to be upgraded because your Recovery CD does not include the
latest upgrades, you will need to perform the upgrade process.
You might need to check a few of the settings on the HMC after performing a new install
even when using a backup DVD-RAM. The enable/disable ssh settings and the
scheduled operations configurations are not backed up by the Back up Critical
Console Data operation.
Restore from a remote system (rather than DVD)

If the critical console data has been archived remotely, the network settings must be
re-configured manually to enable access to the remote system after the HMC is newly
installed. Then from the HMC Management workplace window, select the Restore HMC
Data task. Select the type of remote restore.
If you choose to restore from remote NFS server, follow the directions on the screen to
restore the critical console data. The data is then copied to the HMC from the remote
system and will automatically be installed when the system is rebooted.
If you choose to restore from remote FTP server, follow the directions on the screen to
restore the critical console data. The data is then copied to the HMC from the remote
system and will automatically be installed when the system is rebooted.
Instructor Guide
Instructor notes:
Purpose Describe the HMC recovery procedure.
Details This procedure is to be followed if the HMC must be rebuilt. This is when your
diligent backups of the critical console data is rewarded because your HMC configuration
information, including the partition profile data, will be restored. If you do not have that
backup DVD, I hope your planning worksheets are up to date because you will have to
reconfigure the HMC manually.
Transition statement Next, lets see how to perform concurrent firmware updates on
the managed system.

V5.3
Instructor Guide
Uempty
Managed system firmware update (1 of 2)

IBM Power Systems
Managed system firmware (Licensed Internal Code) updates

Server firmware
Power subsystem firmware
I/O adapter and device firmware
Types of firmware maintenance

Concurrent (must use an HMC)
Disruptive
Reboot of managed system necessary
Deferred
Fixes can be installed concurrently, but will not be activated until the
next IPL.
Figure 5-12. Managed system firmware update (1 of 2) AN111.0
Notes:
Firmware updates
There are various types of firmware updates for the server, the power subsystem, and
various devices on the system. All of these can be updated from the HMC.
These updates might be disruptive, in which case the managed system will
automatically reboot after the install, they might be concurrent which means the
managed system does not, and does not need to be, rebooted after the fix is installed.
They might be also deferred.
What does deferred mean? Concurrent levels of system firmware may, on occasion,
contain fixes that are deferred. These deferred fixes can be installed concurrently, but
will not be activated until the next IPL. Deferred fixes, if any, will be identified in the
Firmware Update Descriptions table of the system firmware description (Desc) file. For
deferred fixes within a service pack, only the fixes in the service pack which cannot be
concurrently activated are deferred.
Instructor Guide
Concurrent levels of system firmware may, on occasion, contain fixes that are deferred.
These deferred fixes can be installed concurrently, but will not be activated until the next
IPL. Deferred fixes, if any, will be identified in the Firmware Update Descriptions table of
the system firmware description (Desc) file. For deferred fixes within a service pack,
only the fixes in the service pack which cannot be concurrently activated are deferred.
Some updates will be designated as disruptive and some will be designated as
concurrent.
System firmware is delivered as a Release Level or a Service Pack. Release Levels
support the general availability (GA) of new function or features and new machine types
or models. Upgrading to a higher Release Level can be disruptive to customer
operations. Thus, IBM intends to introduce no more than two new Release Levels per
year. These Release Levels are supported by Service Packs. Service Packs are
intended to contain only firmware fixes and are not intended to introduce new
functionality. A Service Pack is an update to an existing Release Level.

V5.3
Instructor Guide

Purpose Describe the different firmware updates that might be needed and the
difference between disruptive and concurrent.
Details Explain that some updates will necessarily be disruptive and some will be
concurrent.
Transition statement Lets look at the HMC application where managed system
firmware updates are performed.
Instructor Guide
Managed system firmware update (2 of 2)

IBM Power Systems
Firmware
To examine update
current LIC From CD
levels only
Figure 5-13. Managed system firmware update (2 of 2) AN111.0
Notes:
HMC updates
For each selected managed system, you can launch five tasks. The first task in the list
is where you perform updates to the current LIC release. This is sometimes referred to
as applying fixes to the firmware. There are many options as to where you apply the
update from, whether from an IBM Web site, technical support system, CD, and so
forth. These fixes may be concurrent or disruptive.
If you need to upgrade to a whole new firmware release, this is done with the second
option, Upgrade Licensed Internal Code to a new release. If you are upgrading to a
new release, you may obtain images from an online source; however, they must be
applied from a CD-ROM. For example, you might obtain the CD from IBM, or you might
download an ISO image from an online source and create your own CD. This CD is
used to upgrade the release level of the managed system firmware.
The third task (Flash Side Selection) enables you to select which flash side will be
active after the next activation, t-side (temporary side) or p-side (permanent side). The

V5.3
Instructor Guide
Uempty Service Pack maintains two copies of the server firmware. One copy is held in the t-side
repository (temporary) and the other copy is held in the p-side repository (permanent)
This is for IBM service use only.
The Check system readiness task checks for any errors on the internal code for the
target managed system.
View current firmware level

The Updates Work pane displays the Hardware Management Console code level and
the system code levels (the current firmware level). But there is another way to
determine your current firmware level of the managed system is to select one managed
system, then to choose the Change Licensed Internal Code for current release task.
In the next window, select the View System Information option and click OK. A
window will open and ask for the location of the LIC repository. You can choose None,
an IBM Web site, the IBM support system, and so forth, as locations.
The resulting window if you choose None for the location is shown in the next visual.
Firmware file naming convention

The file naming convention for System Firmware is as follows:
For IBM POWER5 processor-based systems
01SFxxx_yyy_zzz
where
xxx is the release level
yyy is the service pack level
zzz is the last disruptive service pack level
So, for example, System Firmware 01SF240_320 is Release Level 240, Service Pack
320.
For IBM POWER6 processor-based systems
EMxxx_yyy_zzz
where
xxx is the release level
yyy is the service pack level
zzz is the last disruptive service pack level
So, for example, System Firmware 01EM310_026 is Release Level 310, Service Pack
026.
Instructor Guide
Instructor notes:
Purpose Differentiate the three options on the LIC Updates HMC application.
Details The rest of this unit focuses on the first option, which allows you to update the
firmware at the current release.
Additional information The visual shows HMC v7.3.3.
Transition statement Lets examine the current firmware level of your managed
system. The next visual shows the results when the View system information option is
chosen and the location of None is picked for the LIC repository.

V5.3
Instructor Guide
Uempty
Examine current firmware level

IBM Power Systems
This example system is at release level 320, service

pack 040:
Figure 5-14. Examine current firmware level AN111.0
Notes:
Release version versus service pack level

The release level is the major level of firmware. In the visual, this is system firmware
release 320. The service pack level for release 320, in the example, is 040. This is the
minor release level.
The next series of visuals will show how to acquire firmware updates and update the
system.
Concurrent or disruptive update

When certain requirements are met, firmware updates for POWER5 or POWER6-based
systems can be concurrent, which means the managed system does not have to be
rebooted for the firmware to be applied. The HMC software must be version 4.5 or
greater to support concurrent firmware updates. The managed system is capable of
concurrent firmware updates if it is installed with firmware 01SF230_120 or greater.
Instructor Guide
If you are upgrading the firmware release number, then the update will be disruptive.
For example, for POWER5 processor-based system, if you are upgrading from
01SF230_xxx to 01SF240_yyy, then this is a disruptive update. For POWER6
processor-based systems if you are upgrading from 01EL310_xxx to 01EL320_xxx,
then it is also a disruptive update.
Concurrent upgrades are only available when staying within the same firmware release;
for example, if you are upgrading from 01SF230_xxx to 01SF230_yyy then this upgrade
might be concurrent. However, not all updates of service packs within a release level
will be concurrent updates. The firmware image files have file names using this format:
01SFXXX_YYY_ZZZ.rpm, where XXX is the release level, YYY is the service pack
level contained in the file, and ZZZ is the last disruptive service pack level. As an
example, consider the filename 01SF240_261_201.rpm. The last number, 201 in the
filename example, is the last disruptive service pack level. The 261 number specifies
the service pack level of the firmware image contained in that file, and 240 is the
release number. If the service pack level currently installed on your system is lower than
the last disruptive service pack level indicated in the file name, then this upgrade will be
disruptive. For example, if the firmware currently installed on a POWER5 system is
01SF240_235, then the update to 01SF240_261 will be concurrent, since 235 is higher
than 201. But if the current service pack on the system is 190, which is below 201, then
the update will be disruptive.

V5.3
Instructor Guide

Purpose Describe the View System Information pop-up window.
Details This window shows that this system is currently at a particular system firmware
release and at a particular service pack level.
Transition statement The next page shows what might be seen on the IBM Web site
when looking up the latest currently available service pack level.
Instructor Guide
Obtaining new firmware

IBM Power Systems
Check http://www14.software.ibm.com/webapp/set2/firmware
for latest level and service pack:
Check out the

description (Desc)
for details
...
Figure 5-15. Obtaining new firmware AN111.0
Notes:
Check the IBM Web site for the latest level

The visual shows a section of the Web page available at
http://www14.software.ibm.com/webapp/set2/firmware/gjsn. This Web page lists
available microcode (firmware) downloads for Power Systems, IBM System p, eServer
p5, eServer pSeries, eServer OpenPower and RS/6000 servers. sorted by
machine/model type. Select the model number you are interested in and click Go. This
will take you to a page listing all the firmware updates for your system, adapters, drives,
and so forth.
Click the Desc, Impact and Severity links for a particular firmware update for more
detailed information. The description link (Desc) has lots of information such as how to
read firmware level names, how to find the current firmware level of your system, how to
download firmware, how to install new firmware, and if the update is concurrent,
deferred or disruptive.

V5.3
Instructor Guide
Uempty Severity
Each release will have different impact and severity levels. Following are descriptions of
these values.
Impact category description:
AVAILability Improves the availability of resources
DATA Resolves customer data error
FUNCtion Introduces or affects system/machine operation features,
connectivity, resource
PERFormance Improves or resolves throughput or response times
SECurity Improves or resolves security issues
SerViCeability Influences problem determination/fault isolation and
maintenance for diagnostic errors, incorrect FRU calls,
false error (no operational impact)
USEability Improves user interfaces/messages
NA Not Applicable
Severity category description:
ATTention Install at the earliest convenience; fixes low-potential,
low- to medium-impact problems
High Impact/PERvasive Install as soon as possible
PTF in Error Install when convenient; fixes minor problems
SPEcial attention Install at the earliest convenience; fixes low-potential,
high-impact problems
NA Not Applicable
Instructor Guide
Instructor notes:
Purpose Describe how to find out the latest service pack level that is available for a
managed system.
Details This visual shows snapshots from the IBM technical support page that shows
the current available service packs available for various system models.
The user selects the service pack and then clicks Continue on the bottom of the page. This
allows the downloading of multiple products at one time. There are several more screens,
but it eventually takes you to the download page.
Additional information For systems managed by an HMC, the preferred method is to
download the firmware and perform the upgrade using the HMC. Although this is the
preferred method, it can sometimes be much quicker to download the firmware ISO image,
burn a CD, put that in the HMCs DVD drive, then perform the upgrade from there. This
trick also applies when applying corrective service updates.
Transition statement Now that we know we need to update to a new service pack
level, we can proceed using the HMC.

V5.3
Instructor Guide
Uempty
Change LIC for current release (1 of 5)

IBM Power Systems
Figure 5-16. Change LIC for current release (1 of 5) AN111.0
Notes:
Change Licensed Internal Code for the current release task

The visual shows a series of windows that open when you choose the Change
Licensed Internal Code for the current release option from the Updates workplace
window of the HMC. The top right window asks for the LIC repository you want to use to
check, find the latest level. In this case, we have specified the FTP site.You then specify
the FTP site access information, such as the FTP site address, the account access
information and the directory where the firmware rpm file can be found. Then the
Change Licensed Internal Code wizard application is started.
FTP Site
An FTP server holds the server or power subsystem fix. It is any system on which you
have activated the FTP server protocol. Normally, your HMC only has the FTP client
active.
Instructor Guide
The remote site can be IBM, if you are downloading the fix directly from there to your
managed system, or it can be another system where you have already downloaded the fix.
For example, you downloaded the fix to an FTP server yesterday. Today, you want to
retrieve the fix from the FTP server so you can download it to the server at your site.
You must specify the directory on the FTP server that holds the server or power subsystem
fix. You can specify the default directory /opt/ccfw/data, or you can change the directory
path if the fix is in a directory other than the default directory. For example, if you
downloaded the fix and copied it to a unique directory on the FTP server, you can specify
that directory.

V5.3
Instructor Guide

Purpose Describe how to start the process of updating the service pack level for the
system firmware.
Details Describe which options to choose to start the process of performing an update
to the service level of the managed system firmware.
Transition statement If you click the Next button on the Change Licensed Internal
Code wizard window shown on this visual, the next visual shows what will display.
Instructor Guide

IBM Power Systems
Notes:
Change LIC wizard screens

The first window shown in the visual gives you information on the type of update that will
be performed. The second window shows the result of clicking the Advanced Options
button, which simply confirms the information that you already know, that this is a
concurrent installation that will be applied.
If you click the View Information button on the second screen shown in the visual, it
will compare what is currently installed on the system with the LIC repository. The
results are shown on the next visual. This is redundant with our previous steps of
manually checking the IBM Web site, but this screen will confirm our findings.
When you install changes to your firmware, you have three options:
Concurrent install and activate: Fixes can be applied without interrupting
running partitions and restarting managed system.

V5.3
Instructor Guide
Uempty Concurrent install with deferred disruptive activate: Fixes can be applied as
delayed and activated the next time the managed system is restarted.
Disruptive install with activate: Fixes can only be applied by turning off the
managed system.
You want to choose the option that fits the status of the server that you are updating.
For example, you do not want to use a disruptive installation option on a server that is in
production. However, on a test server, this option might not be an issue.
Instructor Guide
Instructor notes:
Purpose Describe the next screens that will appear as you continue with the LIC update
procedure.
Details The first screen confirms that this is a concurrent update.
Transition statement The next screen shows the window if we click the View
Information button on this visual.

V5.3
Instructor Guide
Uempty

IBM Power Systems
View information button
Notes:
Comparing the Activated Level to the currently available level

This screen displays the current level as 40 and there is a level 46 that can be applied.
It can be installed concurrently.
Instructor Guide
Instructor notes:
Purpose Describe the information available when you click the View Information
button.
Details This screen confirms what we looked up earlier.
Transition statement Now, we are ready to perform the concurrent update.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Notes:
Accept the LIC agreement

Read through the agreement, and click Accept to proceed with the update.
Instructor Guide
Instructor notes:
Purpose The user will need to accept the software license agreement before
proceeding.
Details There is one more screen to deal with before the upgrade can start. After
reading the agreement, click Accept to proceed with the firmware upgrade.
Transition statement We are finally ready to start the installation of the firmware
upgrade.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Notes:
Starting the firmware update

The first screen shows the final screen before starting the firmware update. Click the
Finish button to proceed. You will then see a Starting operation status message,
followed some time later by a Completed status message.
The example shows a Managed System update. The Function duration time show in
the bottom right screen displays the estimated amount of time necessary to complete
the task. The Elapsed time displays the actual amount of time that has passed as the
task progresses.
Instructor Guide
Instructor notes:
Purpose Describe how to start the update process.
Details There is one last check, then when you click Next on the first pop up window
shown in the visual, you will get one last pop-up window which will show the status of the
update.
Additional information For information, here are some example firmware update
timings on a IBM System p5-520 with two processors and 4 GB of memory.
1. A concurrent update for 01SF230_120_120 to 01SF230_143_120 took about 40
minutes. However, this update was concurrent so the partitions were still running.
2. A disruptive update from 01SF222_081_081 to 01SF225_096_096 took almost 90
minutes, and since the update was disruptive, all the partitions were stopped for that
period of time.
Transition statement The update for the current release is finished.

V5.3
Instructor Guide
Uempty
Checkpoint
IBM Power Systems
1. Can critical console data be restored on a different HMC?

2. True or False: Performing a Backup Critical Console Data
backs up all partition configuration data.
3. True or False: You can back up critical HMC data to either
DVD-RAM or floppy.
4. From where is your HMC configuration information restored
during the upgrade process?
5. From where is your HMC configuration data restored during the
installation/recovery process?
6. List two things that the Backup Critical Console Data option
backs up.
Notes:
Instructor Guide
Instructor notes:
Purpose Check the students comprehension of the material from the entire unit.
Details Give the students 10 minutes to complete these questions and then review the
answers.
IBM Power Systems

Yes. Perform the installation/recovery process.
2. True or False: Performing a Backup Critical Console Data backs up all partition
configuration data.
It is true because it saves the profile data backup files. Even if you do not
perform any profile data backup operation, there is one automatic file named
backupFile.
3. True or False: You can back up critical HMC data to either DVD-RAM or floppy.
You must back up to DVD.
4. From where is your HMC configuration information restored during the upgrade
process?
From the special area on the HMC disk (if you remembered the Save Upgrade
Data step).
5. From where is your HMC configuration data restored during the installation/recovery
process?
Your Backup Critical Console Data DVD-RAM, or from a remote system using
NFS or FTP.
6. List two things that the Backup Critical Console Data option backs up.
User configuration, user-preference files, platform-configuration files, log files,
partition profile data backup files.

V5.3
Instructor Guide
Uempty
Exercise
IBM Power Systems
Unit
exerc
ise
Notes:
Instructor Guide
Instructor notes:

V5.3
Instructor Guide
Uempty
Unit summary
IBM Power Systems

Schedule regular critical console backups
Install corrective service code on the HMC
Prepare for an HMC upgrade
Perform an HMC upgrade
Perform an HMC reload
Install managed system firmware updates
Notes:
Critical console data backup can be done manually or be scheduled
Corrective service code for the HMC can be installed from the HMC
HMC software can be upgraded from the HMC
The critical data on the HMC can be recovered and loaded on a new HMC installation
(disaster recovery)
The managed system firmware can be updated from the HMC
- The update can be disruptive or concurrent
Instructor Guide
Instructor notes:
Details Touch on each objective and remind the students of the key points on each.
Additional information Review questions are not provided because this unit is the last
one.

V5.3
Instructor Guide
Uempty Unit 6. System power management
Estimated time
00:45

This unit describes the power on process for an IBM POWER5 or
POWER6 processor-based server.

Describe the role of the Operator Panel on an LPAR-capable
system
Power on a managed system using these power-on options:
- Partition standby, System profile, Partition auto start, or
Hardware Discovery
Power off the managed system
Enable the Power Saver mode

Accountability:
Checkpoint
References
Copyright IBM Corp. 2009 Unit 6. System power management 6-1

Instructor Guide
Unit objectives
IBM Power Systems
Describe the role of the Operator Panel on an LPAR-

capable system
Power on a managed system using these power-on

options:
Partition Standby, System Profile, Partition Auto Start, or
Hardware Discovery
Enable the Power saver mode
Notes:

V5.3
Instructor Guide

unit.
Emphasize we are talking about powering on the managed system. The power-on process
for the HMC itself was discussed previously in this course and the start (or more correctly
called the activation) procedure for partitions will be covered later.
This unit is careful to use the terms power on and power off when talking about the
managed system. It uses the term shut down when talking about shutting down partitions,
and the terms starting or activating partitions to describe when partitions start. In other
words, partitions do not power on or off, and a managed system does not start or shut
down.
Transition statement Lets start by discussing the different power-on states for the
managed system.

Instructor Guide
Managed system power states

IBM Power Systems
Plug in managed system
Level 1: Power Off

The service processor is operational including
ASMI. All other system devices are powered off.
Issue Power On command
Level 2: Standby
All devices are initialized and powered on.
System is ready to support partitions.
Start first partition
Level 3: Operating
System is running partitions.
Figure 6-2. Managed System Power States AN111.0
Notes:
Introduction
This visual summarizes conceptually the three overall power levels for a managed
system. These should not be confused with the three power on options that will be
discussed in a few pages.
ASMI refers to the Advanced System Management Interface application, which runs on
the service processor. ASMI is Web-based and can be accessed by using a browser to
connect to the service processors IP address if the service processor is on an open
network. If the service processor is on a private network, ASMI can be accessed from
the HMC menus.
The ASMI allows you to set flags that affect the operation of the system, such as auto
power restart, and to view information about the system, such as the error log and vital
product data.

V5.3
Instructor Guide
Uempty Level 1: Power Off state

The first power level is achieved by plugging in the power cord of the managed system
into a live power socket. The HMC will report that the managed system is in the Power
Off state. No additional buttons need to be pushed and no commands need to be
issued.
The service processor will be initialized and the service processor software will be
loaded and run. If your system has an Operator Panel, you will see codes on the display
panel and after a few minutes, you will also see a steady blinking green light. The HMC
will also display the codes and status information for the managed system. At this point,
the service processor is an active host on the network. You may use the ASMI
application on the service processor. However, the rest of the devices, such as disks,
processors, and so forth, on the managed system are still powered off.
Level 2: Standby state

To advance to the second power on level, a power-on command must be issued to the
managed system. At this point, all devices are initialized and ready to use however, no
partitions are running yet, so their devices are not yet in use. Do not attempt to remove
hardware from the system at this level. The HMC will report that the managed system is
in the Standby state.
Level 3: Operating state

Once you start the first partition on the system, your managed system will be at the third
and highest power on level. The HMC will report the state of the managed system as
Operating. This means it has been fully powered on, initialized, and is running at least
one partition. With the proper procedures and commands, hot-pluggable devices can
be physically removed from the partitions.
When your managed system is in the Operating state, it remains there until you issue a
power off command or a system error changes the state. If you shut down all of the
partitions, but do not power off the managed system, the HMC will still report the
Operating state however at this point the system is in a state functionally equivalent to
the Standby state.
Well see how you can determine the state of your managed system and how to issue
these power on and off commands in this unit.

Instructor Guide
Instructor notes:
Purpose Describe what powering on the managed system means and the different
power levels.
Details Describe the three power levels. Emphasize what is running and what is not for
each.
We will discuss the different options to the Power On command in a few pages. You can
mention that there are four possible options to power on and that you might automatically
and quickly move through the standby power on level if you do not choose the Partition
Standby power-on option. When you choose the Partition Standby power-on option, the
system stops at that level; otherwise, it continues to the Operating level. If you have no
partitions yet configured or if you do not want to start any partitions at that moment, the
Partition standby option is available for partition configuration or other system maintenance
tasks.
Transition statement Lets review the physical button that controls power on most
models.

V5.3
Instructor Guide
Uempty
Managed system power on and off

IBM Power Systems
Physical power on button

Can be used for power on
HMC managed system power on command

Can choose power on options
Power off
Use HMC power off command
Shut down partitions first before powering off managed system
Pinhole reset button Display
Power button
!
Power and Blue buttons:

Attention LEDs Operator panel Scroll up, Enter, and
(for some models) Scroll down
Figure 6-3. Managed system power on and off AN111.0
Notes:
Basic power up
After the required cables are installed, and the power cables are connected, the power
button on the operator panel may be pushed to initialize the system. Not all POWER5 or
POWER6 processor-based systems have operator panels like the one shown in the
visual can, but if your model does (for example, IBM Power 570), you can use it to
power on the system. More likely, though, you will use the HMC to power on the
managed system and this procedure will be covered in this unit.
When you give the command to power on (either through the button or from the HMC),
the green power light goes from blinking to on continuously and any LEDs on I/O
systems will turn on. This indicates that power levels are satisfactory in the subsystems.

Instructor Guide
Operator Panel
Using the HMC to power on the managed system is recommended. However, the white
power button on the operator panel can be used to power on the managed system.

V5.3
Instructor Guide

Purpose Discuss basic power on procedures if you use the button on the operator
panel.
Details We are starting with the buttons in this unit; however, you should power the
system on and off through the HMC.
Additional information As with the previous visual, if a student has more detailed
questions, refer them to the service guides and the installation guides for the specific type
of system.
Transition statement That is an overview of the physical world, now we will discuss
how to power on the managed system with the HMC.

Instructor Guide
Managed system power on options

IBM Power Systems
Power on options
Partition standby
System profile
Partition auto start
Hardware Discovery
Power On
Figure 6-4. Managed system power on options AN111.0
Notes:
Introduction
The visual shows a managed system in the Power Off state. The HMC menu is shown
where you can choose to power on the system. This is the selected menu when the
managed system is selected. The next visual shows you the screen that displays after
choosing Power On on the menu.
HMC command for managed system power on

The chsysstate HMC command can also be used in an SSH session to change the
state of the managed system or partitions. Specific examples of power on commands
will be shown on the following pages.

V5.3
Instructor Guide
Uempty Scheduling the managed system power on

If desired, you can schedule an automatic managed system power on for a particular
date and time and it can be scheduled to repeat. Select the server in the Systems
Management Work pane; then expand Operations menu in the Tasks Pad and select
Schedule Operations task. We will discuss scheduling operations in a later unit.

Instructor Guide
Instructor notes:
Purpose Introduce the different power on options.
Details This visual is an overview of the methods of powering up the system from an
HMC. The next three visuals will go into greater detail on each of these methods.
Emphasize that this is the managed system power on procedure and not of a particular
partition. The managed system must be powered on before any partitions can be activated.
Transition statement So, the first of these options is partition standby.

V5.3
Instructor Guide
Uempty
Partition standby
IBM Power Systems
Is the starting point for building partition definitions

Allows for manual partition start process
Figure 6-5. Partition standby AN111.0
Notes:
Partition standby
The Partition standby power on option allows you to power on the managed system to
a state where it will support the creation and activation of partitions. No partitions will
automatically start. You can use this option if you wish to manually activate partitions or
if it is a new system that does not yet have any partitions. The managed system state
will be Standby.
HMC command for Partition standby power on option

You can use this command to power on the system with the standby option. Use the
proper managed system name instead of managedsysname in this example:
chsysstate -m managedsysname -o onstandby -r sys

Instructor Guide
Instructor notes:
Purpose Discuss the Partition standby power on option in greater detail.
Details Explain the purpose of the partition standby power on option. With a brand new
system, power on with the Partition standby option so you can create new partitions and
system profiles.
Point out the HMC command mentioned in the notes.
Transition statement Now, we will look at powering on using the System profile
option.

V5.3
Instructor Guide
Uempty
System profile
IBM Power Systems
Powers on with a predefined partition start order
All servers system

profiles will be listed.
Select one and click OK.
Figure 6-6. System profile AN111.0
Notes:
System profile
Using the HMC, you can create and activate often-used collections of predefined
partition profiles. This list of profiles is called a system profile and it defines the
partitions and their profiles that you want your system to use. You can create many
different system profiles and give each one a unique name.
When you activate a system profile, the system activates each partition profile listed in
the system profile, in the order that they are listed. For example, a company might want
to switch from using twelve partitions to using only four. To do this, the system
administrator shuts down the twelve partitions and activates a system profile which lists
the four partitions.
In the visual, there are two system profiles from which to choose, an110_ded and
lpar.systemprofile. The lpar.systemprofile profile is currently selected in the example,
but you can select another one.

Instructor Guide
System profiles can be used during the power on process or later after the system is
already powered on.
HMC command for System profile option

You can use this command to power on the system with the System profile option. Use
the actual managed system name and the actual system profile name.
chsysstate -m managedsysname -o onsysprof -r sys -f profilename

V5.3
Instructor Guide

Purpose Discuss the System profile power on option in greater detail.
Details In normal operations, the system profile might be the most common method of
powering up a system. It allows you to list the partitions (and their configurations, which are
kept in profiles) in the order that you want to start when the system is powered on. In this
way you can power on the system and activate a set of partitions all in one operation.
We will discuss later exactly what we mean by a profile and how to create these profiles
for the system and partitions.
Point out that if your system has multiple system profiles, you can pick which one to use on
this screen. The lpar.systemprofile system profile is currently selected but the
administrator can select the an110_ded profile system profile on this screen.
Mention that later we will see how to activate a system profile after the system has been
powered on. This is useful if you must activate a Virtual I/O Server and wait for it to start
completely before starting a number of client partitions.
Transition statement Lets see the Partition auto start power on option.

Instructor Guide

IBM Power Systems
Powers on and starts all partitions configured for auto start

Starts partitions with their last configuration
Figure 6-7. Partition auto start AN111.0
Notes:

This option powers on the managed system and then activates all partitions that have
been configured for auto start. This is configured by selecting the Automatically start
when the managed system is powered on check box on the Settings tab in the
partitions profile. The partition must have been activated previously with this option set
for it to auto start at the next power on operation.
When you shut down a logical partition and reactivate the logical partition using a
partition profile, the partition profile overlays the resource specifications of the logical
partition with the resource specifications in the partition profile. Any resource changes
that you made to the logical partition using Dynamic logical partitioning are lost when
you reactivate the logical partition using a partition profile. This is desirable when you
want to undo Dynamic logical partitioning changes to the logical partition. However, this
is not desirable if you want to restart the logical partition using the resource

V5.3
Instructor Guide
Uempty specifications that the logical partition had when you shut down the managed system. It
is best to keep your partition profiles up to date with the latest resource specifications.
If you shut down a logical partition whose partition profiles are not up to date, and the
logical partition is set to start automatically when the managed system starts, you can
preserve the resource specifications on that logical partition by restarting the entire
managed system using the partition auto start power-on mode. When the logical
partitions start automatically, the logical partitions have the resource specifications that
the logical partitions had when you shut down the managed system.
Autostart example
Here is an example that illustrates how auto start works. A partition is activated with a
profile that is configured with one processor and it is marked as an auto start partition.
Using Dynamic logical partitioning, a second processor is added to the partition. The
profile still says one processor, but the partition is now running with two. If you shut
down the partition, and power off the managed system, then restart the managed
system with the auto start power-on mode, that partition starts up with two processors.
HMC command for Partition auto start option

You can use this command to power on the system with the Partition auto start option:
chsysstate -m managedsysname -o on -r sys

Instructor Guide
Instructor notes:
Purpose Discuss the Partition auto start power on option in greater detail.
Details This option, when used to power on the system, starts any partitions that have
been configured as auto start partitions in their profile.
Review the auto start example student note to illustrate how the auto start option works
when partition configurations have been changed with Dynamic logical partitioning.
Point out exactly how to mark a partition as an auto start partition. This is mentioned in the
first paragraph of the students notes. To do this, select Automatically start when the
managed system is powered on check box on the Settings tab in the partitions profile.
Transition statement There is one more power on option to discuss: Hardware
Discovery.

V5.3
Instructor Guide
Uempty
Hardware Discovery
IBM Power Systems
Capture information about all I/O devices in the managed

system
After the inventory the managed system is in operating state
All logical partitions in Power-off state
Figure 6-8. Hardware Discovery AN111.0
Notes:
Hardware Discovery
The hardware discovery process captures informations about all I/O devices, in
particular, those devices not currently assigned to partitions. When you select the
Hardware Discovery power on option for a managed system, the managed system is
powered on into a special mode, which performs the hardware discovery. After the
hardware discovery process is complete, the system will be in Operating state with its
partitions in power-off state.
The hardware discovery process records the hardware inventory in a cache on the
managed system. The collected information is then available for use when displaying
data for I/O devices or when creating a system plan based on the managed system.
This option is available only if the system is capable of using the hardware discovery
process to capture I/O hardware inventory for the managed system. You can check if
your Power system has this capability by looking at Hardware Discovery Capable
capability value, in the Capabilities tab of the Managed System Properties panel.

Instructor Guide
Instructor notes:
Purpose
Details During the hardware discovery process, a logical partition named IOR Collection
LP is created. This logical partition disappears when the process ends.
Additional information The HMC also can use this capability (hardware discovery) to
enhance the information that it can capture when creating a system plan. System plans are
discussed in the HMC Management unit.
Transition statement Next, we will discuss what happens after you choose one of the
power on options.

V5.3
Instructor Guide
Uempty
System initialization (1 of 2)
IBM Power Systems
After power on, the system state will change and codes will
appear
Codes can be seen in Reference Code column
In the process of
powering on
Figure 6-9. System initialization (1 of 2) AN111.0
Notes:
Managed system states

After we choose one of the power on options, the state of the managed system will
change from Power Off to Initializing. At this point, youll see many codes appear in the
Reference Code column.
After the system finishes initializing, the state may change to Standby if Partition
standby was the power on option. As soon as a partition is activated the managed
system state will change to Operating.
If the state is Authorization Failure, it means that your HMC and your managed system
do not agree on the password to use to communicate with each other.
Reference codes
You can view the latest codes that have appeared in the Reference Code column of the
Systems Management > servers Work pane by looking under the Serviceability

Instructor Guide
application, clicking the Reference Code History option, when the managed system is
selected for POWER6 systems. For POWER5 systems, the history is available under
the Reference Code tab of the managed systems properties.
HMC command for viewing the state of the managed system

You can use this command to view the state of the managed system. Use the actual
managed system name.
lssyscfg -r sys -m managedsysname -F state --header
If you leave off the -F state --header options, you will see all of the available
information about the managed system.

V5.3
Instructor Guide

Purpose Discuss what happens after the system begins its power on process.
Details Describe the power on states for a managed system.
Describe how to view the codes that appear in the Operator Panel Value column after the
codes have already appeared.
Transition statement The next visual shows two managed systems, one with a state of
Operating and one with a state of Standby.

Instructor Guide
System initialization (2 of 2)
IBM Power Systems
Partition standby option places state in Standby

State changes to Operating when a partition is activated
Figure 6-10. System initialization (2 of 2) AN111.0
Notes:
Managed system Standby and Operating states

This visual shows an example of an HMC with its managed system at two different
states. The first example shows the managed system with the Standby state. It was
powered on and no partitions had been activated. The second example shows the
managed system in the Operating state and it has one partition running. When a
managed system has at least one partition running, its state will change to Operating.
A partition state of Not Activated means that it is not running, but it is ready to be
activated. A partition state of Running means that its operating system is running.
Interestingly, if the running partition were to be shut down, all partitions would show their
states as Not Activated but the managed system would still show its state as
Operating even though no partitions are running on it. So Standby simply means that
no partitions have been run yet.

V5.3
Instructor Guide

Purpose Discuss the difference between the Standby and Operating states.
Details This visual is a continuation of the example on the previous visual.
Show the students the difference between the two examples. The second one, which has a
state of Operating, has at least one partition that has been activated.
Mention that even if they shut down all partitions on a managed system, the managed
system state will remain Operating.
Transition statement Now, lets see how to power off the managed system.

Instructor Guide
Power off managed system (1 of 2)

IBM Power Systems
First, shut down the operating system in each partition

System might automatically power off when last partition shuts down
Properties of managed system, General tab:
Or, you may manually power off managed system
Figure 6-11. Power off managed system (1 of 2) AN111.0
Notes:
Power down partitions first

Before you power off the managed system, you must first shut down the operating
systems in each of the running partitions; otherwise, they will terminate abnormally,
which might lead to file system corruption. Log in to each partition and shut down the
operating system as you normally would in that particular operating system.
Alternatively, for AIX and Linux partitions, you can use the HMC to properly shut them
down. Select the partition name in the Systems Management Work pane then from the
Tasks pad, select Shut Down task in the Operation application tasks group. Or you
can use the HMC command chsysstate to shut down AIX and Linux partitions. This
operation will be covered in more detail in a later unit.

V5.3
Instructor Guide
Uempty Automatic power off

The first screen capture in the visual shows a portion of the managed systems
properties window on the General tab. If the check box is selected, then when the last
partition is shut down, the managed system will automatically power off. The default is
that this check box is selected.
Manual power off

To manually power off the managed system, make sure that no partitions are running on
that system, select the managed system name in the Systems Management Work pane
then from the Tasks pad, select Power Off task in the Operation application tasks
group. The next visual shows the window that opens when you do this.
HMC power off command

You can also power off the managed system using the chsysstate command. Use the
actual managed system name.
chsysstate -r sys -m managedsysname -o off

Instructor Guide
Instructor notes:
Purpose Describe the managed system power off procedure.
Details This page describes these main points:
Shut down partitions first before powering down the managed system.
You can power off the managed system from the HMC interface or from the HMC
command line.
The managed system can power off automatically when the last partition is shut down if
configured to do so. This option might be appropriate in a production environment, but
you might want to turn this off in a lab environment. It can be frustrating if the system
powers off when you do not wish it to because it takes time to power back on.
Describe the procedure to power off the managed system.
Transition statement When you issue the Power Off Managed System command from
the HMC interface, a window opens with power off options. The next page shows this
window.

V5.3
Instructor Guide
Uempty
Power off managed system (2 of 2)

IBM Power Systems
Power off options

Normal power off is the recommended option
Figure 6-12. Power off managed system (2 of 2) AN111.0
Notes:
Introduction
After issuing the Power Off Managed System command from the menu, you must
choose between the Normal power off procedure and the Fast power off procedure.
Normal power off: The system ends all active tasks in a controlled manner. During that
time, the service processor and the POWER Hypervisor are allowed to perform cleanup
(end-of-job-processing).
Fast power off: The system ends all active tasks immediately. The programs running in
the service processor and the POWER Hypervisor are not allowed to perform any
cleanup.
The HMC chsysstate command by default issues a normal power off. For fast power
off, add --immed to the end of the command. For example:
chsysstate -r sys -m managedsysname -o off --immed

Instructor Guide
Managed system states during power off procedure

During power off, the managed system states will change from Operating, to Power off
in Progress, to Power off.

V5.3
Instructor Guide
Uempty Instructor Notes:

Purpose Describe the managed system power off procedure.
Details Describe the two power off options.
Mention that if you are using the HMC command chsysstate you must add the --immed
flag at the end for the fast power off.
Transition statement Next is Power Management.

Instructor Guide
Power Management
IBM Power Systems
Figure 6-13. Power Management AN111.0
Notes:
Power saver mode

Using this menu, you can reduce the systems power consumption by changing the
power saver mode. When the power saver mode is enabled, the system lowers the
processor voltage and clock frequency to reduce the power consumption.
To configure power management settings for a managed system that is capable of
POWER6 Power Management, you can enable the power saver mode on this managed
system to reduce the power consumption of the processors.
Enabling the power saver mode on a managed system might affect the accuracy of any
performance monitoring tools that are running on the managed system. Changes to the
power saver mode take effect immediately without having to restart the managed
system.

V5.3
Instructor Guide
Uempty Power Saver Capable

The Capabilities tab of the System Properties panel shows if your system can use the
Power saver mode.
Firmware Power Saver Capable: When this value is True, the firmware that is
currently being used by the managed system allows you to enable the power
saver mode on this managed system. If this value is False, and the Hardware
Power Saver Capable value is True, upgrading the firmware used on the
managed system might enable the managed system to use the power saver
mode.
Hardware Power Saver Capable: When this value is True, the hardware on the
managed system allows you to enable the power saver mode on this managed
system. If this value is False, the managed system does not use processors that
support the power saver mode.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Next is the Checkpoint for this unit.

V5.3
Instructor Guide
Uempty
Checkpoint
IBM Power Systems
1. List at least two methods of powering on the managed system.
2. What are the different Power On options for a managed system?
3. Which option powers up the system using a predefined list of partition

profiles?
4. What is the difference between normal and fast power off options?
5. What HMC command can be used to power on or off the managed

system?
Notes:

Instructor Guide
Instructor notes:
Purpose Review concepts from this unit.
Details
IBM Power Systems

Operator Panel power button, ASMI, HMC Command Line,
HMC GUI application

System profile, Partition standby, Partition auto start, Hardware
Discovery

profiles?
System profile option
The normal option allows all active jobs to end in a controlled manner.
Fast causes jobs to end without cleanup processing.
5. What HMC command can be used to power on or off the managed system?
chsysstate

V5.3
Instructor Guide
Uempty
Exercise
IBM Power Systems
Unit
exerc
ise
Notes:

Instructor Guide
Instructor notes:

V5.3
Instructor Guide
Uempty
Unit summary
IBM Power Systems
Describe the role of the Operator Panel on an LPAR-

capable system
Power on a managed system using these power-on

options:
Partition Standby, System Profile, Partition Auto Start, or
Hardware Discovery
Enable the Power saver mode
Notes:
More review information:
Most systems have an Operator Panel
Typically, you use the HMC to power on systems
Power on a managed system using these power-on options:
- Partition standby, System profile, Partition auto start, or Hardware Discovery
- Use HMC Server Management application or HMC commands
- Be sure to shut down partitions first
You can enable the Power Saver mode if your managed system hardware and firmware
support it.

Instructor Guide
Instructor notes:
Purpose Summary
Details
of each day to review concepts learned during the previous day.
1) List the four managed system power-on options.
Answer: Partition standby, System profile, Partition auto start, and Hardware Discovery
2) Is it possible to shut down partitions and power off managed systems remotely?
Answer: Yes, the HMC chsysstate command can be used to power on or off the managed
system, and can be used to start and stop partitions. These commands could also be
performed remotely.
3) How does the auto start power on option work?
Answer: If partitions have been configured as auto start partitions, then they will start up
automatically when the system is powered on with the auto start option. The partitions will
start with their last configurations and not what is in any particular profile.
Transition statement That is enough about the managed system for now. Next, we will
discuss partitions.

V5.3
Instructor Guide
Uempty Unit 7. Planning and configuring logical partitions
Estimated time
01:30

This unit describes the basic resource configuration rules for partitions

- Minimum partition configuration
- Maximum number of partitions
- Partition IDs and naming conventions
- Partition and system profiles
Describe basic processor and memory configuration options
Define Minimum, Maximum, Desired settings for memory and
processors
Describe I/O concepts and the Required and Desired settings
Use the Create Partition wizard to create a basic partition and a
default profile
Edit a partitions configuration

Accountability:
Checkpoint
Machine exercises
References
IBM System p and AIX Information Center
IBM Systems Hardware Information Center
Copyright IBM Corp. 2009 Unit 7. Planning and configuring logical partitions 7-1
Instructor Guide
Links to Informations Centers

http://www.ibm.com/support/publications/us/library
The following documents can be accessed from the IBM Resource
link: http://www.ibm.com/servers/resourcelink
SA76-0098 Logical Partitioning Guide
SA76-0100 Advanced POWER Virtualization Operations Guide
SA76-0145 Introduction to Virtualization
SA76-0085 Operations Guide for the HMC and Managed Systems

V5.3
Instructor Guide
Uempty
Unit objectives
IBM Power Systems

Minimum partition configuration
Maximum number of partitions
Partition IDs and naming conventions
Partition and system profiles
Describe basic processor and memory configuration
options
Define Minimum, Maximum, and Desired settings for
memory and processors
Describe I/O concepts and the Required and Desired
settings
Use the Create Partition wizard to create a basic partition
and a default profile
Notes:
The objectives list what you should be able to do at the end of this unit.
Instructor Guide
Instructor notes:
Purpose Describe the objectives for this unit.
Details We will discuss the things you need to know to configure a basic partition.
Transition statement First, lets review what we mean by resources that can be
allocated into a partition.

V5.3
Instructor Guide
Uempty
Partition resources
IBM Power Systems
Resources are allocated to partitions

Processors, memory, and I/O slots
LPARs give you the flexibility to allocate resources

depending on need and not physical constraints
Processors
Memory
I/O Slots
Figure 7-2. Partition resources AN111.0
Notes:
Divide system resources

The first step in planning for dividing up your systems resources into logical partitions is
to decide what partitions you will have and what resources will be assigned to each
partition. This step is usually done during the sales process so that you know how large
a system you need to purchase.
System resources
The system resources are processors, memory, and I/O slots. When allocating I/O
slots, the granularity is a single I/O slot, which means if several devices are connected
to the adapter in a slot, all of the devices are allocated to a single partition.
Instructor Guide
Instructor notes:
Purpose Review what is meant by the term resources and the concept of assigning
these to partitions.
Details Describe what we mean by system resources (processors, memory, and I/O
slots). These are the resources that are allocated to partitions. I/O slots can be physical or
virtual.
Transition statement The next page describes the smallest resource configuration for
a partition.

V5.3
Instructor Guide
Uempty
Dividing the system resources (1 of 2)

IBM Power Systems

0.1 processing units if using shared processor pool or 1 processor if
dedicated
128 MB memory
Access to necessary I/O devices:
Adapter for boot disk
Network adapters
Smallest granularity for allocating additional resources
0.01 processing units if shared; 1 processor if dedicated
1 logical memory block (LMB) of memory
LMB sizes range from 16 to 256 MB
One I/O slot
Maximum number of partitions depends on system model and
available resources
Examples:
Maximum for our largest servers is 254 partitions
Maximum for a system with 4 physical processors is 40 partitions
Figure 7-3. Dividing the system resources (1 of 2) AN111.0
Notes:
Minimum partition size

The systems resources can be allocated in small units and are not dependent on
system building block boundaries. The smallest partition can be configured with one
processor core for partitions with dedicated processors, 0.1 processing units for
partitions running with shared processors, and 128 MB of memory. You need at least
one device from which to boot and a network interface card to support the service
monitoring functions and dynamic partition operations.
Logical Memory Block

The logical memory block (LMB) size determines the granularity of memory that can be
allocated to a partition. The LMB size varies between 16 MB and 256 MB, depending on
the amount of physical memory installed in the system.
Instructor Guide
The default LMB sizes are as follows:

Total System Memory Default LMB size
4 GB and less 16 MB
Greater than 4 GB and up to 8 GB 32 MB
Greater than 32 GB 256 MB
The LMB size can be changed using ASMI and can be found under the Performance
Setup menu option. You will need to power off and then power on the managed system
for the change to take effect. The default setting in ASMI is auto, which indicates that
the LMB size will be automatically set based on the amount of total system memory.

The maximum number of partitions that can be created on a system depends on the
system model. The maximum number of simultaneously running partitions depends not
only on the model but also on having enough system resources to support the number
of partitions. For example, a 2-processor IBM system p5 520 can have 20 partitions
created, but at most, you will be able to activate two partitions simultaneously if the
partitions are configured with dedicated processors. If the partitions use shared
processors, you will be able to create and activate up to 20 if you have enough adapters
to support the network and storage needs of the partitions, and you have purchased the
PowerVM standard edition (Advanced POWER Virtualization) feature.
All POWER5 and POWER6 processor-based systems support one partition per
dedicated processor. They will support ten partitions per processor if configured with the
PowerVM standard edition (Advanced POWER Virtualization) feature. With this feature,
this translates to a maximum number of partitions of ten times the number of physical
processors. For example if a IBM System p 520 has two physical processors, with
PowerVM editions, it has a maximum of 20 partitions. Other system examples include:
IBM Power 550: 40 partitions with 4 processors

V5.3
Instructor Guide

Purpose Describe the smallest partition configuration. List the maximum numbers of
partitions supported by each model.
Details Describe the smallest partition configuration supported by the HMC.
Applications and operating systems may, and probably will, demand additional resources.
The LMB size is important because it defines the granularity with which you can assign
memory. You can change this by connecting to the ASMI application and rebooting the
managed system.
Point out the student notes that discuss the maximum number of partitions. Each system
model has its own upper limit that can be created. In all cases, you are limited by the
number of processors and memory if the system has a small configuration.
Transition statement Your partition configuration settings are saved in profiles.
Instructor Guide
Dividing the system resources (2 of 2)

IBM Power Systems
Profiles
Partition profiles describe resources configurations for partitions
System profiles are collections of partition profiles
Custom groups (HMC v7 only)

Group system resources in a single view
ProfileA ProfileB ProfileC ProfileA ProfileB ProfileC
Partition profiles Partition profiles
Be sure to document the

configuration
Figure 7-4. Dividing the system resources (2 of 2) AN111.0
Notes:
Partition profile
A partition profile is a named configuration of resources for a particular partition. A
partition may have multiple partition profiles. For example, on Mondays through
Fridays, Partition 1 can be started with the profile named weekday, which contains a
maximum of resources. On the weekend, the same partition can be restarted with a
profile named weekend, which has a minimum of resources. Or, you might choose to
use dynamic LPAR operations to move resources.
When partitions are activated (started), you specify the partition profile by name.
System profile
A system profile is a named set of partition profiles. When you power on the managed
system you can choose to activate a particular system profile. A system profile is a list
of partition names and associated profiles that you wish to activate.

V5.3
Instructor Guide
Uempty Another benefit to system profiles, is that you can select its name and choose Validate
from the selected menu. This will check to see if there are any resource contention
issues and give you a report on detected conflicts.
Custom groups (HMC Version 7 only)

Custom groups provide a mechanism for you to group system resources together in a
single view or a way to organize the systems or partitions into smaller business or
workload entities
Custom Groups are comprised of logical collections of objects. You can report status on
a group basis, allowing you to monitor your system in a way that you prefer. You can
also nest groups (a group contained within a group) to provide hierarchical or topology
views.
There can be one or more user-defined groups already defined on your HMC. There are
default groups listed under the Custom Groups node under Server Management. The
default groups are All Partitions and All Objects. You can create others, delete the ones
that were created, add to created groups, or delete from created groups by using the
Manage Custom Groups task
Relationship between system and partition profiles

A partition profile belongs to a partition and its name must be unique for that partition. A
system profile is simply a collection of partition profiles. Later in this course you will see
that you can either start partitions individually using a partition profile name, or you can
start a set of partitions by using a system profile name.
Alternative configurations
A benefit of using logical partitions is that when you need extra resources, you can
periodically borrow those from other partitions. For example, in the old days, a company
that needed extra bandwidth only at the end of the month would have to purchase a
single system that can handle the maximum load and the rest of the month the system
would have extra resources that were unused. With logical partitioning, you can
reconfigure the system to borrow resources when you need them from non-critical
activities on other partitions. You can set up these alternative configurations by name
and restart the partitions with the new configurations whenever necessary. You may
choose to use DLPAR for temporary resource re-allocations rather than using different
profiles.
Keep track of the configurations

Be sure to document your configurations. You need to keep track of which partitions will
be active concurrently to ensure that you do not attempt to start partitions with resource
requirements that cannot be met.
Instructor Guide
Dynamic resources changes should also be documented and, if the changes will be
permanent, be sure to change the partition profile too so that when the partition is
activated the new configuration will be used.

V5.3
Instructor Guide

Purpose Define the concept of alternative configurations. Define system and partition
profiles.
Details Define system and partition profiles and describe the hierarchical relationship
between them.
Describe why you might need alternative configurations.
Emphasize the importance of manually documenting all of the profiles and what partitions
will be active concurrently. The HMC cannot tell you if you allocate resources that will be in
use by another partition because it does not know what partition profiles you might use
concurrently.
Transition statement Lets review profiles and the order of creation for partitions and
profiles.
Instructor Guide
Creating partitions and profiles

IBM Power Systems
Partitions name and ID

Partitions and profiles have names which can be changed easily.
Partitions have an LPAR ID, which cannot be changed on a partitions after it
has been created
Partition profiles
Used when the partitions is activated (started)
A partition can have more than one profile, but only one is in use at a time
System profiles
Can be used to activate a set of partitions at power on of the server or after
the server is already running
Or can be used to simply validate that there are no resource contentions for
a set of partitions
Custom groups (HMC v7 only)

Create group of objects; for example, servers and LPARs
Order of creation
1. Create a partition and its default profile
2. Create additional partition profiles, if desired
3. Create system profiles and custom groups, if desired
Figure 7-5. Creating partitions and profiles AN111.0
Notes:
Review partitions and profiles

A partition has a name and an ID number stored in a table. Partition profiles are named
resource configurations and attributes. System profiles can be created to provide an
easy way to either validate that partitions can run simultaneously with no resource
contention issues, or to easily start a certain mix of partitions and their profiles.
Custom groups provide a mechanism for you to group system resources together in a
single view or a way to organize the systems or partitions into smaller business or
workload entities, group of objects can be for example servers and LPARs.
Order of creation
When you create a partition, you must create its first (default) profile at the same time.
You can then create additional profiles with alternate configurations. When the partitions
and their profiles are created, you can create system profiles and custom groups.

V5.3
Instructor Guide

Purpose Review the concept of partitions and profiles.
Details Make sure students understand the relationships between partitions, their
profiles, and system profiles./ custom groups
Review how system and partition profiles are used:
Partition profiles belong to partitions.
The system can be (but does not have to be) powered on with a particular system
profile.
Partition profiles are also used when manually starting partitions.
When planning the configuration, you need to keep track of what partitions you are starting
and how much of the resources are already assigned to other partitions.
Transition statement Now, we will look at each system resource and the specifics on
assigning them to partitions. First, we will look at memory.
Instructor Guide
Memory resources (1 of 2)
IBM Power Systems
Memory allocation
One LMB (16 MB to 256 MB sized logical memory blocks)
For each partition, configure:

Minimum
Partition will not start if this amount is not available
Partition can be decreased to this amount if using dynamic LPAR
Desired
Partition will use up to this amount upon activation if available
Maximum
Partition can be increased to this amount if using dynamic LPAR
Used for sizing the page table for the partition
Figure 7-6. Memory resources (1 of 2) AN111.0
Notes:
Memory configuration
The smallest partition that can be defined on a POWER5 or a POWER6
processor-based system is 128 MB of memory. POWER5 systems support for partitions
running AIX V5.2 with the 5200-04 Recommended Maintenance package as minimum
AIX level. POWER5 and POWER6 systems support AIX V5.3, AIX V6.1, and Linux.
Although partitions can be configured with as little as 128 MB of memory, make sure
that you allocate sufficient memory for the partitions workload to avoid excessive
paging.
The most memory a partition can have is almost all of the physical memory on the
system. It can never use all of the physical memory, because some is reserved and
used for housekeeping tasks by the POWER Hypervisor.
Memory can be allocated in units as small as the size of the systems LMB, which
ranges from 16 MB to 256 MB.

V5.3
Instructor Guide
Uempty Minimum versus desired amounts of memory

Memory is configured with minimum and desired amounts. The system must be able to
allocate the minimum amount of memory or the partition will not start. The system will
attempt to allocate up to the desired amount of memory, in LMB size increments when
the partition is activated.
You might want to set the desired amount to the amount that you normally would use for
the partitions. The minimum should be set to an amount that allows you to not have to
exactly calculate the memory overhead or to allow for a different mix of partition profiles.
When starting multiple partitions, it is the partition that is started last that will end up with
fewer resources than desired if there are not enough resources on the system.
For partitions that support dynamic partitioning, the minimum setting for memory is the
amount of memory to which you can dynamically shrink the partition.
Maximum amount of memory

When you configure partitions, you also need to set a maximum amount of memory.
The maximum is the largest amount of memory that the partition might have if you add
memory dynamically. The HMC task for dynamic configuration of memory will not allow
you to move or add more memory to a partition that is already at its maximum limit. You
cannot change the maximum amount of memory dynamically.
The maximum amount of memory is also the amount that is used when calculating the
amount of memory needed for the page tables to support this partition. The amount set
aside is 1/64 of the value specified for maximum. For this reason, it is not advantageous
to set this maximum setting to an unreasonably high amount because it would waste
memory by setting memory aside for page tables that the partition does not need. For
example, if you create a partition that has a minimum setting of 8 GB, a desired setting
of 12 GB, and a maximum of 64 GB, the page table size would be set to support the 64
GB size and would be 1 GB. The desired setting of 12 GB only needs 256 MB of page
table space.
pSeries POWER4- versus POWER5 / POWER6 processor-based system

comparison
For POWER4, the smallest amount of memory a partition can have is 256 MB because
the POWER4 systems use an LMB that is 256 MB. For POWER4 systems with
pre-October 2002 firmware, the smallest amount of memory is 1 GB. POWER5 and
POWER6 processor-based systems support a minimum partition configuration of 128
MB.
Instructor Guide
Instructor notes:
Purpose Cover the rules for assigning memory to partitions.
Details Describe the amount of memory that can be assigned to a partition.
Describe the minimum, desired, and maximum settings.
Give an example of where the actual memory might be somewhere in between the
minimum and desired settings. For example, if the minimum is 2 GB, the desired is 3 GB
but there is only 2.25 GB available, then the partition would take the 2.25 GB. Explain that
if, later on, more memory becomes available, this does not affect the configurations of the
partitions (unless, of course, you choose to dynamically add some more memory).
There are two scenarios to cover regarding recommendations for the minimum and desired
settings:
a. Set the minimum and desired amounts for different mixes of partition profiles so that
the partition will start with as much memory as is available.
b. Set the minimum and desired amounts to allow for enough memory overhead room
so you do not have to exactly calculate this overhead.
Mention that if a system has plenty of processors but does not have a lot of memory,
memory could be the limiting factor in how many simultaneous, running partitions a system
can have. With the new lower limit of 128 MB of memory per partition, this is not likely, but
it is possible.
Transition statement Minimum and maximum memory amounts must also conform to
valid ranges.

V5.3
Instructor Guide
Uempty
Memory resources (2 of 2)
IBM Power Systems
Valid memory ranges are based on a ratio for minimum and

maximum settings
POWER5+ or POWER6 processor-based servers with AIX6:
Ratio is 1:8192 (maximum is effectively limitless)
For all other scenarios:
Partitions configured with < 256 MB of memory use a ratio of 1:16
Maximum cannot be > 16 times actual memory size
Example: 128 MB : 2 GB
Partitions configured with >= 256 MB of memory use a 1:64 ratio
Maximum cannot be > 64 times actual memory size
Example: 1 GB : 64 GB
Minimum Maximum
128 MB 2 GB 1:16 ratio
256 MB 16 GB 1:64 ratio
512 MB 32 GB
768 MB 48 GB
1 GB 64 GB
and so forth
Figure 7-7. Memory resources (2 of 2) AN111.0
Notes:
Valid memory ranges

The ratio discussed on this visual is between the amount the partition is actually using
when it is activated, and the maximum. The actual amount could be the desired
amount, the minimum amount, or some amount in between. Because you can
dynamically shrink the partition memory down to the minimum, use that amount for your
configuration planning. You do not want to be in a situation where the operating system
refuses to boot because it received less memory upon activation than it normally does.
The HMC will allow you to set the partition profile setting to a range outside of these
ratios; however, when you boot AIX it will fail.
An example AIX boot failure error message due to an invalid ratio is:
Fatal Error: Unsupported Memory:MaxMemory Ratio
Instructor Guide
Ratio specifics
For AIX 6 running on servers that support 64K memory pages (POWER5+ and
POWER6 processor-based servers), the maximum setting is effectively limitless given
the amount of possible physical memory in todays systems.
The all other scenarios referred to on the visual above means for:
Linux or AIX on servers that do not support 64K memory pages (POWER4 and
POWER5 processor based servers)
AIX versions prior to AIX 6 on POWER5+ or POWER6 processor-based servers
For those other scenarios, the following rules apply:
For partitions that are initially sized less than 256 MB, the maximum size cannot
be more than 16 times the current size. This scenario is rarely seen these days
since most LPARs wont boot with less than 256 MB anyway, particularly if they
have virtual adapters or Integrated Virtual Ethernet adapter ports. If AIX starts to
boot and hangs with no error, it could be because it is not configured with enough
memory.
For partitions initially sized 256 MB or larger, the maximum size cannot be more
than 64 times the current size.

V5.3
Instructor Guide

Purpose Describe the valid memory ranges for partitions.
Details The two important points here are:
1. AIX will refuse to boot if the memory is set outside of the valid ranges. The HMC does
not enforce these limits.
2. It is really not the delta between the minimum and maximum that is used, but the delta
between what is actually in use by the partition and its maximum. But because a
partition might start with as little as the minimum or you could shrink it down to the
minimum, you should use that configuration setting for planning how large the
maximum amount should be.
Transition statement The next visual shows the four ways memory is used.
Instructor Guide
Memory usage (1 of 2)
IBM Power Systems
Power Hypervisor memory Address N

TCE Memory
Variable in size
TCE memory
{
Partition 2
Used for DMA to I/O devices Partition 2 Memory
"chunks"
Page tables for each partition
Used for mapping partition pages
Size is 1/64th of partition maximum size
Page Table
Partition memory
Partition 1 { Partition Memory

"chunks"
Page Table
Hypervisor Memory
Address 0
Figure 7-8. Memory usage (1 of 2) AN111.0
Notes:
Introduction
This page lists the uses of memory on a managed system. You need to be aware of the
memory overhead when dividing up the memory between partitions to make sure you
have enough.
DMA on the visual is direct memory access.
POWER Hypervisor memory
The POWER Hypervisor requires memory to support the logical partitions on the server.
The amount of memory required by the POWER Hypervisor varies according to several
factors. Factors influencing the POWER Hypervisor memory requirements include:
Number of logical partitions
Partition environments of the logical partitions

V5.3
Instructor Guide
Uempty Number of physical and virtual I/O devices used by the logical partitions
Maximum memory values given to the logical partitions
The POWER Hypervisor memory is always located at Address 0 in physical memory.
Translation Control Entries memory

Translate Control Entries (TCE) memory is used to translate the I/O addresses to
system memory addresses. This is a global amount of memory that is not based on the
number of partitions. This memory is allocated for the total number of I/O slots on a
system regardless of whether they are actually used. TCE memory is always allocated
at the top of physical memory.
TCE memory is not new for System p systems. In a non-LPAR system, AIX uses some
of the system memory for TCE tables. In a partitioned environment, the TCE tables are
allocated separately from memory that is allocated to any individual partitions, since this
then allows I/O slots to be moved dynamically from one partition to another. Dynamic
LPAR operations on I/O slots would not be possible if a partition controlled the physical
memory used for its TCE tables.
Partition page tables

Page tables are used to map physical memory pages to virtual memory pages. Like the
TCE tables, page tables are not a unique overhead for LPARs. In other AIX non-LPAR
systems this overhead memory is part of the memory that AIX allocates at boot.
Each partition needs 1/64th of its memory size, rounded up to a power of 2, for page
table space in memory. The amount of page table space that is allocated is based on
the maximum memory setting in the partitions profile.
Memory is allocated in LMB size segments. If a partition needs less than one LMB of
page table space, it will allocate an entire LMB. However, multiple partitions can share
one LMB if the accumulative page table amounts required fit within a single LMB.
Instructor Guide
Maximum Partition Memory Page Table Space

128 MB 2 MB
256 MB 4 MB
512 MB 8 MB
768 MB 16 MB
1 GB 16 MB
1.25 - 2 GB 32 MB
2.25 - 4 GB 64 MB
4.25 - 8 GB 128 MB
8.25 - 16 GB 256 MB
16.25 - 32 GB 512 MB
32.25 - 64 GB 1 GB
64.25 - 128 GB 2 GB
128.25 - 256 GB 4 GB
256.25 - 512 GB 8 GB
and so forth
Partition memory
Partition memory is the memory that you assign to a partition and is used by the
operating system.

V5.3
Instructor Guide

Purpose Describe how memory is divided up when in LPAR mode. Describe the
additional memory requirements when using partitions.
Details Cover each of the memory uses and how much memory they use.
Discuss how to figure out how much partition page table memory overhead is used by
various sizes of partitions (refer to the information in the student notes).
Transition statement The next page shows how to take the guesswork out of
configuring memory.
Instructor Guide
Memory usage (2 of 2)
IBM Power Systems
Where is all the memory?

Check the Managed Systems property sheet
Physical
Currently
free to use
832 MB in use as
overhead
(TCE, POWER
Hypervisor, and page
tables)
4224 MB in use
for the partitions
Figure 7-9. Memory usage (2 of 2) AN111.0
Notes:
Where did the memory go?

You can check the current memory usage of a system by viewing the Memory tab in the
managed systems property sheet as shown in the visual. Select the managed system
name in the HMC System Management for HMC v7, click Properties from the menu,
then click the Memory tab.
This screen shows the following information.
Installed memory: This is the amount of total physical memory installed in the
system.
Deconfigured memory: This is the amount of physical memory deconfigured by
the system due to a detected hardware error.
Available memory: This is the amount of memory currently free for use by
partitions. This memory is not currently assigned to any partition.

V5.3
Instructor Guide
Uempty Configurable memory: This is the amount of installed memory less the amount
of deconfigured memory.
Memory region size: This is the logical memory block (LMB) size.
Current memory available for partition usage: This is the amount of
configurable memory for partition usage. This amount will vary depending on the
number of partitions that are defined for this system.
System firmware current memory: This is the amount of memory used by
TCE, POWER Hypervisor, and page tables. This value wasnt displayed with
HMC version 6.
Partition Memory Usage table: This table shows partitions and the amount of
memory configured for each. Unlike POWER4 systems, these partitions do not
necessarily have to be running to show up in this property sheet.
The partitions do not have to currently be running for the memory and processor usage
information to show the amount allocated to the partitions.
Memory in use by Hypervisor, TCE memory, and page tables

With the HMC Version 7 and later, the memory used by the system firmware is
displayed in the system properties. This is not the case with HMC version 6. With HMC
version 6, you can determine how much memory is reserved for the Hypervisors
housekeeping tasks and how much memory is available for partition use. To calculate
the overhead memory amount, you would have to subtract the current memory
available for partition usage from the configurable memory amount.
Using the HMC command line for memory information

Memory information can be seen using the following HMC command:
lshwres -r mem -m managedsysname --level sys
Here is an example command on a managed system called sys046.
hscroot@sys13hmc:~> lshwres -r mem -m sys136 --level sys
configurable_sys_mem=16384,curr_avail_sys_mem=11328,pend_avail_sys_mem=1
1328,installed_sys_mem=16384,max_capacity_sys_mem=deprecated,deconfig_sy
s_mem=0,sys_firmware_mem=832,mem_region_size=64,configurable_num_sys_hug
e_pages=0,curr_avail_num_sys_huge_pages=0,pend_avail_num_sys_huge_pages=
0,max_num_sys_huge_pages=0,requested_num_sys_huge_pages=0,huge_page_size
=16384,total_sys_bsr_arrays=16,bsr_array_size=8,curr_avail_sys_bsr_array
s=16
Instructor Guide
Instructor notes:
Purpose Describe how to determine memory usage on a system.
Details Explain how to get to this properties screen.
Because the amount of memory the Hypervisor uses is variable, use this screen to see
what memory has been allocated for overhead and what is available for use.
Transition statement That is it for memory. Lets discuss the processor configuration
guidelines.

V5.3
Instructor Guide
Uempty
Processor resources
IBM Power Systems
Processor allocation
Dedicated or shared processors
Increments can be in 0.01 processing units (for shared)
For each partition, configure:

Minimum
Partition will not start if this number is not available
Partition can be decreased to this number if using
dynamic LPAR
Desired
Partition will use up to this number upon activation if available
Maximum
Partition can be increased to this number if using dynamic LPAR
Figure 7-10. Processor resources AN111.0
Notes:
Processor allocation
A partition can have as little as one dedicated processor or 0.1 shared processing units,
as much as all of the processor resources in the system, or any number between.
A dedicated processor can be assigned to only one active partition at a time. Shared
processing units are accessed from a single Shared Processor Pool.
Dynamic allocation
If dynamic partitioning is supported for a particular partition, then processors or
processing units can be added and removed dynamically. Dynamic means that you do
not have to reconfigure the partition profile and then restart the partition; that is, you can
add or remove processors while the partition is running.
Instructor Guide
Unassigned resources
It is okay to have free resources, such as processors, that are not assigned to any
partition. They are simply not used. They can be kept in reserve to be added
dynamically to partitions as they are needed.
Free processors are part of the shared processing pool. If a partition with dedicated
processors is activated, the processors are taken from the shared pool and assigned
exclusively to that partition.
There are two check boxes in the partition profiles properties labelled Allow when
partition is inactive and Allow when partition is active. If the check box is selected,
then when the partition is shut down, its processors return to the shared pool. If the
second check box is selected, then the active partition can cede its idle CPU cycles to
the Shared Processor Pool. This option is available only on POWER6
processors-based systems.
Minimum resources
Minimum resources are the resources that are required for a partition. If there are not
enough resources to meet this required minimum then the partition will not start.
Minimum resources are typically what you need to have if you were to run the partition
in a diminished capacity.
For partitions that support dynamic partitioning, the minimum setting is also the number
of processors to which the partition can shrink.
Desired resources
Desired resources are what you would like to have for normal operation of the partition.
When you start the partition, the system will allocate the number of available processors
up to the desired number.
Using minimum and desired settings

Set the desired setting to the amount you would like for normal operation and the
minimum setting to what your application could handle if a resource failed or is needed
by another partition.
For example, lets say the desired processor setting for a partition is 6 and the minimum
is 5. If a processor is automatically deconfigured from the system because of errors or
is taken by another partition, and the partition is later reactivated for some reason, then
the partition would be able to start with just five processors instead of six.
You can also use the minimum and desired settings if a particular profile will be used
with a different mix of other partition profiles. Sometimes our example partition will start
with six processors, and sometimes it will start with five.

V5.3
Instructor Guide
Uempty One of the steps in planning for partitions is deciding the order in which the partitions
will be started on the system. The minimum and desired resource settings are important
because if there are not enough resources, it is the last partition that you activated that
will end up with either less than the desired amount or not enough resources to start.
Maximum resources
The maximum setting defines the largest number of processors you can assign to this
partition. The HMC task for dynamic configuration of processors will not allow you to
add more processors to a partition that is already at its maximum limit.
Instructor Guide
Instructor notes:
Purpose Cover the rules for allocating processors to partitions.
Details Describe the allocation of processors to partitions. You must have a minimum of
one processor core per partition for dedicated processor partitions and 0.1 for shared
processor partitions.
Dedicated processors are not shared between partitions.
The maximum configuration setting for processors is used for only one thing: this is the
upper limit of the number of processors a partition can have when you add processors
dynamically.
You cannot pick which physical processors to allocate to a partition. You get whichever
ones are available when the partition starts. For dedicated processor partitions, the system
will use affinity information for the hardware to attempt to assign processors and memory
with some degree of locality. Processors (cores) will be allocated from the same chip or
MCM where possible, and memory will be local to those processors where possible.
On POWER4-based systems, if the maximum or minimum value needed to be changed
while the partition was running so that there was greater flexibility for dynamic LPAR
operations, you could simply alter the active profile for the partition and the change would
be immediate. On POWER5 and POWER6 processor-based systems this is no longer an
option. You cannot change the minimum and maximum values for a running partition and
have the change be dynamic, so make sure you plan ahead and set them to something
reasonable.
Transition statement That is it for processors. Now, lets look at I/O resources.

V5.3
Instructor Guide
Uempty
I/O resources
IBM Power Systems
A partition requires a minimum of:

One boot device in allocated I/O slot
One network adapter in allocated I/O slot
Other I/O adapters for storage and network access
I/O slots can be required or desired

Empty slots can be allocated to a partition
Useful if not able to allocate dynamically
Allocation to partitions is by individual slots

Multiple devices connected to a single SCSI adapter are allocated together
PowerVM standard Edition (Advanced POWER

Virtualization) feature allows for virtual SCSI and Shared
Ethernet configurations
Must install and configure Virtual I/O Server software
Figure 7-11. I/O resources AN111.0
Notes:
Boot device
You need to boot a partitions operating system from a disk or some other device and
the I/O slot that controls this device must be assigned to the partition.
Network adapter
Each partition needs at least one network adapter. This is used for general network
communications between the partition and the HMC, for Service Focal Point, and for
dynamic LPAR communications. This adapter can be shared with regular user network
traffic as well.
Other network and I/O adapters

Realistically speaking, most applications will need more disks, tape drives, and so forth,
to function.
Instructor Guide
Required versus desired

The partition will start only if all of the required slots are available and it will attempt to
assign those that are desired. Slots that are required cannot be dynamically removed or
moved from the partition.
Plan for which resources will be allocated to partitions

I/O slots can be dynamically added and removed to and from partitions that allow
dynamic operations.
You might want to purchase additional CD-ROM drives, tape drives, and other devices
that each partition will need to use. You need to know what PCI adapters are installed
on the I/O drawers and to which partition each will be allocated.
Empty slots
You can allocate empty slots to partitions if you plan to add PCI adapters to the system
at a later time.
Mix of devices on a single SCSI adapter

Be careful of the mix of devices that you attach to a single SCSI adapter because it is
the adapter that is allocated to a partition (or more accurately, it is the slot that it is in).
For example, if you had a single DVD-ROM drive on a system and it was connected to
the same SCSI adapter as a partitions boot disk, you could not then reallocate that
adapter to another partition that may need to use that DVD-ROM device.

V5.3
Instructor Guide

Purpose Cover the rules for planning to assign I/O slots to partitions.
Details Describe that you need to divide up the I/O devices between partitions and that
I/O slots cannot be shared.
Also, if you currently use devices that are shared in a network environment, this is
unaffected by the partition allocations. You will continue to be able to share these network
devices between partitions as you normally would between networked systems.
Transition statement Now lets finish with the virtual SCSI and virtual Ethernet options.
Instructor Guide
Virtual SCSI devices

IBM Power Systems
Virtual SCSI configurations allow a client LPAR to use the

physical storage on a Virtual I/O Server partition
Backing storage might be a logical volume, a physical volume or an optical
media drive
Must install and configure Virtual I/O Server software
On the client, you need to know the virtual adapter ID that

the server has set up for that client
The server configures Virtual I/O Client LPAR The client
a virtual SCSI server configures a
Server (AIX or
adapter using the virtual SCSI
HMC Linux)
client adapter
using the HMC
which points to a
The backing storage specific Virtual
is set up on the Physical Virtual device I/O Server and its
Virtual I/O Server storage virtual adapter ID
command line
Adapter 14 Adapter 8
Figure 7-12. Virtual SCSI devices AN111.0
Notes:
Terminology
Virtual I/O is the term used to describe the ability to share physical I/O resources
between partitions.
Backing storage is the term for the physical devices that will be used as virtual devices
for client partitions. A backing storage device is associated with a specific virtual SCSI
server adapter. More than one device can be associated with a single virtual SCSI
server adapter.
Virtual SCSI is a type of virtual device where a Virtual I/O Server is configured to allow
other partitions to use its disk or optical devices. These devices do not need to be SCSI
type devices; for example, the optical media drive is an IDE type device. The disks can
be whole disks or logical volumes on the Virtual I/O Server. When the client views the
devices from its operating system, it appears as an hdisk or a cd device. For example, if
the Virtual I/O Server configures a logical volume named lv_client1, in the clients
operating system this device is an hdisk.

V5.3
Instructor Guide
Uempty Configuring the client to use a virtual SCSI disk involves configuring the backing
storage on the Virtual I/O Server first. Then, when configuring the client you need to
know which adapter on the Virtual I/O Server to configure. For example, if the
administrator for the Virtual I/O Server says that adapter 18 is for your client, then when
you configure your clients virtual SCSI adapter you specify the Virtual I/O Servers
virtual slot 18. Thats all there is to it when configuring the client to use virtual devices.
Instructor Guide
Instructor notes:
Purpose Describe what a virtual SCSI device is.
Details Describe the types of virtual SCSI devices that can be setup with a Virtual I/O
Server.
Describe roughly how the virtual SCSI client is configured. Just say that when you create
the client adapter you specify the Virtual I/O Server and the virtual adapter ID that has been
set up for that client. How the server is configured is outside the scope of this course. As
part of the create LPAR wizard screens coming up in the next section of this unit, the
students will see the screen where the client configures a virtual SCSI client adapter.
Additional information If asked, another new type of backing storage was added in
November 2007 called file-backed.
Transition statement Next, the virtual Ethernet options are described.

V5.3
Instructor Guide
Uempty
Virtual Ethernet options

IBM Power Systems
Two choices for Virtual Ethernet, both configured with the HMC:
Virtual Ethernet adapter:
Networking between multiple LPARs on same server
Hypervisor acts as the Ethernet switch
Virtual I/O Server can bridge the virtual Ethernet traffic to an external
network using a physical adapter
This configuration is called a Shared Ethernet adapter
Integrated Virtual Ethernet adapter (IVE):

Also known as the Host Ethernet Adapter
POWER6 processor-based systems only
Physical adapter that can be shared by up to 16 or 32 partitions
(depending on the model purchased)
Each partition configures a logical port associated with a physical port on
the Host Ethernet Adapter
Figure 7-13. Virtual Ethernet options AN111.0
Notes:
Virtual Ethernet adapter

Virtual Ethernet adapters can be configured in multiple partitions on the same server
and these adapters appear as ent devices to the AIX operating system and eth devices
to Linux. To connect this virtual Ethernet to an outside network, a bridge can be
configured in a Virtual I/O Server called a Shared Ethernet adapter.
Integrated Virtual Ethernet adapter

This adapter, also known as the Host Ethernet Adapter, is a physical adapter integrated
into all POWER6 processor-based servers. It is considered virtual because the physical
ports on this adapter can be shared by multiple partitions. A partition configures one of
the logical ports on the adapter and the logical port appears as an ent device to AIX or
as an eth device to Linux.
Instructor Guide
Instructor notes:
Purpose Describe the two virtual Ethernet options.
Details Differentiate between the two types of virtual Ethernet options. Mention that
these are in addition to the physical Ethernet adapters partitions might have.
Transition statement Next, well start the process to create a partition using the Create
LPAR Wizard.

V5.3
Instructor Guide
Uempty
Create a logical partition: System state

IBM Power Systems
Managed system must be powered on and its status must be

Operating or Standby.
Figure 7-14. Create a logical partition: System state AN111.0
Notes:
Introduction
The first step in creating partitions is to power on your managed system. You do this
from the System Management > Servers Work pane on the HMC. Any of the
managed system power on options will bring your system up to a state where partitions
can be created.
Instructor Guide
Instructor notes:
Purpose Describe that the system must be powered on before you can create
partitions.
Details Point out that we are in the Systems Management user interface. This user
interface contains a tree view of managed resources. Resources might include Servers,
Frames, and Custom Groups.
Show the Operating state for the managed system.
Transition statement Next, we will see how to begin creating a partition.

V5.3
Instructor Guide
Uempty
Create logical partition wizard

IBM Power Systems
Select a server in the work pane table; then click Configuration > Create
Logical Partitions > AIX or Linux
Figure 7-15. Create logical partition wizard AN111.0
Notes:
Introduction
To access the Create Logical Partition menu, select the server name in the Work pane
table (click the Select column). Select the Configuration task group from the tasks
pad. Expand the task group then, select the task, and then click Create Logical
partition > AIX or Linux. The task window opens. You can also use the context menu
button (double right arrows) that is displayed next to the object name you have
selected. Click the button and the task groups menu is displayed for that particular
object. Click Configuration > Create Logical Partition > AIX or Linux.
Instructor Guide
Instructor notes:
Purpose Describe how to access the menu to create partitions.
Details The visual shows the tasks pad that appears below the Work pane when you
have selected an object you want to work with. The tasks are available for the currently
selected target objects in the navigation pane tree or the Work pane table view.
The context menu lists the tasks groups appropriate for the selected object. Context menus
are available only for table selections. For example, in the Select column of the Servers
Work pane table, select the object you want to work with. The context menu button is
displayed next to the object name you have selected. Then select a task to open for the
object.
Transition statement The next visual shows the Create Logical Partition wizard that
displays after you click Create Logical Partition > AIX or Linux menu option.

V5.3
Instructor Guide
Uempty
Partition ID and name

IBM Power Systems
Enter a partition ID and name.
Name can be
changed later in
partition properties
Figure 7-16. Partition ID and name AN111.0
Notes:
Introduction
After you specify the partition ID and name, click the Next button to proceed to the next
wizard screen.
Partition IDs
The first screen in the Create Logical Partition wizard allows you to set the partition ID
and the partition name.
The partition ID will default to the next available number, but you can override it. The
partition ID number must be a whole number that is between one and the total number
of partitions that the system will support. For example, on a p5-520, the number must
be a number from 1 to 20. Partition IDs are occasionally used in command outputs and
can be seen in some HMC applications.
Instructor Guide
When your partition has an operating system and is booted, you can view its partition ID
and partition name with the AIX uname -L command or the lparstat -i command. For
example:
# uname -L
2 partition2
Partition name
The partition name can be very long and contain spaces. If you plan to use the
command line interface on the HMC, the partition names should be easy to type.
Quotation marks will need to be used on the command line if a partition name contains
spaces.

V5.3
Instructor Guide

Purpose Describe how to set the partition ID and partition name.
Details Describe the rules for setting partition IDs and naming partitions.
Mention the uname -L command for determining a partitions ID and name from within the
partition itself.
Transition statement Next, you must name the default partition profile.
Instructor Guide
Profile name
IBM Power Systems
Enter a partition profile name.
Name can be
changed later by
editing the profile
Check if this will be the only partition

and it will use all of the resources on the
server
Figure 7-17. Profile name AN111.0
Notes:
Partition profile name

A partition must have at least one partition profile, which contains the resource
configuration information. When you create a partition, you create the default profile.
The default profile can be changed to a different profile later. The default profile is the
one that is used when you activate a partition if you do not choose a different profile.
Like the partition name, the profile name can be very long and contain spaces. If you
plan to use the command line interface on the HMC, the partition names should be easy
to type. Quotation marks will need to be used on the command line if a profile name
contains spaces. Typically, profile names are descriptive of what is different between it
and another profile.

V5.3
Instructor Guide
Uempty Use all the resources in the system check box

You can set a partition profile so that, when it is activated, the logical partition uses all of
the resources on the managed system. If you add additional resources to the managed
system, and then activate such a partition profile, the logical partition automatically
recognizes and uses the resources that you have added.
Because all of the hardware (both required and desired) is assigned to this partition, no
other partitions can be started when this partition is running. Likewise, the partition that
uses all of the system resources cannot be started while other partitions are running.
Instructor Guide
Instructor notes:
Purpose Describe the default partition profile and partitions that use all hardware
resources.
Details Describe what is meant by a default partition profile.
Describe when to use the check box for using all resources on the system.
Transition statement Next, we will select the processor type: dedicated or shared.

V5.3
Instructor Guide
Uempty
Set processor type

IBM Power Systems
Figure 7-18. Set processor type AN111.0
Notes:
Set processor type

The first question about processors to answer in the wizard program is whether the
partition will use shared or dedicated processors.
When you click the Next button to proceed to the next page, the actual page you see
will depend on whether you specified shared or dedicated processors.
Instructor Guide
Instructor notes:
Purpose Describe how to configure the type of processors that this partition will use.
Details Choose dedicated or shared processors for this partition on the screen shown in
the visual. It is not possible to mix the two types of processors in the same partition.
Transition statement The next page allows you to specify the quantity of dedicated
processors.

V5.3
Instructor Guide
Uempty
Configure dedicated processors

IBM Power Systems
Figure 7-19. Configure dedicated processors AN111.0
Notes:
Dedicated processors
Dedicated processors are allocated in whole numbers from one to the total number of
available physical processor cores.
Instructor Guide
Instructor notes:
Purpose Describe how to set the quantity of dedicated processors.
Details Enter whole numbers for dedicated processors.
Transition statement The next screen allows you to specify the quantity of shared
processors.

V5.3
Instructor Guide
Uempty
Configure shared processors

IBM Power Systems
Figure 7-20. Configure shared processors AN111.0
Notes:
Configure shared processors

Configure the quantity of processing units for this partition.
For the purpose of this course, well leave all of the advanced processor options (virtual
processors and uncapped status and weight) at the default values.
Instructor Guide
Instructor notes:
Purpose Show where to configure the processing units for a shared processor partition.
Details The intent of this visual is to show where to configure the shared processing
units for a partition. You can ask the students to answer questions about Minimum,
Desired, and Required values as described earlier in this unit.
Transition statement Next, well see how to configure memory.

V5.3
Instructor Guide
Uempty
Configure memory
IBM Power Systems
Figure 7-21. Configure memory AN111.0
Notes:
Allocate memory
The visual shows the screen where memory is configured for a partition. The GB and
MB settings are additive; so if the desired setting is set to both 2 GB and 256 MB, then
that partition will have a desired setting of 2.25 GB.
Set the minimum, desired, and maximum settings using the configuration rules
described earlier in this unit. You can use the up and down arrows, or type in values, to
enter the amounts.
The granularity for setting the memory amount is the LMB size.
After setting the amounts for memory, click the Next button to proceed to the next page.
Instructor Guide
Instructor notes:
Purpose Describe how to allocate memory to a partition.
Details Describe how the GB and MB settings are additive and how to set the minimum,
desired, and maximum amounts.
Mention that in very high performance environments you may wish to configure huge page
memory. The configuration cannot be changed dynamically. You can see the huge page
memory configuration options only if you select the Show details check box. Mention also
that this Show details check box is no more available on HMC Version 7 and later.
Managing huge pages can only be done by modifying the logical partition profile properties.
Ask the students the following questions:
1. What happens if the partition starts with a certain amount of memory and the maximum
is greater than 64 times that amount.
- Answer: AIX would fail to boot.
2. What happens if the partition settings are within a valid range, but the maximum amount
is higher than it needs to be.
- Answer: There would be wasted memory allocated to page table space.
3. To illustrate how the minimum and desired numbers work together, tell the students to
look at the configuration amounts in the visual. What would happen if only 512 MB of
memory was available when this partition is activated?
- Answer: The partition would get 512 MB.
Transition statement Next, we will see how to allocate I/O slots.

V5.3
Instructor Guide
Uempty
Configure I/O slots

IBM Power Systems
Select the slot first, then click

the required or desired button
Figure 7-22. Configure I/O slots AN111.0
Notes:
Allocating I/O slots

The panel list all buses and slots found for the system. The Unit column displays the
unit number of the system unit or expansion unit in which each I/O slot is located. The
Slot column displays the slot ID that identifies each I/O slot within the unit and bus.
If the slot has an adapter, the label will be displayed in the description column. You can
select an adapter and click the Properties button for more details on that adapter. To
get more details on a slot, you can click the slot number (it's a link with POWER6) or
select an adapter and click the Properties button (Power5).
To allocate slots to a partition, select a slot and click either the Add as required or Add
as desired button. If you change your mind after adding a slot, select it and click the
Remove button.
Instructor Guide
Instructor notes:
Purpose Describe how to configure I/O slots for a partition.
Details Explain that the panel is a list of all I/O on the system. To list slots in the
configuration, select them in the panel and click the proper button for desired or required
slots.
Point out the column named Added that indicates a slot is required or desired.
Mention that this is how physical slots are allocated to partition. Virtual I/O slots are
configured in a totally different way and this is covered in a future unit.
Transition statement Next, you are asked about setting up virtual I/O.

V5.3
Instructor Guide
Uempty
Virtual I/O adapters setup

IBM Power Systems
Maximum virtual adapters value

Must be greater than the number of virtual adapters expected to be configured
Cannot be changed dynamically
Use the Actions menu to add

virtual adapters
Specify the maximum number

of virtual adapters (default is
10 for AIX/Linux partition)
Figure 7-23. Virtual I/O adapters setup AN111.0
Notes:
Configuring virtual adapters

On the Virtual Adapters screen, use the Actions menu to create a new virtual SCSI or
virtual Ethernet adapter. This virtual Ethernet adapter is the virtual Ethernet in which the
Hypervisor acts as the network switch for partitions on the same server. The next visual
shows the screen for configuring the virtual SCSI adapter.
Maximum number of virtual adapters

By default, a new AIX or Linux partition will have the maximum number of virtual
adapters set to ten. This can be increased on this screen. This maximum number
cannot be increased dynamically while the partition is running, so be sure to increase
this number if youll need more than eight additional virtual adapters. If you do need to
increase this number later, you can make the change in the profile properties and
re-activate the partition.
Instructor Guide
Serial adapter
There are two serial adapters to support the partition console connections. Do not
delete these or make any additional serial adapters.

V5.3
Instructor Guide

Purpose Describe how to specify whether a partition will use virtual I/O adapters.
Details Point out the Actions menu, the table of existing virtual adapters, and the
maximum number of virtual adapters input box.
Mention that after you use the Actions menu to create an adapter, the new adapter will be
listed in the table on the virtual adapters screen.
Transition statement Next, is a page to specify a Logical Host Ethernet Adapter.
Instructor Guide
Logical Host Ethernet Adapter (1 of 3)

IBM Power Systems
Choose an HEA to define an LHEA
Choose which physical port
Click Configure button
Figure 7-24. Logical Host Ethernet Adapter (1 of 3) AN111.0
Notes:
Logical Host Ethernet adapters (LHEA)

This LHEA is the integrated physical Ethernet adapter on POWER6 processor-based
servers which can be shared with up to 16 or 32 partitions. Each partition will configure
a logical port on which is associated with a physical port. All partitions configured for the
same physical port will share the bandwidth of that port.
This adapter is also known as the Integrated Virtual Ethernet (IVE) adapter.
Configuring a logical port

To configure this partition for a logical port, first use the pull down at the top to choose
which HEA to use. A multiple system drawer p570 server will have an IVE in each
system drawer.
Next, select which physical port this partition will use.
Ignore the LHEA Capability option as this option is not yet fully implemented.

V5.3
Instructor Guide
Uempty After having selected the physical port, the next step is to configure a LHEA port for that
particular logical partition by clicking the Configure button.
Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Lets see the LHEA configuration window for selecting the logical
port

V5.3
Instructor Guide
Uempty

IBM Power Systems
Select a logical port

that is
unassigned
Allow all VLAN IDs
Notes:
Use this window to select the logical port to use for the physical port that you selected in
the LHEA page. The logical partition will be able to connect to the physical port on the
HEA using the logical port that you select here.
You can also select VLANs in which the selected logical port can participate. The logical
port does not need to participate in any VLANs. You can set the logical port to
participate in all VLANs, or you can set the logical port to participate in up to 20 VLANs
that you specify. After clicking the OK button, youll return to the screen shown in the
last visual.
Instructor Guide
Instructor notes:
Purpose Describe how to configure a logical port.
Details
Transition statement The next screen is the LHEA table once the logical port has been
selected.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Notes:
Once the Logical Host Ethernet Adapter port is configured, it appears in the LHEA table
in the column Logical Port IDs associated with the physical port of the selected HEA.
The ID numbers of the virtual LANs in which the logical port can participate are
displayed in the Allowed VLAN IDs column.
Instructor Guide
Instructor notes:
Purpose
Details
Transition statement There are a few more optional settings to set for this partition

V5.3
Instructor Guide
Uempty
Optional settings
IBM Power Systems
Figure 7-27. Optional settings AN111.0
Notes:
Connection monitoring
This determines if this partition will have its network connection with the HMC monitored
by service tools. If the partition is monitored, if there is a connection failure, it will be
logged in the service tools.
Automatically start with the managed system

If you want this partition to automatically start when you choose the managed systems
Partition Auto Start power on option, then select this check box.
Enable redundant error path reporting

Select this option to enable the reporting of server common hardware errors from this
logical partition to the Hardware Management Console. The service processor is the
primary path for reporting server common hardware errors to the HMC. Selecting this
Instructor Guide
option allows you to set up redundant error reporting paths in addition to the error
reporting path provided by the service processor.
Server common hardware errors include errors in processors, memory, power
subsystems, the service processor, the system unit vital product data (VPD),
non-volatile random access memory (NVRAM), I/O unit bus transport (RIO and PCI),
clustering hardware, and switch hardware. Server common hardware errors do not
include errors in I/O adapters (IOAs) or I/O device hardware.
If this option is selected, this logical partition reports server common hardware errors
and partition hardware errors to the HMC. If this option is not selected, this logical
partition reports only partition hardware errors to the HMC.
This option is available only if the server firmware allows you to enable redundant error
path reporting (the Redundant Error Path Reporting Capable option on the Capabilities
tab in Managed System Properties is True).
Boot modes
You can set the default boot mode for this partition profile. When you activate a partition
you can override the default boot mode.
Normal: This option uses the normal bootlist stored in the partition NVRAM.
System Management Services (SMS): This option does not use the normal bootlist,
but instead stops at SMS upon activation of the partition.
DIAG_DEFAULT: This selection is similar to Power On Diagnostic Stored Boot List
Profile (DIAG_STORED), except the system boots using the default boot list that is
stored in the system firmware. This is normally used to try to boot diagnostics from the
CD-ROM drive. This is the preferred way to run stand-alone diagnostics. This can also
be used to boot from CD-ROM to install the operating system.
DIAG_STORED: This selection 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. This is the preferred way to run online diagnostics.
OPEN_FIRMWARE: This profile is used by service personnel to obtain additional
debug information. When this selection is enabled, the system boots to the Open
Firmware prompt.

V5.3
Instructor Guide

Purpose Describe the Optional Settings when creating partitions.
Details Describe the three settings on this page: connection monitoring, auto start, and
the default boot mode.
Transition statement That is it. The only page left is the summary page to check that
you have not made any mistakes.
Instructor Guide
Check logical partition profile summary

IBM Power Systems
Figure 7-28. Check logical partition profile summary AN111.0
Notes:
Summary
The last page that displays when you create a partition is the Profile Summary page.
Check over all of the configuration settings that you chose. You can click the Back
button to fix anything, or click the Finish button to create the partition and its default
profile.
Additional partition profiles

To create additional partition profiles, you can either copy an existing profile and edit it,
or you can create a new one. When you create new additional profiles for a partition,
youll see all of these screens again except the very first one where you set the partition
ID.

V5.3
Instructor Guide

Purpose Describe the purpose of the summary page.
Details Simply check the configuration and click the Finish button to complete the
create partition procedure.
Transition statement Now that your partition and its profile have been created, you
might want to edit the configuration.
Instructor Guide
Editing a partition's configuration

IBM Power Systems
After a partition is created, you can edit its configuration from the
partition properties or from the partition profile properties:
Manage Profiles screen:

Select profile name and
choose Actions -> Edit
Figure 7-29. Editing a partitions configuration AN111.0
Notes:
Editing the partition properties

Usually, a partitions properties are viewed to see the partitions current configuration.
For example, if partition2 has two processors listed in its profile then later you use the
dynamic logical partitioning feature to add one more, the profile will still list two
processors but the properties will show the current configuration of three processors.
There are a few configuration options available in the partition properties. These
changes are dynamic, that is, you do not need to re-activate the partition for these
changes to take effect.

V5.3
Instructor Guide
Uempty Editing the partition profile

There are two reasons to edit a partitions profile. First, you may need to change the
configuration and second there are some additional configuration options only available
in the profile after the partition has been created. The changes only take effect after the
partition is shut down and activated again. This is covered in more detail on the next
page.
Instructor Guide
Instructor notes:
Purpose Describe how to edit a partitions profile.
Details
Transition statement Now, lets look at additional configuration options that are not
available in the Create LPAR Wizard.

V5.3
Instructor Guide
Uempty
Additional configuration options (1 of 2)

IBM Power Systems
Not all partition configuration options are available in the

Create LPAR wizard
Commonly used additional partition properties screen options:
Change LPAR name (General tab)
Configure dedicated processors for sharing mode (Hardware, Processors tab)
Configure Available Physical Processor (app) performance statistic
Figure 7-30. Additional configuration options (1 of 2) AN111.0
Notes:
Partition configuration options available in the properties screens

The visual above summarizes the configuration options available in the partition
properties screens. Most information is read-only but there are a few items that are
dynamically configurable.
The app statistic is viewable from performance analysis commands such as the
lparstat AIX command. You can enable the app statistic by checking the Allow
performance information collection checkbox.
The processor sharing modes are specific to dedicated processors. The first checkbox
will enable the dedicated processors to return to the shared processing pool (to be used
by shared processor partitions) when this partition is shut down. The second checkbox
allows idle dedicated processor cycles to be donated to the shared processing pool.
The dedicated processor has priority and will regain the dedicated processors
dynamically when it needs them.
Instructor Guide
Instructor notes:
Purpose Describe that if you make a change in the properties of a partition, that change
is dynamic.
Details Detailed discussion of the processor sharing modes is beyond the scope of this
course.
Transition statement Next, lets see what additional options are in the partition profile
screens.

V5.3
Instructor Guide
Uempty
Additional configuration options (2 of 2)

IBM Power Systems
Some additional options are only found in the partition

profile properties:
BSR arrays
Huge page
memory
Figure 7-31. Additional configuration options (2 of 2) AN111.0
Notes:
Page sizes for very high-performance environments (Huge page

memory)
In addition to 4 KB and 64 KB page sizes, AIX supports 16 MB pages, also called large
pages, and 16 GB pages, also called huge pages. These page sizes are intended to be
used only in high-performance environments, and AIX will not automatically configure a
system to use these page sizes.
The number of pages of each of these page sizes must also be configured. AIX can not
automatically change the number of configured 16 MB or 16 GB pages based on
demand.
The memory allocated to 16 MB large pages can only be used for 16 MB large pages,
and the memory allocated to 16 GB huge pages can only be used for 16 GB huge
pages. Thus, pages of these sizes should only be configured in high-performance
environments. Also, the use of 16 MB and 16 GB pages is restricted: in order to allocate
Instructor Guide
pages of these sizes, a user must have the CAP_BYPASS_RAC_VMM and

CAP_PROPAGATE capabilities, or root authority.
You can specify the desired, minimum, and maximum amount of huge page memory for
a partition profile. When you activate this partition profile, the system commits a huge
page memory amount to the logical partition. The number of pages of huge page
memory that the system commits to the logical partition depends upon the settings on
this page and the availability of system resources.
Configuring the number of huge pages

Huge pages must be configured through a system's Hardware Management Console
(HMC), and is supported on systems with POWER5+ and POWER6 processors but is
not supported on systems with POWER5 processors. If your managed system has
POWER5 processors, you will not see information related to huge page memory.
The managed system must first be configured with a pool of huge pages before they
can be allocated to partitions. This configuration requires the managed system to be
powered off. Configure the number of requested pages on the managed systems
Properties Advanced tab first, then you will be able to assign 16 GB huge pages to
individual partitions by changing the partitions profile. Applications must be altered to
specifically request the use of 16 MB or 16 GB pages.
Barrier Synchronization Register (BSR) Arrays

The BSR is a logical facility within a system that provides a means to accomplish barrier
synchronization between software tasks in a manner more efficient than utilizing
standard memory based synchronization flags and algorithms.
While BSR was available with POWER5 and POWER5+ processor-based servers, it
was not configurable in multiple partitions; the entire BSR was assigned to the partition
configured as the service partition. With POWER6, the BSR facility may be partitioned
by allocating arrays to individual LPARs in 8-byte granules.
Configuring the BSR in a partition may provide performance optimization with certain
types of code, for example, numerically intensive single instruction multiple data (SIMD)
code. Do not change the configuration of the BSR unless an LPAR will be used to run a
software application that is written to explicitly use the BSR facility. The
documentation/instructions for the software should indicate the number of BSR arrays
required.

V5.3
Instructor Guide

Purpose Describe these two advanced memory options.
Details Emphasize that these two memory options should not be configured unless an
application which will be installed in this partition needs to use them.
Additional information In addition to 4 KB and 64 KB page sizes, AIX supports 16 MB
pages, also called large pages, and 16 GB pages, also called huge pages.
Transition statement Its time for a checkpoint.
Instructor Guide
Checkpoint (1 of 2)
IBM Power Systems
1. Match the terms Minimum, Desired, and Maximum to the proper

description:
a. This is the upper limit of processors or memory that cannot be exceeded when
using dynamic operations.
b. This is the lower limit of processors or memory when using dynamic operations.
c. This is the amount of processors or memory that a partition receives if there are
more than enough resources on the system when the partition is activated (starts).
2. True or False: The amount of desired processors must always be

greater than or equal to the amount of minimum processors.
3. What is the minimum amount of memory for an AIX V5.3 or AIX

V6.1 partition?
4. True or False: Empty I/O slots can be allocated to partitions.
Notes:

V5.3
Instructor Guide

Purpose Check students understanding of concepts in this unit.
Details Give the students 5 minutes to complete both pages of Checkpoint questions.
Solution:
IBM Power Systems

description:
using dynamic operations. Maximum
Minimum
more than enough resources on the system when the partition is activated
(starts). Desired


V6.1 partition?
128 MB or, if the LMB size of the partition is 256 MB, then the
minimum would be 256 MB.
Transition statement There is another page of questions.
Instructor Guide
Checkpoint (2 of 2)
IBM Power Systems
5. What happens if the minimum (or required) amount of a resource is not

available when a partition is activated?
6. How many processors is a partition allocated if, when it starts, it has a
minimum of three processors, desires five processors, and four
processors are currently available on the system?
7. What happens if a partition is currently running with its three minimum
processors, but it desires five processors and another processor
becomes available after the partition is started?
8. What is the granularity of allocating processor resources when
configuring partitions?
9. When incrementing the amount of memory for a partition profile, the
minimum unit is how much?
10. Can you assign the HEA itself to a logical partition?
Notes:

V5.3
Instructor Guide

Purpose Check students understanding of concepts in this unit.
Details Solution:
IBM Power Systems
5. What happens if the minimum (or required) amount of a resource is not available when a
partition is activated?
The partition will not start.
6. How many processors is a partition allocated if, when it starts, it has a minimum of three
processors, desires five processors, and four processors are currently available on the system?
It starts with four processors.
7. What happens if a partition is currently running with its three minimum processors, but it desires
five processors and another processor becomes available after the partition is started?
Nothing
8. What is the granularity of allocating processor resources when configuring partitions?

For dedicated processor partitions, allocations are made in units of 1. For partitions
using the shared processor pool, allocations are made in units of 0.01, with a minimum
allocation of 0.1 processing units.
9. When incrementing the amount of memory for a partition profile, the minimum unit is how
much? It is
the amount of the LMB (16 MB 256 MB)
10. Can you assign the HEA itself to a logical partition? No,
multiple logical partitions can connect directly to the HEA and use the HEA resources.
Instructor Guide
Exercise
IBM Power Systems
Unit
exerc
ise
Notes:

V5.3
Instructor Guide

Instructor Guide
Unit summary
IBM Power Systems

Partition IDs and naming conventions
Partition and system profiles
Describe basic processor and memory configuration options
Define Minimum, Maximum, and Desired settings for memory and
processors
Describe I/O concepts and the Required and Desired settings
Use the Create Partition wizard to create a basic partition and a
default profile
Notes:
Partition concepts:
- Minimum partition configuration
Processors, memory, I/O slots
- Maximum number of partitions depends on model and amount of resources
- Partition profiles contain resource configuration information
- System profiles are lists of partitions and profiles to start in a particular order
Minimum, Maximum, and Desired settings for memory and processors
Required and Desired settings for I/O slots
Create Partition wizard leads you through creating partitions and profiles

V5.3
Instructor Guide

Purpose Review each objective and check in with the students that they feel that they
have met these objectives.
Details
1) What is the smallest LMB size?
Answer: The smallest LMB size can be 16 MB. This is the default for systems with 4 GB of
physical memory.
2) What is the minimum amount of memory that you can configure in an AIX or Linux
partition?
Answer: 128 MB
3) Just using the number of processors as your guide, how many partitions can be
supported on a system?
Answer: If all other resources are available, a system can support up to one partition per
physical processor if using dedicated processors. If using shared processors, then each
physical processor can support 10 partitions.
4) What are the minimum and maximum memory settings used for?
Answer: These are the lower and upper bounds for DLPAR operations. The maximum
amount also sets the page table size for the partition. The minimum amount must be met
when the partition activates or the activation will fail.
5) What partitions are started when you use the Auto Start power on option to power
on the managed system?
Answer: Those partitions with Automatically start with managed system check box
selected on the Optional Settings tab in the partition profile.
Transition statement The next unit covers the additional partition operations.
Instructor Guide

V5.3
Instructor Guide
Uempty Unit 8. Partition operations
Estimated time
01:00

This unit describes the procedures for operations with partitions, such
as activating, stopping, and backing up partition profile data. Also
covered are ways to troubleshoot activation failures.

Activate and shut down partitions
Modify, copy, and delete partition profiles
Create, modify, delete, and activate system profiles
Open and close terminal windows
Change partition availability priority
Back up and restore partition profile data
Troubleshoot partition activation errors

Accountability:
Checkpoint questions
References
Copyright IBM Corp. 2009 Unit 8. Partition operations 8-1

Instructor Guide
Unit objectives
IBM Power Systems

Schedule operations on partitions
Notes:

V5.3
Instructor Guide

Details Summarize what will be covered and what the students should be able to do by
the end of the unit.
This unit covers operational activities that you can do with partitions in the Server
Management application and has three sections:
1. The first section covers how to activate and shut down partitions, which was covered
briefly in a previous unit.
2. The next section of this unit covers things that you can do to partitions and their profiles
such as copying, deleting, and backing up profiles. Also included is how to create and
use system profiles.
3. The last section in this unit covers activation failures and how to figure out why your
partition will not activate.
Transition statement We will start this unit by looking at the HMC Web-based user
interface: Systems Management.

Instructor Guide
Web-based user interface: Systems Management

IBM Power Systems
Create, copy, delete, back up system and partition profiles

Activate partitions
Managed
Systems
Figure 8-2. Web-based user interface: Systems management AN111.0
Notes:
Introduction
The navigation pane in the left portion of the window, contains the primary navigation
links for managing your system resources and the HMC. This pane contains the primary
navigation links for managing your system resources such as the Systems
Management. When Systems Management is selected, its contents, which might
include Servers, Frames, and Custom Groups, are displayed in the Work pane. To view
the partitions defined on a server, you can select it from the Navigation pane on in the
Work pane.
When a server is selected in the Navigation pane, the Work pane displays all logical
partitions defined on the server.

V5.3
Instructor Guide
Uempty Functions in the Systems Management node

The bullets in the visual list some common tasks that are performed when using the
System Management node. You can create system and partition profiles, activate (start)
partitions, shut down and restart operating systems, power on and off the system,
watch the status codes, and open virtual console windows.
Managed system
In the visual, the managed systems are in the Operating state. The status column lists
the current state for the managed system. Example states for a managed system are:
Power Off: The managed system is powered off. Partitions cannot be configured or
started. Power is available to the service processor but system devices (such as I/O)
are not initialized.
Initializing: The managed system is powering on and is running through its initialization
procedures. These procedures can take 5 minutes to an hour depending on the
configuration of the system.
Standby: The managed system was powered on using the Partition Standby power
on option and no partitions have been started.
Operating: The managed system is powered on and functioning normally. At least one
partition has been activated.
Pending Authorization: The HMC is attempting to gain authorization from the
managed system.
Authorization Failure: The passwords used by the HMC and the managed system for
authorization for the HMC do not match.
Incomplete: This state signifies that the HMC cannot gather complete logical partition,
profile, or resource information from the managed system. Rebuild the managed
system to correct.
No Connection: The HMC is not connected, or the handshake with the managed
system failed. You might need to reset the connection from the HMC to the managed
system.
Recovery: In this state, the save area for the service processor is not synchronized
with the HMC database. You might need to restore the partition data from a backup.
Error: This state automatically generates a call to the service support center if the
function is enabled. If the function is not enabled, contact IBM support.
CoD Click To Accept: The old capacity card has been replaced; enter the activation
code.
CoD Recovery: The Capacity on Demand agreement process waits for confirmation;
click the specified button to confirm.

Instructor Guide
In addition, the Status column displays icons representing an unacceptable state, active
Attention LED, or both.
HMC command to determine managed system state

The HMC command to determine the managed system state is:
lssysscfg -r sys -m managedsysname -F state --header
Reference code column

The Operator Panel Value column will display both boot and error codes for the
managed system. Just click the reference code in the table to get detailed description.
Available processing units

This column displays the amount of processing units that are available for assignment
to logical partitions on the managed system. This is the total number of processing units
that are activated on the managed system minus the number of processing units that
are assigned to the logical partitions, including the logical partitions that are shut down.
Available memory
Displays the number of memory that is available for assignment to logical partitions on
the managed system. This is the total amount of memory that is activated on the
managed system minus the amount of memory needed by managed system firmware
minus the amount of memory that is assigned to the logical partitions, including the
logical partitions that are shut down on the managed system.
Optional attributes in the table

The Servers Work pane table can also display some other optional attributes in the
table, such as:
Serial Number
Type-Model
CoD Processor Capable
CoD memory Capable
Permanent Processors and so on
These optional attributes can be displayed when you click the Column configuration
icon on the table toolbar.

V5.3
Instructor Guide
Uempty Launching tasks for managed objects

After you have chosen the objects to work with (the server) you are ready to perform the
appropriate tasks on them. The tasks the objects can perform include the following task
groups:
Operations
Configuration
Connections
Hardware (Information)
Updates
Serviceability
Capacity on Demand

Instructor Guide
Instructor notes:
Purpose Describe the primary navigation links for managing your system resources,
and introduce the things that you can do there.
Details Point out the Navigation panel (left) and the working pane (right).
Describe how to select an object and how to launch tasks for managed objects.
Describe the functions of the status, Available Processing, Available Memory, and
reference code columns. We will cover the different partition states on an upcoming page.
Additional information If you happen to have an HMC hooked up to a projector in the
classroom, you could demonstrate how to get to the partition management area. Show how
to select an object and to launch tasks for managed objects.
Transition statement First, we will talk about different ways of activating partitions.

V5.3
Instructor Guide
Uempty
Activating partitions
IBM Power Systems
To start a partition, you activate it

When a partition is activated
You choose which partition profile to use
What happens depends on the partition profile configuration
Partitions can be activated by one of these methods:

Activate a system profile
Activate an individual partition
Configure partitions to automatically activate when managed system is powered on
Scheduled operation
Activations can be done either in the HMC interface or with the

HMC chsysstate command
For example:
chsysstate -m msname -r lpar -o on -f profilename -n LPARname
Figure 8-3. Activating partitions AN111.0
Notes:
Activating partitions
To activate a partition means to begin the process to boot its operating system.
Partitions can be activated with a menu command in the HMC interface, at power-on of
the managed system, as a scheduled operation, or when a system profile is activated. A
system profile is a named list of partitions and their profiles which are activated in the
order in which they are listed.
The managed system must be in the Standby or Operating state to activate a partition.
Partition boot options

One of the configuration options in partition profiles is the boot option. This can be set to
different values depending on the type of operating environment (that is, AIX/Linux or
i5/OS) for which the partition has been configured. For example, you could set the boot
option to load the operating system or to stop at an open firmware prompt.

Instructor Guide
Instructor notes:
Purpose Define what is meant by activating a partition and describe that there are
multiple ways to do this.
Details Do not discuss the actual procedure to manually activate a partition yet; we will
get to that on the next visual.
The student notes mention that partitions can be activated as a scheduled operation. The
students will have a chance to explore this in the lab.
Transition statement Now, lets see the procedure to activate a partition.

V5.3
Instructor Guide
Uempty
Activate partitions with a system profile

IBM Power Systems
A system profile can be used to activate partitions either during

system power on or after it is already on
System state
is Standby or
Operating
Select system
profile name and
click Activate
Figure 8-4. Activate partitions with a system profile AN111.0
Notes:
Introduction
You can start multiple partitions with one command by using a system profile.
Remember that a system profile is a named list of partitions and their profiles. All of the
partitions in that system profile will be activated in the order that they are listed.
The HMC does not wait until partitions operating systems are fully operational before
activating the next partition in the system profile list. So if there are dependencies
between partitions (such as with a Virtual I/O Server and its clients), you might need to
start some partitions first manually or have multiple system profiles.
You can use a system profile to start multiple partitions even if there are already
partitions running. If a partition is already running, you will get a warning, but the
partition will not be affected if a system profile attempts to activate it again.

Instructor Guide
There are two ways to activate a system profile. One is during power on of the system,
and one is after the system has already been powered on to the Standby or Operating
state.
Activating a system profile after system is powered on

1. Select the system name object in the working pane; then use the context menu
button or the tasks pad to access the Manage System Profile window.
2. Select one system profile; then click Actions > Activate. This is illustrated on the
visual.
Activating a system profile during power on of the system

When you power on the system, there are four power on options (this was covered in a
previous unit):
System Profile
Partition Auto Start
Partition Standby
Hardware Discovery
If you choose System Profile, you will be asked which system profile you want to use.
This option will be unavailable to you until you create a system profile.
HMC command for activating a system profile

You can use the chsysstate command to activate a system profile. For example, this
command activates the system profile with the name xyz. The managed system must
be powered on first before executing this command. Replace managedsysname with the
actual managed system name.
chsysstate -m managedsysname -r sysprof -n xyz -o on

V5.3
Instructor Guide

Purpose Describe the procedure to manage system profiles, how to select one then to
Activate it in the Manage System Profiles window.
Details Discuss why you would want to activate partitions by using a system profile.
Mention that if a system crashes and reboots, it does not look for a particular system profile
to use. NVRAM has information on what partitions were running and with what
configurations. It uses this information to configure the system.
Describe the two procedures to activate a system profile:
1. Activate a system profile when the managed system is already powered on
2. Activate a system profile when the managed system is powering on
Transition statement Now we will look at how to activate individual partitions.

Instructor Guide
Activating an individual partition

IBM Power Systems
Partition must be in the Not Activated state
List of
LPARs
Managed
systems
HMC command:
chsysstate -m MSname -r lpar -o on -n lparname -f profile
Figure 8-5. Activating an individual partition AN111.0
Notes:
Introduction
To activate a partition manually, select either the partition name or its profile and choose
the Activate option from the menu.
To activate partitions, the managed system must be powered on and in either the
Standby or the Operating state.
Partition Status column

The status column for partitions can have the following values:
Not Activated: The partition is ready to be activated.
Running: The partition has finished its boot routines. The operating system
might be performing its own boot routines or is in its normal running state.

V5.3
Instructor Guide
Uempty Not Available: This partition is not available for use. Logical partitions will be
listed as Not Available if the system is powered off.
Shutting Down: The partition has been issued the Partition Shut Down
command and is in the process of shutting down.
Open Firmware: The partition has been activated and started with the open
firmware boot option.
Error: The last attempt to activate the partition failed. Fix the activation issue and
use the Activate menu option to activate the partition.
Partition must be in the Not Activated state to activate

Partitions that are in the Not Activated state are available to be activated. You can view
the state of a partition from the HMC interface or by issuing an HMC command
remotely. If a partition has an Error state due to an activation error, you may need to
shut down the partition first before attempting to re-activate. To do this, select the
partition name, then click the context menu and click Operation > Shut Down. This
procedure is covered later in this unit.
To view the states of all partitions on a particular managed system, use this HMC
command:
lssyscfg -r sys -m managedsysname -F name,state --header
Here is an example command and its output for a managed system named sys046:
hscroot@hmc:~> lssyscfg -r sys -m sys046 -F name,state --header
name,state
sys046,Operating
To see just a single partitions state, you must use the filter option to the lssyscfg
command. Beware! The filter names do not match the field names in the lssyscfg
output. You must look at the lssyscfg man page for the valid filter names.
Here is an example command using a filter and its output on a system named sys046
looking for the state of the partition named sys046_v3_T6. The output is Running.
hscroot@hmc:~> lssyscfg -r lpar -m sys046 --filter
"lpar_names=sys046_v3_T6" -F state
Running
Activating a partition
To activate a partition, select the partition name, click the context menu button and click
Operation > Activate on the menu. Another window opens, which is shown in next
visual. This default partition profile will be selected automatically in the window that
opens.

Instructor Guide
Alternatively, you can select the partition profile name, in the Managed Profiles window.
click Actions, and click Activate on the menu.
HMC commands for activating a partition

The HMC command to activate a partition is shown below. Use the actual managed
system name for managedsysname, the actual partitions name for partitionname and
the actual partition profile name for profile.
chsysstate -m managedsysname -r lpar -o on -n partitionname -f profile

V5.3
Instructor Guide

Purpose Describe how to activate a single partition manually.
Details This visual shows how to manually activate a single partition.
Describe how the state of the partition will change from Not Activated to (hopefully)
Running.
If the partition state is Not Available it is probably because the managed system is not
powered on yet.
If the state is Open Firmware, open a terminal window to the partition if you wish to boot it
to the operating system. You will need to use whatever the proper open firmware procedure
is for booting. For example, with AIX V5.3, exit out of the SMS screens to boot AIX V5.3
To shut down a partition at the Open Firmware state, use the Shut Down menu option to
shut down the partition.
Additional information If the partition state is Open Firmware and the partition is in
SMS, if you want to boot the operating system, you can just exit SMS using the menu
options. However, if the state is Open Firmware and the LED code is AA00E1A8, then the
partition is at the Open Firmware prompt; there is no menus or anything else to guide you.
You can try typing boot to start the boot sequence, or you can use the HMC menus to stop
the partition.
Transition statement When you activate a partition, a secondary window opens which
is shown on the next page.

Instructor Guide
Activating with open terminal window

IBM Power Systems
Select the profile name and optionally select the terminal

window checkbox
Figure 8-6. Activating with open terminal window AN111.0
Notes:
Introduction
The window shown in the visual opens after you select a partition profile for activation. It
verifies the correct partition name and has the profile already selected. You can choose
whether open the virtual terminal window as part of the activation process.
Complete the activation of a partition

On this window, check to make sure the correct profile name is selected and choose
whether you want to open a console window when the partition starts. If you do, select
the check box and then click OK.
No errors will occur if you do not open a terminal window and you can open a terminal
window later after the partition is already running. This procedure is covered in a few
pages.

V5.3
Instructor Guide
Uempty If a virtual console window already open for this partition, do not select the check box
and it will use the same open window. The window might still be open because you just
used it to shut down the operating system.

Instructor Guide
Instructor notes:
Purpose This is a continuation from the previous page to continue the partition
activation procedure.
Details The only thing you will have to do in this dialog box is check (or change) the
profile, select the open terminal window check box, and then click OK.
A page is coming up that describes the features of the virtual console window.
Transition statement Lets look at the virtual terminal windows.

V5.3
Instructor Guide
Uempty
Terminal window: Normal boot

IBM Power Systems
Copy and LPAR name

paste from Change font and managed
Edit menu and text size system name
with Font
menu
Figure 8-7. Terminal window: Normal boot AN111.0
Notes:
Introduction
This visual shows an example terminal window on a Windows PC to a partition running
the AIX V6.1 operating system. When the AIX V6.1 boot is successful, you will see the
Console login: prompt.
You can have only one Virtual Terminal Session to a particular partition open at any one
time.
Window border
Notice that the top window border lists the partition name (sys046_v3_T6), and the
managed system name (sys046). This helps to keep track of which window belongs to
which partition.

Instructor Guide
Introduction to the Virtual Terminal

The virtual terminal implementation provides a means for a system console to be
accessed on logical partitions that have no physical serial port assigned. Operating
systems need a console for things like operating system installations, boot processes,
and for some service types of functions.
Virtual Terminal facts

An xterm window is used as the terminal emulator when running natively on the HMC.
When running remotely using the WebSM client application (HMC Version 6 and
before), a component of the IBM Host on Demand package is used to supply a
Java-based terminal emulator, which emulates a vt320 terminal. The terminal is an
adaptation of the IBM Host on demand terminal emulator.

V5.3
Instructor Guide

Purpose Illustrate what a virtual console window into a partition looks like.
Details The virtual console window looks and feels similar to a typical character-based
session.
Mention that all of the normal boot messages show up in the window just like any other
console.
Transition statement Next, we will see the window that opens if you click the
Advanced button on this visual.

Instructor Guide
Activating with advanced options

IBM Power Systems
Click the Advanced button to choose override options.
Figure 8-8. Activating with advanced options AN111.0
Notes:
Introduction
This is the window that opens if you click the Advanced button shown in the previous
visual.
You can use this feature to override the keylock position (manual or normal) and boot
mode settings in the partition profile configuration.
The Boot mode list varies depending on the operating system environment the partition
is configured to use (AIX/Linux, i5/OS, or Virtual I/O Server). The keylock position has
significance for only i5/OS.

V5.3
Instructor Guide

Purpose Discuss the advanced partition activation options.
Details These features are convenient if you sometimes want to activate the partition in
a certain way. You do not need to alter the partition profile to accomplish this.
Transition statement What if you forgot to open a console window when you activated
a partition? The next page describes how to open a console window for an active partition.

Instructor Guide
Open or close a terminal window

IBM Power Systems
You can also open (or close) the terminal window when a
partition is already running.
Figure 8-9. Open or close a terminal window AN111.0
Notes:
Open a virtual terminal window for a running partition

If there is not an open virtual terminal window for an active partition, you can select the
partition name, click the context menu button, and click Console Window > Open
Terminal Window.
Close a terminal window

There are two ways to close a virtual terminal.
1. The preferred, usual method of closing a terminal window, is to use the icon in the
upper left corner to close the window. This removes the window from the desktop
and closes the connection.
2. You might need to force a virtual terminal window to close by selecting the partition
name object in the working pane of the HMC, click the context menu, and click
Console Window > Close Terminal Connection. Use this procedure when the

V5.3
Instructor Guide
Uempty virtual terminal window is already open (by another user) and you want to turn off
that session or as a recovery in case you cannot close the window for some reason.
HMC commands to open and close a terminal session

You can open a virtual terminal session to a partition after it is activated, with the
following HMC command:
To open the session: mkvterm -m managedsysname -p partitionname
Alternatively, you can use the partition ID instead of the partition name as shown in the
following example.
You can also use the HMC vtmenu command which provides a convenient menu of the
partitions on the managed system. Simply select the partition from the menu to open its
console window.
To close the session, exit out of the shell and type ~. (tilde dot) at the login prompt and
answer y (yes) to terminate the session.
Here is an example mkvterm command and session where managedsysname is the
actual managed system name and lparID is the actual partition ID number.
mkvterm m managedsysname --id lparID
AIX Version 6
Console login:
# exit
Console login: ~.
Terminate session? [y/n]
Use the rmvterm command to close a different virtual terminal session (that is perhaps
on the HMC or another remote workstation):
rmvterm -m managedsysname -p partitionname

Instructor Guide
Instructor notes:
Purpose Cover how to manually open and close a terminal window.
Details Describe the procedure to open and close the terminal windows.
Mention that you can access the virtual terminal for a partition from the HMC command
line. This was already covered in Unit 3 of this course.
Transition statement Now that you know how to activate a partition, lets talk about
how to stop it.

V5.3
Instructor Guide
Uempty
Stopping a partition
IBM Power Systems
Two ways to stop a partition cleanly:

Log in to the operating system and use the proper shut down command
Use the HMC: Either by using the Operation menu, then select Shut Down option or
chsysstate command
Figure 8-10. Stopping a partition AN111.0
Notes:
Stopping a partition
When you shut down the operating system in the partition, this stops the partition. The
partition state returns to the Not Activated state.
You can shut down a partition by logging in and executing the appropriate operating
system shut down command. You can also use the Shut Down option from the
Operations menu or use the chsysstate HMC command to shut down the operating
system; for example:
chsysstate -m managedsysname -o shutdown -r lpar -n lparname --immed
Automatic power off

Recall that in the managed system properties, there is a setting that will power off the
managed system if you stop the last partition on the system.

Instructor Guide
Instructor notes:
Purpose Describe the procedures for stopping a partition and resetting the operating
system in a partition.
Details Cover stopping a partition using the proper operating system shut down
command (for example, shutdown in AIX and Linux), the automatic power off feature, and
the operating system reset feature. The next visual is a continuation of the operating
system shutdown feature
Emphasize that there is no deactivate menu option. Some people assume that the opposite
command to activate would be deactivate and look for such a command.
Transition statement The next visual shows the partition shutdown options.

V5.3
Instructor Guide
Uempty
Partition shutdown options

IBM Power Systems
Use the operating system options if available:
Network connection
between LPAR and HMC
needed for OS options
Shutdown immediate HMC command

chsysstate -m MSname -o shutdown -r lpar -n lparname --immed
Figure 8-11. Partition shutdown options AN111.0
Notes:
Introduction
The visual shows the window that opens if you select a running partition and click
Partition Shut Down on the menu. Select the appropriate check box to select the
option you want to use, and then click the OK button.
The first two options use the Hypervisor to cause the operating system to stop.
Warning
Do not use these Hypervisor options unless the operating system is not running (if, for
example, the partition is in SMS) or if the operating system is not responding and you must
stop it.
Damage to the partitions data could occur if you use these options.

Instructor Guide
The second two options issue the shutdown or shutdown -F commands to the AIX
operating system. It is faster to open a Telnet window or console window, log in to the
partition, and shut down the partition manually. The RMC daemons must be functioning
on both the partition and the HMC, and the network between the partitions and the HMC
must be functioning for these options to be available.

V5.3
Instructor Guide

Purpose Describe the procedures for stopping the operating system in a partition.
Details Cover the shut down options that you can choose when shutting down a
partition.
Emphasize that the top two options should not be used except as a last resort. Data
corruption could occur.
The student notes mention that the two operating system options will not be available if the
network connection between the HMC and its partitions or the appropriate RMC daemons
are not running. We will discuss the RMC daemons in the Dynamic logical partitioning unit
of this course.
Transition statement Now, lets see the window when you select a partition and click
Restart option from the context menu or from the Tasks menu or from the Task pad.

Instructor Guide
Restart partition options

IBM Power Systems
Figure 8-12. Restart partition options AN111.0
Notes:
Introduction
This window opens when you select a running partition and click the Restart option.
Although the option is called Restart, all that happens is the operating system is
restarted. The partition itself is not stopped and then re-activated, so the partition will
not pick up any changes that were made to its profile.
Dump option
The dump option is equivalent of pressing the Reset button on a non-LPAR AIX system.
The partition will initiate a system dump to the primary dump device if configured to do
that. Otherwise, the partition will simply reboot. After the dump is completed, the
operating system will be notified to restart.

V5.3
Instructor Guide
Uempty Immediate option

This option is the equivalent of pressing the power button on a non-LPAR AIX system.
This halts the operating system in the partition immediately and programs are not
allowed to perform cleanup activities. Data in the partition may be left in a uncertain
state.
Operating system restart (AIX only)

The other two options on Restart Partition screen will issue the shutdown -r or
shutdown -Fr command to restart the AIX operating system in the partition. If these
options are not available, then there is a problem with the network between the HMC
and the partition or the appropriate RMC daemon is not functioning on either the HMC
or the partition.
Dump Retry:
Grey tint option only available for I/5 OS LPARs

Instructor Guide
Instructor notes:
Purpose Describe the restart options for partitions.
Details Describe the difference between a delayed and an immediate restart of the
operating system and what the system will do when you choose these options.
Transition statement The next task you might want to do when managing partitions is
to create a system profile.

V5.3
Instructor Guide
Uempty
Create a system profile (1 of 2)

IBM Power Systems
System profile is a list of partitions and profiles used to activate

partitions or validate resource allocations to avoid contention:
To create a system profile:
1. Select the managed system name in the server table view.
2. Choose Configuration > Manage System Profiles from the menu.
3. Then from the Actions menu, choose New.
Figure 8-13. Create a system profile (1 of 2) AN111.0
Notes:
System profiles
Recall that a system profile is a named set of partition profiles. When you activate a
system profile, all of the partition profiles that belong to it are activated. The intent of a
system profile is that it allows you to activate your entire system at once rather than
having to manually activate each partition. System profiles might be named after the
types of system loads (such as normal or high performance), or the name might refer to
a time period (such as weekday or end-of-month).
Create a system profile

To create a system profile, select the managed system name object, click the context
menu, and click Configuration -> Manage System Profiles on the menu. A window
opens that enables you to select the partition profiles that should belong to this system
profile. This window is shown in the next visual.

Instructor Guide
Instructor notes:
Purpose Show how to create a system profile.
Details Remind the students what a system profile is.
Describe the procedure to create a system profile. The second half of the procedure is
shown on the next visual.
Transition statement Lets continue the process of creating a system profile.

V5.3
Instructor Guide
Uempty
Create a system profile (2 of 2)

IBM Power Systems
Click Actions;
then select Select partition
New to create profile names
a new system on the left and
profile. click Add >>.
Figure 8-14. Create a system profile (2 of 2) AN111.0
Notes:
Enter a name for the system profile

Enter a new system profile name. This name must be unique for all system profiles on
the managed system, but it can have the same name as partition profiles.
Adding and removing partition profile names

Click the expand icons in the first panel to expand or collapse the output. Select
partition profiles on the left and use the Add>> button to add the profiles to the system
profile list. To remove partition profiles from the list, select the partition and profile
names on the right and use the <<Remove button.

Instructor Guide
Order of partition profiles is important

The order of the partition profiles is important as it is the order the partitions are
activated when the system profile is activated.
To reorder the list of partition profiles, remove the profiles that are out of order and add
them again in the correct order.
Modify a system profile

To modify a system profile, select the managed server object in the working pane. From
the context menu, click Configuration > Manage System Profiles. In the Manage
System Profiles window, select the system profile then click on Actions menu and
select Edit to modify it.
Delete a system profile

To delete a system profile, select the managed server object in the working pane. From
the context menu, click Configuration > Manage System Profiles. In the Manage
System Profiles window, select the system profile; then click the Actions menu and
click Delete to delete it.

V5.3
Instructor Guide

Purpose Describe how to create a system profile.
Details Describe how to add and remove partition profile names from a system profile.
Mention that we are looking at this window box because we created a new system profile. It
is the same screen youd see if you were to select an existing system profile.
You cannot easily reorder the list of partition profiles in a system profile. You must add them
in the correct order.
Transition statement Next, the System Profile Validate option is described.

Instructor Guide
Validate allocations with a system profile

IBM Power Systems
From the manage system profiles task, select the system profile
and use the Validate option on the Actions menu.
Figure 8-15. Validate allocations with a system profile AN111.0
Notes:
Validate system profile

After you create a system profile, select the managed server object in the working pane.
From the context menu, click Configuration > Manage System Profiles. In the
Manage System Profiles window, select the system profile then click the Actions menu
and click Validate to see if there are any resource conflicts between the partitions. The
validate function will list all conflicts in detail.

V5.3
Instructor Guide

Purpose Describe the System Profile Validate option.
Details
Transition statement Next, we will look at some other tasks you might need to perform
with partitions and their profiles. First lets look at default profiles.

Instructor Guide
Change the default partition profile

IBM Power Systems
The first profile created for a partition is the default.

The default profile cannot be deleted but you can change the
default profile.
Select partition, and choose Change Default Profile option in the menu.
Figure 8-16. Change the default partition profile AN111.0
Notes:
Default profile
When you activate a partition and do not specify a profile name, the system highlights
the default profile name by default. Every partition must have one default partition
profile. You cannot delete the default partition profile unless you first designate another
profile as the default profile for that partition. Having a default profile prevents you from
accidently deleting the last profile for a partition.
Change the default partition profile

The first partition profile you create for a partition will be its default partition profile. To
change the default partition profile, select the partition name, click the context menu
and click Change Default Profile. A window opens with the list of partition profile
names. Choose the partition profile you want as the new default profile for this partition.
This option will not display on the menu if the partition has only one profile.

V5.3
Instructor Guide

Purpose Describe default partition profiles.
Details Define what a default partition profile is and how it is used.
Mention that the first partition profile that is created for a partition is automatically the
default until you change it.
You cannot delete the default profile. If you want to delete it, you will have to designate a
different profile as the default for that partition.
The default profile is used only if you choose to activate a partition and you do not choose
a profile name to use.
A common misunderstanding is to think the default profile is used if the system were to
reboot because of a partition or managed system crash; this is not the case. If a partitions
operating system crashes and it has been configured to restart after a crash, it will restart
using the same partition resources that it had when it crashed. If the entire managed
system were to crash because, for example, a power outage, and the service processor
restart policy is set to true, then all the of partitions that were active at the time of the crash
will restart with their existing configurations. If any resources are deconfigured when the
system restarts, then one or more partitions might not be able to start if their minimum
resource requirements can no longer be met.
Transition statement Next, we will see how to copy a partition profile.

Instructor Guide
Copy a partition profile (1 of 2)

IBM Power Systems
Select a partition and click Configuration > Manage Profiles.
Figure 8-17. Copy a partition profile (1 of 2) AN111.0
Notes:
Introduction
The HMC allows you to copy a partition profile. For instance, you might decide that you
need a partition profile that is like one that you have already created, but with a small
change in resource allocation. Copy the profile and then edit the partition properties to
change the resource configuration.
You can only copy profiles within the same partition.
Copying partition profiles

To copy a partition profile, select the partition name object, click the context menu
button and click Configuration > Manage Profiles. In the Manage Profiles window,
select the profile you want to copy, click Actions and click Copy from the menu. A
window opened and you must enter a name for your new profile. This window is shown
on the next visual.

V5.3
Instructor Guide

Purpose Describe how to copy a partition profile.
Details Describe why you might want to copy a partition profile.
Describe the procedure to copy a partition profile.
Transition statement The next visual shows the window that opens to enter the new
name for the partition profile.

Instructor Guide
Copy a partition profile (2 of 2)

IBM Power Systems
Select the profile to copy from the Managed Profiles window;

then choose Actions > Copy.
Enter a new profile name.
Figure 8-18. Copy a partition profile (2 of 2) AN111.0
Notes:
Enter a name for the new partition profile

Enter a partition profile name for the copy. This name must be unique within the
partition. Click OK to finish creating the copy. The copy will appear in the list of profiles
for that partition.

V5.3
Instructor Guide

Purpose Show the window that opens when you copy a partition profile.
Details Describe the window that opens when you copy a partition profile. Mention that
the name must be unique for the partition.
Transition statement Lets take a look at the Save profile function.

Instructor Guide
Save configuration in a partition profile

IBM Power Systems
Save running partition configuration changes in a profile.
Figure 8-19. Save configuration in a partition profile AN111.0
Notes:
Save profiles
Over time, you might make dynamic changes to a running partition. When you make
dynamic changes, the partition profile does not automatically get updated. You would
need to manually alter the existing partition profile if you want the change to be part of
the profile in preparation for the next time the partition is activated. Another way to do
this is to save a new profile based on the current running configuration. Use the Save
menu option to do this. To use it, select a running partition, choose Save option from the
Configuration menu, then in the window, give the new partition profile a name that is
different for other profiles for that partition. A new partition profile will be created using
the running partitions current configuration.

V5.3
Instructor Guide

Purpose Describe how the new Save profile function works.
Details This Save feature is useful when dynamic changes have been made to a
running partition. You can save the new configuration in a profile.
Transition statement Now that you can create and copy partition profiles, you will
probably want to edit them. We will look at how to do this next.

Instructor Guide
Modify a partition profile

IBM Power Systems
Modify the profile properties.

This can be done while the partition using the profile is active.
Changes take effect the next time partition is activated with this profile.
Reboot of operating system does not re-read the profile.
Need to stop the partition and reactivate it
Figure 8-20. Modify a partition profile AN111.0
Notes:
Introduction
The system must be powered on either to the Standby or Operating state for partition
profiles to be modified.
Access partition profile properties to modify configuration

To modify the configuration of a partition profile, you must access the Manage Profile
window. Select the partition name object, click Configuration from the context menu
and click Manage Profiles. From the Manage Profiles window, select the profile; then
click the Actions menu and click Edit.
You can alter the partition profile properties while the partition is active. The partition will
not use the new configuration until you reactivate the partition using the new profile.

V5.3
Instructor Guide
Uempty Activating an active partition with the new profile

If the partition is currently active, you will need to completely shut down the operating
system and reactivate the partition with the new profile name to use the new profile. If
you just reboot the operating system, the partition will continue to use the old profile
configuration.

Instructor Guide
Instructor notes:
Purpose Explain how to modify the properties of a partition profile.
Details When you access the properties screen for a partition profile, they are the same
as those we saw earlier to configure processors, memory, I/O slots, and the boot options.
Describe the procedures for changing a partition from using one partition profile to another.
Do not simply reboot the operating system because this does not reactivate the partition.
You must shut down the operating system and then reactivate the partition.
Transition statement Next, we will cover how to delete a partition profile.

V5.3
Instructor Guide
Uempty
Delete a partition profile

IBM Power Systems
Deleting a partition profile deletes only the profile and not the
partition.
Cannot delete the default profile
Cannot delete the profile used to activate a running partition
Figure 8-21. Delete a partition profile AN111.0
Notes:
Introduction
You might need to delete a partition profile. This does not delete the partition to which it
belongs.
You cannot delete the default partition profile. To delete the default profile, you will need
to make another profile the default.
You cannot delete a partition profile that was last used to activate a partition if the
partition is still running.
If you delete a partition profile, it is removed from any system profiles in which it is
listed.
Delete a partition profile

Select the partition profile name, in the Manage Profiles window, click Actions and click
Delete from the menu.

Instructor Guide
Instructor notes:
Purpose Describe how to delete a partition profile.
Details Describe when you might want to delete a partition profile and the points made
in the Introduction in the student notes.
Describe the procedure to delete a partition profile.
Transition statement You may want to delete a partition, rather than a partition profile.
This is covered on the next page.

V5.3
Instructor Guide
Uempty
Delete a partition
IBM Power Systems
Delete a partition: Select partition, and click Operations > Delete

option in the menu.
Deletes all of its partition profiles
Partition cannot be active
Figure 8-22. Delete a partition AN111.0
Notes:
Things to remember when deleting partitions

Deleting a partition deletes all of its partition profiles.
You cannot delete an active partition.
To delete a partition, the managed system must be powered on.
The partition is also deleted from all system profiles automatically.
Delete a partition
Select the partition name object, click the context menu and click Operations > Delete
from the menu.
Notice that it would be easy to mistakenly delete the partition when you meant to delete
just a partition profile. When deleting, be sure to double-check which item you have
selected.

Instructor Guide
Instructor notes:
Purpose Describe how to delete a partition and what happens when you do.
Details Cover each point in the student notes under Things to remember...
Describe the procedure to delete a partition.
Ask the students what else they should do if they delete a partition. The answer is to
update their worksheets with the configuration changes.
Transition statement You might want to change the partition availability priority value.
This is covered on the next pages.

V5.3
Instructor Guide
Uempty
Partition availability priority (1 of 2)

IBM Power Systems
Only available on POWER6 processor-based systems

Select the server name; then from the menu, click
Configuration > Partition Availability Priority.
Figure 8-23. Partition availability priority (1 of 2) AN111.0
Notes:
Introduction
The managed system uses partition-availability priorities in the case of processor
failure. If a processor fails on a logical partition, and there are no unassigned
processors available on the managed system, the logical partition allows the logical
partition with the higher partition-availability priority to continue running after a
processor failure.
When a processor fails on a high-priority
The managed system follows these steps to acquire a replacement processor for the
high-priority logical partition.
1. If there are unassigned processors on the managed system, the
managed system replaces the failed processor with an unassigned
processor.

Instructor Guide
2. If there are unassigned processors on the managed system checks

the logical partitions with lower partition-availability priorities,
starting with the lowest partition-availability priority.
a. A lower-priority logical partition uses dedicated processors, the
managed system shuts down the logical partition and replaces
the failed processor with one of the processors from the
dedicated-processor partition.
b. If a lower-priority logical partition uses shared processors, and
removing a whole processor from the logical partition would not
cause the logical partition to go below its minimum value. The
managed system removes a whole processor from the
shared-processor partition using Dynamic logical partitioning
and replaces the failed processor with the processor that the
managed system removed from the shared-processor partition.
c. If a lower-priority logical partition uses shared processors, but
removing a whole processor from the logical partition would
cause the logical partition to go below its minimum value, the
managed system skips that logical partition and continues to
the logical partition with the next higher partition availability.
3. If the managed system still cant find a replacement processor, the
managed system shuts down as many of shared-processor
partition as it needs to acquire the replacement processor. The
managed system shuts down the shared-processor partitions in
partition-availability priority order, starting with the lowest
partition-availability priority.
Setting partition availability priority
To set partition-availability priorities for your managed system using version 7 or later of
the HMC, follow these steps:
1. In the navigation pane, open Systems Management and click
Servers.
2. In the contents pane, select the managed system whose
partition-availability priorities you want to set, click the Tasks
button, or the context menu button and click Configuration >
Partition Availability Priority.

V5.3
Instructor Guide

Purpose
Details
Transition statement Lets see how to change a partition availability priority value for a
selected logical partition.

Instructor Guide
Partition availability priority (2 of 2)

IBM Power Systems
Change the partition availability priority for the selected logical

partition.
Select from five predefined processor availability priority levels
Or use a custom processor availability priority value
Figure 8-24. Partition availability priority (2 of 2) AN111.0
Notes:
Partition list
This table lists the logical partitions that currently exist on the selected managed system
and the processor-availability priority for these logical partitions. To change the
processor-availability priority for a logical partition, select the logical partition in the
table, change the processor-availability priority setting in Availability priority, and click
Apply.
Default availability priority value
By default, the partition availability priority of Virtual I/O Server logical partitions is set to
191. The partition-availability priority of all other logical partitions is set to 127 by
default.
You can enter any value from 0 to 255 into Availability priority, or you can select one of
the preset choices. All selected logical partitions are set to the same partition-availability
priority value.

V5.3
Instructor Guide

Purpose
Details
Transition statement Now that you know how to set up your partitions the way you
want them, we will see how to back up partition profile data.

Instructor Guide
Backing up partition profile data (1 of 2)

IBM Power Systems
Backup partition profile data

Backs up partition and system profile configuration data
Creates the backup file on the HMC hard disk drive
Select the managed system name and click Configuration > Manage Partition data >
Backup from the menu
You are prompted for a backup file name
Figure 8-25. Backing up partition profile data (1 of 2) AN111.0
Notes:
Introduction
The Manage Partition Data > Backup command will create a backup file on the HMCs
hard disk drive of all the partitions profile information. The data is saved as a file on the
HMC in the /var/hsc/profiles/SN directory where SN is the serial number of the
managed system. The files are fairly small, for example, a backup file for a system with
four partitions is 32 KB.
The HMC automatically saves partition profile information in a backup file called
backupFile. You will see this file if you choose the Restore option. This backupFile is
updated each time you make a profile configuration change and is useful only for
holding the most up-to-date configuration so that when you do an HMC critical console
backup it will pick up this backup file. (This is done just in case you never manually back
up your profile data.) HMC critical console backups are covered later in this course. You
should plan to do additional backups of good configurations in case you were to
accidently delete a partition or other such emergency.

V5.3
Instructor Guide
Uempty Backup partition profile data

To backup the partition profile data, select the managed system name, click the context
menu and click Configuration > Manage Partition Data > Backup. A window will ask
you to name the backup file. This will create the backup file on the HMCs hard disk
drive.
HMC command for profile data backup

The HMC command bkprofdata can also be used to backup the profile data. An
advantage to using this command is that you can backup the profile data to media, such
as a floppy diskette. This command will backup the profile data to a file called
Mybackup on the floppy:
bkprofdata -m managedsysname -f /mnt/floppy/Mybackup
The diskette must be formatted first and your HMC must have a floppy drive. Use the
Format Removable Media application under the Licensed Internal Code application to
format the floppy.
Other Profile Data options

There are other menu choices on the Profile Data menu:
Restore: This option allows you to restore your backed-up partition profile data. Well
see more information on this in a few pages.
Initialize: This option removes all partitions and profiles! (Youll wish you had a backup
file if you ever accidently choose this menu option.)
Remove: This option allows you to remove backup files that you created with the
Backup option.

Instructor Guide
Instructor notes:
Purpose Describe how to back up partition profile configuration data to back up files on
the HMC.
Details Describe that the procedure using the HMC GUI to back up the partition profile
configuration information will save the backup file to HMC hard disk drive (not to media). In
a future unit we will see that it is possible to back up the HMCs critical console data, which
includes these partition profile backup files, to media. If you use the HMC bkprofdata
command, then you can save the backup file to media.
Transition statement The next visual shows the window that opens where you enter
the file name for the backup file.

V5.3
Instructor Guide
Uempty
Backing up partition profile data (2 of 2)

IBM Power Systems
Use descriptive filenames for the backup files.
Figure 8-26. Backing up partition profile data (2 of 2) AN111.0
Notes:
Enter the name for the backup file

This is the window that opens when you specify Manage Partition Data > Backup.
Enter a descriptive name for the file. A typical naming convention uses the current date
in the filename. Click OK to perform the backup.
Profile data backups can be scheduled

You can schedule the profile data backup operation so that the backups can happen at
a certain date and time and can be set up to repeat. Go to the HMC, select a server
name object in the Table, then click the context menu and click Operations > Schedule
Operations. The Customize Scheduled Operations window opens. Click Options >
New. The Add a Scheduled Operation window opens. Click Backup Profile Data
option and then click OK. The Set up a Scheduled Operation window opens allowing
the set time window for backing up Partition data.

Instructor Guide
Instructor notes:
Purpose Describe how to name the backup file.
Details Typically, the current date is used to differentiate the backup files.
Transition statement Now lets see how to restore the data.

V5.3
Instructor Guide
Uempty
Restoring partition profile data

IBM Power Systems
How do you want to data restored?
Pick the
backup file
you want
to use.
Full is only
available if all
partitions are
Not Activated.
Figure 8-27. Restoring partition profile data AN111.0
Notes:
Procedure: Restore partition data

To restore the partition profile data from a backup file on the HMCs hard disk drive, the
managed system must be in the Operating or Standby state. Select the managed
system name, click the context menu button and click Configuration > Manage Profile
Data > Restore. In the window, select which backup file you want to use.
Then choose the backup priority so that the backup file takes priority or the managed
system data takes priority.
Restore options
Full restore from selected backup file
This option restores all profile data using your backup file only. Profile modifications
performed after the selected backup file was created will be lost. This restore option
will not work if any partitions are running.

Instructor Guide
Backup priority and managed system priority

These two options both merge the backup data with the recent profile activity on the
HMC. In this way, if you accidently remove a partition, you can restore the partition
and its profile information from your latest backup file. The way these two options
perform the merge of the data is different.
The partition IDs for partitions are what are used with these two priority options,
rather than their names. If I delete a partition and it has a partition ID of 5, I could
then create a new (and perhaps very different) partition with that same ID number.
The restore operation uses these ID numbers when performing the restores. If you
had performed a backup before the original partition with ID 5 was removed and you
then perform a restore, there is a conflict. The two merge options on the restore
screen allow you to decide how this conflict should be resolved.
Backup priority means that such conflicts will be resolved by using the
configuration data from the backup. That is, in our example, the newly created
partition ID 5s data would disappear and be replaced by the original partition ID 5s
configuration data.
Managed system priority will resolve conflicts by preserving the current
configuration for that partition ID. In our example, if you take a backup, then delete a
partition, add a partition which reuses the ID number, then perform a managed
system priority restore, then you will see no change because although there is
conflict during the restore, the managed system takes priority.
In cases where there is no conflict (for example, a partition is deleted without
creating a new one with the same ID), then either type of restore method would
bring back that configuration.
HMC command for profile data restore

The HMC command rstprofdata can also be used to restore profile data. The following
command will perform a full restore of the profile data from a file called Mybackup on
the floppy:
rstprofdata -m managedsysname -f /mnt/floppy/Mybackup -l 1
The -l (lowercase L) arguments are 1 for full restore, 2 for backup priority, and 3 for
managed system priority.

V5.3
Instructor Guide

Purpose Describe the procedure to restore partition profile data.
Details Describe each step of the restore procedure.
Describe the difference between performing a full restore, a managed system priority
merge, and a backup priority.
Mention that for a full restore, there can be no running partitions.
Transition statement You might want to remove older backup files that you no longer
need.

Instructor Guide
Removing backup files

IBM Power Systems
Remove backup files that you no longer need.

Select the managed system name, choose Configuration > Manage Partition Data >
Delete.
Select file name and click OK.
Figure 8-28. Removing backup files AN111.0
Notes:
Removing backup files

Periodically you might want to prune the list of backup files. In fact, just like other
computer systems, you should create a backup policy. For example, this policy might be
to perform a weekly backup, keep backup files for 4 weeks, and after each backup is
successful, the oldest backup file is removed. Or, you might want to just back up the
profile data every time a change is made. The problem with this policy is that you might
be in a hurry and forget this crucial step.
These backup files are fairly small and the HMC hard disk drive is adequate to hold
many, many backup files. However, you still might want to remove backup files after
awhile.

V5.3
Instructor Guide

Purpose Describe how backup files can be removed.
Details This visual shows how to clean up old backup files that are not longer needed.
Transition statement The next slide talks about how to schedule an operation on a
logical partition.

Instructor Guide
Scheduling operations (1 of 4)
IBM Power Systems
Operations can be scheduled based on date and time.

Once or recurring
From Schedule Operations task, click Options -> New to create a new
scheduled operation.
Figure 8-29. Scheduling operations (1 of 4) AN111.0
Notes:
Scheduling operations
There are different types of operations that can be scheduled depending on the type of
object that is selected first. For example, if you select the server, then operations such
as server power on or off operations can be scheduled, a system profile can be
activated, or partition data can be backed up. For a partition, operations such as
activation, DLPAR operations, and shutdown can be scheduled. In addition, you can
schedule operations specific to the HMC if you access the Schedule Operations task
from the HMC Management application.

V5.3
Instructor Guide

Purpose Describe example of scheduled operations.
Details Scheduled operations are scheduled based on a time and date and can be
recurring. The list of operations depends on whether you are scheduling it for the server or
for partitions (or for the HMC itself as mentioned in the student notes).
Transition statement The next visual shows the operations available for a partition.

Instructor Guide
IBM Power Systems
Available operations for an LPAR:
Specify date and time:
Notes:
Add a Scheduled Operation

One you choose Options -> New from the menu, a window will pop up with a list of
available operations. Choose one and click OK.
Date and Time tab

After you choose an operation and click OK, the Set up a Scheduled Operation
window appears. An example is shown in the visual above. By default, you are initially
on the Date and Time tab.
From here, set up the date and time of the operation. If the operation cannot be
performed at that exact date and time, then the time window will be used to determine if
the operation should be performed or cancelled. For example, if the operation was
supposed to happen at 1:00 AM and the partition was in the middle of a restart, and the

V5.3
Instructor Guide
Uempty time window was set to 30 minutes, then the operation can start if the partition is ready
by 1:30 AM.
Notice the three tabs in the visual above. If the operation needs to repeat, click the
Repeat tab to configure a repeated scheduled operation. The Options tab is where you
specify any specifics for the operation.

Instructor Guide
Instructor notes:
Purpose Describe how to schedule operations.
Details Describe the options on the Date and Time tab.
Review the example mentioned in the student notes to illustrate how the Time Window
setting works.
Transition statement Next, well see the Repeat tab.

V5.3
Instructor Guide
Uempty
IBM Power Systems
Recurring operations:
Notes:
Repeat tab
The Repeat tab is used to configure repeating scheduled operations. For example, you
might want to move 2.0 processing units from one partition to another at midnight every
night and then move them back at 7 AM. Select the Set up a repeated scheduled
operation check box and then specify the days of the week and the other options.
Interval and Repetitions

The Interval field is a required field and the maximum is 26 weeks. This is the number
of weeks to elapse before performing the scheduled operation again on each selected
day. For example, if you want the operation to happen every other week, enter a 2 for
the number of weeks in the Interval field.
The Repetitions field is also a required field and the maximum is 100 or you have the
choice of selecting the Repeat indefinitely check box.

Instructor Guide
For example, to have a move operation occur every night at midnight, you would select
all of the days, then if you wanted the DLPAR operation to happen for 10 weeks, enter a
10 in the Repetitions field.
The visual shown above is an example of an operation that will occur on Saturdays,
every week, for 52 weeks (one year).

V5.3
Instructor Guide

Purpose Describe how to schedule DLPAR operations.
Details Use an example to illustrate how to set up a repeating scheduled operation.
Values must be entered for both the Interval and the Repetitions settings.
Transition statement Now that weve set the date and time and the repeating function,
well click the Options tab to configure specifics for the operation.

Instructor Guide
IBM Power Systems
Specifics for operation:
Notes:
Options tab
The Options tab will change depending on the operation being configured. In the
example in the visual above, the operation is a partition activation so the necessary
information to configure is the profile to use. For a DLPAR operation, you would specify
the resource and quantity to add, remove, or move.

V5.3
Instructor Guide

Purpose Describe the purpose of the Options tab.
Details The Options tab configuration options are dependent on the which operation is
being configured.
Transition statement The last section in this unit talks about how to troubleshoot
partition activation failures.

Instructor Guide
Troubleshooting activation failures (1 of 3)

IBM Power Systems
Partition activation failures are typically the result of not

enough resources to meet the minimum or required settings.
Check your documentation and the managed system
properties to figure out why.
Keep your worksheets up to date!
Dont let this be

you...
Example failure: Only first conflict is shown.
Figure 8-33. Troubleshooting activation failures (1 of 3) AN111.0
Notes:
Typical failures
If theres a partition activation failure, it is probably because you attempted to start more
resources than you have available. Assuming that you did not make a calculation error
when figuring how many processors or how much memory to configure, there must be
another reason for the error.
Managed system properties

You can select the name of the managed system and choose the Properties to see
what resources are allocated to which partitions.

V5.3
Instructor Guide

Purpose Describe the causes of typical partition activation failures.
Details The process to fix the failure is to start with reviewing what is currently in use on
the system and review your planning worksheets to see why there is a lack of resources.
In a few pages, we will go through the managed system properties screens.
Transition statement Lets look at some specific reasons why a partition will not
activate.

Instructor Guide

IBM Power Systems
Not enough processor or memory resources to meet

minimum requirement.
A partition will attempt to allocate up to its desired amount
Desired amounts for partitions too high?
Partition activation order may be a factor
Maximum memory might be set too high so that memory overhead is
too high
Do not forget to factor in overhead memory needs
I/O slot in required list is not available
Is it configured in a running partition?
Cannot find boot device
This is technically not an activation failure, but it still prevents the
operating system from loading
Boot list should be checked, especially if reusing a disk that was
previously loaded in another LPAR.
Notes:
Plan ahead
It is best to plan ahead to avoid these types of errors. Build in a buffer for the resources
using the minimum and desired settings. Then you will not have to reconfigure and
reactivate partitions multiple times to get them running.
Do not forget to plan for the memory that the Hypervisor uses.
If maximum memory is set too high, then partitions will allocate too much memory for
page tables and this memory will be wasted.
Insufficient resources activation failure

Check your documentation (that is, the planning worksheets) and the managed system
properties to figure out why you are attempting to allocate more processors or memory
than the managed system has. Perhaps the partitions that started or their profiles were
not the ones you expected or when the partitions started they came up in a different

V5.3
Instructor Guide
Uempty order, and all of the partitions with high desired numbers for processors grabbed too
many of them.
Do not forget to factor in memory overhead

The Hypervisor uses a small amount of system memory and partitions use additional
memory for hardware page tables. You can get the overhead amounts used by looking
at the managed system properties screens.
Cannot find boot device

Technically, by the time the partition discovers it cannot find its boot device, it has
already activated successfully. However this scenario is included here because it is
another common reason that a partition cannot fully start up. If you activate partitions
with an open terminal window you will be able to monitor the partition starting up. The
partition will stop and display error information in the terminal window. From the HMC it
looks like the partition has activated normally (which, technically it has).

Instructor Guide
Instructor notes:
Purpose This visual lists some specific reasons why a partition will not activate.
Details Stress that these types of errors can generally be avoided with clear and
up-to-date worksheets. It is too easy to become confused when you have many partitions,
each with multiple profiles. This is particularly an issue with dynamic partitioning and so you
should clearly log any dynamic partitioning operations. If you do not, your planning
worksheets might be up to date, but you might have forgotten about some dynamic move
operations! And if you are confused, you might end up having to reconfigure and reactivate
the partition multiple times to get it running.
Transition statement Next, we will see some things you can do if you are faced with a
partition activation failure.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Actions to take
Use managed system properties or HMC commands to check
system resources
Use the System Profile Validate menu option to discover
discrepancies
Use DLPAR to free up additional resources
Reduce minimum setting for partition you are trying to activate
Reconfigure partition profiles and update documentation (so this
does not happen next time)
I/O slot conflict
Notes:
Solving the activation failure issue

First, find out the cause of the current failure and then come up with a plan to fix it. The
fix might be to dynamically remove resources from a running partition, to shut down
partitions and reconfigure their resources, or to lower the minimum requirements on the
partition you want to start.
Next, you should figure out which part of your procedures were not followed that led you
to this problem. Perhaps configuration changes were made but the planning
worksheets were not updated or a dynamic reallocation was made without being
documented.
If your system has been running happily with this same configuration and now one
partition will not start because of insufficient memory, it is probably because you have
started the partitions in a different order. Perhaps previously, the last partition to start
never got its desired amount of memory but it was happy with what it received. If you
start this partition prior to other partitions, it will grab its desired amount and the net

Instructor Guide
effect is that it received more memory this time. Now the last partition to start might not
have enough to meet its minimum requirement.
Use the Validate option for the system profile

One technique you can use is to create a system profile with a list of all of the partitions
and their profiles that you wish to run simultaneously. Select the system profile name
and use the Validate menu option. This will report any discrepancies in resource
allocations.

V5.3
Instructor Guide

Purpose This visual describes techniques to use to solve the activation failure.
Details Check the documentation (that is, planning worksheets), the HMC event log,
and the managed system properties screens to figure out what resource is lacking. When
you figure out the issue, you can use other techniques to solve the problem, such as using
dynamic partition (DLPAR) commands to free up resources.
Transition statement Now, lets see how we can use the managed system properties to
figure out why there are not enough resources for a partition to activate.

Instructor Guide
Managed system properties (1 of 9)

IBM Power Systems
After partitions have been activated for the first time, you can
check the managed system properties to see what resources
have been allocated to which partitions
You can look at an individual partitions properties instead, but you will only see the
resources allocated to that partition.
Select the
server and
choose
Properties
on the menu
Figure 8-36. Managed system properties (1 of 9) AN111.0
Notes:
Introduction
Select the managed system name and click the context menu button; or click Tasks
and choose Properties to get to the managed system properties screens. These
screens show you what resources are allocated to what partitions.

V5.3
Instructor Guide

Purpose Describe how to access the managed system Properties screen.
Details Describe how to access the managed system Properties screen and a
high-level description of what is in there (lists of resources and to which partition they are
currently allocated).
Mention that you can also see current resource information for each partition individually if
you select the partition name and click Properties, or if you click directly on the partition
name object in the Working pane.
Transition statement Before diving into the lists of resources, lets view the General
tab in the managed system properties.

Instructor Guide

IBM Power Systems
Notes:
Introduction
If you select the managed system name and click Properties from the menu, it will take
you to a screen like the one in the visual. Notice the tabs; we will walk through each one
of these.
If the system is powered down, you will see limited information.
General tab
The General tab shows the overall system information about the managed system. You
may change the name of the managed system here.
You can also specify which partition will be the service partition here. Only one partition
on the managed system has the authority to update the system and other policy
parameters without having to power off the server or managed system. This partition is
known as the service partition. You are not allowed to delete the service partition. If you

V5.3
Instructor Guide
Uempty want to delete this partition, you will have to either designate another partition as the
service partition or set this option to Unassigned.
Automatic Power Off

If the Power off the system after all the logical partitions are powered off check
box is selected, then the managed system will power off when the last partition is shut
down. Depending on the version of the HMC software, the default for this check box
might or might not be selected.

Instructor Guide
Instructor notes:
Purpose Show the information available on the General tab.
Details You can change the name of the managed system here. This is not a TCP/IP
host name; it is simply the name that the HMC calls the managed system in its interface
and in any HMC commands that you execute.
Notice that this machine is a POWER6 processor based system and may be configured
with a maximum of 80 partitions.
Mention the Policy box, which specifies whether the system will power off when you shut
down the last partition. The behavior of automatically powering off could be annoying if you
are working on partitions and you happen to shut down the last one, then your system
powers down. You will end up waiting several minutes for it to power on again.
Transition statement Lets see what is on the Capabilities tab.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Notes:
Capabilities
The Capabilities tab lists the current capabilities for the managed system. Some
capabilities are dependent on the model of the system and some capabilities, such as
CoD, Micro-Partitioning, and Virtual I/O Server, are dependent on certain authorization
keys being activated. Some of the capabilities shown in the visual above are:
i5/OS Capable value of False means that this managed system cannot create
i5/OS (OS/400) partitions.
CoD Capable stands for Capacity on Demand.
Micro-Partitioning and Virtual I/O Server Capable mean that at least the
PowerVM standard edition (Advanced POWER Virtualization) feature has been
purchased and activated.
Active Partition Mobility Capable mean that the PowerVM Enterprise edition
feature has been purchased and activated.

Instructor Guide
Instructor notes:
Purpose Describe the Capabilities tab.
Details This tab is important for troubleshooting if you are trying to get a new feature to
work. For example, if you cannot create a partition with shared processors, see if the
Micro-Partitioning capability is True in this tab.
Transition statement Lets see what is on the Power-On Parameters tab.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Notes:
Power-on parameters
These power-on parameters allow you to control the initial program load (IPL) source
mode for restarting.
The Keylock position is provided for legacy System i hardware support. For security
reasons, the keylock position should always be set to manual.
The Manufacturing defaults section allows you to specify the boot method that will be
used if your system is using the manufacturing default configuration, which is the initial
partition setup of the managed system as received from your service provider. Typically
this will be a single partition that has a name the same as the serial number of the
managed system. It will be configured with one profile, called default, which is
configured to use all available system resources. This allows you to use the system with
one partition without an HMC.

Instructor Guide
The Advanced Options section allows you to select the boot speed (fast or slow) used
when the managed system is powered-on. A slow boot performs more extensive built-in
self-tests (BISTs) and Power On Self Tests (POST) than a fast boot. You can also select
which firmware image instance (Temporary or Permanent) you wish the system to use.
This tab is not useful when troubleshooting partition activation failures.

V5.3
Instructor Guide

Purpose Describe the options on the Power-On Parameters tab.
Details Briefly skip over this tab. It is included because the tab name is prominently
shown at the top. It is not a useful tab for troubleshooting configuration issues.
Transition statement Now, lets look at the additional tabs.

Instructor Guide

IBM Power Systems
Check processor allocation on the Processors tab in the

managed system's properties:
Physical
Currently
free
Partitions
allocated
processors
HMC command to view processor usage

lshwres -r proc -m MSname --level sys
lshwres -r proc -m MSname --level lpar
Notes:
Processor tab
The visual shows the information available from the Processors tab. The top part
shows the overall processor resources for the managed system. The number of
deconfigured processing units may be important if a processor is deconfigured by the
system because of errors.
The visual shows an example system with eleven partitions and height processors.
Partition Processor Usage

The box at the bottom of the screen shows partition usage. Partitions are listed along
with the processor usage information.

V5.3
Instructor Guide
Uempty HMC commands to see processor information

The following command lists all of the information for all configurable processors for all
partitions on a particular managed system: note this system is a POWER5
lshwres -m managedsysname -r proc --level lpar
Here is an example command and the output for one partition on a managed system
named sys046:
hscroot@sys046-hmc:~> lshwres -m sys046 -r proc --level lpar
lpar_name=sys046_v3,lpar_id=7,curr_shared_proc_pool_id=0,curr_shared_proc_poo
l_name=DefaultPool,curr_proc_mode=shared,curr_min_proc_units=0.1,curr_proc_un
its=0.35,curr_max_proc_units=2.0,curr_min_procs=1,curr_procs=2,curr_max_procs
=2,curr_sharing_mode=uncap,curr_uncap_weight=128,pend_shared_proc_pool_id=0,p
end_shared_proc_pool_name=DefaultPool,pend_proc_mode=shared,pend_min_proc_uni
ts=0.1,pend_proc_units=0.35,pend_max_proc_units=2.0,pend_min_procs=1,pend_pro
cs=2,pend_max_procs=2,pend_sharing_mode=uncap,pend_uncap_weight=128,run_proc_
units=0.35,run_procs=2,run_uncap_weight=128
lpar_name=sys046_v3_T5,lpar_id=8,curr_proc_mode=ded,curr_min_procs=1,curr_pro
cs=1,curr_max_procs=1,curr_sharing_mode=share_idle_procs_always,pend_proc_mod
e=ded,pend_min_procs=1,pend_procs=1,pend_max_procs=1,pend_sharing_mode=share_
idle_procs_always,run_procs=1
lpar_name=sys046_v3_T6,lpar_id=9,curr_shared_proc_pool_id=0,curr_shared_proc_
pool_name=DefaultPool,curr_proc_mode=shared,curr_min_proc_units=0.1,curr_proc
_units=0.35,curr_max_proc_units=2.0,curr_min_procs=1,curr_procs=2,curr_max_pr
ocs=2,curr_sharing_mode=uncap,curr_uncap_weight=128,pend_shared_proc_pool_id=
0,pend_shared_proc_pool_name=DefaultPool,pend_proc_mode=shared,pend_min_proc_
units=0.1,pend_proc_units=0.35,pend_max_proc_units=2.0,pend_min_procs=1,pend_
procs=2,pend_max_procs=2,pend_sharing_mode=uncap,pend_uncap_weight=128,run_pr
oc_units=0.35,run_procs=2,run_uncap_weight=128
The following command shows information for all dedicated or virtual processors in use
by partitions:
lshwres -m managedsys -r proc --level lpar -F lpar_name,run_procs --header
Here is an example command and the output for a managed system named sys046:
hscroot@sys046hmc:~> lshwres -m sys046 -r proc --level lpar -F \
lpar_name,curr_procs --header
lpar_name,curr_procs
sys046_v3,2
sys046_v3_T5,1
sys046_v3_T6,2
The following command shows the entitled capacity for shared processors in use by
partitions:
lshwres -m managedsys -r proc --level lpar -F lpar_name,curr_proc_units --header

Instructor Guide
Here is an example command and the output for a managed system named sys044
which has three partitions using shared processors:
hscroot@sys046hmc:~> lshwres -m sys044 -r proc --level lpar -F \
lpar_name,curr_proc_units --header
lpar_name,curr_proc_units
sys044_v3,0.35
sys044_v3_T5,0.35
sys044_v3_T6,0.35

V5.3
Instructor Guide

Purpose Show the information available from the Processors tab.
Details Describe the information in each column: You see what partitions have
processors allocated and the status of each processor.
Transition statement Lets see which I/O slots are allocated to each active partition.

Instructor Guide

IBM Power Systems
Check I/O slot allocation (ownership) on the I/O tab in the

managed system's properties:
HMC command to view I/O usage

lshwres -r io --rsubtype slot -m MSname
Notes:
I/O tab
This tab shows you all of the I/O slots on your system and which slots are allocated to
active partitions. The Owner column shows the name of the partition to which the slot is
currently allocated.

V5.3
Instructor Guide

Purpose Show the information available from the I/O Slot tab.
Details Describe the information shown on this visual: You see which I/O slots are
currently allocated to running partitions.
Troubleshooting question: The I/O screen should be straightforward. Are you attempting to
allocate an I/O slot that is already part of another running partition? Look for the slot and
see if there is an owner.
Transition statement Next, lets see how much memory each partition has.

Instructor Guide

IBM Power Systems
Check memory allocation on the Memory tab in the managed

system's properties:
Partitions
allocated
memory
HMC command to view memory usage

lshwres -r mem -m MSname --level sys
lshwres r mem m MSname --level lpar
Notes:
Memory tab
The Memory tab shows the status of the memory on the managed system.
Installed memory: This is the amount of total physical memory installed in the
system.
Deconfigured memory: This is the amount of physical memory deconfigured by
the system due to a detected hardware error.
Available memory: This is the amount of memory currently free for use by
partitions. This memory is not currently assigned to any partition.
Configurable memory: This is the amount of installed memory less the amount
of deconfigured memory.
Memory region size: This is the logical memory block (LMB) size.

V5.3
Instructor Guide
Uempty Current memory available for partition usage: This is the amount of
configurable memory for partition usage. This amount will vary depending on the
number of partitions that are defined for this system.
System firmware current memory: This is the amount of memory used by
TCE, POWER Hypervisor, and page tables. This value wasnt displayed with
HMC version 6.
Partition Memory Usage table: This table shows partitions and the amount of
memory configured for each. Unlike POWER4 systems, these partitions do not
necessarily have to be running to show up in this property sheet.
At the bottom, there is a list of partitions and the amount of memory allocated to
each of the partitions. The amounts are all in megabytes (MB). The partitions do
not have to currently be running for the memory and processor usage
information to show the amount allocated to the partitions. The partitions just
have to have run once before.
When troubleshooting memory allocation issues, ask yourself if these memory
amounts are what you expected. Did you plan for the overhead memory? Are
you attempting to allocate more than the available memory?
Memory in use by Hypervisor, TCE memory, and page tables

With the HMC Version 7 and later, the memory used by the system firmware is
displayed in the system properties. This is not the case with HMC version 6. With HMC
version 6 you can determine how much memory is reserved for the Hypervisors
housekeeping tasks and how much memory is available for partition use. To calculate
the overhead memory amount, you would have to subtract the current memory
available for partition usage from the configurable memory amount.
Using the HMC command line for memory information

Memory information can be seen using the following HMC command:
lshwres -r mem -m managedsysname --level sys
Here is an example command on a managed system called sys046.
hscroot@sys046hmc:~> lshwres -r mem -m sys046 --level sys
configurable_sys_mem=16384,curr_avail_sys_mem=6976,pend_avail_sys_mem=69
76,installed_sys_mem=16384,max_capacity_sys_mem=deprecated,deconfig_sys_
mem=0,sys_firmware_mem=1216,mem_region_size=64,configurable_num_sys_huge
_pages=0,curr_avail_num_sys_huge_pages=0,pend_avail_num_sys_huge_pages=0
,max_num_sys_huge_pages=0,requested_num_sys_huge_pages=0,huge_page_size=
16384,total_sys_bsr_arrays=16,bsr_array_size=8,curr_avail_sys_bsr_arrays
=16

Instructor Guide
Instructor notes:
Purpose Show the information available from the Memory tab.
Details Describe the information shown on this visual.
Describe how to calculate the amount of memory in use by the Hypervisor. This should be
a review as it was covered in Unit 6.
Transition statement The next tab gives information about the Live Partition Mobility
feature on POWER6.

V5.3
Instructor Guide
Uempty

IBM Power Systems
Notes:
Migration
Use the Managed System Properties - Migration page to view the partition mobility
properties for the managed system. The following properties are shown:
Type
Active partition mobility lets you move a running logical partition from one system to
another system; you do not need to shut down applications.
Inactive partition mobility lets you move a powered-off logical partition from one
system to another system.
Capable
True indicates that the managed system can participate in this type of partition
mobility.
Supported shows the number of movements supported on the managed system.

Instructor Guide
In progress shows the number of movements that are currently in progress on the
managed system.

V5.3
Instructor Guide

Purpose Describe the Mobility tab.
Details
Transition statement Lets look at the Advanced tab.

Instructor Guide

IBM Power Systems
Notes:
Advanced tab
This Advanced tab shows a summary of which partitions are configured for huge page
memory, and BSR arrays.
Configuring the number of huge pages

Huge pages must be configured through a system's Hardware Management Console,
and is supported on systems with POWER5+ and POWER6 processors but is not
supported on systems with POWER5 processors. If your managed system has
POWER5 processors, you will not see this Advanced tab.
The managed system must first be configured with a pool of huge pages before they
can be allocated to partitions. This configuration requires the managed system to be
powered off. Configure the number of requested pages on this Advanced tab first, then
assign the 16 GB huge pages to individual partitions by changing the partitions profile.

V5.3
Instructor Guide
Uempty Information displayed on Advanced tab

Available huge page memory (in pages): Displays the number of pages of huge page
memory that are available for partition usage on the managed system. These pages are
not currently assigned to any partition.
Configurable huge page memory (in pages): Displays the number of pages of huge
page memory that can be assigned to partitions on the managed system. This number
includes pages that are currently assigned to partitions on the system. This number
changes only when the value in the Huge Page Memory requested field is changed and
the system is restarted.
Page size (in GB): Displays the size (in gigabytes) of one page of huge page memory
on the managed system.
Maximum huge page memory (in pages): Displays the maximum number of pages of
huge page memory that you can have on this managed system. The system may not be
able to allocate the maximum amount of huge page memory if it is requested. This
number changes only when one of the following occurs:
- More memory is physically added to the managed system
- Memory is physically removed from the managed system
- The amount of deconfigured memory changes
Requested huge page memory (in pages): Configure how many total huge pages will
be used by all partitions. The managed system must be powered off for this operation.
Additional detail on huge page memory

Support for certain page sizes depends on the hardware being used. For example,
POWER5+ and POWER6 processors support four page sizes (4 KB, 64 KB, 16 MB and
16 GB). POWER5 and POWER4 processors do not support 64 KB or 16 GB; they only
have 4 KB and 16 MB. All other currently supported processors only support 4 KB
pages. 64 KB and 16 GB pages are only supported under the 64-bit kernel.
Applications must be altered to specifically request the use of 16 MB or 16 GB pages.
Detail on BSR arrays
The POWER6 processor-based system contains processors with Barrier
Synchronization Register (BSR) arrays and supports the use of the BSR arrays on the
processors. If an operating system supports the use of BSR arrays, a
parallel-processing application running on that operating system can use a BSR array
to perform barrier synchronization, which is a method for synchronizing the threads in
the parallel-processing application. If you use logical partitions, BSR arrays can be
assigned to logical partitions.
On logically partitioned systems, BSRs are divided into arrays. You can assign BSR
arrays to partition profiles. Each BSR array is 8 bytes long. The number of BSR arrays

Instructor Guide
that are available on a managed system depends on the number and type of
processors used on the server model. Available BSR arrays displays the number of
BSR arrays that have not yet been assigned to partition profiles on the managed
system.

V5.3
Instructor Guide

Purpose Describe the huge page memory information on the Advanced tab.
Details This tab has a field where the total number of huge pages for the entire
managed system is configured. For example, if Logical partition sys046_v1_T1 will be
configured for one huge page and Logical partition sys046_v1_T2 will be configured for two
huge pages, then configure the managed system for three huge pages. The managed
system must be powered off to configure the number of huge pages.
Additional information You can assign BSR arrays only to logical partitions that use
dedicated processors. Also not all operating system versions support use of BSR. Consult
your operating system documentation.
Transition statement Next are the checkpoint questions for this unit.

Instructor Guide
Checkpoint (1 of 2)
IBM Power Systems
1. How can you stop a partition?
2. What states must the managed system be in to create partitions?
3. True or False: The last partition profile you create for a partition is
automatically its default profile.
4. True or False: You can copy a partition profile within a partition but
not to a different partition.
5. When you modify a partition profile's configuration, what must you do

to apply the new configuration to an active partition?
6. True or False: If you delete a partition, you delete all of its partition
profiles.
Notes:

V5.3
Instructor Guide

Details Solutions:
IBM Power Systems

Log in to a partition and shut down. Or use HMC shut down
menu option or the chsysstate command.
Standby or Operating
The first one is the default.
5. When you modify a partition profile's configuration, what must you
do to apply the new configuration to an active partition?
Shut down the partition and reactivate it.
profiles.
Transition statement There is another page of Checkpoint questions to answer.

Instructor Guide
Checkpoint (2 of 2)
IBM Power Systems
7. List two things you can do if a partition will not activate.
8. Match the partition states to their definitions.

States: Not Activated, Shutting Down, Running, Not
Available
a. __________The partition is in the process of stopping.
b. __________The partition has been successfully activated.
c. __________The partition is not running but is available to
be activated.
d. __________The system is in a state that prevents the
partition from being activated (such as the
managed system is powered off).
9. True or False: When activating a partition, you must use the

Open Terminal Window option.
Notes:

V5.3
Instructor Guide

Details Solutions:
IBM Power Systems
7. List at least two things you can do if a partition will not activate.
Use DLPAR to free up resources. Reconfigure partitions. Use the
managed system properties to determine current resource
allocations.

States: Not Activated, Shutting Down, Running, Not Available
a. _Shutting Down The partition is in the process of stopping.

b. _Running_____ The partition has been successfully activated.
c. _Not Activated_ The partition is not running but is available to be
activated.
d. _Not Available_ The system is in a state that prevents the partition
from being activated (such as the managed system
is powered off).
9. True or False: When activating a partition, you must use the Open
Terminal Window option.

Instructor Guide
Exercise
IBM Power Systems
Unit
exerc
ise
Notes:

V5.3
Instructor Guide


Instructor Guide
Unit summary
IBM Power Systems

Schedule operations on partitions
Notes:
Activation options for partitions
- Manually, system profile, automated, HMC chsysstate command
Partition states
- Not Activated, Starting, Running, Error, Not Available
Partition profiles can be modified, copied, deleted, backed up, restored, and initialized
- Change default profiles
System profiles
- Are lists of partitions and a selected profile
- Can be used during power on or after the managed system is operating
Partition console windows
- Can be opened or closed, and accessed from HMC command line
Partition activation errors are usually caused by an attempt to use resources that are
already in use

V5.3
Instructor Guide

Details
1) What are some ways you can activate partitions?
Answer: Manually from the Server Management HMC application, by using a system
profile, from the HMC command line with the chsysstate command.
2) If a partitions boot mode is set to Normal and you want to boot to SMS, what can
you do?
Answer: Use the Advanced button when activating the partition and override the boot
mode.
3) What can you do if someone else on another HMC has a console window open to
a partition and you need access?
Answer: It might be nice to verify that this person is not actively working in the window, then
force it to close by selecting the partition and choosing Close Terminal Window on the
menu.
4) If you use the Profile Data > Backup utility to back up the profile data, where is the
backup stored?
Answer: On the HMC hard drive.
5) If you change a partition profile, then reboot the operating system, do the changes
in the profile take effect?
Answer: Not if you just reboot the operating system. You must shut down the operating
system and activate the partition.
Transition statement The next unit covers dynamic logical partition operations.

Instructor Guide

V5.3
Instructor Guide
Uempty Unit 9. Dynamic resource allocation
Estimated time
01:15

This unit describes the procedures for performing dynamic resource
allocations on partitions. Also covered is the subsystem used for HMC
and partitions communication for DLPAR operations. Potential issues
and error messages and their causes are described.

List the system requirements for Dynamic logical partitioning
(DLPAR)
Dynamically remove, add, and move processors, memory, and I/O
slots to and from partitions
Perform operating system operations necessary to dynamically
add and remove I/O slots
Use HMC commands to perform DLPAR operations and list
hardware resources
Schedule DLPAR operations
Describe the features of Partition Load Manager
Describe how RSCT is used for DLPAR operations
Use AIX and HMC commands to verify DLPAR is operational
Stop and start necessary RMC daemons
Reinitialize RMC configuration
Troubleshoot DLPAR operation errors

Accountability:
Lets Review and Checkpoint questions
Copyright IBM Corp. 2009 Unit 9. Dynamic resource allocation 9-1

Instructor Guide
References
SG24-7940 PowerVM virtualization on IBM system p: Introduction
and Configuration
SG24-6615 A Practical Guide for Resource Monitoring and Control
(RMC)

V5.3
Instructor Guide
Uempty
Unit objectives
IBM Power Systems

List the system requirements for dynamic logical partitioning
(DLPAR)
Dynamically remove, add, and move processors, memory, HEA
logical ports and I/O slots to and from partitions
Perform operating system operations necessary to dynamically
add and remove I/O slots
hardware resources
Notes:
Introduction
In this unit, we will look at both performing partition dynamic resource allocation and
troubleshooting potential problems.

Instructor Guide
Instructor notes:
Details Explain at a high level what will be covered and what the students should be
able to do by the end of the unit.
Transition statement This unit is separated into two topics. Lets look at what is
included in the first topic.

V5.3
Instructor Guide
Uempty 9.1. Dynamic LPAR operations

What students will do Students will learn how to perform dynamic resource allocations
on partitions.
How students will do it Students will participate in the lecture, answer Lets Review
questions, and perform a lab exercise at the end of this topic.
What students will learn Students will learn both how to use the HMC Web interface
and the command line commands to add, move, and remove processors, memory, logical
HEA ports and I/O slots. Also covered are the extra AIX commands that are necessary
when adding or removing I/O slots that contain adapters.
How this will help students on their job Dynamically reallocating resources is seen as
a vital operation on complex managed systems to maintain performance expectations and
to support changing workload needs.

Instructor Guide
Topic 1: Dynamic LPAR operations objectives

IBM Power Systems

List the system requirements for dynamic logical
partitioning (DLPAR)
Dynamically remove, add, and move processors, memory,
and I/O slots to and from partitions
Perform operating system operations necessary to
dynamically add and remove I/O slots
Use HMC commands to perform DLPAR operations and
list hardware resources
Figure 9-2. Topic 1: Dynamic LPAR operations objectives AN111.0
Notes:
Introduction
In this topic, we will see procedures for dynamically reallocating the resources in
running partitions.

V5.3
Instructor Guide

able to do by the end of the topic.
Transition statement First, lets talk about what is meant by Dynamic logical
partitioning.

Instructor Guide

IBM Power Systems
DLPAR is the ability to add, remove, and move resources

without reactivation of a partition
Processor, memory, and I/O allocation changes
Dynamic CUoD (processors and memory)
Supported operating systems

AIX V5.2 , AIX V5.3 and AIX V6.1 support all DLPAR options
Red Hat RHEL AS 3 does not support DLPAR
SUSE SLES 9, Redhat RHEL AS 4 support processor and I/O slot DLPAR
Redhat RHEL AS 5 and SUSE SLES 10 supports all DLPAR except
removal of memory
Applications might or might not be DLPAR-aware

Network connection between the HMC and the partition
must be available
DLPAR operations may be done manually from the HMC or
can be scheduled at a certain date and time
Figure 9-3. Dynamic logical partitioning (DLPAR) AN111.0
Notes:

Dynamic means that we can add, move, or remove resources without having to
reactivate the partition. So if there are partitions that need more or can do with fewer
resources, you can dynamically move the resources between partitions within the
managed system without shutting down the partitions. Both the source and the
destination partitions must support the dynamic partitioning operation.
Linux support
The full titles of the Linux software distributions are:
SUSE LINUX Enterprise Server 9 for POWER
SUSE LINUX Enterprise Server 10 for POWER
Red Hat Enterprise Linux AS 3 for POWER

V5.3
Instructor Guide
Uempty Red Hat Enterprise Linux AS 4 for POWER

Red Hat Enterprise Linux AS 5 for POWER
Check the Linux on System p Web site
(http://www-03.ibm.com/systems/power/software/linux/index.html) for the latest Linux
support and purchase information.
For Linux DLPAR operations, there are RPMs that must be obtained from IBM and
loaded. For more information on RPMs for specific versions of Linux see the Service
and Productivity tools for Linux on POWER Systems Web site
(https://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/home.html).
Applications
Some applications and utilities might not be DLPAR-aware. If they bind to a processor
or PIN memory, then you might need to stop these processes before you are able to
perform the DLPAR operation. IBM provides an Application Programming Interface
(API) for third-party program DLPAR support on AIX 5 and AIX 6.
HMC and partition daemons must be able to communicate for DLPAR

operations
The daemons that support DLPAR operations must be running both on the HMC and on
the partitions. The partition daemons start automatically when the operating system
starts. These daemons must communicate with the daemons on the HMC before
DLPAR operations can be performed. There is a slight waiting period after a partition or
HMC reboot; so if you get a DLPAR operation failure after a reboot, wait a bit and try
again.
POWER4 versus POWER5-based systems

The visual shows the operating systems and the DLPAR operations allowed for IBM
POWER5 processor-based systems. HMCs must be at least at Version 4.2.0 to support
IBM POWER5 processor-based systems.
For POWER4-based pSeries servers, the partition must be running AIX 5.2 (or later),
the managed system firmware must be a version dated October 2002 or later, and the
HMC software must be Release 3 Version 1.1 or later. All partitions running AIX V5.1
on POWER4-based pSeries servers are static partitions, which means a partition must
be reactivated to change its resource configuration. The versions of Linux (SLES9 and
RHEL4) support DLPAR when running on POWER4 systems. Older versions of Linux
do not support DLPAR operations.

Instructor Guide
POWER6-based systems
Depending on the POWER6 model, the following minimum Linux releases are
supported.
Red Hat Enterprise Linux V4.5 for POWER
Novell SUSE Linux Enterprise Server 10 for POWER SP1 update 1
Novell SUSE Linux Enterprise Server 10 Service Pack 2 for POWER

V5.3
Instructor Guide

Purpose Define what is meant by DLPAR and review the operating systems that
support DLPAR.
Details Describe what is meant by DLPAR.
Describe the differences in what is supported in the various operating systems. Mention
that you should check www.ibm.com when new versions of the operating systems are
released to see which DLPAR operations are supported (particularly with Linux versions).
Point out that the minimum Linux version (either SLES or RedHat) that can run on
POWER6-based systems depends on the model. For example POWER6 p520 requires
SUSE Linux Enterprise Server 10 SP1 as minimum level while the high end server p595
requires SUSE Linux enterprise Server 10 SP2 as minimum level.
The visual and notes mention that there must be communication between the HMC
daemons and daemons on the partition for DLPAR operations to work. We will talk about
this in more detail later in this unit.
Transition statement Lets see which DLPAR operations are supported.

Instructor Guide
DLPAR operations overview

IBM Power Systems
Processors and memory

Quantities are bound by the maximum and minimum partition profile
settings
Can change virtual processor and uncapped/capped settings
CUoD processors and memory can be added dynamically
I/O slots
Required slots cannot be dynamically removed
Can change the required setting dynamically by modifying the active profile
Slots must first be removed in AIX before being dynamically removed
Can add or remove a virtual I/O slot
Dynamic operations do not change the profiles

Update the partition profile to make changes permanent
Auto start power on option uses a partitions last configuration, not a partition
profile configuration
Figure 9-4. DLPAR operations overview AN111.0
Notes:
Introduction
The operations listed in the visual are for AIX V5.2, AIX V5.3 and AIX V6.1. See the
previous visual for additional information about Linux.
Processors and memory

Recall that there is a maximum and a minimum configuration option for processors and
memory. You cannot exceed these boundaries when performing dynamic reallocation
operations. For example, you can continue to remove processors from an active
partition until the total number of processors in use is equal to the minimum amount.
The limits in use are those in the active partition profile.

V5.3
Instructor Guide
Uempty Dynamic LPAR with Capacity Upgrade on Demand

CUoD processors that have not been activated are available for dynamic processor
sparing. If the server detects the impending failure of an active processor, it will attempt
to activate one of the unused CUoD processors and add it to the system configuration.
This helps to keep the server's processing power at full strength until a repair action can
be scheduled.
I/O slots
For I/O slots, you cannot remove any slot that is required in the active partition profile.
You also cannot remove any slot that contains an adapter that connects to a device that
is in use.
If an I/O slot is on the required list, it cannot be dynamically removed from the partition.
The slot can be moved from the required list to the desired list in the active partition
profile and then it can be dynamically removed.

Instructor Guide
Instructor notes:
Purpose Describe the DLPAR operations that are available.
Details Mention that so far, the course has pointed out that the partition profile is only
read upon activation of the partition, but with DLPAR operations, the minimum and
maximum settings for processing units and memory, and the desired and required settings
for I/O slots, are viewed at the time of the dynamic operation.
Dynamic operations do not alter the partition profile settings. Explain that this means that if,
for example, you dynamically add 128 MB of memory to a partition and later you reactivate
that partition with its profile, then that partition starts with whatever is in the profile, which
does not include that extra 128 MB of memory. So if you want to make a dynamic change
permanent, you should also update the profile so the next time the partition is activated, it
will use the new resource configuration.
Mention that a common mistake people make when learning about DLPAR is that they alter
the running partitions profile and wait for the change to occur. When it does not happen,
they wonder what is wrong with their system. The reason is that DLPAR operations do not
happen in the partitions profiles; there is a special menu you use to make the changes
occur. This is what we will see on the next visual.
Transition statement Now, we will see how to perform DLPAR operations.

V5.3
Instructor Guide
Uempty
DLPAR operations
IBM Power Systems
Select the partition, then either from the tasks pad or the
context menu, choose Dynamic Logical Partitioning and
then which type of resource and operation
Figure 9-5. DLPAR operations AN111.0
Notes:
Dynamic logical partitioning menu option

The visual on this page shows how to begin a dynamic reallocation operation. Select
the partition name, then from the Tasks pad or the context menu, choose Dynamic
logical partitioning, the type of resource from the menu, and the operation to perform.
For a move operation, you need to select the destination partition.

Instructor Guide
Instructor notes:
Purpose Show how to access the Dynamic logical partitioning menu options.
Details Review the procedure of selecting the running partition name and choosing the
Dynamic logical partitioning menu options.
Transition statement First, we will cover adding processors.

V5.3
Instructor Guide
Uempty
Add/Remove dedicated processor operation

IBM Power Systems
What is
available
Is it a valid
operation?
Enter
amount
How long are
you willing
to wait?
Figure 9-6. Add/Remove dedicated processor operation AN111.0
Notes:
Adding processors
A resource must be free before you can add it. Free means that no other running
partition is using it. Select the partition and access the Dynamic logical partitioning
menu. Click Processor, then Add or Remove to add free processing units to a running
partition.
In the visual, the Available system processors: 2 line tells us that the managed
system has two free processors so this is the most you can add to any partition.
You can add up to the maximum processors for the partition specified in the active
partition profile. Note that the screen in the visual tells you what this number is. Look at
the Maximum column. The Current column tells you what is currently allocated to the
partition.

Instructor Guide
Moving processors
When you move processors, you initially select the source partition and then start the
dynamic reallocation operation. You indicate the destination partition for a move
operation in the window.
Dedicated versus shared processors

The example screen in the visual shows a dynamic operation for a partition with
dedicated processors. Next, you will see how this screen will change when the partition
is using shared processors.

V5.3
Instructor Guide

Purpose Review the procedure to add or remove dedicated processors.
Details Point out that this visual shows the General tab.
Emphasize that this visual shows the screen for a partition using dedicated processors.
The next visual will show the DLPAR screen for shared processor partitions.
Review the fields on the visual, and point out the Maximum column and its importance
when adding processors.
Mention that removing resources is similar. You would enter the desired Assigned value
and would pay attention to the Minimum column rather than the Maximum column.
Point out that a move operation is really a remove operation on one partition, and an add
operation on the destination partition. On the first partition, you can remove processors
down to the minimum setting in the active partition profile. On the destination partition, you
can add processors up to the maximum.
We will see some more examples in the following visuals plus students will have a chance
to explore the DLPAR screens in the lab exercise.
Transition statement Lets see how this screen looks if the partition is using shared
processors.

Instructor Guide
Add/Remove shared processing units operation

IBM Power Systems
Is it a valid
operation?
What is
available
Enter
Capped/
quantities
uncapped
and weight
Messages
detail
Figure 9-7. Add/Remove shared processing units operation AN111.0
Notes:
DLPAR with shared processors

The example screen in the visual shows a Dynamic logical partitioning > Processor
> Add or Remove processor resources operation for a partition with shared
processors. With a shared processor partition, you can dynamically add and remove
processing units, add and remove virtual processors, change the capped/uncapped
setting, and change the capped weight setting. In the next unit, you will learn all about
these shared processor settings.
Detail level
In the Detail level field, select the level of feedback you would like to see while the
HMC performs the task. Details shown include the operating systems standard output
and standard error information.

V5.3
Instructor Guide
Uempty Timeout setting

You can specify a timeout setting in minutes. This is the amount of time that the HMC
has to complete this operation. If it does not complete the operation within this amount
of time, the operation will fail. This is not typically an issue when performing an add
operation. However, when you remove a processor, the current task must finish and the
jobs in the run queue for that processor must be migrated to another processor. You
might want to set a timeout setting in minutes for the memory move or remove
operations. It might take some time to free memory that is currently in use.
The timeout setting by default is 0, which means that the HMC will wait as long as it
takes for the operation to finish.

Instructor Guide
Instructor notes:
Purpose Describe the differences in the DLPAR window when adding dedicated
processors versus shared processing units.
Details After describing the new fields specific to shared processors and describing the
example in the visual, ask the students this question: Would the adding of 0.7 processing
units succeed or fail?
Answer: This would fail. Even if the managed system has 1.25 processing units free,
this partition already has 0.35 and the maximum is 1.0. So, the maximum processing
units you can add to this partition is 0.65.
Transition statement Next, lets see the DLPAR working window.

V5.3
Instructor Guide
Uempty
DLPAR status (1 of 3)
IBM Power Systems
Check the status in the Working window

Window will close when operation is successful or will show a failure
Figure 9-8. DLPAR status (1 of 3) AN111.0
Notes:
Working window
This visual shows the status of a dynamic reallocation operation. The Working window
opens automatically.
The window closes quickly once the operation finishes. If the window did not stay open
with a Failed message, then you know it was a success.
The example above shows a dynamic operation for processors, but this type of window
is used to show the status of all dynamic reallocation operations.

Instructor Guide
Instructor notes:
Purpose Show how to find out if the dynamic reallocation operation is finished and its
status.
Details The Working window shows the status of the dynamic reallocation operation.
This status window is not specific to processors or even to dynamic operations. But with
dynamic operations it is nice to watch the progress and know when the operation is
finished.
Transition statement The next visual shows an example of a failed operation.

V5.3
Instructor Guide
Uempty
IBM Power Systems
Here is an example
of a failure:
Notes:
Introduction
This visual shows an example of what happens when the dynamic operation fails. The
working window will report the status as Failed (although it might close so quickly that
you cannot read it) and a second window opens with information about the specific
failure. Fix the problem, and try the operation again.
Example error
The example error in the visual above shows what will happen if you allocate a quantity
of processing resources that is out of range with the number of virtual processors. We
will get to this rule later in this course.

Instructor Guide
Instructor notes:
Purpose Show what happens when a dynamic operation fails.
Details Tell the students that the secondary window will describe the specific failure.
Do not go into a lot of detail about the error message on the visual. It is just an example.
You can briefly mention the scenario that could cause this error if the students seem
interested although they probably do not have enough background yet to understand the
situation: The virtual processor setting was set too high for the amount of processing units
in the partition. The rule is that you cannot have more than 10 virtual processors to 1.0
processing units. This error might occur if you had 10 virtual processors, and dynamically
reduced the processing units from 1.0 to 0.9.
Transition statement Some errors happen as soon as you try to run the DLPAR menu
option. Lets look at an example.

V5.3
Instructor Guide
Uempty
IBM Power Systems
Here is another example of a failure:
Some errors
happen before
you even get
to the DLPAR
menu
Notes:
DLPAR error example

The visual shows another error that you may see. In this case, the user was unable to
access the DLPAR screens because the HMC reports that the particular partition
resource is already at its maximum, so you cannot do that operation. For example, if the
partition is running with two processors and the maximum processor number was set to
2, then the HMC will not allow you to attempt to dynamically add another processor
because the partition is already running with its maximum.

Instructor Guide
Instructor notes:
Purpose Show another example of a DLPAR error.
Details The visual shows an example of an error that might occur when you access the
DLPAR menu option. The HMC is reporting that the partition is already running at the
maximum and so the add operation the user is attempting is not valid. A similar message
will occur if the partition is already running at the minimum setting of the resource and you
are attempting a remove or move operation.
Additional information In case a student asks, the example described in the student
notes could be slightly more complex, if it involves virtual processors. The complexity is
that the virtual processor setting would also have to be at its maximum. The HMC will let
you into the processor Add DLPAR screen when the processing resources are set to the
maximum if the virtual processor setting is not at its maximum yet. This allows you to tune
the virtual processor setting.
Transition statement Now, lets look at dynamic memory operations.

V5.3
Instructor Guide
Uempty
Move Memory operation

IBM Power Systems
Is it a valid
operation?
Enter quantity
Move to which
partition?
Is it a valid
operation?
Figure 9-11. Move Memory operation AN111.0
Notes:
Moving memory
In the example in the visual, Memory and Move were the options picked on the
Dynamic logical partitioning menu. In this window:
1. Check to make sure that the operation you want to perform is valid
given the configuration settings.
2. Type the amount or use the arrows to set the amount.
3. Choose the destination logical partition.
In the example shown in the visual above, 128 MB of memory is being moved from the
sys046_v3_T6 partition (shown in the window title) to the sys046_v1 partition. The
smallest unit that can be moved is the LMB size for the system.

Instructor Guide
Moving processors works the same way

If this were the screen to move processors, similar information would be shown. You
would see the maximum and minimum settings for processing units (or dedicated
processors) and virtual processors, and you would need to specify the destination
partition.

V5.3
Instructor Guide

Purpose Show how to add, move, and remove memory.
Details Explain the fields in the memory window.
On the last visual, we saw an example of an add operation. On this visual, we see a move
operation. The screens for memory and processor add, move, and remove operations look
similar.
Ask the students if we know if the operation shown in the example is a valid operation.
Transition statement Now, lets look at dynamically adding I/O slots.

Instructor Guide
Add I/O slots operation

IBM Power Systems
Select the adapter or adapters to add
Figure 9-12. Add I/O slots operation AN111.0
Notes:
Dynamically adding I/O slots

The visual shows an example of adding a free I/O slot to a running partition. You get to
this window by selecting the partition name, then choosing from the menu: Dynamic
logical partitioning, Physical Adapters, and Add. A free I/O slot is one that does not
belong to another running partition.
Simply pick the I/O slots you want using the descriptive information provided on the
screen and then click the OK button. You can select more than one slot at a time.

V5.3
Instructor Guide

Purpose Describe how to dynamically add I/O slots to a partition.
Details You can dynamically add any free slots to a partition that supports dynamic
partitioning. The slots might be empty or have an adapter in them.
Transition statement The next page shows the necessary AIX commands when
performing dynamic operations on I/O which contain adapters.

Instructor Guide
AIX commands for I/O operations

IBM Power Systems
After adding slots with adapters from the HMC

Must run cfgmgr in AIX destination partition for it to discover the newly added devices
Use lsdev -C in AIX to list devices
When removing I/O slots

Use rmdev to remove the devices from the source partition
Cannot remove:
Slots that are listed as required in the active partition profile
Slots with devices that have not been removed in AIX
Can remove required designation for a slot in the active profile
When moving I/O slots, it is really a remove operation followed

by an add operation
Do not forget to run rmdev in source partition and cfgmgr in destination partition
In Linux, devices are automatically configured when added, and

automatically deconfigured when removed
Figure 9-13. AIX commands for I/O operations AN111.0
Notes:
Introduction
This page summarizes the add, move, and remove operations for I/O slots.
cfgmgr command
After you have dynamically added the slots to the running partition, you need to tell AIX
to discover any new devices. The cfgmgr command (no options are necessary) will
discover the new devices.
Recall that a move operation is really a remove followed by an add; so do not forget
to run the cfgmgr command in the destination partition when you move I/O slots.
You can also run the cfgmgr command using SMIT. Use this fastpath:
# smitty cfgmgr

V5.3
Instructor Guide
Uempty Sequence of dynamically adding, moving, or removing I/O slots

Adding I/O slots:
1. Add the I/O slots to the partition from the HMC.
2. Run cfgmgr in the destination partition.
Removing I/O slots:
1. First log in to the partition and remove the devices from the
partition using the rmdev AIX command. You must remove all of
the devices associated with that I/O slot in the order of the children
up to the parent. (There is more on this coming up.)
2. Dynamically remove the I/O slots from the partition using the HMC.
3. If you are moving slots, do everything for a remove, then perform
the DLPAR move operation, and then run the cfgmgr command in
the destination AIX 5L partition.
You do not need to run commands similar to cfgmgr or rmdev in Linux because
devices are automatically configured and deconfigured by Linux kernel modules.

Instructor Guide
Instructor notes:
Purpose Discuss the process of adding, moving, or removing I/O slots.
Details For add I/O slot operations, first you issue the add operation in the HMC to the
partition, then you run cfgmgr in the destination partition.
For remove or move operations, first you must rmdev -l all of the devices (in order of
children up to parent) in AIX first, then perform the move operation in the HMC, then run
cfgmgr in the destination partition.
Transition statement Lets see an example of moving an I/O slot that contains a Fiber
channel adapter with hdisks devices connected to.

V5.3
Instructor Guide
Uempty
Removing I/O slots in AIX (1 of 2)

IBM Power Systems
Removing (or moving) slots

Must rmdev -dl all the devices in AIX that are controlled by that PCI slot device
Example: Remove a Fiber Channel Adapter
What other devices are connected through the slot?
May have other devices such as hdisks devices
Must rmdev peer devices (hdisks), the bus, and the PCI slot device
PCI slot device
Bus Remove devices

recursively or
manually from the
bottom up
Tape
drive
Figure 9-14. Removing I/O slots in AIX (1 of 2) AN111.0
Notes:
Introduction
If you want to move an I/O slot from one partition to another, it is probably because
there is an adapter in that slot that you want to be part of another partition. That adapter
may have devices (such as tape drives, disks, and so forth) and it might even have
multiple buses, such as the Ultra320 Dual Port SCSI adapter. The devices such as the
hdisks, the buses, and the PCI slot itself must all be removed in AIX before you can
move them to another partition using the HMC GUI or command line. The HMC
software will not move I/O slots that have devices that are in use.
You remove these devices from AIX by using the rmdev -l XXX where XXX represents
the device name. For example, rmdev -l hdisk4 will remove the hdisk4 device. The
trick is figuring out the list of devices to remove. This process is shown on the next
visual.

Instructor Guide
Instructor notes:
Purpose Describe the whys and hows of removing devices from AIX before dynamically
moving or removing I/O slots from a partition using the HMC.
Details This example shows a scenario where we want to move a Fiber channel adapter
to another partition. We know that there might be multiple hdisks devices that can be
connected to the same adapter. We are moving the I/O slot, not the device, so anything
connected to that slot will move as well.
Emphasize that when you remove the devices in AIX you must start from the bottom up or
use the recursive option to rmdev.
Transition statement So, how do you figure out exactly which devices you need to
remove? Lets look at an example.

V5.3
Instructor Guide
Uempty
Removing I/O slots in AIX (2 of 2)

IBM Power Systems
First, find out which devices need to be removed

In the LPAR, find out the devices parent, the PCI device, and the slot in use
# lsdev -Cl hdisk3 F parent
fscsi0
# lsdev Cl fscsi0 F parent
fcs0
# lsdev C | grep fcs0
fcs0 Available 02-00 4Gb FC PCI Express Adapter (df1000fe)
# lsdev C | grep 02-00
fcnet0 Defined 02-00-01 Fibre Channel Network Protocol device
fcs0 Available 02-00 4Gb FC PCI Express Adapter (df1000fe)
fscsi0 Available 02-00-02 FC SCSI I/O Controller Protocol Device
hdisk3 Available 02-00-02 MPIO Other FC SCSI Disk Drive
# lsslot -c slot l fcs0
U7311.D20.650443C-P1-C07 Logical I/O Slot pci2 fcs0 fcs1
Or, attempt the DLPAR operation and read the error
Then, remove the PCI device and all of the devices belonging it
# rmdev -l pci2 -R
fcnet0 Defined
hdisk3 Defined
fscsi0 Defined
fcs0 Defined
pci2 Defined
Figure 9-15. Removing I/O slots in AIX (2 of 2) AN111.0
Notes:
Discovering affected devices

Start the process with what you know. In this case, we know we want to move the
hdisk3 (an external LUN on an external storage subsystem) from the logical partition to
a destination logical partition. With DLPAR, you need to move the entire I/O slot and not
just a device.
First, we find out the hdisk3 devices parent with lsdev or odmget. The lsdev
command is shown in the visual above. An equivalent odmget command is:
# odmget -q name=hdisk3 CuDv | grep parent
parent=fscsi0
The parent is fscsi0 and this is not a PCI slot devices, so we need to figure out
the parent of fscsi0 with the lsdev command, which turns out to be fcs0 (the
Fiber Channel adapter port0).

Instructor Guide
# lsdev -Cl fscsi0 -F parent

parent=fcs0
The parent is fcs0 and this is not a PCI slot device, so we need to figure out the
parent of fcs0 with the lsslot command, which turns out to be pci2. The
command lsdev -Cl fcs0 -F parent can be used too, but the advantage of lsslot
is that it also displays the physical location code. This tells you that ultimately it is
slot C07 that you will dynamically move in the HMC application.
Now that we have a path all the way back to the PCI slot, at this point, we could
simply use the rmdev -1 pci2 -R command to remove the pci2 device and all of
its child devices. However, you might first want to discover what these are before
removing them.
To find out what other devices are involved, do an odmget query to find out what
has pci2 as a parent. We know fcs0 has it as a parent, but there might be
additional buses or devices.
For example:
Find out everything that belongs to pci2. In this example, pci2 is the parent of
fcs0.
# odmget -q parent=pci2 CuDv | grep name
name=fcs0
Now we need to know about any children of the fcs0 device and we find fcnet0
and fscsi0.
Find out everything that belongs to fcs0:
# odmget -q parent=fcs0 CuDv | grep name
name=fcnet0
name=fscsi0
Now we need to know about any children of the fcnet0 and fscsi0.
Find out everything that belongs to fcnet0 and fscsi0
# odmget -q parent=fscsi0 CuDv | grep name
name=hdisk3
So now we have our list of the devices that will need to be unconfigured in AIX:
hdisk3, fcnet0, fscsi0, fcs0, and pci2. We remove these from AIX and now we can
go back to the HMC and dynamically move the I/O slot C07 to another partition.
Another way to see which devices are owned by pci2 is to attempt to dynamically
remove the slot from the HMC before removing the devices in AIX. The error message
will list all the devices that need to be unconfigured. An example of this error message
is shown on the visual.
Note about removing devices: Some adapters, such as the USB adapter and graphic
adapters, are not meant to be unconfigured. They cannot be moved between partitions

V5.3
Instructor Guide
Uempty or hot-plugged. If you are moving disks as well as SCSI adapters, you will need to
unmount the filesystems and export the volume groups before unconfiguring the
devices. The integrated SCSI adapters can be moved between partitions as long as
they are not being used for rootvg.
Removing devices individually

If you want to remove the devices individually, rather than with the -R (recursive) option,
be sure to execute the commands so that you remove the devices from the bottom up.
For example:
# rmdev -l hdisk3
# rmdev -l fscsi0
# rmdev -l fcnet0
# rmdev -l fcs0
# rmdev -l pci2

Instructor Guide
Instructor notes:
Purpose Describe how to discover all of the devices that need to be removed in AIX
before you can dynamically remove or move them to another partition.
Details Describe the thought processes in discovering all of the devices involved. Start
with what you know; if you want to move an adapter, figure out its PCI slot device and any
children that may be connected to it.
Additional information The rmdev -l command sets the devices as defined in the
ODM. If you use the rmdev -l device -d command, it removes the devices completely from
the ODM.
The example in the visual is from a POWER6 p550 system.
Transition statement Now that the devices have successfully been removed from AIX,
we can now go into the HMC and perform the remove or move operation.

V5.3
Instructor Guide
Uempty
Move/Remove I/O slots operation

IBM Power Systems
Choose slot
Choose partition
Specify None
to remove the
I/O slot
Figure 9-16. Move/Remove I/O slots operation AN111.0
Notes:
Removing and moving I/O slots

The visual shows the HMC Dynamic logical partitioning > Physical Adapters >
Move or Remove window. The window shows slots that can be moved or removed
from the logical partition. Those slots that are listed are not required in the partition
profile, or that have been added (as desired) from a previous dynamic add operation.
The previous couple of visuals illustrated how you would remove the necessary devices
from the operating system. Now that the proper devices have been removed in AIX, you
may remove the I/O slot using the HMC application. Beware that the slots will show up
in the adapters window whether you have performed the appropriate AIX rmdev
operations.

Instructor Guide
Instructor notes:
Purpose Show how to select the I/O slots that are to be moved or removed.
Details To move or remove I/O slots, first perform any necessary operating system
commands. Then select the slots from the I/O Adapter Move/Remove window (as shown in
the visual) and click OK.
Transition statement You can also dynamically add, move, or remove LHEA
resources.

V5.3
Instructor Guide
Uempty
LHEA dynamic operations

IBM Power Systems
You can Add, Move, or Remove logical HEA resources
Figure 9-17. LHEA dynamic operations AN111.0
Notes:
This menu allows adding, moving or removing Logical Host Ethernet Adapter logical
ports dynamically to a running logical partition. These ports allow the logical partition to
access and use the physical port resources on a physical Host Ethernet Adapter.
To add logical ports dynamically to the logical partition, select the HEA whose resources
you want to use, select the physical port for which you want to create a logical port, and
click Configure. If you change your mind about adding a logical port to the logical
partition, select the physical port that corresponds to the logical port and click Reset.

Instructor Guide
Instructor notes:
Purpose
Details
Transition statement Lets see how to move or remove an LHEA.

V5.3
Instructor Guide
Uempty
Move/Remove an LHEA from the logical partition

IBM Power Systems
Select the logical

port to move or to
remove
Choose partition
Specify None to
remove the LHEA
Figure 9-18. Move/Remove an LHEA from the logical partition AN111.0
Notes:
Here is an example of moving or removing a Logical Host Ethernet Adapter logical port
dynamically from the selected partition.
Select the HEA whose logical port you want to remove, select the physical port whose
logical ports you want to remove and click OK.
To move logical ports dynamically from the logical partition to another running logical
partition, select also the destination logical partition in Logical Partition and click OK.
To move or remove LHEA from a logical partition, first perform any necessary operating
system commands.
On the logical partition, the HEA logical port has entx as child device. Before
moving or removing the HEA logical port from the logical partition, you need to
remove the devices (lheax and entx). We find out the lhea0 child device ent1 with
lsdev or odmget.
# odmget -q parent=lhea0 CuDv | grep name
name=ent1

Instructor Guide
Using the lsslot command, you can also see the lhea0 and its child device ent1.
# lsslot -c slot | grep lhea
# slot Description Device(s)
HEA 1 Logical I/O slot lhea0 ent1
Then perform rmdev -dl lhea0 -R command before performing the dynamic
move or remove operation.

V5.3
Instructor Guide

Purpose
Details
Transition statement You will also want to change hardware resources using the
chhwres command.

Instructor Guide
chhwres HMC command for DLPAR

IBM Power Systems
Change hardware resource (chhwres) command

chhwres -r {resource} -o {a|r|m} -t "T-LPAR" \
-p "S-LPAR -m MSname -q {#} -w {#}
Examples for a managed system named lou

Add 16 MB unit of memory
chhwres -r mem -o a -p LPAR1 -m lou -q 16 -w 0
Move 1 processor from LPAR1 to LPAR2

chhwres -r proc -o m -p LPAR1 -t LPAR2 \
-m lou -q 1 -w 0
Addition of I/O slot

chhwres -r io -rsubtype slot -o a -p LPAR1 \
-m lou l 21030003 -w 0
DRCindex
Figure 9-19. chhwres HMC command for DLPAR AN111.0
Notes:
Introduction
You can use the chhwres command to perform dynamic partition operations. The
visual shows a subset of the options available for this command. For more information
on the command options, log in to the HMC through SSH and use the man chhwres or
chhwres --help commands.
I/O slot operations and the DRC index

To specify an exact I/O slot, you use the DRC index for a particular slot. Use the
lshwres HMC command to find out what the DRC index is for a slot. The DRC index is
not a static address and might change if the physical I/O hardware is reconfigured; so
always check the address first with lshwres before issuing a chhwres for dynamic I/O
slot operations. An example of this lshwres command and its output is shown on the
next page.

V5.3
Instructor Guide

Purpose Describe the chhwres command for performing DLPAR operations.
Details Describe the syntax of the command and go over the examples.
Mention that quotes must be used if any of the partition or managed system names have
spaces in them.
Students will have a chance to practice this command in the lab exercise.
Transition statement You will also want to list information about resources using the
lshwres command.

Instructor Guide
List resources with lshwres command

IBM Power Systems
List hardware resource (lshwres) command

lshwres -r {resource} -m MSname -level type \
F attr1,attr2 -header
Examples for a managed system named lou

List memory information
lshwres -r mem -m lou -level lpar
List processor information
lshwres -r proc -m lou -level lpar
List IO slot information
lshwres -r io m lou -rsubtype slot
List only desired attributes
lshwres -r proc m lou -level lpar \
F lpar_name,curr_proc_units --header
Figure 9-20. List resources with lshwres command AN111.0
Notes:
Introduction
You can use the lshwres command to view results of dynamic partition operations or to
view current configurations before running chhwres commands. The visual shows a
subset of the options available for this command. For more information on the
command options, log in to the HMC through SSH and use the man lshwres or
lshwres --help commands.
The name of the lshwres command is the shortened form of the phrase List Hardware
Resources. The name of the chhwres command is the shortened form of the phrase
Change Hardware Resources.

V5.3
Instructor Guide
Uempty I/O operations and DRC index

Here is an example of the lshwres command to find out the DRC index for a specific
I/O slot. In this example, on the managed system named sys046, the DRC index for the
C5 slot that contains an Ethernet adapter is 21010203:
hscroot@sys046hmc:~> lshwres -r io -m sys046 --rsubtype slot|grep C5
unit_phys_loc=U78A0.001.DNWGCPM,bus_id=515,phys_loc=C5,drc_index=2101020
3,lpar_name=sys046_v3_T5,lpar_id=8,slot_io_pool_id=none,description=PCI
10/100/1000Mbps Ethernet UTP
2-port,"feature_codes=5706,5706,5706",pci_vendor_id=8086,pci_device_id=1
079,pci_subs_vendor_id=1014,pci_subs_device_id=0289,pci_class=0200,pci_r
evision_id=03,bus_grouping=0,iop=0,parent_slot_drc_index=none,drc_name=U
787A0.001.DNWGCPM-P1-C5

Instructor Guide
Instructor notes:
Purpose Describe the lshwres command for listing the current resource configuration.
Details Describe the syntax of the command and go over the examples.
Mention that quotes must be used if any of the partition or managed system names have
spaces in them.
Students will have a chance to practice this command in the lab exercise.
Transition statement Next, lets review topic 1.

V5.3
Instructor Guide
Uempty
Lets review Topic 1

IBM Power Systems
1. The upper and lower limits for dynamically adding and removing memory
are bound by what two partition configuration settings?
2. Which operating systems support the dynamic reallocation of resources?
3. What types of slots can you dynamically remove from a running

partition?
4. True or False: If you want to dynamically add memory to a partition, but

this would put it past its maximum memory setting, you can simply alter
the active partition profile to change the maximum setting.
Notes:

Instructor Guide
Instructor notes:
Purpose Check the students comprehension of the material for the topic.
Details Review all Lets Review solutions.

IBM Power Systems
1. The upper and lower limits for dynamically adding and removing memory are
bound by what two partition configuration settings?
Maximum and minimum settings in the active profile
2. Which operating systems support the dynamic reallocation of resources? AIX V5.3
and V5.2, AIX V6.1, SLES 9, SLES 10, RHEL AS 4 and RHEL AS 5 support
DLPAR
3. What types of slots can you dynamically remove from a running partition? Desired
slots or those added by a previous dynamic add operation can be removed.
The adapters in the slots cannot be in use and must be removed with rmdev
in AIX.
4. True or False: If you want to dynamically add memory to a partition, but this would
put it past its maximum memory setting, you can simply alter the active partition
profile to change the maximum setting.
You cannot change the minimum or maximum settings for a running partition
and have them take immediate effect. You must change the profile and
reactivate the partition.
concepts in this topic.

V5.3
Instructor Guide
Uempty
Exercise
IBM Power Systems
Topic
1
exerc
ise
Notes:

Instructor Guide
Instructor notes:
Details There is a Topic 1 hands-on exercise in the Exercise Guide to reinforce the
concepts in this topic. The instructor can choose to defer this exercise until the end of the
unit and have students do the Topic 1 and Topic 2 exercise steps together.
Transition statement The second topic in this unit is on DLPAR troubleshooting.

V5.3
Instructor Guide
Uempty 9.2. DLPAR troubleshooting

What students will do Students will learn how DLPAR operations work, how to spot
potential problems, and how to resolve issues with DLPAR operations.
How students will do it Students will participate in the lecture, answer Lets Review
questions, and perform a lab exercise at the end of this topic.
What students will learn Students will learn commands to verify the proper functioning
of DLPAR operations and see potential problems and how to resolve them.
How this will help students on their job Dynamically reallocating resources is seen as
a vital operation on complex managed systems to maintain performance expectations and
support changing workload needs. Any student in a system administration or support role
will need to know how to avoid and troubleshoot any DLPAR issues.

Instructor Guide
Topic 2: DLPAR troubleshooting objectives

IBM Power Systems
Use AIX and HMC commands to verify DLPAR is

operational
Stop and start RMC daemons
Figure 9-23. Topic 2: DLPAR troubleshooting objectives AN111.0
Notes:

V5.3
Instructor Guide

able to do by the end of the topic.
Transition statement First, lets review how DLPAR works and then we will expand on
this information.

Instructor Guide
How DLPAR works

IBM Power Systems
1
HMC
HMC command
2
3 3
Partition A Partition B
Hypervisor 4
Figure 9-24. How DLPAR works AN111.0
Notes:
Introduction
The visual illustrates how a dynamic move operation works:
1. The DLPAR request originates at the HMC.
2. The request is made over the network to the POWER Hypervisor.
This is the private network connected to HMC ports on managed
systems.
3. Partition A and Partition B communicate with the HMC about the
DLPAR operation through a process running on both partitions.
This public network is a way the HMC communicates with Ethernet
adapters in the LPARs (physical or virtual). This carries RMC
traffic.
4. The POWER Hypervisor makes the resource allocation change.

V5.3
Instructor Guide
Uempty 5. As you can see in the visual, DLPAR operations are dependent on
a functioning network between the HMC and the managed system,
and between the HMC and the partitions.
If the network is down either between the HMC and the managed system or between
the partitions and the HMC, or if there are problems with routing, then DLPAR
operations cannot occur.
POWER4 and POWER5-based or POWER6-based servers comparison

In POWER4-based servers, the HMC communicates with the Hypervisor through a
serial link between the HMC and the service processor on the managed system. In
POWER5 or POWER6 processor-based managed systems, this link is accomplished
using an Ethernet connection between the HMC and the service processor.

Instructor Guide
Instructor notes:
Purpose Show whats involved in a DLPAR operation.
Details Review the components involved and what they do during a DLPAR operation.
The point to make on this slide is that there are two separate network connections that
must be fully functional to make DLPAR operations work. First, the link between the HMC
and the service processor is used to initiate the operation, then the link to the partition or
partitions is used to complete the operation.
Transition statement Next, we will see a key communication system used for DLPAR
operations.

V5.3
Instructor Guide
Uempty
Reliable Scalable Cluster Technology

IBM Power Systems
Reliable Scalable Cluster Technology (RSCT)

Designed initially to enable clustering but now has many uses
Special management domain: HMC for DLPAR Management
Resource Monitoring and Control (RMC)
Resource
Entity that provides services
Has persistent and dynamic attributes
Example: /var filesystem
Resource class
Collection of resources with similar characteristics
Example: IBM.FileSystem
Resource manager
Software component that manages classes
Example: IBM.FSRM manages IBM.FileSystem class
Figure 9-25. Reliable Scalable Cluster Technology AN111.0
Notes:
RSCT overview
RSCT was firstly introduced with the Parallel System Support Program Version 2.2. Its
former name was HAI (High Availability Infrastructure). With the release of the ES
Version of HACMP, RSCT became an integral part of HACMP. Other software products
like GPFS and VSD even relied on RSCT services. The major function of RSCT is to
enable a cluster-wide coordination and communication between nodes.
With AIX 5L V5.1, RSCT became part of the operating system. Its major use is to
monitor defined conditions on the local machine only and to automate responses if a
monitored condition becomes true.
The subsystem itself is not called RSCT, but RMC - Resource Monitoring and Control.
The number of resource managers on your system will depend on the AIX 5L version.
DLPAR related resource managers were added in AIX 5L V5.2 as well as the
IBM.WLMRM. resource manager.

Instructor Guide
Instructor notes:
Purpose Give a brief overview of RSCT and its RMC subsystem.
Details The basics here are that there are things to be monitored (resources) that are
grouped into classes and are managed by resource managers. There can be events or
triggers configured and the resource manager can respond in some way. Most of this
happens in the background without interference from people. This is being introduced
because the HMC has resource managers which interact with the partitions. One in
particular, IBM.DRM, must be present for DLPAR to work.
Transition statement Lets look at some of the resource managers in use by AIX.

V5.3
Instructor Guide
Uempty
Resource managers (1 of 2)
IBM Power Systems
Common resource managers you will see on AIX

# lssrc -g rsct_rm
Subsystem Group PID Status
IBM.ERRM rsct_rm 221312 active
IBM.HostRM rsct_rm 250012 active
IBM.CSMAgentRM rsct_rm 159868 active
IBM.AuditRM rsct_rm 241804 active
IBM.DRM rsct_rm 237716 active
IBM.ServiceRM rsct_rm 184388 active
IBM.LPRM rsct_rm 233636 active
Resource managers start upon use or upon start of ctrmc

daemon
List resource managers with lssrc or ps command
After a reboot, it may be necessary to wait a few minutes for all subsystems to
become active
Figure 9-26. Resource managers (1 of 2) AN111.0
Notes:
Resource managers
Some resource managers manage several related resource classes. For example,
IBM.DMSRM manages the IBM.ManagedNode, IBM.NodeGroup,
IBM.NodeAuthenticate and IBM.DmsCtrl resource classes.
The resource managers list in the visual is not a complete list. Some of the resource
managers are so-called lazy daemons that will become active upon demand. This is
what you will probably see on most AIX machines after installation.
See the redbook A Practical Guide for Resource Monitoring and Control (RMC) for
more information on RMC.
Alternate lssrc command

You can also use the -a option with lssrc to see a list of the resource managers. It also
shows if the ctcas process is running.

Instructor Guide
# lssrc -a | grep rsct

ctrmc rsct 262274 active
IBM.ServiceRM rsct_rm 266384 active
IBM.HostRM rsct_rm 278666 active
IBM.ERRM rsct_rm 282768 active
IBM.AuditRM rsct_rm 229544 active
IBM.CSMAgentRM rsct_rm 233664 active
IBM.DRM rsct_rm 274586 active
IBM.LPRM rsct_rm 245914 active
ctcas rsct inoperative
RSCT/RMC startup
The startsrc -s ctrmc startup command is called from /etc/inittab during system
initialization.

V5.3
Instructor Guide

Purpose Describe how to view what resource managers are active.
Details Describe the lssrc command can be used to see the active resource managers.
Explain that the list is dynamic because some resource managers are only active when
they are needed.
The next page shows a list of common resource managers that can be seen on an AIX
system.
Mention that there are also RMC daemons running on the HMC, but there is no way to see
them because of the restricted shell.
Transition statement The next page lists the most common resource managers.

Instructor Guide
Resource managers (2 of 2)
IBM Power Systems
CSM resource managers

IBM.DMSRM Domain Management System RM (MS)
IBM.HWCTRLRM Hardware Control RM (MS)
IBM.CSMAgentRM CSM Client Resource Agent RM (nodes)
Reacting to events
IBM.ERRM Event Response RM
IBM.ServiceRM Service RM
Monitoring data
IBM.FSRM File System RM
IBM.HostRM Host RM
IBM.SensorRM Sensor RM
IBM.WLM Workload Manager RM
Logging
IBM.AuditRM Audit Log RM
Further resource managers

IBM.ConfigRM Configuration RM
IBM.DRM Dynamic Resource Manager (DLPAR)
Figure 9-27. Resource managers (2 of 2) AN111.0
Notes:
Cluster System Management

Cluster System Management (CSM) provides a centralized way to manage a large
number of machines from a single point of control. CSM simplifies tasks, such as
installing, operating, and maintaining clusters of servers. It provides one consistent
interface for managing both AIX and Linux and has the flexibility to manage across
multiple hardware platforms, various network topologies, and different geographic sites.
To perform these centralized tasks, CSM uses RSCT to communicate with various
systems. Over time, other types of tasks, such as DLPAR operations, were developed
using RSCT for communications between systems.

V5.3
Instructor Guide
Uempty Resource managers

IBM.DRM and IBM.HostRM are lazy started resource managers, which means they are
only started when they get used. If IBM.DRM and IBM.HostRM are inoperative, there is a
good chance that you are having network/host name setup problems between the HMC
and the partition. After partition start, it might take up to 5 minutes until you see the
resource managers.

Instructor Guide
Instructor notes:
Purpose Provide a reference for the most common resource managers
Details Point out the last resource manager, the IBM.DRM. This is the resource manager
that DLPAR needs to function.
This page is intended to simply show different types of resource managers. It is not
intended to be a complete list, nor a lesson in what all these resource managers do. Simply
state that there are various resource managers and that these are examples. For DLPAR
we are particularly interested in the IBM.DRM resource manager.
The next two pages shows how the behavior of the resource managers that are important
to HMC and LPAR communications.
Transition statement Lets see how RMC is used for communication between the HMC
and partitions.

V5.3
Instructor Guide
Uempty
HMC and LPAR initial communication

IBM Power Systems
HMC
Acts as a special kind of CSM server
Writes its IP address to NVRAM of managed system
Waits for the LPAR to initiate RMC connection
Creates a managed node object in the database
LPARs
Managed nodes for DLPAR, Service Agent, and Service Focal Point
Initially reads IP address of HMC from NVRAM
IBM.CSMAgentRM reads HMCs IP address
IBM.DRM configures automatically to contact the HMC
IBM.ServiceAgent and IBM.Sfp are registered at the HMC
Figure 9-28. HMC and LPAR initial communication AN111.0
Notes:
Role of the HMC

From an RSCT point of view, the HMC is the management server for all LPARs. Each
LPAR is a ManagedNode object. The registration is done through RMC as soon as a
network connection to the HMC becomes available. The CSM version the HMC uses is
a special one that is used only for the following tasks:
Dynamic allocation of hardware resources on the partitions
Graceful shutdown of the AIX operating systems running on the partitions
Propagation of hardware error log entries from the AIX partitions to the HMC to
provide a single focal point for error collection
Unlike with CSM, an LPAR can have more than one Management Server.

Instructor Guide
Role of the LPAR

The partitions managed by one or two (in the case of redundant HMCs) HMCs, are
managed objects. That is, listing the persistent attributes of the
IBM.ManagementServer on a partition will show up to two HMCs as the management
server. The distinction between a CSM server and the HMC as the management server
is done in the ManagerType field. The partition gets the IP address of the HMC from
the managed systems NVRAM. Well see this in the output of an lsrsrc command
coming up in a few pages.

V5.3
Instructor Guide

Purpose Describe the roles of the HMC and LPARs when establishing the RMC
connection.
Details Describe the roles of the HMC and the LPAR to establish a connection using
RMC for DLPAR operations and the service tools.
There is more on the role of the IBM.CSMAgentRM resource manager on the next page.
Transition statement The next page shows more about the RMC authentication
process.

Instructor Guide
HMC and LPAR authentication

IBM Power Systems
DMSRM on HMC writes secret key to NVRAM every five minutes

CSMAgentRM on LPAR
Reads the HMC's key and IP address from NVRAM
Contacts DMSRM (on HMC) to create a ManagedNode resource
Creates a ManagementServer resource
Grants HMC permission to access necessary resource classes
LparCmdRM (on HMC) queries the partition for operating system

information and DLPAR capabilities
LPARs CSMAgent
communicates with HMCs
DMSRM for setup LPAR
HMC CSMAgentRM
DRM
HMCs LparCmdRM retrieves LPARs CSMAgentRM
status; waits for contact from retrieves HMC IP
LPARs DRM address and key
NVRAM
HMCs DMSRM stores IP
address and key in NVRAM
Figure 9-29. HMC and LPAR authentication AN111.0
Notes:
RSCT authentication
Authentication is the process of ensuring that another party is who it claims to be.
Authorization is the process by which a cluster software component grants or denies
resources based on certain criteria. The RSCT component that implements
authorization is RMC. It uses access control list (ACL) files to control user access to
resources. The RMC component subsystem uses cluster security services to map the
operating system user identifiers, specified in the ACL file, to network security identifiers
to determine if the user has the correct permissions. This is performed by the identity
mapping service, which uses information stored in the identity mapping files
ctsec_map.global and ctsec_map.local.

V5.3
Instructor Guide
Uempty Authorization details

1. On HMC: DMSRM pushes down the secret key and HMC IP address to NVRAM when it
detects a new CEC; this process is repeated every five minutes. Each time an HMC is
rebooted or DMSRM is restarted, a new key is used.
2. On AIX: CSMAgentRM, through RTAS, reads the key and HMC IP address out from
NVRAM. It will then authenticate the HMC.
This process is repeated every five minutes on a partition to detect a new HMCs and if
the key has changed. An HMC with a new key is treated as a new HMC and will go
though the authentication and authorization processes again.
3. On AIX: After authenticating the HMC, CSMAgentRM will contact the DMSRM on the
HMC to create a ManagedNode resource to identify itself as a partition of this HMC. (At
the creation time, the managed nodes Status attribute will be set to 127.)
CSMAgentRM then creates a compatible ManagementServer resource on AIX.
4. On AIX: After the creation of the ManagedNode and ManagementServer resources
on HMC and AIX respectively, CSMAgentRM grants HMC permission to access
necessary resource classes on the partition. After the granting the HMC permission,
CSMAgentRM will change its ManagedNode, on the HMC, Status to 1. (It should be
noted that without proper permission on AIX, the HMC would be able to establish a
session with the partition but will not be able to query for OS information, DLPAR
capabilities, or execute DLPAR commands afterwards.)
5. On HMC: After the ManagedNode Status is changed to 1, LparCmdRM establishes a
session with the partition, queries for operating system information and DLPAR
capabilities, notifies CIMOM about the DLPAR capabilities of the partition, and then
waits for the DLPAR commands from users.

Instructor Guide
Instructor notes:
Purpose Give an overview of the authentication process for the HMC and its partitions.
Details Review the main points on the visual. There is a lot of additional detail in the
notes; however, it all works without configuration so it is not important in this course to
cover the details.
Transition statement There is a command on the HMC you can use to see if the
DLPAR function is working.

V5.3
Instructor Guide
Uempty
Verifying HMC for DLPAR

IBM Power Systems
HMC command to verify DLPAR operation
hscroot@lou-hmc:~> lspartition dlpar
<#0> Partition:<1*8204-E8A*65BF7D1, , 10.6.104.45>

Active:<1>, OS:<AIX, 6.1, 6100-00-02-0750>, DCaps:<0x4f>,
CmdCaps:<0xb, 0xb>, PinnedMem:<256>
<#1> Partition:<2*8204-E8A*65BF7D1, , 10.6.104.46>

Active:<1>, OS:<AIX, 6.1, 6100-00-02-0750>, DCaps:<0x4f>,
CmdCaps:<0xb, 0xb>, PinnedMem:<256>
Figure 9-30. Verifying HMC for DLPAR AN111.0
Notes:
Verifying DLPAR on the HMC

The lspartition command can be used on the HMC to check to see if it thinks the
partitions that are running support DLPAR. If all active AIX partitions are listed as shown
in the output above, the system has been properly set up for DLPAR.
If an active partition is not listed, make sure the HMC and the missing partition can ping
each other. If they can, you can try restarting the RMC daemons on the partition first,
then if it still does not work, you can reboot the HMC to restart its RMC daemons. The
next page shows how to restart the RMC daemons on the AIX partition.

Instructor Guide
Instructor notes:
Purpose Describe how you can verify that the HMC recognizes partitions that are
capable of DLPAR.
Details Cover the lspartition HMC command. The important thing for DLPAR
troubleshooting is to see if all active partitions are listed. You do not need to cover the fields
and values shown for each partition.
If an active (running) partition is missing, try ping and restarting of the RMC daemons to fix
the issue. Make sure you wait the 5-7 minutes after the restart of the RMC daemons.
Transition statement Lets see how to look at and restart the RMC daemons in AIX.

V5.3
Instructor Guide
Uempty
RMC management
IBM Power Systems
Service tools and dynamic operations rely on RMC daemons

Wait up to 5-7 minutes after partition or HMC has booted
Check the RMC daemons (as root)
# lssrc -a | grep rsct
May also use ps or lssrc g rsct_rm to see if IBM.DRM is running
Resource Monitoring and Control (RMC) daemons

Started from /etc/inittab
Subsystem name is ctrmc
Run in both the partition and on the HMC
To stop the daemons (LPAR)

# /usr/sbin/rsct/bin/rmcctrl z
To start the daemons (LPAR) and enable remote client

communications
# /usr/sbin/rsct/bin/rmcctrl A
# /usr/sbin/rsct/bin/rmcctrl p
To restart daemons on HMC, reboot
Figure 9-31. RMC management AN111.0
Notes:
Verifying RMC daemons on the AIX 5L partitions

The Resource Monitoring and Control daemons are part of the Reliable, Scalable
Cluster Technology and are controlled by the System Resource Controller. These
daemons run in all partitions and communicate with equivalent RMC daemons running
on the HMC. The daemons start automatically when the operating system starts and
synchronize with the HMC RMC daemons. The daemons in the partitions and the
daemons on the HMC must be able to communicate over the network for Dynamic
logical partitioning operations to succeed. This is not the network connection between
the managed system (FSP) and the HMC; it is the network connection between the
operating system in each partition and the HMC.
Wait up to 5-7 minutes after activating partition

The polling interval for the RMC daemons to check with the HMC daemons is 5
minutes; so you need to wait long enough for the daemons to start up and synchronize.

Instructor Guide
What RMC daemons should be running?

Some daemons will start and stop as needed; so do not be too concerned if your
favorite one is not showing at any particular moment. Some may even show as inactive
which is fine; they become active when needed. You should, however, see some
running.
There are RMC daemons that run in AIX and Linux LPARs and that run on the HMC.
There are also RMC tasks that run in i5/OS partitions.
Log in as root to use lssrc -a

If you do not log in as root when you run this command you will see the error: The
System Resource Controller is having socket problems. This command works on AIX
and Linux.
Stopping and starting the RMC daemons

Normally, you should not have to stop and restart the daemons. They are started from
/etc/inittab and should work out of the box. If you cannot find any other obvious
issues, you can try stopping and starting the RMC daemons. Then wait 5-7 minutes
before testing DLPAR operations.
To stop the daemons:
/usr/sbin/rsct/bin/rmcctrl -z
To start the daemons:
/usr/sbin/rsct/bin/rmcctrl -A
To enable the daemons for remote client connections (HMC to LPAR and vice versa):
/usr/sbin/rsct/bin/rmcctrl -p
If you are familiar with the System Resource Controller (SRC) you might be tempted to
use stopsrc and startsrc commands to stop and start these daemons. Do not do it;
use the rmcctrl commands instead.
Additional potential issues

You should also check the following items:
/var is fragmented (see errpt) or approaching 100%.
IP addresses can be reached. Verify with the ping command.
All necessary ports are active on HMC and LPAR. They are fine by default.
If /var is 100% full, use chfs to expand it. If there is no more space available, examine
subdirectories and remove unnecessary files (for example, trace.*, core, and so forth).

V5.3
Instructor Guide
Uempty If there was not enough space available while initializing the RMC daemons, the
configuration of the resources might be corrupted.

Instructor Guide
Instructor notes:
Purpose Describe the role of the RMC daemons for DLPAR operations.
Details The rmcctrl -A command ensures that the subsystem group (rsct) and the
subsystem (ctrmc) objects are added to the SRC, and an appropriate entry added to the
end of /etc/inittab and it starts the daemons. The rmcctrl -z command just stops the
daemons.
These daemons should work out of the box and are not typically the cause of DLPAR
issues. However, you can try stopping and restarting the daemons when troubleshooting
issues.
Ask student to guess how to start/stop the RMC daemons on the HMC. The answer is that
because it is a black box and there is no option in the HMC applications to do this, you
must reboot the HMC.
Transition statement Lets look at a command to view RMC information.

V5.3
Instructor Guide
Uempty
Viewing resource class information

IBM Power Systems
# lsrsrc IBM.ManagementServer
Resource Persistent Attributes for IBM.ManagementServer
resource 1:
Name = 10.6.104.40"
Hostname = 10.6.104.40"
ManagerType = "HMC"
LocalHostname = 10.6.104.45"
ClusterTM = "9078-160"
ClusterSNum = ""
ActivePeerDomain = ""
NodeNameList = {partition5"}
Figure 9-32. Viewing resource class information AN111.0
Notes:
Verify that the partition knows its HMC

The lsrsrc command shown in the visual ensures that the LPAR knows its HMC. The
HMC in this case has the IP address of 10.6.104.40. If the command does not show the
correct or any HMC, this is probably due to a network error.
Listing the persistent attributes of the IBM.ManagementServer on a partition will show
up to two HMCs as management servers. The distinction between a CSM server and
the HMC as management server is done in the ManagerType field. The NodeNameList
attribute shows the host name of the partition and LocalHostname shows the partitions
IP address.

Instructor Guide
Instructor notes:
Purpose Describe how to see if the LPAR recognizes its HMC.
Details Describe the fields in the lsrsrc command shown in the visual. It will list up to
two HMCs if redundant HMCs are configured.
Transition statement If DLPAR still is not working after a restart of the RMC daemons,
you may want to reinitialize the RMC files. This is shown on the next page.

V5.3
Instructor Guide
Uempty
Reinitializing RMC configuration

IBM Power Systems
Whole system can be reinitialized

Stops RMC processes and resource managers
All ACL files deleted
New files are copied from templates
Fastest way to fix a broken configuration or to clear out files after cloning
Command:
# /usr/sbin/rsct/install/bin/recfgct
Figure 9-33. Reinitializing RMC configuration AN111.0
Notes:
Reinitializing RMC configuration

As a last resort if you suspect corruption, or if you have cloned LPARs as part of the
installation process, use recfgct utility to reinitialize the RMC files.

Instructor Guide
Instructor notes:
Purpose Describe when to use recfgct and what it does.
Details Review the points on the slide and mention that if all else fails when
troubleshooting DLPAR issues, you can try this command.
Transition statement Lets look at some messages that you might see if a DLPAR
operation fails.

V5.3
Instructor Guide
Uempty
DLPAR troubleshooting: Symptoms (1 of 2)

IBM Power Systems
RMC communication
problems in a partition
or on the HMC, or on
the network in between,
can result in different
error messages
Check RMC daemons
and network issues
All three example errors

resulted because of no
RMC communication to the
LPAR
Figure 9-34. DLPAR troubleshooting: Symptoms (1 of 2) AN111.0
Notes:
Symptoms
The visual shows three example error messages when a DLPAR operation fails. As in
most cases, it is important to know the context of the error. For example, did the system
or partition just reboot? Has the DLPAR operation ever worked?
Typically, errors are caused by the HMC not being able to communicate correctly with
the LPAR over the network connection. The problem may be as simple as you forgot to
wait up to 7 minutes after activating an LPAR before attempting a DLPAR operation. We
will look at other potential causes in the next series of pages.
No RMC connection or other failed message

The messages in the visual show what displays when the RMC daemons on the
partition cannot communicate with the RMC daemons on the HMC.

Instructor Guide
If you see one of these messages, the first question to ask yourself is, has this
operation ever worked before? If not, then check your network configuration. If it has
worked before, then perhaps the network or some network service, such as a gateway
system, may be down. Also, the partition may not be running or the partition may have
just been activated (or the HMC rebooted) and the RMC daemons have not had a
chance to synchronize.

V5.3
Instructor Guide

Purpose Show potential DLPAR error messages.
Details Typically, errors are TCP/IP configuration error or network services errors.
Transition statement Lets look at some more symptoms.

Instructor Guide
DLPAR troubleshooting: Symptoms (2 of 2)

IBM Power Systems
Sometimes it is not an error, but an invalid operation

Could prevent you from accessing DLPAR screens, or might fail after your
attempt
Invalid operation examples

Trying to add processors or memory when there are not any free
Trying to add processors or memory when LPAR is at maximum
Trying to move or remove processors or memory when a partition is at its
minimum
Altering processing unit and virtual processor quantities such that they are
out of the 1:10 range
The following information message means you are

attempting an invalid add operation.
Figure 9-35. DLPAR troubleshooting: Symptoms (2 of 2) AN111.0
Notes:
There are no resources to add

The screen in the visual is an example of a message that will appear when you attempt
an invalid operation due to lack of resources. An example of when you would see this
message is if your partition permits DLPAR but you do not have any resources available
for DLPAR. For example, a partition might have its minimum, maximum, and desired
processor amount set to 4. You will not be able to add, move, or remove processors to
or from this partition until you alter the profile and reactivate the partition.
Other Information (Info) windows

Figure 7-10 in this unit showed another type of Information window that described an
invalid operation that had been attempted. The message was Attempted to allocate
processing units less than the minimum capacity allowed with the specified virtual
processor setting. This is reporting that someone attempted to alter the processing

V5.3
Instructor Guide
Uempty units settings such that it did not follow the rule of no more than 10 virtual processors for
every 1.0 processing units. We will cover this rule in a later unit.
Another type of information message was also mentioned briefly in this unit. If you
attempt to remove I/O slots dynamically and there are adapters in them but the devices
have not been removed with rmdev in AIX, then an information window will report the
exact devices that must be removed.

Instructor Guide
Instructor notes:
Purpose Show potential DLPAR error messages.
Details The example message in the visual shows the error that would occur if you
attempted to add resources but the partition configuration would not allow it. This would
happen if the maximum for that resources had already been reached.
Transition statement Lets review some basic network configuration options that can
have an impact on DLPAR operations.

V5.3
Instructor Guide
Uempty
DLPAR troubleshooting: Network setup

IBM Power Systems
#1 issue for DLPAR problems
Standard TCP/IP configuration must be working

correctly between each LPAR and the HMC
HMC Configuration -> Customize Network Settings
Be sure IP address, netmask, default gateway, network routes,
DNS server are all set correctly
Select the Partition communications checkbox in HMC
configuration screen for LAN adapter that is used for HMC-to-
partition communication
Partitions on POWER5 and POWER6 processor-based servers
do not depend on host name resolution for DLPAR operations
Test routes
Use ping and HMCs Test Network Connectivity task
Figure 9-36. DLPAR troubleshooting: Network setup
Notes:
Network configuration
DLPAR operations are dependent on the network configuration. The first tool to try
when troubleshooting is ping, to figure out if the HMC and LPARs can communicate.
From the HMC, ping the LPARs IP address. To do this, go to the HMC Management
node in the navigation area. Click Test Network Connectivity in the working area.

Instructor Guide
Instructor notes:
Purpose Review key network configuration points as they relate to DLPAR operations.
Details Use standard TCP/IP troubleshooting skills to determine why a partition and its
HMC cannot communicate.
Additional information Host name resolution was very important for the
communication of POWER4 processor-based systems partitions and their HMCs. The
POWER4 processor-based systems partitions and HMCs use IP addresses rather than
host names to identify each other.
Transition statement Next is a review of topic 2.

V5.3
Instructor Guide
Uempty
Lets review Topic 2

IBM Power Systems
1. True or False: DLPAR operations depend on host name resolution

services to work on POWER5-based and POWER6-based systems.
2. How does an LPAR learn the IP address of its HMC?
3. True or False: The /usr/sbin/rsct/bin/rmcctrl z command can be

used on AIX partitions and the HMC to stop the RMC daemons.
4. What command can be used to test the connectivity between LPARs

and the HMC?
Figure 9-37. Lets review Topic 2
Notes:

Instructor Guide
Instructor notes:
Purpose Check the students comprehension of the material for the topic.
Details Review all Lets Review solutions.

IBM Power Systems


CSMAgentRM on the partition reads the HMC's secret key and IP
address from NVRAM.

This is true only for AIX 5 and AIX 6. To stop and start the RMC
daemons on the HMC you must reboot the HMC.

and the HMC?
The ping command can be used. The HMCs interface to ping is
Test Network Connectivity on the HMC Management node.
Transition statement Now we have a Checkpoint with questions on the entire unit.

V5.3
Instructor Guide
Uempty
Checkpoint
IBM Power Systems
1. List the most common issue that prevents DLPAR operations from
working.
2. True or False: Dynamically reallocating resources on a partition does

not alter the contents of the active partition profile.
3. If a partitions processor or memory resource is already at its

maximum setting, and you need to add more, what do you need to
do?
4. What dynamic reconfiguration operations can be scheduled on the

HMC?
Notes:

Instructor Guide
Instructor notes:
Purpose Check the students comprehension of the material for the entire unit.
Details Have the students answer these questions. This checkpoint covers the entire
unit and serves as a last chance for questions.
IBM Power Systems
1. List the most common issue that prevents DLPAR operations from working.
Network issues
2. True or False: Dynamically reallocating resources on a partition does not alter
the contents of the active partition profile.
In addition to the DLPAR operation itself, if you want the change to occur
the next time you activate the partition, make the change in the profile.
3. If a partitions processor or memory resource is already at its maximum setting,
and you need to add more, what do you need to do?
Shut down the partition, increase the maximum setting in the profile, and
4. What dynamic reconfiguration operations can be scheduled on the HMC?
All DLPAR operations (add, move, and remove operations for
processors, memory and I/O slots).

V5.3
Instructor Guide
Uempty
Exercise
IBM Power Systems
Topic
exerc 2
ise
Notes:

Instructor Guide
Instructor notes:

V5.3
Instructor Guide
Uempty
Unit summary
IBM Power Systems
List the system requirements for dynamic logical partitioning

(DLPAR)
Dynamically remove, add, and move processors, memory, HEA
logical ports and I/O slots to and from partitions
Perform operating system operations necessary to dynamically add
and remove I/O slots
hardware resources
Notes:
The DLPAR capabilities of the different operating systems vary
Processors, memory, and I/O slots may be dynamically removed, added, and moved to
and from partitions
- Quantities are bounded by minimum and maximum, or desired and required settings
- Not all of the operating systems support all of the DLPAR operations
Additional AIX commands are necessary when dynamically adding and removing I/O
slots
HMC commands can be used to perform DLPAR operations
DLPAR operations can be scheduled on the HMC
Troubleshooting DLPAR operation errors involves looking at the network configuration,
RMC configuration, and validity of the operation

Instructor Guide
Instructor notes:
Details
1) What are the two limits in an active partition profile that are used for dynamic
partitioning for processors and memory?
Answer: You cannot reduce the amount of memory or the number of processors to less
than the minimum amount. You cannot grow these amounts more than the maximum.
2) If you reach the maximum number of processing units for a partition and you want
to dynamically add more, what could you do?
Answer: You will need to change the partitions profile and reactivate the partition.
3) What DLPAR operations can be automated from the HMC Configuration
application?
Answer: You can add, move, or remove processing units, memory, and I/O slots; that is, all
DLPAR operations are supported.
4) If you see the message There is currently no RMC connection when you
attempt a DLPAR operation, what should you do?
Answer: Suspect that there is a network issue, or perhaps the partition is not running. Open
a terminal window to the partition and check that the operating system is running. Did the
partition just start up and you have not waited 5-7 minutes? Use commands like ping and
netstat -r to check network services.
Transition statement The next unit will cover advanced processor concepts.

V5.3
Instructor Guide
AP Appendix A. Checkpoint solutions

Unit 1
IBM Power Systems
1. 1. True or False: A partition is an independent operating environment.

3. Which of the following statements are true for dynamic partition operations?
resources.

Processors, memory, I/O slots (including the Host Ethernet Adapter)
Copyright IBM Corp. 2009 Appendix A. Checkpoint solutions A-1

Instructor Guide
Unit 1
IBM Power Systems

that can be activated when you need them? Capacity on Demand
(CoD)


partitions? POWER Hypervisor

configure CoD, and provide access to virtual consoles? HMC or IVM

partitions? Micro-Partitioning
A-2 PowerVM Virtualization I Copyright IBM Corp. 2009

V5.3
Instructor Guide
AP Unit 2
IBM Power Systems
1. What is the maximum number of partitions per processor that

can be created on an IBM Power System 570 with four
a. 40
b. 20
c. 10
2. Which are features of the Power 550 system?

d. Can be cabled with other Power 550s to create 8-, 12-, or 16-way SMP
system

Instructor Guide
Unit 2
IBM Power Systems
550, and 570 system drawers.
Processors, memory, PCI-X slots, disks
Standard Edition feature has not been ordered?
The maximum number of partitions is the same as activated physical
processors.
of slots?
T slots are integrated slots on the system planar and do not
correlate to the PCI-X or PCI Express slots on the system drawer.
At the end of a location code, a T followed by a number indicates a
specific port on an adapter.
7. List at least three functions of the Flexible Service Processor.
Provides system initialization, connects to the HMC, runs ASMI for
setting system flags, includes hardware error detection.

V5.3
Instructor Guide
AP Unit 3

IBM Power Systems


server? When it is on a private network and there is no
other DHCP server.

The connection uses Ethernet.

systems.

Instructor Guide
Unit 3
Unit

IBM Power Systems

c. You can set multiple task roles and multiple managed resource roles
for a user.
d. A user with a custom task role can be created, which allows the
user to access only the HMC command line and not the Web
browser user interface.

Remote Web connection, SSH login

line?
Open firewall, enable SSH access from HMC Management Work
pane, install SSH on client
4. True or False: The communication between a remote Web browser and the
HMC is SSL encrypted by default.

V5.3
Instructor Guide
AP Unit Unit 3
IBM Power Systems

c. The IP address for the service processor can be set to any valid IP
address.
d. The network configuration for the service processor can be changed in
the ASMI application.


Use the Shutdown or Restart task from the HMC Management
work pane or log in with SSH to the HMC command line and type
hmcshutdown r t now

Instructor Guide
Unit 3
IBM Power Systems

A user account is used to log in. A task role is a predefined set
of access rights.
Remote virtual console, SSH access, remote Web connection

system. The HMC allows only restricted shell access to a
reduced set of Linux commands.

V5.3
Instructor Guide
AP Unit 4
IBM Power Systems




Instructor Guide
Unit 5
IBM Power Systems

Yes. Perform the installation/recovery process.
2. True or False: Performing a Backup Critical Console Data backs up all partition
configuration data.
It is true because it saves the profile data backup files. Even if you do not
perform any profile data backup operation, there is one automatic file named
backupFile.
3. True or False: You can back up critical HMC data to either DVD-RAM or floppy.
You must back up to DVD.
4. From where is your HMC configuration information restored during the upgrade
process?
From the special area on the HMC disk (if you remembered the Save Upgrade
Data step).
5. From where is your HMC configuration data restored during the installation/recovery
process?
Your Backup Critical Console Data DVD-RAM, or from a remote system using
NFS or FTP.
6. List two things that the Backup Critical Console Data option backs up.
User configuration, user-preference files, platform-configuration files, log files,
partition profile data backup files.

V5.3
Instructor Guide
AP Unit 6
IBM Power Systems

Operator Panel power button, ASMI, HMC Command Line,
HMC GUI application

System profile, Partition standby, Partition auto start, Hardware
Discovery

profiles?
System profile option
The normal option allows all active jobs to end in a controlled manner.
Fast causes jobs to end without cleanup processing.
5. What HMC command can be used to power on or off the managed system?
chsysstate

Instructor Guide
Unit 7
IBM Power Systems

description:
using dynamic operations. Maximum
Minimum
more than enough resources on the system when the partition is activated
(starts). Desired


V6.1 partition?
128 MB or, if the LMB size of the partition is 256 MB, then the
minimum would be 256 MB.

V5.3
Instructor Guide
AP Unit 7
IBM Power Systems
5. What happens if the minimum (or required) amount of a resource is not available when a
partition is activated?
The partition will not start.
6. How many processors is a partition allocated if, when it starts, it has a minimum of three
processors, desires five processors, and four processors are currently available on the system?
It starts with four processors.
7. What happens if a partition is currently running with its three minimum processors, but it desires
five processors and another processor becomes available after the partition is started?
Nothing
8. What is the granularity of allocating processor resources when configuring partitions?

For dedicated processor partitions, allocations are made in units of 1. For partitions
using the shared processor pool, allocations are made in units of 0.01, with a minimum
allocation of 0.1 processing units.
9. When incrementing the amount of memory for a partition profile, the minimum unit is how
much? It is
the amount of the LMB (16 MB 256 MB)
10. Can you assign the HEA itself to a logical partition? No,
multiple logical partitions can connect directly to the HEA and use the HEA resources.

Instructor Guide
Unit 8
IBM Power Systems

Log in to a partition and shut down. Or use HMC shut down
menu option or the chsysstate command.
Standby or Operating
The first one is the default.
5. When you modify a partition profile's configuration, what must you
do to apply the new configuration to an active partition?
Shut down the partition and reactivate it.
profiles.

V5.3
Instructor Guide
AP Unit 8
IBM Power Systems
7. List at least two things you can do if a partition will not activate.
Use DLPAR to free up resources. Reconfigure partitions. Use the
managed system properties to determine current resource
allocations.

States: Not Activated, Shutting Down, Running, Not Available
a. _Shutting Down The partition is in the process of stopping.

b. _Running_____ The partition has been successfully activated.
c. _Not Activated_ The partition is not running but is available to be
activated.
d. _Not Available_ The system is in a state that prevents the partition
from being activated (such as the managed system
is powered off).
9. True or False: When activating a partition, you must use the Open
Terminal Window option.

Instructor Guide
Unit 9

IBM Power Systems
1. The upper and lower limits for dynamically adding and removing memory are
bound by what two partition configuration settings?
Maximum and minimum settings in the active profile
2. Which operating systems support the dynamic reallocation of resources? AIX V5.3
and V5.2, AIX V6.1, SLES 9, SLES 10, RHEL AS 4 and RHEL AS 5 support
DLPAR
3. What types of slots can you dynamically remove from a running partition? Desired
slots or those added by a previous dynamic add operation can be removed.
The adapters in the slots cannot be in use and must be removed with rmdev
in AIX.
4. True or False: If you want to dynamically add memory to a partition, but this would
put it past its maximum memory setting, you can simply alter the active partition
profile to change the maximum setting.
You cannot change the minimum or maximum settings for a running partition
and have them take immediate effect. You must change the profile and

V5.3
Instructor Guide
AP Unit 9

IBM Power Systems


CSMAgentRM on the partition reads the HMC's secret key and IP
address from NVRAM.

This is true only for AIX 5 and AIX 6. To stop and start the RMC
daemons on the HMC you must reboot the HMC.

and the HMC?
The ping command can be used. The HMCs interface to ping is
Test Network Connectivity on the HMC Management node.

Instructor Guide
Unit 9
IBM Power Systems
1. List the most common issue that prevents DLPAR operations from working.
Network issues
2. True or False: Dynamically reallocating resources on a partition does not alter
the contents of the active partition profile.
In addition to the DLPAR operation itself, if you want the change to occur
the next time you activate the partition, make the change in the profile.
3. If a partitions processor or memory resource is already at its maximum setting,
and you need to add more, what do you need to do?
Shut down the partition, increase the maximum setting in the profile, and
4. What dynamic reconfiguration operations can be scheduled on the HMC?
All DLPAR operations (add, move, and remove operations for
processors, memory and I/O slots).

V5.3
backpg
Back page

AN11 Power Systems For AIX I LPAR Configuration and Planning Instructor Guide 2009 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AN11 Power Systems For AIX I LPAR Configuration and Planning Instructor Guide 2009 PDF

Uploaded by

Copyright:

Available Formats

Power Systems for AIX I:

LPAR Configuration and

(Course code AN11)

June 2009 edition

Copyright International Business Machines Corporation 2009. All rights reserved.

iii PowerVM Virtualization I Copyright IBM Corp. 2009

iv PowerVM Virtualization I Copyright IBM Corp. 2009

Instructor course overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Course description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Unit 1. Introduction to partitioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Copyright IBM Corp. 2009 Contents v

Unit 2. Hardware system overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Unit 3. Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1

vi PowerVM Virtualization I Copyright IBM Corp. 2009

TOC Toolbar features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55

Copyright IBM Corp. 2009 Contents vii

IVM LPAR management: Common Web interface . . . . . . . . . . . . . . . . . . . . . . . .3-177

Unit 4. System Planning Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Unit 5. HMC and managed system maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

viii PowerVM Virtualization I Copyright IBM Corp. 2009

TOC Examine current firmware level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39

Unit 6. System power management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Unit 7. Planning and configuring logical partitions . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Copyright IBM Corp. 2009 Contents ix

Configure dedicated processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-53

Unit 8. Partition operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

x PowerVM Virtualization I Copyright IBM Corp. 2009

TOC Scheduling operations (2 of 4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-76

Unit 9. Dynamic resource allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Copyright IBM Corp. 2009 Contents xi

Resource managers (1 of 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-67

Appendix A. Checkpoint solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

xii PowerVM Virtualization I Copyright IBM Corp. 2009

Copyright IBM Corp. 2009 Trademarks xiii

xiv PowerVM Virtualization I Copyright IBM Corp. 2009

pref Instructor course overview

Copyright IBM Corp. 2009 Instructor course overview xv

xvi PowerVM Virtualization I Copyright IBM Corp. 2009

pref Course description

Copyright IBM Corp. 2009 Course description xvii

Configure and manage the HMC, including users and permissions,

xviii PowerVM Virtualization I Copyright IBM Corp. 2009

Copyright IBM Corp. 2009 Agenda xix

xx PowerVM Virtualization I Copyright IBM Corp. 2009

Uempty Unit 1. Introduction to partitioning

What this unit is about

What you should be able to do

How you will check your progress

Copyright IBM Corp. 2009 Unit 1. Introduction to partitioning 1-1

1-2 PowerVM Virtualization I Copyright IBM Corp. 2009

After completing this unit, you should be able to:

Figure 1-1. Unit objectives AN111.0

Copyright IBM Corp. 2009 Unit 1. Introduction to partitioning 1-3

1-4 PowerVM Virtualization I Copyright IBM Corp. 2009

From One to Many

Copyright IBM Corporation 2009

Figure 1-2. What is a partition? AN111.0

Independent operating environment

Copyright IBM Corp. 2009 Unit 1. Introduction to partitioning 1-5

1-6 PowerVM Virtualization I Copyright IBM Corp. 2009

Physical partition (PPAR)

SMP building block SMP building block SMP building block

Operating System Operating