IBM PowerVC Introduction and Configuration

ibm.com/redbooks
Draft Document for Review November 20, 2013 5:11 pm SG24-8199-00
IBM PowerVC
Introduction and Configuration
Guillermo Corti
Sylvain Delabarre
Ho Jin Kim
Ondrej Plachy
Marcos Quezada
Gustavo Santos
Installation requires just 20 minutes to
get a virtual machine up and running
Intelligent virtual machine
deployment
Deep integration with
Power Systems
Front cover

IBM PowerVC Introduction and Configuration
November 2013
International Technical Support Organization
Draft Document for Review November 20, 2013 5:11 pm 8199edno.fm
SG24-8199-00

8199edno.fm Draft Document for Review November 20, 2013 5:11 pm
© Copyright International Business Machines Corporation 2013. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
First Edition (November 2013)
This edition applies to Version 1, Release 2 of IBM PowerVC Standard Edition (5765-VCS) and
IBM PowerVC Express Edition (5765-VCX).
This document was created or updated on November 20, 2013.
Note: Before using this information and the product it supports, read the information in
“Notices” on page xvii.

iii
Draft Document for Review November 20, 2013 5:11 pm 8199edno.fm
Note: This book is based on a pre-GA version of a product and may not apply when the
product becomes generally available. We recommend that you consult the product
documentation or follow-on versions of this redbook for more current information.

8199edno.fm Draft Document for Review November 20, 2013 5:11 pm
iv IBM PowerVC Introduction and Configuration

© Copyright IBM Corp. 2013. All rights reserved. v
Draft Document for Review November 20, 2013 5:11 pm 8199TOC.fm
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Authors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Now you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . xxi
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Stay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 IBM PowerVC overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 IBM PowerVC Express Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 IBM PowerVC Standard Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.4 OpenStack Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.4.1 The OpenStack foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.4.2 OpenStack projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Chapter 2. Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 PowerVC positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.2 IBM Power Virtualization Center requirements . . . . . . . . . . . . . . . . . . . . . 10
2.2.1 Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.2 IBM Power Virtualization Center Express. . . . . . . . . . . . . . . . . . . . . 11
2.2.3 IBM Power Virtualization Center Standard . . . . . . . . . . . . . . . . . . . . 13
2.2.4 Planning Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3 IBM PowerVC Storage Access Planning. . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.3.1 Storage Connectivity Groups and Tags in IBM PowerVC Standard . 21
2.3.2 Storage Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4 Users and groups planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.4.1 Users management planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.4.2 Groups management planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
2.5 Security management planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
2.5.1 Ports used by IBM Power Virtualization Center . . . . . . . . . . . . . . . . 36
2.5.2 Providing a certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

8199TOC.fm Draft Document for Review November 20, 2013 5:11 pm
vi IBM PowerVC Introduction and Configuration
2.6 Hosts and clients management planning . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.6.1 Hardware Management Console Planning . . . . . . . . . . . . . . . . . . . . 38
2.6.2 Multiple Virtual I/O Servers planning. . . . . . . . . . . . . . . . . . . . . . . . . 38
2.7 Storage management planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.7.1 Possible storage configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
2.7.2 Specifying fibre channel ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.7.3 Storage volumes planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.8 Networks management planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.8.1 Multiple networks planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
2.8.2 Shared Ethernet Adapter planning . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2.9 Templates planning and placement policy . . . . . . . . . . . . . . . . . . . . . . . . 42
2.9.1 Placement policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
2.9.2 Templates planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Chapter 3. Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.1 Setting up the IBM Power Virtualization Center Standard environment . . 52
3.1.1 Creating the virtual machine to host PowerVC . . . . . . . . . . . . . . . . . 52
3.1.2 Changing Maximum Virtual Adapters in VIOS server . . . . . . . . . . . . 53
3.1.3 Downloading the RHEL 6.4 package . . . . . . . . . . . . . . . . . . . . . . . . 53
3.1.4 Red Hat Linux Base Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.1.5 Verify SELinux is Permissive or Disabled . . . . . . . . . . . . . . . . . . . . . 54
3.1.6 Setting default network interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.1.7 Setting DNS, and host name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.1.8 IBM Installation toolkit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.2 Installing IBM Power Virtualization Center from media . . . . . . . . . . . . . . . 55
3.2.1 Configuring the yum repository for the IBM PowerVC install . . . . . . 56
3.2.2 Installing IBM PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.3 Uninstalling IBM Power Virtualization Center . . . . . . . . . . . . . . . . . . . . . . 58
3.4 Consideration of installing virtual machines managed by PowerVC . . . . . 59
3.4.1 Linux virtual machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.4.2 AIX virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Chapter 4. IBM PowerVC Set up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.1 PowerVC setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.1.2 Connecting to PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.2 Hosts setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.3 Storage and SAN Fabric Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.3.1 Add storage controller and SAN Fabric to PowerVC . . . . . . . . . . . . 70
4.4 Storage port tags setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
4.5 Storage Connectivity Groups setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
4.6 Networks Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.7 Environment verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Contents vii
Draft Document for Review November 20, 2013 5:11 pm 8199TOC.fm
4.7.1 Verification report validation categories . . . . . . . . . . . . . . . . . . . . . . 82
4.8 Compute Templates setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.9 Storage Templates Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.10 Storage Volumes Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.11 IBM PowerVC Standard VM setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.11.1 Virtual machine onboarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.11.2 Virtual machine operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Chapter 5. IBM PowerVC Express Edition specifics . . . . . . . . . . . . . . . . 155
5.1 Installation and setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.1.1 Installing IBM PowerVC Express . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5.1.2 Setup and preparation of IBM PowerVC Express environment. . . . 156
5.2 Import, capture and deploy ISO images . . . . . . . . . . . . . . . . . . . . . . . . . 165
5.2.1 Import ISO images for deployments . . . . . . . . . . . . . . . . . . . . . . . . 165
5.2.2 Deploy a RHEL ISO image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.2.3 Image Capture and deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Chapter 6. PowerVC lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
6.1 Hardware infrastructure for PowerVC Standard edition . . . . . . . . . . . . . 196
6.2 Hardware Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6.3 Power Systems hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6.4 Storage infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6.4.1 Storage SAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6.5 Software stack for PowerVC Standard lab environment . . . . . . . . . . . . . 197
6.6 Hardware infrastructure for PowerVC Express edition . . . . . . . . . . . . . . 199
6.7 Power Systems hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6.8 Storage infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6.8.1 Storage SAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6.9 Software stack for PowerVC Express lab environment. . . . . . . . . . . . . . 199
6.10 Lab environment hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6.11 IBM PowerVC installation tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206

8199TOC.fm Draft Document for Review November 20, 2013 5:11 pm
viii IBM PowerVC Introduction and Configuration

© Copyright IBM Corp. 2013. All rights reserved. ix
Draft Document for Review November 20, 2013 5:11 pm 8199LOF.fm
Figures
1-1 IBM PowerVC technology overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1-2 Openstack framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2-1 IBM PowerVC Express Storage™ Access . . . . . . . . . . . . . . . . . . . . . . . . 20
2-2 IBM PowerVC Standard Storage Access . . . . . . . . . . . . . . . . . . . . . . . . . 21
2-3 Storage Connectivity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2-4 Storage Connectivity Groups And Tags . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2-5 Examples of Storage Groups Deployments . . . . . . . . . . . . . . . . . . . . . . . 24
2-6 Storage Template definition - Advanced Settings . . . . . . . . . . . . . . . . . . . 26
2-7 Users account view on the IBM PowerVC management host. . . . . . . . . . 28
2-8 Refresh users account view on the IBM PowerVC management host . . . 29
2-9 Detailed user account information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2-10 View updated user account information . . . . . . . . . . . . . . . . . . . . . . . . . 31
2-11 Users groups view on the IBM PowerVC management host . . . . . . . . . 34
2-12 Detailed view of viewer users group on management host. . . . . . . . . . . 35
2-13 Memory Region Size view on the HMC . . . . . . . . . . . . . . . . . . . . . . . . . 48
3-1 Processors configuration for PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3-2 Memory configuration for PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3-3 Configure maximum virtual adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
4-1 PowerVC login screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4-2 PowerVC Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4-3 HMC connection info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4-4 PowerVC Add hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4-5 PowerVC -Show managed hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4-6 host information, and the Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . 69
4-7 IBM PowerVC Standard Add Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4-8 IBM PowerVC Standard Select Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4-9 IBM PowerVC standard Add Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4-10 IIBM PowerVC Standard Add Fabric 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4-11 PowerVC - Show Storage Providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4-12 PowerVC Fibre Channel Port Configuration . . . . . . . . . . . . . . . . . . . . . . 75
4-13 PowerVC Storage Connectivity Groups . . . . . . . . . . . . . . . . . . . . . . . . . 76
4-14 PowerVC Add Member to Storage Connectivity Group . . . . . . . . . . . . . 78
4-15 PowerVC Defining a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4-16 IBM PowerVC interface while environment verification in process. . . . . 81
4-17 Verification Results view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4-18 Example of a validation message for an error status . . . . . . . . . . . . . . . 85
4-19 Example of a validation message for a valid status . . . . . . . . . . . . . . . . 86
4-20 PowerVC Create Compute Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

8199LOF.fm Draft Document for Review November 20, 2013 5:11 pm
x IBM PowerVC Introduction and Configuration
4-21 PowerVC Compute Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4-22 PowerVC Create Storage Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4-23 PowerVC Create Storage Template Advanced. . . . . . . . . . . . . . . . . . . . 92
4-24 PowerVC Storage Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4-25 PowerVC Create Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4-26 PowerVC Storage Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4-27 PowerVC management host web interface login screen . . . . . . . . . . . . 96
4-28 PowerVC management host home screen . . . . . . . . . . . . . . . . . . . . . . . 97
4-29 Selecting host view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4-30 Selected hosts view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
4-31 Collapse and expand buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4-32 Manage Existing button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4-33 Onboarding existing virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4-34 Example of information pop up message . . . . . . . . . . . . . . . . . . . . . . . 102
4-35 Display existing messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
4-36 Existing virtual machine view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
4-37 Virtual machine detailed view with collapsed sections . . . . . . . . . . . . . 104
4-38 Virtual Machine detailed view of expanded information section . . . . . . 105
4-39 Virtual Machine detailed view of expanded specification section . . . . . 107
4-40 Virtual Machine detailed view of expanded network section. . . . . . . . . 108
4-41 Detailed Network view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
4-42 Detailed view of the tree links to move backwards in the views . . . . . . 109
4-43 Virtual Machine detailed view of expanded details section . . . . . . . . . . 110
4-44 Operations buttons on the virtual machine view . . . . . . . . . . . . . . . . . . 111
4-45 Virtual machine powering on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
4-46 Virtual machine powered off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
4-47 Verify volume screen when pressing Capture button. . . . . . . . . . . . . . 121
4-48 Information and confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . 122
4-49 Entering the name for the capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
4-50 Image snapshot in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
4-51 Image creation in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4-52 Image view with a finished capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
4-53 Storage Volumes view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
4-54 Expanded information section of an image capture . . . . . . . . . . . . . . . 126
4-55 Expanded specification section of an image capture . . . . . . . . . . . . . . 128
4-56 Virtual Machines section of an image capture . . . . . . . . . . . . . . . . . . . 129
4-57 Image capture selected for deployment . . . . . . . . . . . . . . . . . . . . . . . . 130
4-58 Information to Deploy an image capture . . . . . . . . . . . . . . . . . . . . . . . . 132
4-59 New virtual machine deployed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4-60 Virtual Machine resize. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
4-61 Virtual Machine resize. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
4-62 Exceeded value for resizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
4-63 Virtual machine resize in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Figures xi
Draft Document for Review November 20, 2013 5:11 pm 8199LOF.fm
4-64 Display and review existing messages . . . . . . . . . . . . . . . . . . . . . . . . . 137
4-65 Migrate selected virtual machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
4-66 Select target server before migration . . . . . . . . . . . . . . . . . . . . . . . . . . 140
4-67 Virtual machine migration in progress. . . . . . . . . . . . . . . . . . . . . . . . . . 140
4-68 Virtual machine migration finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
4-69 Attaching a new volume to a virtual machine . . . . . . . . . . . . . . . . . . . . 142
4-70 Volume attaching in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
4-71 Attached volumes view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
4-72 Detach volume from a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . 145
4-73 Confirmation dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
4-74 Virtual machine reset state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
4-75 Reset state confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
4-76 Image selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4-77 Delete an image confirmation dialog. . . . . . . . . . . . . . . . . . . . . . . . . . . 149
4-78 Image deleted message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
4-79 Delete virtual machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
4-80 Delete virtual machine confirmation window . . . . . . . . . . . . . . . . . . . . . 152
4-81 Pop up message after a virtual machine is deleted . . . . . . . . . . . . . . . 152
5-1 IBM PowerVC Express Edition login window . . . . . . . . . . . . . . . . . . . . . 157
5-2 PowerVC Home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5-3 PowerVC “Add Host” box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5-4 IBM PowerVC Express Edition after host is added . . . . . . . . . . . . . . . . . 159
5-5 Add a storage to IBM PowerVC Express Edition . . . . . . . . . . . . . . . . . . 160
5-6 SVC Storage Pool choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
5-7 The new SVC storage provider is successfully added . . . . . . . . . . . . . . 161
5-8 Add a network to PowerVC configuration . . . . . . . . . . . . . . . . . . . . . . . . 162
5-9 Network is now configured . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5-10 Verify Environment in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5-11 Failed verification caused by SVC compatibility . . . . . . . . . . . . . . . . . . 165
5-12 Import an AIX ISO image into IBM PowerVC Express . . . . . . . . . . . . . 167
5-13 Import a RHEL ISO image into IBM PowerVC Express . . . . . . . . . . . . 168
5-14 ISO images are imported to PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . 169
5-15 Status of imported ISO images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5-16 RHEL ISO image details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
5-17 File list of the glance images directory . . . . . . . . . . . . . . . . . . . . . . . . . 170
5-18 Check storage templates in configuration . . . . . . . . . . . . . . . . . . . . . . . 171
5-19 SVC default storage template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5-20 Select the RHEL64 image for deployment . . . . . . . . . . . . . . . . . . . . . . 172
5-21 Virtual machine deployment parameters. . . . . . . . . . . . . . . . . . . . . . . . 173
5-22 Virtual machine building.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5-23 First active status for virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5-24 Virtual is shutdown after building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5-25 Open the vm’s console from IBM PowerVC Express . . . . . . . . . . . . . . 175

8199LOF.fm Draft Document for Review November 20, 2013 5:11 pm
xii IBM PowerVC Introduction and Configuration
5-26 First boot of virtual machine vmlnx02 . . . . . . . . . . . . . . . . . . . . . . . . . . 175
5-27 Default vm console choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5-28 .Startup banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
5-29 Select boot option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5-30 Boot options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5-31 Select boot devices menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5-32 Select the CD-ROM device for boot . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5-33 SMS boot mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
5-34 Exit SMS and boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
5-35 The vm boots from the chosen device . . . . . . . . . . . . . . . . . . . . . . . . . 180
5-36 Boot the Linux installation media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5-37 Reboot the installed vm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
5-38 Initial start banner after installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
5-39 Select boot options from SMS menu. . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5-40 Configure boot device order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5-41 Configure boot device order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5-42 Select boot device type menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5-43 Select media type menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5-44 Select Media Adapter menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
5-45 Select device menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
5-46 Set boot sequence menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
5-47 Exit SMS and boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
5-48 Confirm boot and exit SMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
5-49 First boot prompt. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
5-50 Exit the virtual machine console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
5-51 vmlnx02 is deployed and active. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
5-52 Start the vm capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
5-53 Capture a vm based on an ISO image . . . . . . . . . . . . . . . . . . . . . . . . . 192
5-54 Choose name and capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
5-55 Capture queued . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
5-56 The vm image is ready for deployment . . . . . . . . . . . . . . . . . . . . . . . . . 194
6-1 Lab environment for PowerVC Standard edition. . . . . . . . . . . . . . . . . . . 198
6-2 Lab environment for PowerVC Express edition. . . . . . . . . . . . . . . . . . . . 201

© Copyright IBM Corp. 2013. All rights reserved. xiii
Draft Document for Review November 20, 2013 5:11 pm 8199LOT.fm
Tables
2-1 Power Systems Virtualization Management Solutions . . . . . . . . . . . . . . . 10
2-2 Hardware and OS requirements for IBM PowerVC Express . . . . . . . . . . 11
2-3 Minimum resource requirements for the IBM PowerVC virtual machine. . 12
2-4 Supported virtualization platforms for IBM PowerVC . . . . . . . . . . . . . . . . 13
2-5 IBM PowerVC-supported network hardware and software . . . . . . . . . . . . 13
2-6 IBM PowerVC-supported storage hardware . . . . . . . . . . . . . . . . . . . . . . . 13
2-7 Hardware and operating system support for IBM PowerVC hosts . . . . . . 14
2-8 Minimum resource requirements for the IBM PowerVC virtual machine. . 15
2-9 HMC requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2-10 Supported virtualization platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2-11 Supported network hardware and software . . . . . . . . . . . . . . . . . . . . . . 16
2-12 Supported storage hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2-13 Supported security software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2-14 Ports used for inbound and outbound communication . . . . . . . . . . . . . . 36
2-15 Ports used by HMC, IVM and SVC with IBM PowerVCt . . . . . . . . . . . . . 36
2-16 Additional ports used by IBM PowerVC to connect. . . . . . . . . . . . . . . . . 36
2-17 Processor compatibility Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
4-1 Information section fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
4-2 Specifications section fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
4-3 Details section fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
4-4 Description of the fields on the information section. . . . . . . . . . . . . . . . . 126
4-5 Description of the fields on the Specifications section . . . . . . . . . . . . . . 127
6-1 HMC requirements used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6-2 Hardware test environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6-3 Storage switch specifications.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6-4 Software version and releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6-5 Hardware test environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6-6 Storage switch specifications.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6-7 Software version and releases used on PowerVC Express lab . . . . . . . 200

8199LOT.fm Draft Document for Review November 20, 2013 5:11 pm
xiv IBM PowerVC Introduction and Configuration

© Copyright IBM Corp. 2013. All rights reserved. xv
Draft Document for Review November 20, 2013 5:11 pm 8199LOE.fm
Examples
2-1 Adding admin user account with the useradd command . . . . . . . . . . . . . 28
2-2 Updating admin user account with the usermod command . . . . . . . . . . . 30
2-3 Delete an user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3-1 How to set SELINUX mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3-2 How to set repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3-3 yum repolist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3-4 powervc installation command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3-5 Accept the agreement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3-6 installing powervc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3-7 installation completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3-8 How to install linux in NPIV attachment of SAN volumes . . . . . . . . . . . . . 59
3-9 RSCT installation in Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4-1 Original scratchpad.txt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4-2 Edited scratchpad.txt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
4-3 Specific device names for the /etc/fstab file. . . . . . . . . . . . . . . . . . . . . 117
4-4 Default /etc/lilo.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
4-5 Specific devices names for the /etc/lilo.conf file. . . . . . . . . . . . . . . . 117
4-6 Commands to enable activating engine on a previously captured VM . . 118
4-7 Output from the /opt/ibm/ae/AE.sh -R command. . . . . . . . . . . . . . . . . 118

8199LOE.fm Draft Document for Review November 20, 2013 5:11 pm
xvi IBM PowerVC Introduction and Configuration

Draft Document for Review November 20, 2013 5:11 pm 8199spec.fm
© Copyright IBM Corp. 2013. All rights reserved. xvii
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your
local IBM representative for information on the products and services currently available in your area. Any
reference to an IBM product, program, or service is not intended to state or imply that only that IBM product,
program, or service may be used. Any functionally equivalent product, program, or service that does not infringe
any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and
verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The
furnishing of this document does not grant you any license to these patents. You can send license inquiries, in
writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of
express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new editions of the publication. IBM may make
improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time
without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in any
manner serve as an endorsement of those websites. The materials at those websites are not part of the materials
for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any
obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore, the results
obtained in other operating environments may vary significantly. Some measurements may have been made on
development-level systems and there is no guarantee that these measurements will be the same on generally
available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual
results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm the
accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them as
completely as possible, the examples include the names of individuals, companies, brands, and products. All of
these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is
entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any
form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs
conforming to the application programming interface for the operating platform for which the sample programs are
written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample
programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing
application programs conforming to IBM's application programming interfaces.

8199spec.fm Draft Document for Review November 20, 2013 5:11 pm
xviii IBM PowerVC Introduction and Configuration
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corporation in the United States, other countries, or both. These and other IBM trademarked
terms are marked on their first occurrence in this information with the appropriate symbol (® or ™),
indicating US registered or common law trademarks owned by IBM at the time this information was
published. Such trademarks may also be registered or common law trademarks in other countries. A current
list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
AIX®
DB2®
Express Storage™
IBM®
IBM Flex System™
IBM SmartCloud®
POWER®
Power Architecture®
Power Systems™
POWER6®
POWER6+™
POWER7®
POWER7+™
PowerLinux™
PowerVM®
PureFlex™
Redbooks®
Redbooks (logo) ®
Storwize®
System Storage®
System x®
System z®
The following terms are trademarks of other companies:
Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel
Corporation or its subsidiaries in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Java, and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its
affiliates.
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. 2013. All rights reserved. xix
Draft Document for Review November 20, 2013 5:11 pm 8199pref.fm
Preface
IBM PowerVC is an advanced enterprise virtualization management offering for
IBM Power Systems based on the OpenStack technology. This IBM®
Redbooks® publication will introduce and position IBM Power Virtualization
Center and will help you understand its positioning, planning, installation, and
setup.
IBM PowerVC is available in two editions, Express Edition to manage small
deployments through IVM and Standard Edition to manage larger deployments
through the HMC. IBM PowerVC can manage Linux on Power and AIX, running
on POWER hardware including Flex System POWER compute nodes.
PowerVC editions include the following features and benefits:
򐂰 Virtual Image capture, deployment, and management
򐂰 Policy-based Virtual Machine (VM) placement to improve utilization
򐂰 Targeted VM placement for deployment to reduce complexity
򐂰 Managing real-time optimization and VM resilience to increase productivity
򐂰 VM Mobility with placement policies to reduce burden on IT staff in a
simple-to-install and easy-to-use GUI
򐂰 An open and extensible PowerVM management system that enables you to
adapt as you need and runs in parallel with existing infrastructure, preserving
your investment
򐂰 A management system that manages existing PowerVM deployments
You will also find all the details on how we set up the lab environment used in this
book.
This IBM Redbooks publication is intended for experienced IBM PowerVM® and
other virtualization solutions users wanting to understand and implement the next
generation of enterprise virtualization management for Power Systems™.
Authors
This book was produced by a team of specialists from around the world working
at the International Technical Support Organization, Poughkeepsie Center.
Guillermo Corti is an IT specialist at IBM Argentina. He has been with IBM since
2004, with a 20 years technical background on Power Systems and AIX®. He
has a degree in Systems from Moron University. He also has 10 years

8199pref.fm Draft Document for Review November 20, 2013 5:11 pm
xx IBM PowerVC Introduction and Configuration
experience working in service delivery on AIX, Virtual I/O Server, and HMC for
North American accounts.
Sylvain Delabarre is a certified IT Specialist at the IBM Client and Power
Systems Linux center in Montpellier, France. He has been with IBM France since
1988. He works as a Power Systems Benchmark Specialist since 2010. He also
has 20 years of AIX System Administration and Power Systems experience
working in service delivery, AIX, Virtual I/O Server, and HMC support for EMEA.
Ho Jin Kim is a senior Power Systems System Service Representative in IBM
Korea. He has been with IBM since 2001. He has a Master degree in
Management Information Sciences from Hankook University of Foreign Studies.
And he has supported Finance Sector accounts for 7 years. He is a Red Hat
Certified Engineer, and His areas of expertise include Power Systems solutions,
PowerLinux™, AIX, and PowerVM.
Ondrej Plachy is an IT System Engineer in Comparex CZ, s.r.o. He has 18 years
of experience in the UNIX and storage systems. He holds the Ing. academic
degree in computer science from Czech Technical University (CVUT), Prague.
He has worked at IBM for nine years in the IBM AIX software services team.
Now, he is responsible for HA, DR project design, implementation, and support of
large-scale datacenter computer systems in Comparex company. Comparex is
IBM business partner in Czech Republic.
Marcos Quezada is a Consulting I/T Specialist at IBM Global Techline. He is an
IBM Level II Certified I/T Specialist with 15 years of I/T experience performing on
several related positions as a Brand Development Manager and IT Specialist for
the UNIX sector. He holds a degree in Systems Engineering from Fundación
Universidad de Belgrano. His areas of expertise include Product Branding,
Competition, Distribution, Marketing Strategy and Channel Enablement. As a
Consulting I/T Specialist he leads IBM teams in promoting the cause of I/T, and
of POWER® Architecture technologies, in order to achieve buy-in from client's
management and I/T communities. He consults on virtualization, cloud
computing, high availability, software defined environment solutions and other IT
infrastructure offerings running on IBM UNIX Systems.
Gustavo Santos is an IT Architect at IBM Delivery Center Argentina. He has
been with IBM since 1997. He has 17 years of experience in Power Systems and
Unix field. He holds a degree in Systems Engineering from Universidad Abierta
Interamericana. He also has 15 years experience working in service delivery on
AIX, Virtual I/O Server, and HMC for multiple accounts in US and LA. His areas
of expertise include Power Systems, AIX, Virtual I/O Server and Unix.
Thanks to the following people for their contributions to this project:

Preface xxi
Draft Document for Review November 20, 2013 5:11 pm 8199pref.fm
Dave Archer, Senthil Bakthavachalam, David Bennin, Eric Brown, Rich Conway,
Joe Cropper, Rishika Kedia, Yan Koyfman, Samuel D Matzek, John R Niemi,
Geraint North, Atul Patel, Jeff Tenner, Drew Thorstensen, and
Ramesh Veeramala.
International Technical Support Organization, Poughkeepsie Center
Now you can become a published author, too!
Here’s an opportunity to spotlight your skills, grow your career, and become a
published author—all at the same time! Join an ITSO residency project and help
write a book in your area of expertise, while honing your experience using
leading-edge technologies. Your efforts will help to increase product acceptance
and customer satisfaction, as you expand your network of technical contacts and
relationships. Residencies run from two to six weeks in length, and you can
participate either in person or as a remote resident working from your home
base.
Find out more about the residency program, browse the residency index, and
apply online at:
ibm.com/redbooks/residencies.html
Comments welcome
Your comments are important to us!
We want our books to be as helpful as possible. Send us your comments about
this book or other IBM Redbooks publications in one of the following ways:
򐂰 Use the online Contact us review Redbooks form found at:
ibm.com/redbooks
򐂰 Send your comments in an email to:
redbooks@us.ibm.com
򐂰 Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099
2455 South Road
Poughkeepsie, NY 12601-5400

8199pref.fm Draft Document for Review November 20, 2013 5:11 pm
xxii IBM PowerVC Introduction and Configuration
Stay connected to IBM Redbooks
򐂰 Find us on Facebook:
http://www.facebook.com/IBMRedbooks
򐂰 Follow us on Twitter:
http://twitter.com/ibmredbooks
򐂰 Look for us on LinkedIn:
http://www.linkedin.com/groups?home=&gid=2130806
򐂰 Explore new Redbooks publications, residencies, and workshops with the
IBM Redbooks weekly newsletter:
https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm
򐂰 Stay current on recent Redbooks publications with RSS Feeds:
http://www.redbooks.ibm.com/rss.html

© Copyright IBM Corp. 2013. All rights reserved. 1
Draft Document for Review November 20, 2013 5:11 pm 8199ch01.fm
Chapter 1. Introduction
IBM PowerVC is the next generation of enterprise virtualization management for
Power Systems. With a powerful yet simple and intuitive graphical user interface
(GUI) and a deep integration with IBM PowerVM virtualization technologies, IBM
PowerVC enables virtualization without limits for the Power Systems family of
servers running PowerLinux, IBM AIX and IBM i operating systems.
Before you continue you should be familiar and have some practical experience
with the contents included in the following IBM Redbooks publications: IBM
PowerVM Virtualization Introduction and Configuration, SG24-7940, and IBM
PowerVM Virtualization Managing and Monitoring, SG24-7590.
This book provides introduction and configuration information on IBM PowerVC.
You can go through the pages starting right here or just jump to whatever is that
you are interested in. The following is a list of chapters describing IBM PowerVC
overview, positioning, planning, installation, and setup, including a lab
environment installation of the product:
򐂰 IBM PowerVC overview
򐂰 IBM PowerVC positioning and planning
򐂰 IBM PowerVC installation
򐂰 IBM PowerVC setup
1

8199ch01.fm Draft Document for Review November 20, 2013 5:11 pm
2 IBM PowerVC Introduction and Configuration
Note: IBM plans to support IBM Power Virtualization Center (PowerVC) to
manage systems running the IBM i operating system.

Chapter 1. Introduction 3
1.1 IBM PowerVC overview
IBM Power Virtualization Center (PowerVC) is designed to simplify the
management of virtual resources in your Power Systems environment.
Once the product code is laid out, IBM PowerVC’s no-menus interface will guide
you through three simple configuration steps to register physical hosts, storage
providers, and network resources to start capturing and intelligently deploying
your virtual machines among other tasks shown in the following list:
򐂰 Create virtual machines and then resize and attach volumes to them.
򐂰 Import existing virtual machines and volumes so they can be managed by
IBM PowerVC.
򐂰 Monitor the utilization of the resources that are in your environment.
򐂰 Migrate virtual machines while they are running (hot migration).
򐂰 Deploy images quickly to create new virtual machines that meet the demands
of your ever-changing business needs.
IBM PowerVC is built on OpenStack. OpenStack is an open source software that
controls large pools of server, storage, and networking resources throughout a
datacenter. IBM PowerVC leverages IBM Platform Enterprise Grid Orchestrator
(EGO) to extend OpenStack set of technologies into Power Systems
environments with enhanced security, intelligent placement of virtual machines
and other advanced policy-based features required on enterprise clouds.
EGO is a proven technology used in Grid and scaled out environments by over
2000 clients. Its open, extensible architecture supports policies such as
reservations, energy-aware, and over-subscription, as well as user-defined
policies.
IBM PowerVC is available in two editions: IBM Power Virtualization Center
Express Edition and IBM Power Virtualization Center Standard Edition.
Figure 1-1 on page 4 shows a graphic representation for IBM Power
Virtualization Center technology overview.

Figure 1-1 IBM PowerVC technology overview
1.2 IBM PowerVC Express Edition
IBM PowerVC Express Edition is intended for entry environments where virtual
machine hosts are POWER7® and POWER7+™ based IBM Power Systems
Express servers managed by the Integrated Virtualization Manager (IVM).
As a result only a single Virtual I/O Server per host is supported to access
storage that can be deployed as storage area networks, local storage or a
combination. Supported hardware include:
򐂰 IBM Storwize® V3700
򐂰 IBM Storwize V7000
򐂰 IBM SAN Volume Controller
򐂰 IBM Integrated Virtualization Manager local storage
P ower SSP*
PowerVCSystem Admin Console
Nova API Cinder API Quantum API Keystone API Glance API
AMQP
Message Broker
QPID
Scheduler
Platform EGO
Policy Engine
Security Devices Image Registry
Data
Management
Servers
Allocations
Images
User/Roles
/etc/config
Nova Compute
HMC Driver
Nova Compute
IVM Driver
Quantum Service
Cinder Drivers
Cinder Drivers
HMC
Power Systems
PowerVM
VM
Power Sys tems
Power VM
Power Sy stems
PowerVM
Networ k
EMC*
SVC
SAN Switch
REST
REST
AMQP AMQP
VM
VM
V
M
V
M
VM
CLI
Controlling
System
Managed
System
Resource Managers Kernel Applications *Planned
Key

1.3 IBM PowerVC Standard Edition
IBM PowerVC is available in two editions: IBM Power Virtualization Center
Express Edition and IBM Power Virtualization Center Standard Edition.
IBM PowerVC Standard Edition is aimed for enterprise class virtualization
environments where virtual machine hosts are POWER6®, POWER7 and
POWER7+ based IBM Power Systems servers managed by the Hardware
Management Console.
Dual Virtual I/O Server per host are supported to access storage and network.
Virtual machines can also use NPIV attached storage. Supported hardware
include:
򐂰 IBM SAN Volume Controller
1.4 OpenStack Overview
PowerVC is based on the OpenStack initiative. Before we actually go into the
heart and details of PowerVC, we would like to provide a high level of
understanding about OpenStack.
1.4.1 The OpenStack foundation
OpenStack is an Infrastructure as a Service (IaaS) solution applied to the cloud
computing domain, lead by the OpenStack Foundation.
The OpenStack Foundation is a non-commercial organization, which purpose is
to promote the OpenStack project and, help the developers within the OpenStack
community.
Many major information technology companies and actors do contribute to the
OpenStack Foundation.
You can find further information about the OpenStack foundation at:
http://www.openstack.org/foundation/
IBM is a major actor in the OpenStack community. Multiple IBM divisions have a
key role as a member of the OpenStack Foundation.

IBM contributes on a large number of levels to the OpenStack ecosystem and
projects via code contributions, governance and support within its products.
OpenStack is a free and open-source software released under the terms of the
Apache License.
1.4.2 OpenStack projects
OpenStack has a modular architecture based on various components and
projects. The current major components listed below are part of a non fixed and
continuously extending list. The major projects for OpenStack are listed below.
Nova Manages the lifecycle and operations of hosts and compute
resources.
Swift This is the OpenStack project for object oriented storage. It is
meant for distributed and high availability in virtual containers.
Cinder This is the project for the management for block storage within
OpenStack (Such as Storwize or San Virtual Controller in the IBM
storage offering).
Glance Is the image service which provides discovery, registration, and
delivery services for virtual disk images.
Horizon Dashboard project, Horizon is the web service management and
user interface to integrate the various OpenStack services.
Neutron Neutron is the network management service for OpenStack.
Formerly named Quantum, Neutron includes various aspects such
has IP addresses management.
You can find a complete description of the main OpenStack projects on:
https://wiki.openstack.org/wiki/Main_Page
Other very important projects from OpenStack implemented in PowerVC are
listed below.
Keystone Security, identity, and authentication services.
ceilometer The ceilometer project is meant for metering, to provide
measurement and billing across all OpenStack components.

Figure 1-2 is an outlook of the OpenStack framework and main components.
Figure 1-2 Openstack framework
Nova (Compute)
Glance (Image Service)
APIs
OpenStack Shared Services
HARDWARE
Applications
Horizon
(Dashboard)
Neutron (Networking)
Swift (Object Storage)
Cinder (Block Storage)

© Copyright IBM Corp. 2013. All rights reserved. 9
Chapter 2. Plan
2.1 PowerVC positioning
Why IBM PowerVC? Why is there another virtualization management offering?
When more than 70% of IT budgets are spent on operations and maintenance,
there are must be new development efforts to reduce this cost and unleash
innovation within IT departments around the world.
IBM is introducing Power Virtualization Center to give Power Systems customers
out of the box virtualization management that accepts most all pre-existing
virtualization configurations as the starting point.
IBM PowerVC joins the PowerVM set of enterprise virtualization technologies to
provide a virtualization management solution that is deeply integrated with Power
Systems, is based on open standards and will be the building block of IBM
Infrastructure as a Service offerings based on Power Systems.
IBM Power Virtualization Center sits right between the Hardware Management
Console and IBM SmartCloud® Infrastructure as a Service (IaaS) offerings, to
provide a systems management product that our enterprise customers require to
effectively manage the advanced features offered by our premium hardware,
drive up resource utilization and manage workloads for performance and
availability.
2

Table 2-1 shows the ultimate set of platform and virtualization management
solutions for Power Systems used as the foundation for IBM SmartCloud
solutions that integrate PowerVM.
Table 2-1 Power Systems Virtualization Management Solutions
2.2 IBM Power Virtualization Center requirements
In this section we describe the hardware and software necessary for the IBM
Power Virtualization Center on UNIX AIX and LINUX platforms.
The following are key prerequisites for IBM Power Virtualization Center
installation and configuration.
򐂰 PowerVM Standard edition (5765-PVS); basic function
򐂰 PowerVM Enterprise edition (5765-PVE); full function
IBM PowerVC will be available as two editions, Express and Standard. Express
will support IVM managed hosts for small deployments and Standard will support
Offering Solution Functions
SmartCloud Cloud management End-user self-service provisioning
Service catalog with virtual systems and
applications
Subscriber and account management
(multi-tenancy)
Delivered as IBM SmartCloud Entry, IBM
SmartCloud Provisioning and IBM
SmartCloud Orchestrator solutions
PowerVC Power Systems
virtualization management
Leadership solution for PowerVM
Intelligent virtual image management
and deployment
Resource pooling and dynamic virtual
management placement
On-going optimization and virtual
machine resilience
HMC Power Systems platform
management
PowerVM configuration and
virtualization setup
Hardware and firmware configuration
and controls
Service, support and update
management

Chapter 2. Plan 11
HMC managed hosts for larger deployments. IBM PowerVC can manage Linux
on Power and AIX, running on Power hardware including Flex System POWER
compute nodes. IBM PowerVC (version 1.2.0) does not allow management of
IVM and HMC managed hosts in a single installation.
2.2.1 Hardware and software requirements
We describe the hardware and software and minimum requirements for the IBM
Power Virtualization Center Express and Standard Editions.
2.2.2 IBM Power Virtualization Center Express.
The following information provides a consolidated view of the hardware and
software requirements for your IBM Power Virtualization Center Express
environment.
IBM PowerVC management and managed hosts
Table 2-2 and Table 2-3 on page 12 describe the hardware, software and
minimum requirements for IBM PowerVC Express edition.
Table 2-2 Hardware and OS requirements for IBM PowerVC Express
Host type Supported hardware Supported Operating
Systems (OS)
IBM PowerVC
management host
IBM Power
processor-based models:
򐂰 IBM PowerLinux 7R1
and 7R2 servers IBM
POWER7 and
POWER7+ servers.
򐂰 IBM System x®
servers that meet the
following minimum
requirements:
Processors - Intel or
AMD x64 processors
with 2 or more logical
cores and a speed of 2
Gigahertz. Memory -
10 Gigabytes. Hard
disk - 40 Gigabytes.
Red Hat Enterprise Linux
(RHEL), version 6.4 for
IBM Power or x86_64.

Table 2-3 Minimum resource requirements for the IBM PowerVC virtual machine
In addition, all hosts need to have Fibre Channel cards that are suitable for
connecting to the SAN switches.
Virtualization platform
Table 2-4 on page 13 includes the virtualization platform version requirement for
IBM PowerVC Express edition.
Managed hosts IBM PowerLinux 7R1 and
7R2 servers. IBM
POWER7 and POWER7+
servers.
Notes: The hosts you
manage should be IBM
PowerLinux, POWER6, or
POWER7 and POWER7+
models and not a
combination.
򐂰 Red Hat Enterprise
Linux 5.9 and 6.4
򐂰 SUSE Linux Enterprise
Server (SLES), version
11 SP3
򐂰 AIX, version 6.1 TL9
and AIX 7.1 TL3
System resource Amount
Processors Minimum: An uncapped shared processor
virtual machine with 1.0 processor unit of
entitled processing capacity and 2 virtual
processors. Recommended (one of the
following): An uncapped shared processor
virtual machine with a minimum of 2.0
processor units of entitled processing
capacity and 2 virtual processors. A virtual
machine with 2 dedicated processors.
Memory 10 Gigabytes
Hard disk 40 Gigabytes if you are using SAN storage
60 Gigabytes if you are using local storage
Tip: You must temporarily store ISO images before you import them into IBM PowerVC.
If you plan to store them temporarily on your IBM PowerVC virtual machine, then you
may need to create the virtual machine with more than the minimum 40 or 60 GB of hard
disk space. Choose the size based on the number and size of the ISO images that you
plan to import.
Host type Supported hardware Supported Operating
Systems (OS)

Chapter 2. Plan 13
Table 2-4 Supported virtualization platforms for IBM PowerVC
Network resources
Table 2-5 describes the network infrastructure supported by IBM PowerVC
Express edition.
Table 2-5 IBM PowerVC-supported network hardware and software
Storage providers
Table 2-6 shows hardware supported by IBM powerVC Express edition.
Table 2-6 IBM PowerVC-supported storage hardware
2.2.3 IBM Power Virtualization Center Standard
The following information provides a consolidated view of the hardware and
software requirements for IBM Power Virtualization Center Standard version.
Any IBM system that includes an IBM POWER6, POWER7, or POWER7+
processor on a Power Server or PureFlex™ Foundation (build to order) that is
managed through HMC.
Platform Requirement
Virtual I/O Server (VIOS) Version 2.2.2.1 or later
Item Requirement
Network switches that are supported by
IBM PowerVC
Any entry-level IBM or Cisco switch that
supports VLAN tagging
Note: IBM PowerVC does not manage network switches.
Item Requirement
Storage systems that can be managed by
IBM PowerVC.
Version 6.4 or higher of IBM Storwize
V3500 (China only), V3700, and V7000,
and SAN Volume Controller (SVC).
Storage area network (SAN) switches that
are supported by IBM PowerVC
IBM System Networking SAN24B-5
Note: IBM PowerVC Express Edition does not manage network switches, but supports
network configurations that use VLAN-capable switches. Standard Edition supports
management of SAN switches.

IBM PowerVC management and managed hosts
Table 2-7 and Table 2-8 on page 15 describe the hardware, software, and
minimum requirements for IBM PowerVC Standard edition.
Table 2-7 Hardware and operating system support for IBM PowerVC hosts
Host type Supported hardware Supported operating
systems
IBM PowerVC
management host
IBM Power
processor-based models:
򐂰 IBM POWER7 and
POWER7+
processor-based
blades.
򐂰 IBM Flex System™
Power Architecture®
compute nodes.
򐂰 IBM System x servers
that meet the following
minimum
requirements:
Processors: Intel or
AMD x64 processors
with 2 or more logical
cores and a speed of 2
Gigahertz.
Memory: 10
Gigabytes.
Hard disk: 40
Gigabytes.
Red Hat Enterprise Linux
(RHEL), version 6.4 for
IBM Power or x86_64
Managed hosts 򐂰 IBM POWER6,
POWER6+™,
POWER7, and
POWER7+
processor-based
servers.
򐂰 IBM POWER6 and
POWER7
processor-based
blades. IBM Flex
System Power
Architecture compute
nodes.
򐂰 Red Hat Enterprise
Linux5.9 and 6.4
򐂰 SUSE Linux Enterprise
Server (SLES), version
11SP3
򐂰 AIX, version 6.1 TL9
and 7.1 TL3
Tip: The IBM PowerVC management host will recommend to have at least
200 Maximum Virtual Adapters configured on each VIO server.

Chapter 2. Plan 15
Table 2-8 Minimum resource requirements for the IBM PowerVC virtual machine
Hardware Management Console
Table 2-9 shows HMC version and release requirements to support IBM
PowerVC standard edition.
Table 2-9 HMC requirements
Virtualization platform
Table 2-10 includes Virtual I/O version requirement for IBM PowerVC Standard
edition.
Table 2-10 Supported virtualization platforms
Network resources
Table 2-11 on page 16 describes the network infrastructure supported by IBM
PowerVC Standard edition.
System resource Power Systems System x
Processors Minimum: An uncapped
shared processor virtual
machine with 1.0
processor unit of entitled
processing capacity and 2
virtual processors.
Recommended (one of the
following): An uncapped
shared processor virtual
machine with a minimum of
2.0 processor units of
entitled processing
capacity and 2 virtual
processors. A virtual
machine with 2 dedicated
processors.
Intel or AMD x64 with two
or more logical cores each
with a speed of 2
Gigahertz.
Memory 10 Gigabytes 10 Gigabytes
Hard disk 40 Gigabytes 40 Gigabytes
Item Requirement
Software level Version 7.7.8 or later
Platform Requirement
Virtual I/O Server (VIOS) Version 2.2.3 or later

Table 2-11 Supported network hardware and software
Storage providers
Table 2-12 shows hardware supported by IBM PowerVC Standard edition.
Table 2-12 Supported storage hardware
Security
Table 2-13 includes security features supported.
Table 2-13 Supported security software
2.2.4 Planning Information
Direct customer support
For technical support or assistance, contact your IBM representative or visit
http://www.ibm.com/support
Item Requirement
Network switches IBM PowerVC does not manage network
switches, but supports network
configurations that use VLAN-capable
switches.
Virtual networks Supports Shared Ethernet Adapters for
virtual machine networking
Item Requirement
Storage systems Version 6.4 or higher of IBM Storwize
V3500 (China only), V3700, V7000, and
SAN Volume Controller (SVC).
Storage area network (SAN) switches Can manage the IBM System Networking
SAN24B-5 and SAN48B-5 switches.
Attachments NPIV-capable Fibre Channel - required for
storage controllers.iSCSI is not
supported.
Item Requirement
Lightweight Directory Access Protocol
(LDAP) server (optional).
All versions of OpenLDAP

Chapter 2. Plan 17
Packaging
The IBM PowerVC Standard and Express Editions contain DVD that include
product installation documentation and files. Your Proof of Entitlement (PoE) for
this program is a copy of a paid sales receipt, purchase order, invoice, or other
sales record from IBM or its authorized reseller from whom you acquired the
program, provided that it states the license charge unit (the characteristics of
intended use of the program, number of processors, number of users) and
quantity acquired.
Software Maintenance
This software license offers Software Maintenance, previously referred to as
Software Subscription and Technical Support.
Processor core (or processor)
Processor Core (or Processor) is a unit of measure by which the program can be
licensed. Processor Core (or Processor) is a functional unit within a computing
device that interprets and executes instructions. A processor core consists of at
least an instruction control unit and one or more arithmetic or logic unit. With
multi core technology, each core is considered a Processor Core. Entitlements
must be acquired for all activated Processor Cores available for use on the
server.
In addition to the entitlements required for the program directly, licensee must
obtain entitlements for this program sufficient to cover the processor cores
managed by program.
A Proof of Entitlement (PoE) must be acquired for all activated processor cores
available for use on the server. Authorization for the IBM PowerVC Express &
Standard Editions program is based on the total number of activated processors
on the machines running the program and the activated processors on the
machines being managed by the program.
Licensing
IBM International Program License Agreement including the License Information
document and Proof of Entitlement (PoE) govern your use of the program. PoEs
are required for all authorized use.
This software license includes Software Subscription and Support (also referred
to as Software Maintenance).

2.3 IBM PowerVC Storage Access Planning
To plan for configuration of SAN and storage in IBM PowerVC, the following initial
steps has to be done:
򐂰 Configuration of the Fibre Channel fabric for the IBM PowerVC environment
should be planned first - cable attachment, SAN fabrics, redundancy. Best
practice would be to create at least two independent fabrics to provide best
redundancy.
򐂰 All Virtual I/O Servers that will be managed by IBM PowerVC will provide
shared storage base for Virtual Machines. In IBM PowerVC Standard, the
storage is accessed via NPIV. In IBM PowerVC Express, the storage access
is by vSCSI LUN mapping.
򐂰 In IBM PowerVC Standard, it is possible to further distinguish by which
particular Fibre Channel ports will Virtual I/O Servers access Storage
Controllers. Proper cable connections to individual fabrics should be in place.
򐂰 Plan for initial configuration for the SAN switches. Administrator user ID and
password should be setup to be used by IBM PowerVC.
򐂰 Plan for initial configuration of the storage controller. This configuration
includes setting up user authentication and creating volumes for first Virtual
Machines.
򐂰 In IBM PowerVC Express, initial zoning should be in place to provide access
from Virtual I/O Servers to Storage Controllers.
򐂰 In IBM PowerVC Standard, initial setup for first VM should be in place. The
preparation steps involve:
– Virtual I/O Server must be setup for NPIV to provide virtual FC access
from VM to the SAN (vfcmap command in Virtual I/O Server).
– SAN zoning to provide access from virtual FC ports in VM to Storage
Controllers must be prepared.
– First LUN for successful installation of OS in the first VM (that will be later
on-boarded to IBM PowerVC Standard) must be prepared on Storage and
masked to virtual FC ports in VM.
With access to storage controllers and switches, IBM PowerVC Standard does
the following:
򐂰 collect inventory on fibre channel fabric
򐂰 collect inventory on storage devices (pools, volumes)
򐂰 monitor for health
򐂰 detect misconfigurations

Chapter 2. Plan 19
򐂰 manage zoning
򐂰 manage LUNs on storage devices
򐂰 manage masking of LUNs on storage devices
򐂰 manage snapshots on storage devices
򐂰 manage LUN copy operations on storage devices
IBM PowerVC Express manages Storage Controllers but does not manage SAN
switches.
Storage access in IBM PowerVC Express
The following Figure 2-1 on page 20 shows how VMs in IBM PowerVC Express
access storage. IBM PowerVC Express uses vSCSI for access to storage.
A description of the flow of storage management from physical Storage LUNs to
VMs in IBM PowerVC Express follows:
򐂰 LUNs are provisioned on a supported Storage Controller
򐂰 LUNs are masked to IVM Fibre Channel ports and are discovered as hdisk
logical devices in IVM
򐂰 LUNs are mapped (mkvdev) from IVM to VMs over vSCSI virtual adapter pair

These steps are done automatically by IBM PowerVC Express. No zoning is
involved, because individual VM do not access physical LUNs directly over SAN.
Figure 2-1 IBM PowerVC Express Storage™ Access
Storage access in IBM PowerVC Standard
The following Figure 2-2 on page 21 shows how VMs in IBM PowerVC Standard
access storage.
A description of the flow of storage management from physical Storage LUNs to
VMs in IBM PowerVC Standard follows:
򐂰 access to SAN from VMs is configured on Virtual I/O Servers using FC
adapter pair and NPIV (vfcmap)
򐂰 LUNs are provisioned on a supported Storage Controller
򐂰 LUNs are masked to VMs virtual Fibre Channel ports
򐂰 SAN zoning is adjusted so that VMs have access from their virtual FC ports to
Storage Controller host ports. Changes in zoning are done automatically by
IBM PowerVC Standard, because individual VM access physical LUNs
directly over SAN.
IBM PowerVC Express
SAN
IVM (VIOS)
AIX
Linux
Storage
vSCSI
vSCSI
IBM Power Server
PowerVC Express
manages IVM and Storage
PowerVC Express
instructs IVM
to map LUNs to VMs
by vSCSI
Zoning must be
done manualy,
zones are:
Storage host ports
to VIOS FC ports
PowerVC Express
manages LUNs and LUN
masking on storage,
LUNs are masked to VIOS
FC ports

Chapter 2. Plan 21
򐂰 LUNs and are discovered as logical devices in VMs
These steps are done automatically by IBM PowerVC Standard.
Figure 2-2 IBM PowerVC Standard Storage Access
2.3.1 Storage Connectivity Groups and Tags in IBM PowerVC
Standard
IBM PowerVC Standard uses Storage Connectivity Groups and Tags. IBM
PowerVC Express does not include concept of connectivity groups and tags.
Storage Connectivity Groups
A Storage Connectivity Group is a set of Virtual I/O Servers that have access to
the same storage controllers. It can span several host systems in IBM Power
Server landscape managed by IBM PowerVC Standard.
When a new Virtual Machine is deployed from an image, a Storage Connectivity
Group must be specified and the Virtual Machine will belong to that Storage
Connectivity Group. A virtual machine can be deployed only to IBM Power
IBM PowerVC Standard
Brocade SAN
AIX/Linux
Storage
Virtual FC
HMC
IBM Power Server
VIOS 2
Virtual FC
VIOS 1
PowerVC Standard
manages Storage, SAN
and VIOSes (via HMC)
PowerVC Standard
instructs VIOS
to map virtual FC
to VMs (NPIV),
dual VIOS configuration
is supported
PowerVC Standard
manages SAN zoning
zones are:
Storage host ports
to VM virtual FC ports
(N PIV)
PowerVC Standard
manages LUNs and LUN
masking on storage,
LUNs are masked directly
to VM

Systems hosts that contain at least one Virtual I/O Server that is part of the
storage connectivity group. In another words, by using specific SCG, it is
determined which hosts (through its Virtual I/O Servers) are eligible to deploy the
Virtual Machine.
Also a Virtual Machine migrate operation is only supported within the specified
storage connectivity group. IBM PowerVC will ensure that the source and
destination servers have access to the required storage controllers and LUNs.
The Figure 2-3 shows an overview of Storage Connectivity Group (SCG)
technology. It shows two IBM Power System servers each with three Virtual I/O
Servers. Two Virtual I/O Servers from each server are part of Production SCG
and one Virtual I/O Server from each server is part of Development SCG.
Figure 2-3 Storage Connectivity Groups
Storage Port Tags
A further concept in IBM PowerVC Standard - Storage Port Tags - allows
arbitrary tags to be placed on fibre channel ports. A storage connectivity group
can be configured to connect only through Fibre Channel ports with a specific
tag.
IBM Power Systems Server A
Hypervisor
VM1 VM2 VM3
vSCSI
vSCSI
IBM Power Systems Server B
Hypervisor
VM4 VM5 VM6
vSCSI
vSCSI
Production
VIOS A2
VIOS A1
FC FC FC FC
Production
VIOS B2
VIOS B1
FC FC FC FC
Dev
VIOS A3
FC FC
Dev
VIOS B3
FC FC
Redundant
production SAN Development SAN
Production SCG
Development
SCG

Chapter 2. Plan 23
You can also specify which fabric each port is connected to a specific SAN fabric
by assigning a tag such name that will be the same as fabric name or purpose
(for example Production1, Production2, Development_locality, etc.).
The following Figure 2-4 shows possible usage of tags. There are two IBM Power
System servers, each having two Virtual I/O Servers. Each Virtual I/O Server has
three Fibre Channel ports. First two FC ports are tagged ProductionSCG and are
connected to redundant production SAN, the third port is tagged DevelopmentSCG
and is connected to development SAN. Client Virtual Machines that belong to
both Storage Configuration Groups (ProductionSCG and DevelopmentSCG)
share the same Virtual I/O Servers but do not share Fibre Channel ports.
Figure 2-4 Storage Connectivity Groups And Tags
The Virtual I/O Servers in a storage connectivity group provide storage
connectivity to a set of Virtual Machines that have common requirements. An
administrator can use several approaches to configure Storage Connectivity
Groups, the Figure 2-5 on page 24 shows possible scenarios:
򐂰 Uniform - all Virtual Machines use all Virtual I/O Server servers and all Fibre
Channel ports
IBM Power Systems Server A
Hypervisor
VM1 VM2 VM3
vSCSI
vSCSI
VIOS A1
FC FC FC
Redundant
production SAN Development SAN
VIOS A2
FC FC FC
IBM Power Systems Server B
Hypervisor
VM4 VM5 VM6
vSCSI
vSCSI
VIOS B1
FC FC FC
VIOS B2
FC FC FC
Development
SCG
Production
SC G

򐂰 Virtual I/O Server segregation - different groups of different Virtual Machines
use different sets of Virtual I/O Servers but all Fibre Channel ports on that
Virtual I/O Server.
򐂰 Port segregation - different groups of different Virtual Machines use all Virtual
I/O Servers but different Fibre Channel ports according to tags on those
ports.
򐂰 Combination of Virtual I/O Server and Port segregation - different groups of
different Virtual Machines use different sets of Virtual I/O Servers and
different Fibre Channel ports according to tags on those ports.
Figure 2-5 Examples of Storage Groups Deployments
In IBM PowerVC Standard, there is always one default storage connectivity
group. The default group, Default Connectivity to All Registered SANs, includes
every Virtual I/O Server and all FC ports. This group can be disabled, but not
deleted.
IBM Power Systems Server
VM1 VM2 VM3
vSCSI
VIOS 1
FC FC FC
VIOS 2
FC FC FC
VM1 VM2 VM3
vSCSI
VIOS 1
FC FC FC
VIOS 2
FC FC FC
VIOS 3
FC FC FC
Production SCG Production SCG Dev SCG
VM1 VM2 VM3
vSCSI
FC
VIOS 2
FC FC FC
Production SCG
Dev SCG
VIOS 1
FC
FC FC
VM1 VM2 VM3
VIOS 3
FC FC FC
Dev SCG
vSCSI
VIOS 1
FC FC FC FC
Production 1 SCG
vSCSI
VIOS 2
FC FC FC FC
Production 2 SC G
Uniform VIOS Segregated
Port Segregated VIOS And Port Segregated

Chapter 2. Plan 25
2.3.2 Storage Templates
Storage template is a concept to provide administrator-defined storage
configuration to use when creating a new disk. Disk size is not part of the
template. Storage Template concept is the same in IBM PowerVC Standard and
IBM PowerVC Express. Here is the information that is included in a template:
򐂰 name of the storage template
򐂰 storage provider
򐂰 storage pool within storage provider
򐂰 thin or thick (full) allocation (full allocation can be chosen by selecting Generic
type of volume)
򐂰 If Thin Provisioned is selected, advanced settings will become available:
– Real capacity% of Virtual Capacity - determines how large space for the
volume will be allocated immediately after creating the volume.
– Automatically Expand - check box yes or no. Prevents the volume from
using up all of its capacity and going offline. As a thin-provisioned volume
uses more of its capacity, this feature maintains a fixed amount of unused
real capacity, called the contingency capacity.
– Warning threshold - when real capacity reaches given percentage of
virtual capacity a warning alert is sent.
– Thin provisioned grain size - Grain size can be selected in the range 32KB
to 256KB. Grain is a chunk used for allocating space. The grain size
affects the maximum virtual capacity for the volume. Generally, smaller
grain sizes save space but require more metadata access, which can
adversely impact performance. The default grain size is 256 KB, and is the
strongly recommended option. The grain size cannot be changed after the
thin-provisioned volume has been created. With grain size of 32KB, the
volume size cannot exceed 260,000 GB.
A storage template is then selectable during volume creation operations.

The following Figure 2-6 on page 26 shows a dialogue that will be presented to
an IBM PowerVC administrator when defining advanced settings during a
thin-provisioned storage template definition.
Figure 2-6 Storage Template definition - Advanced Settings
2.4 Users and groups planning
Default configuration for users and groups are managed by the operating system
and is reflected immediately in IBM PowerVC.

Chapter 2. Plan 27
2.4.1 Users management planning
When you install the IBM PowerVC, by default it is configured to use the security
features of the operating system on the management host. This configuration set
the root operating system user account as the only available account with access
to the PowerVC server.
System Administrator must create a new operating system user account to
replace root user account in IBM PowerVC management host configuration. For
more information about how to add, modify or remove users go to “Operating
system user account management” on page 27
The user account planning is important to define standard accounts. In addition
define the process and requirements to manage these accounts. IBM PowerVC
management host can manage users account using the operating system
security tools or can be configured to use the services provided by a Lightweight
Directory Access Protocol (LDAP)
Operating system user account management
Each user is added, modified or removed by the system administrator on the
operating system and becomes available in IBM PowerVC. It is accomplished
using the operating system commands.
Users managed by the operating system require some experience using
command lines but are easy to maintain. There is no dependency with other
server or service and the accounts are shown instantly in the IBM PowerVC
console.
Important: IBM PowerVC management host stores data in IBM DB2®. When
the installation of IBM PowerVC is complete, an operating system user
account is created for the main DB2 process to run under. This user account is
pwrvcdb. Do not remove or modify this user.

To see user accounts in the IBM PowerVC management hosts click on Users in
the upper black bar with the IBM logo, as shown in Figure 2-7 on page 28.
Figure 2-7 Users account view on the IBM PowerVC management host
System Administrator of IBM PowerVC management host must replace the
default root user account configuration. After that adding the new user account
to the admin group in the operating system and then removing root from this
group.
Adding users accounts with administrator role
To add a new user account to the operating systems on the IBM PowerVC
management host, run as root the command
useradd [options] login_name
Using the command shown in the Example 2-1 you create the user admin, with
/home/admin as the home and base directory, the viewer group as the main
group and a comment with additional information like “PowerVC”
Example 2-1 Adding admin user account with the useradd command
useradd -b /home/admin -c "PowerVC" -d /home/admin -g viewer -m
admin

Chapter 2. Plan 29
When the user is created, click on the Refresh button inside the Users tab on
the IBM PowerVC management host to see the changes, as shown in Figure 2-8
on page 29.
Figure 2-8 Refresh users account view on the IBM PowerVC management host

The new user is created with viewer role in the IBM PowerVC management host
because it is part of the viewer users group. Double click on the admin user
account to see detailed information, as shown in Figure 2-9.
Figure 2-9 Detailed user account information
Update users accounts
To update an user account in the operating systems on the IBM PowerVC
usermod [options] login_name
Using the command shown in the Example 2-2 you update the admin user
account. The new comment is “IBM Power VC admin user account” and you
move it at the same time to the admin users group
Example 2-2 Updating admin user account with the usermod command
usermod -c "IBM Power VC admin user account" -g admin admin
Note: The useradd command has more options. If you need more information
about the useradd command, please refer to the manual pages in your linux
distribution.

Chapter 2. Plan 31
After this modification is done the admin user account becomes part of the
admin user groups and can manage the IBM PowerVC management host, as
shown in Figure 2-10.
Figure 2-10 View updated user account information
Disable root user account
Remove the root user account from the admin users group in the IBM
management hosts. To do this run as root the command:
usermod -G root root
Remove users accounts
To remove an user account in the operating systems on the IBM PowerVC
userdel [options] login_name
Tip: You can use the Enabled check box to enable or to disable the user
account in the IBM PowerVC management console. This will not affect the
user account to log in to the systems using another method, like telnet or ssh.
Note: The usermod command has more options. If you need more information
about the usermod command, please refer to the manual pages in your linux
distribution

Using the command shown in the Example 2-3 you remove the admin user
account from the IBM PowerVC management hosts.
Example 2-3 Delete an user account
userdel -r admin
Lightweight Directory Access Protocol (LDAP)
LDAP is an open standard for accessing global or local directory services over a
network and/or the Internet. A directory can handle as much information as you
need but commonly is used to associate names with phone numbers and mail
addresses.
LDAP is a client server solution. The client request for information and the server
answers this requests. LDAP could be used as an authentication server. This
approach need more maintenance and another server to install and configure
LDAP.
IBM PowerVC can be configured to query an LDAP server for authentication
instead of operating system users accounts authentication
Selecting the authentication method
You should have to select the authentication method and plan the accounts
needed in advance. We recommend to use the operating system authentication
method to manage the users accounts. Most of the IBM PowerVC installations
can be managed using this method.
Use LDAP authentication method only if you already have an LDAP server
installed and configured and your domain is complete and accurate. Some
complex and large installation can be benefited using LDAP authentication
method. This is part of the security planning. IBM PowerVC do not require LDAP,
it is supported but not mandatory
Note: The userdel command has more options. If you need more information
about the userdel command, please refer to the manual pages in your linux
distribution
Link: For more information about OpenLDAP visit
(http://www.openldap.org/)

Chapter 2. Plan 33
2.4.2 Groups management planning
When you install IBM PowerVC, by default it is configured to use the security
features of the operating system on the management host. IBM PowerVC
includes three user groups with the following privileges:
admin
Users in this group can perform all tasks and have access to all
resources.
deployer
Users in this group can perform all tasks except the following:
• Adding, updating, or deleting storage systems
• Adding, updating, or deleting hosts
• Adding, updating, and deleting networks
• Viewing users and groups
viewer
Users in this group can view resources and the properties of resources,
but can not perform tasks. They cannot view the users and groups
properties.
The members of these groups are determined by the users who are in these
groups in the operating system on the management host. To add or remove
users from these groups, you must add or remove them on the operating system.
Any changes to the group are reflected in IBM PowerVC.

IBM PowerVC management host can display the user accounts belonging to
each group. To see this, log in to the IBM PowerVC management host and click
on Users on the upper black bar with the IBM logo, then click on the Groups tab.
See Figure 2-11 for reference.
Figure 2-11 Users groups view on the IBM PowerVC management host

Chapter 2. Plan 35
This view display the three defaults groups. To access detailed information for
each group, double click on the desired group. See Figure 2-12 on page 35 for
reference
Figure 2-12 Detailed view of viewer users group on management host
2.5 Security management planning
IBM Power Virtualization Center provides security services that support a secure
environment.
IBM Power Virtualization Center provides the following security services:
– LDAP support for authentication and authorization information (users and
groups).
– Apache HTTPD configured as the web server provides HTTPS support for
managing resources.
– Host key and certificate verification of Hosts, Storage, and Switches
– Commands to encrypt and decrypt passwords, tokens, audit records, and
other persisted strings.
– Audit logs are recorded and available

2.5.1 Ports used by IBM Power Virtualization Center
This topic lists the ports used by IBM PowerVC management hosts for inbound
and outbound traffic. This topic also lists the local ports used by IBM PowerVC
management host. The management host is configured during installation, and
the host should be reserved for IBM PowerVC and the operating system on
which it runs. No additional software should be installed on the management
host. When IBM PowerVC is installed, the installation opens ports 80 and 443 for
inbound and outbound traffic. If a firewall is configured on the management host
the installer change the firewall configuration to allow ports 80 and 443 access.
Table 2-14 displays the ports used by Apache Web Server.
Table 2-14 Ports used for inbound and outbound communication
Table 2-15 displays the ports used by the services running on the Hardware
Management Console, the Integrated Virtualization Manager and the Storage
Volume Controller.
Table 2-15 Ports used by HMC, IVM and SVC with IBM PowerVCt
Table 2-16 displays additional ports used by the services running on IBM
PowerVC management host.
Table 2-16 Additional ports used by IBM PowerVC to connect
Usage Port Protocol
Apache HTTPD Web Server 80 (optional) HTTP
Apache HTTPD Web Server 443 (required) HTTPS
Usage Port Protocol
IVM 22 SSL
SVC 22 SSL
HMC 12443 HTTPS
Usage Port
EGO 7870
DB2 50110
NOSQL support for DB2 27017
Keystone 443
Keystone admin 443

Chapter 2. Plan 37
2.5.2 Providing a certificate
Self-signed certificates are certificates that you create yourself for private use.
After you create a self-signed certificate, you can use it immediately. Because
anyone can create self-signed certificates, they are not considered publicly
trusted certificates. You can replace default, expired, or corrupted certificates
with a self-signed certificate. You must delete the default certificate before you
complete this procedure.
IBM Power VC management hosts is installed with a default self signed
certificate and a key. The certificates are installed in the following locations:
/etc/pki/tls/certs/localhost.crt
/etc/pki/tls/private/localhost.key
After you install IBM PowerVC, you can replace the default self-signed certificate
with a certificate of your own. You must restart IBM PowerVC after you replace
the default certificate. This new certificate can be requested from a certificate
authority (CA). The certificate request can include the following information:
– Key size: determines strength of cryptographic keys for certificate.
– Certificate label: the certificate with a unique string of characters.
– Common name: the fully qualified host name of the server for which the
certificate is being created.
– Organization name: the company that uses this certificate.
– Locality or city: the city or a locality designation for your organization.
– State or province: the state or province in which you use this certificate.
– Country or region: identifies, with a two-letter designation, the country, or
region in which you use this certificate.
Glance 9292
Nova 8774
Cinder 9000
Neutron 9696
Validator 8428
Ceilometer 8777
Bumblebee 5470
Usage Port

2.6 Hosts and clients management planning
When you plan for the hosts in your IBM Power Virtualization Center
environment, you need to consider the HMCs that manage your hosts and the
benefits of using multiple Virtual I/O Servers.
2.6.1 Hardware Management Console Planning
Advanced installations typically use redundant HMCs to manage the hosts.
Consider which HMC and hosts you want IBM PowerVC to manage. IBM
PowerVC only supports one HMC managing any particular host. Redundant
HMCs are not supported. If the HMC that you select for IBM PowerVC becomes
unavailable, the hosts cannot be managed by IBM PowerVC.
2.6.2 Multiple Virtual I/O Servers planning
Plan more than one Virtual I/O Server if you want a failover Virtual I/O Server or
expanded Virtual I/O Server functionality. IBM PowerVC provides the option to
utilize more than one Virtual I/O Server. Consider a second redundant Virtual I/O
Server to provide redundancy and reliability to the hosts. Having two Virtual I/O
Servers avoid outages to the hosts when you need to perform maintenance,
updates or changes in the configuration.
2.7 Storage management planning
IBM Power Virtualization Center manages storage volumes, which can be
attached to virtual servers. These storage volumes can be on IBM Storwize or
SAN Volume Controller (SVC) devices. PowerVC uses the term storage provider
for any system that provides storage volumes.
2.7.1 Possible storage configurations
PowerVC can manage any number of supported devices. In this example, there
are two storage devices; an external storage device used for development, and
one used for production. It is important that your virtual machines can access the
necessary storage.
IBM PowerVC assumes that all host systems that can access external storage
controllers have access to the same external storage controllers. Additionally,

Chapter 2. Plan 39
when a virtual server is deployed, you can only deploy to a host system that can
connect to the storage on which the deployment image resides.
The administrator can define storage connectivity groups to further constrain the
selection of host systems. Storage connectivity groups can be used to group host
systems together, for example, the administrator could define “Production” and
“Development” groups. They can also be used to manage systems that contain
multiple VIOS pairs, to direct deployments to a specific pair.
Default storage connectivity groups are automatically created. When a new
virtual machine is deployed from an image, a storage connectivity group must be
specified. The server will be deployed only to a host that contains at least one
VIOS that is part of the storage connectivity group. Similarly, if you want to
migrate a virtual machine, it can only be migrated within the specified storage
connectivity group. This lets you ensure that the source and destination servers
have access to the required storage controllers; for the list of supported storage
controllers; please see 2.3, “IBM PowerVC Storage Access Planning” on
page 18.
2.7.2 Specifying fibre channel ports
Storage connectivity groups that share a VIOS can use different physical Fibre
Channel ports on the VIOS. The IBM PowerVC administrator achieves this by
assigning storage port tags to physical fibre channel ports on the desired VIOS.
These tags are labels that can be assigned to specific Fibre Channel ports
across your IBM Power Systems systems. A storage connectivity group can be
configured to connect only through Fibre Channel ports that have a specific tag
when deploying with NPIV direct connectivity. For further information, refer to
2.3.1, “Storage Connectivity Groups and Tags in IBM PowerVC Standard” on
page 21.
2.7.3 Storage volumes planning
When you register a storage provider with IBM PowerVC, a default storage
template is created for that provider. Storage templates let you specify properties
of a storage volume, such as the storage provider and provisioning method.
When creating a new storage volume, you must select a storage template. All of
the properties that are specified in the storage template are applied to the new
volume, which is created on the storage provider that is specified in the storage
template.

IBM PowerVC Introduction and Configuration

IBM PowerVC Introduction and Configuration

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to IBM PowerVC Introduction and Configuration

Similar to IBM PowerVC Introduction and Configuration (20)

More from IBM India Smarter Computing

More from IBM India Smarter Computing (20)

Recently uploaded

Recently uploaded (20)

IBM PowerVC Introduction and Configuration