Ibm power vc version 1.2.3 introduction and configuration

Redbooks
Front cover
IBM PowerVC Version 1.2.3
Introduction and Configuration
Marco Barboni
Guillermo Corti
Benoit Creau
Liang Hou Xu

International Technical Support Organization
IBM PowerVC Version 1.2.3: Introduction and
Configuration
October 2015
SG24-8199-02

© Copyright International Business Machines Corporation 2014, 2015. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule
Contract with IBM Corp.
Third Edition (October 2015)
This edition applies to version 1, release 2, modification 3 of IBM® Power Virtualization Center
Standard Edition (5765-VCS).
Note: Before using this information and the product it supports, read the information in “Notices” on
page xv.

© Copyright IBM Corp. 2014, 2015. All rights reserved. iii
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvi
IBM Redbooks promotions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Authors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix
Now you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xx
Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Stay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi
Chapter 1. PowerVC introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 PowerVC overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1.1 PowerVC functions and advantages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 OpenStack overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.1 The OpenStack Foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.2 OpenStack framework and projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2.3 PowerVC high-level architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 PowerVC Standard Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.4 PowerVC adoption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2. PowerVC versions and releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2.1 Previous versions and milestones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1.1 PowerVC release to OpenStack edition cross-reference . . . . . . . . . . . . . . . . . . . 10
2.1.2 IBM PowerVC first release (R1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1.3 IBM PowerVC version 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1.4 IBM PowerVC version 1.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 IBM PowerVC version 1.2.2 enhancements and new features. . . . . . . . . . . . . . . . . . . 11
2.2.1 Image management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.2 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.2.3 Host maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.4 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2.5 Cisco Fibre Channel support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.2.6 XIV storage support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2.7 EMC storage support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2.8 Virtual SCSI support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.2.9 Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.2.10 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3 New in IBM PowerVC version 1.2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.3.1 Major software changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.3.2 Significant scaling improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.3 Redundant HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.3.4 Error scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3.5 Host groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

iv IBM PowerVC Version 1.2.3: Introduction and Configuration
2.3.6 Advance placement policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.7 Multiple disk capture and deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.3.8 PowerVC remote restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.3.9 Cloud-init for the latest service pack of AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Chapter 3. PowerVC installation planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.1 IBM PowerVC requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.1.1 Hardware and software requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.1.2 PowerVC Standard Edition requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.1.3 Other hardware compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.2 Host and partition management planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.2.1 Physical server configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.2.2 HMC or PowerKVM planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.2.3 Virtual I/O Server planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.3 Placement policies and templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3.1 Host groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.3.2 Placement policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.3.3 Template types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.3.4 Information that is required for compute template planning . . . . . . . . . . . . . . . . . 42
3.4 PowerVC storage access SAN planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.4.1 vSCSI storage access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.4.2 NPIV storage access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.4.3 Shared storage pool: vSCSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.4.4 Storage access in PowerVC Standard Edition managing PowerKVM . . . . . . . . . 50
3.5 Storage management planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.5.1 PowerVC terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.5.2 Storage templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.5.3 Storage connectivity groups and tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.6 Network management planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.6.1 Multiple network planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.6.2 Shared Ethernet adapter planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.7 Planning users and groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.7.1 User management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.7.2 Group management planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
3.8 Security management planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
3.8.1 Ports that are used by IBM Power Virtualization Center. . . . . . . . . . . . . . . . . . . . 74
3.8.2 Providing a certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.9 Product information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Chapter 4. PowerVC installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.1 Setting up the PowerVC environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.1.1 Create the virtual machine to host PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
4.1.2 Download and install Red Hat Enterprise Linux . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.1.3 Customize Red Hat Enterprise Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4.2 Installing PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.3 Uninstalling PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.4 Upgrading PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.4.1 Before you begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.4.2 Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
4.5 Updating PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.6 PowerVC backup and recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.6.1 Backing up PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4.6.2 Recovering PowerVC data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Contents v
4.6.3 Status messages during backup and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.6.4 Consideration about backup and recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.7 PowerVC command-line interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.7.1 Exporting audit data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
4.8 Virtual machines that are managed by PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.8.1 Linux on Power virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4.8.2 IBM AIX virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.8.3 IBM i virtual machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Chapter 5. PowerVC Standard Edition for managing PowerVM . . . . . . . . . . . . . . . . . . 97
5.1 PowerVC graphical user interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5.2 Introduction to PowerVC setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5.3 Connecting to PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5.4 Host setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5.5 Host Groups setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.6 Hardware Management Console management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.6.1 Add an HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.6.2 Changing HMC credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5.6.3 Change the HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.7 Storage and SAN fabric setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.7.1 Add a storage controller to PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5.7.2 Add SAN fabric to PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.8 Storage port tags setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
5.9 Storage connectivity group setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.10 Storage template setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5.11 Storage volume setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.12 Network setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
5.13 Compute template setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5.14 Environment verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5.14.1 Verification report validation categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5.15 Management of virtual machines and images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
5.15.1 Virtual machine onboarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
5.15.2 Refresh the virtual machine view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5.15.3 Start the virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.15.4 Stop the virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5.15.5 Capture a virtual machine image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.15.6 Deploy a new virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5.15.7 Add virtual Ethernet adapters for virtual machines . . . . . . . . . . . . . . . . . . . . . . 165
5.15.8 Add collocation rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
5.15.9 Resize the virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5.15.10 Migration of virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
5.15.11 Host maintenance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5.15.12 Restart virtual machines remotely from a failed host . . . . . . . . . . . . . . . . . . . 175
5.15.13 Attach a volume to the virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5.15.14 Detach a volume from the virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
5.15.15 Reset the state of a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5.15.16 Delete images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5.15.17 Unmanage a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5.15.18 Delete a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Chapter 6. PowerVC Standard Edition for managing PowerKVM . . . . . . . . . . . . . . . . 187
6.1 Install PowerVC Standard to manage PowerKVM . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
6.2 Set up PowerVC Standard managing PowerKVM . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

vi IBM PowerVC Version 1.2.3: Introduction and Configuration
6.2.1 Add the PowerKVM host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6.2.2 Add storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6.2.3 Add a network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6.3 Host group setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6.4 Import ISO images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6.4.1 Importing ISO images by using the command-line interface. . . . . . . . . . . . . . . . 202
6.4.2 Importing ISO images by using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
6.4.3 Deploying an RHEL ISO image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6.5 Capture a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
6.5.1 Install cloud-init on the virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
6.5.2 Change devices to be mounted by name or UUID . . . . . . . . . . . . . . . . . . . . . . . 215
6.5.3 Capture the virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
6.6 Deploy images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
6.7 Resize virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
6.8 Suspend and resume virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
6.9 Restart a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
6.10 Migrate virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
6.11 Restarting virtual machines remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
6.12 Delete virtual machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
6.13 Create and attach volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
6.14 Attach volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Chapter 7. PowerVC lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
7.1 PowerVC Standard Edition lab environment for managing PowerVM . . . . . . . . . . . . 234
7.1.1 Hardware Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
7.1.2 Power Systems hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7.1.3 Storage infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7.1.4 Storage configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7.1.5 Storage connectivity groups and port tagging. . . . . . . . . . . . . . . . . . . . . . . . . . . 239
7.1.6 Software stack for PowerVC lab environment. . . . . . . . . . . . . . . . . . . . . . . . . . . 242
7.2 PowerVC Standard managing PowerKVM lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

© Copyright IBM Corp. 2014, 2015. All rights reserved. vii
Figures
1-1 OpenStack framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1-2 OpenStack main components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1-3 PowerVC implementation on top of OpenStack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3-1 VIOS settings that need to be managed by PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . 37
3-2 Modifying maximum virtual adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3-3 Host group sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3-4 Migration of a partition by using a placement policy . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3-5 Memory region size view on the HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3-6 PowerVC Standard Edition storage access by using vSCSI. . . . . . . . . . . . . . . . . . . . . 48
3-7 PowerVC Standard Edition storage access by using NPIV . . . . . . . . . . . . . . . . . . . . . 49
3-8 PowerVC Standard Edition storage access by using an SSP . . . . . . . . . . . . . . . . . . . 50
3-9 PowerVC Standard Edition managing PowerKVM storage access . . . . . . . . . . . . . . . 51
3-10 PowerVC storage providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3-11 Fabrics window that lists a switch with a switch GUI . . . . . . . . . . . . . . . . . . . . . . . . . 53
3-12 Storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3-13 Storage templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3-14 Storage template definition: Advanced settings, thin-provisioned . . . . . . . . . . . . . . . 57
3-15 Volume creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3-16 List of storage connectivity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3-17 Storage connectivity groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3-18 Content of a storage connectivity group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3-19 Storage connectivity groups and tags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3-20 Examples of storage connectivity group deployments . . . . . . . . . . . . . . . . . . . . . . . . 63
3-21 Users information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3-22 Detailed user account information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3-23 Groups tab view under Users on the PowerVC management host. . . . . . . . . . . . . . . 72
3-24 Detailed view of viewer user group on the management host . . . . . . . . . . . . . . . . . . 73
4-1 Maintenance message for logged-in users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4-2 Maintenance message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
5-1 Home page access to a group of functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
5-2 PowerVC Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
5-3 Initial system check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
5-4 HMC connection information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5-5 PowerVC Add Hosts dialog window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5-6 Managed hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5-7 PowerVC shows the managed hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5-8 Host information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5-9 Host Groups page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5-10 Create Host Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5-11 Add HMC Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5-12 Changing HMC credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
5-13 Change HMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5-14 Select the new HMC for hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5-15 Adding extra storage providers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5-16 Add Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
5-17 PowerVC Standard Edition window to select a storage pool . . . . . . . . . . . . . . . . . . 113
5-18 Add Fabric window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5-19 IPowerVC Standard Edition Add Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

viii IBM PowerVC Version 1.2.3: Introduction and Configuration
5-20 PowerVC Storage providers tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5-21 PowerVC Fibre Channel port configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5-22 PowerVC Storage Connectivity Groups dialog window . . . . . . . . . . . . . . . . . . . . . . 117
5-23 PowerVC Add Member to storage connectivity group window . . . . . . . . . . . . . . . . . 118
5-24 Disabling a storage connectivity group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5-25 IBM XIV storage template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
5-26 PowerVC Create Storage Template window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
5-27 PowerVC Create Storage Template Advanced Settings . . . . . . . . . . . . . . . . . . . . . 122
5-28 PowerVC Storage Templates page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
5-29 PowerVC Create Volume window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5-30 List of PowerVC storage volumes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
5-31 PowerVC network definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
5-32 IP Pool tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
5-33 PowerVC Create Compute Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
5-34 PowerVC Compute Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
5-35 PowerVC interface while environment verification in process. . . . . . . . . . . . . . . . . . 129
5-36 Verification Results view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
5-37 Example of a validation message for an error status . . . . . . . . . . . . . . . . . . . . . . . . 132
5-38 Example of a validation message for an informational message status . . . . . . . . . . 133
5-39 Operations icons on the Virtual Machines view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
5-40 Selecting a host window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
5-41 Selected hosts window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
5-42 Collapse and expand sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
5-43 Adding existing VMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
5-44 Example of an informational pop-up message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5-45 Virtual machine detailed view with collapsed sections . . . . . . . . . . . . . . . . . . . . . . . 138
5-46 Virtual machine detailed view of expanded Information section . . . . . . . . . . . . . . . . 139
5-47 Virtual machine detailed view of expanded Specifications section . . . . . . . . . . . . . . 140
5-48 Virtual machine detailed view of expanded Network Interfaces section . . . . . . . . . . 141
5-49 Detailed Network Overview tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
5-50 Virtual machine Refresh icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
5-51 Virtual machine fully started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
5-52 Virtual machine powered off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5-53 Capture window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
5-54 Capture boot and data volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
5-55 Capture window confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5-56 Image snapshot in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
5-57 Image creation in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5-58 Storage volumes view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
5-59 Expanded information for a captured image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5-60 Volumes section and Virtual Machines section. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
5-61 Image capture that is selected for deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
5-62 Information to deploy an image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
5-63 Newly deployed virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
5-64 Add an Ethernet adapter for a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
5-65 Create Collocation Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
5-66 Virtual Machine resize. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
5-67 VM Resize dialog window to select a compute template . . . . . . . . . . . . . . . . . . . . . 167
5-68 Exceeded value for resizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
5-69 Migrate a selected virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5-70 Select target server before the migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
5-71 Virtual machine migration in progress. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
5-72 Virtual machine migration finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Figures ix
5-73 Enter Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
5-74 Migrate virtual machines to other hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5-75 Exit Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
5-76 Create a compute template with enabled remote restart capability . . . . . . . . . . . . . 176
5-77 Correct remote restart state under the Specifications section . . . . . . . . . . . . . . . . . 177
5-78 Remotely Restart Virtual Machines option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
5-79 Remotely Restart Virtual Machines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5-80 Destination host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
5-81 Attaching a new volume to a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
5-82 Attached Volumes tab view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
5-83 Detach a volume from a virtual machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
5-84 Confirmation window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
5-85 Resetting the virtual machine’s state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
5-86 State reset confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5-87 Image selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
5-88 Delete an image confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5-89 Unmanage an existing virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
5-90 Delete a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
5-91 Confirmation window to delete a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
6-1 PowerVC Login window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6-2 PowerVC Home page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
6-3 PowerVC Add Host window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
6-4 Informational messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
6-5 Host added successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
6-6 PowerVC managing PowerKVM hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
6-7 Detailed Hosts view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
6-8 PowerKVM host information and capacity section . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
6-9 PowerKVM Virtual Switches and Virtual Machines sections. . . . . . . . . . . . . . . . . . . . 193
6-10 Add a storage device to PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
6-11 SVC storage pool choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
6-12 The new SVC storage provider. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6-13 Add a network to the PowerVC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
6-14 Network is configured now . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
6-15 List of virtual switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6-16 Edit virtual switch window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
6-17 Message about conflicts with the updated virtual switch selections . . . . . . . . . . . . . 200
6-18 Details of the virtual switch components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
6-19 Create a host group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
6-20 Upload Image window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
6-21 ISO images that were imported to PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
6-22 Status of the imported ISO image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
6-23 RHEL ISO image details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6-24 Select the image for deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
6-25 Virtual machine deployment parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
6-26 Deployment in-progress message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
6-27 Successful deployment verification message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
6-28 Virtual Machines view with highlighted State and Health columns . . . . . . . . . . . . . . 208
6-29 Detailed information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
6-30 Detailed information with expanded or collapsed sections . . . . . . . . . . . . . . . . . . . . 210
6-31 Stopping the virtual machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
6-32 Virtual machine started and active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
6-33 Warning message before you capture the VM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
6-34 Capture window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

x IBM PowerVC Version 1.2.3: Introduction and Configuration
6-35 Snapshot in-progress message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
6-36 Status from the Virtual Machines view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
6-37 Snapshot status from the Images view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
6-38 General and network sections of the window to deploy a VM . . . . . . . . . . . . . . . . . 220
6-39 Activation Input section of the window to deploy a virtual machine . . . . . . . . . . . . . 221
6-40 Deployment is started message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
6-41 Virtual Machines view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
6-42 Resize virtual machine window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
6-43 Suspend or pause a virtual machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
6-44 Restart a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
6-45 Migrate a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
6-46 Migrating a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
6-47 Remotely Restart Virtual Machines option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
6-48 Select virtual hosts to restart remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
6-49 Virtual machines that were restarted remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
6-50 Delete a virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
6-51 Create Volume window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
6-52 Attaching new volume to a virtual machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
6-53 Attach an existing volume to this virtual machine . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
7-1 PowerVC Standard Edition hardware lab for managing PowerVM. . . . . . . . . . . . . . . 234
7-2 Physical to logical management layers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
7-3 Shared storage pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
7-4 Storage configuration that was set for this publication . . . . . . . . . . . . . . . . . . . . . . . . 239
7-5 Storage groups and tagged ports configuration lab . . . . . . . . . . . . . . . . . . . . . . . . . . 240
7-6 Storage connectivity groups in the lab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
7-7 Fibre Channel port tags that are used in the lab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
7-8 PowerVC Standard managing PowerKVM lab setup . . . . . . . . . . . . . . . . . . . . . . . . . 243

© Copyright IBM Corp. 2014, 2015. All rights reserved. xi
Tables
2-1 PowerVC releases cross-referenced to OpenStack versions . . . . . . . . . . . . . . . . . . . . 10
2-2 Updated support matrix for SSP, NPIV, and vSCSI storage paths in PowerVC version
1.2.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2-3 New functions that are introduced in PowerVC 1.2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2-4 Scaling capabilities for PowerKVM and PowerVM in PowerVC . . . . . . . . . . . . . . . . . . 23
2-5 List of supported and unsupported multiple disk combinations . . . . . . . . . . . . . . . . . . 26
3-1 Hardware and OS requirements for PowerVC Standard Edition . . . . . . . . . . . . . . . . . 31
3-2 Minimum resource requirements for the PowerVC VM. . . . . . . . . . . . . . . . . . . . . . . . . 31
3-3 Supported activation methods for managed hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3-4 HMC requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3-5 Supported virtualization platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3-6 Supported network hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3-7 Supported storage hardware for PowerVM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3-8 Supported storage hardware for PowerKVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3-9 Supported security software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3-10 Processor compatibility modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3-11 Preferred practices for shared Ethernet adapter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4-1 RHEL packages that relate to PowerVC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4-2 Options for the PowerVC install command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4-3 Available options for the powervc-uninstall command . . . . . . . . . . . . . . . . . . . . . . . . . 85
4-4 Options for the powervc-backup command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4-5 Options for the powervc-restore command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4-6 PowerVC available commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4-7 Commands for PowerVC Standard for managing PowerKVM . . . . . . . . . . . . . . . . . . . 93
4-8 Options for the powervc-audit-export command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
5-1 Information section fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
5-2 Specifications section’s fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
5-3 Details section’s fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
5-4 Modules and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
5-5 Description of the fields in the Information section . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
5-6 Description of the fields in the Specifications section . . . . . . . . . . . . . . . . . . . . . . . . . 159
5-7 Host states during the transition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
7-1 HMC that was used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
7-2 Hardware test environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7-3 Storage switch specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7-4 IBM SAN Volume Controller specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
7-5 Software versions and releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

xii IBM PowerVC Version 1.2.3: Introduction and Configuration

© Copyright IBM Corp. 2014, 2015. All rights reserved. xiii
Examples
2-1 The chdef commands to set the reserve policy and algorithm on new disks . . . . . . . . 17
2-2 How to check whether a host can use remote restart from PowerVC. . . . . . . . . . . . . . 26
2-3 Example of clouddev and ghostdev output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2-4 Obtain the values that are set on the ghostdev and clouddev attributes . . . . . . . . . . . 27
3-1 Adding an admin user account with the useradd command . . . . . . . . . . . . . . . . . . . . . 68
3-2 Verify users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3-3 Updating the admin user account with the usermod command . . . . . . . . . . . . . . . . . . 70
4-1 Installing the gettext package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
4-2 Installing PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4-3 Installation completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4-4 Uninstallation successful. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4-5 Update successfully completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4-6 Example of PowerVC backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4-7 Mismatch between backup and recovery environments . . . . . . . . . . . . . . . . . . . . . . . . 89
4-8 Example of PowerVC recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4-9 powervc-audit command use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4-10 IBM Installation Toolkit sample output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
4-11 RMC status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5-1 scratchpad.txt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
5-2 scratchpad.txt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5-3 Specific device names for the /etc/fstab file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5-4 /etc/lilo.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
5-5 Specific devices names for the /etc/lilo.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
5-6 Commands to enable the activation engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
5-7 Output from the /opt/ibm/ae/AE.sh -R command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6-1 Importing a Red Hat ISO image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
6-2 ISO image location and naming in PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
6-3 virsh list --all output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
6-4 Virtual console that shows Disc Found message . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
6-5 Symbolic links mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
6-6 Sample device names before the change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
6-7 Sample device names after the change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
6-8 lilo.conf file before change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
6-9 lilo.conf file after change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

xiv IBM PowerVC Version 1.2.3: Introduction and Configuration

© Copyright IBM Corp. 2014, 2015. All rights reserved. xv
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.

xvi IBM PowerVC Version 1.2.3: 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®
Enterprise Storage Server®
FlashCopy®
GDPS®
Geographically Dispersed Parallel
Sysplex™
GPFS™
HACMP™
IBM®
IBM SmartCloud®
IBM Spectrum™
Parallel Sysplex®
POWER®
Power Systems™
POWER6®
POWER6+™
POWER7®
POWER7 Systems™
POWER7+™
POWER8®
PowerHA®
PowerVM®
Redbooks®
Redbooks (logo) ®
Storwize®
SystemMirror®
XIV®
The following terms are trademarks of other companies:
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, and the Windows logo are trademarks of Microsoft Corporation 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.
Other company, product, or service names may be trademarks or service marks of others.

IBM REDBOOKS PROMOTIONS
Find and read thousands of
IBM Redbooks publications
Search, bookmark, save and organize favorites
Get up-to-the-minute Redbooks news and announcements
Link to the latest Redbooks blogs and videos
Download
Now
Get the latest version of the Redbooks Mobile App
iOS
Android
Place a Sponsorship Promotion in an IBM
Redbooks publication, featuring your business
or solution with a link to your web site.
Qualiﬁed IBM Business Partners may place a full page
promotion in the most popular Redbooks publications.
Imagine the power of being seen by users who download
millions of Redbooks publications each year!
®
®
Promote your business
in an IBM Redbooks
publication
ibm.com/Redbooks
About Redbooks Business Partner Programs
IBM Redbooks promotions

THIS PAGE INTENTIONALLY LEFT BLANK

© Copyright IBM Corp. 2014, 2015. All rights reserved. xix
Preface
IBM® Power Virtualization Center (PowerVC™) is an advanced enterprise virtualization
management offering for IBM® Power Systems™, which is based on the OpenStack
framework. This IBM Redbooks® publication introduces PowerVC and helps you understand
its functions, planning, installation, and setup.
Starting with PowerVC version 1.2.2, the Express Edition offering is no longer available and
the Standard Edition is the only offering. PowerVC supports both large and small
deployments, either by managing IBM PowerVM® that is controlled with the Hardware
Management Console (HMC) or by managing PowerKVM directly. PowerVC can manage IBM
AIX®, IBM i, and Linux workloads that run on POWER® hardware, including IBM PurePower
systems.
PowerVC editions include the following features and benefits:
Virtual image capture, deployment, and management
Policy-based virtual machine (VM) placement to improve use
Management of real-time optimization and VM resilience to increase productivity
VM Mobility with placement policies to reduce the burden on IT staff in a simple-to-install
and easy-to-use graphical user interface (GUI)
An open and extensible PowerVM management system that you can adapt as you need
and that runs in parallel with your existing infrastructure, preserving your investment
A management system for existing PowerVM deployments
You will also find all the details about how we set up the lab environment that is used in this
book.
This book is for experienced users of IBM PowerVM and other virtualization solutions who
want to understand and implement the next generation of enterprise virtualization
management for Power Systems.
Unless stated otherwise, the content of this book refers to versions 1.2.2 and 1.2.3 of
IBM PowerVC.
Authors
This book was produced by a team of specialists from around the world working at the
International Technical Support Organization, Poughkeepsie Center.
Marco Barboni is an IT Specialist at the IBM Rome Software Lab in Italy. He has 4 years of
experience in cloud virtualization and management in the IBM Power infrastructures field. He
holds a degree in Information Technology from “Roma Tre” University. His areas of expertise
include AIX administration, virtualization on Power, HMC, IBM Power Systems, IBM Linux on
Power, and also IBM Systems Director and IBM PowerVC infrastructure management.

xx IBM PowerVC Version 1.2.3: Introduction and Configuration
Guillermo Corti is an IT Architect at IBM Argentina. He has been with IBM since 2004 and
has 20 years experience with Power Systems and AIX. He has a degree in Systems from
Moron University and 11 years of experience working in service delivery for North American
accounts. His areas of expertise include Power Systems, AIX, IBM Linux on Power, and IBM
PowerVM solutions.
Benoit Creau is an AIX Systems Engineer who works in large French banks (currently BNP
Paribas). He has six years of experience managing client production environments with IBM
Power Systems. His areas of expertise include AIX, Virtual I/O Servers, Power Systems, and
PowerVC. He currently focuses on integrating new technology (IBM POWER8® and
PowerVC) in client environments. He has participated in the community by writing a blog
about Power Systems and related subjects for more than 5 years (chmod666.org).
Liang Hou Xu, PMP, is an IT Architect at IBM China. He has 16 years of experience in Power
Systems and four years of experience in the cloud field. He holds a degree in Engineering
from Tsinghua University. His areas of expertise include Power Systems, AIX, Linux, cloud,
IBM DB2®, C programming, and Project Management.
The project that created this book was managed by:
Scott Vetter, PMP
Thanks to the following people for their contributions to this project:
Dave Archer, Senthil Bakthavachalam, David Bennin, Eric Brown, Ella Buslovich,
Chun Shi Chang, Rich Conway, Joe Cropper, Rebecca Dimock, William Edmonds,
Edward Fink, Nigel Griffiths, Nicolas Guérin, Kyle Henderson, Philippe Hermes, Amy Hieter,
Greg Hintermeister, Bhrugubanda Jayasankar, Liang Jiang, Rishika Kedia,
Sailaja Keshireddy, Yan Koyfman, Jay Kruemcke, Samuel D. Matzek, John R. Niemi,
Geraint North, Sujeet Pai, Atul Patel, Carl Pecinovski, Taylor Peoples, Antoni Pioli,
Jeremy Salsman, Douglas Sanchez, Edward Shvartsman, Anna Sortland, Jeff Tenner,
Drew Thorstensen, Ramesh Veeramala, Christine Wang, and Michael Williams
Thanks to the authors of the previous editions of this book. The authors of the first edition,
IBM PowerVC Version 1.2.0 and 1.2.1 Introduction and Configuration, which was published in
October 2014, were Bruno Blanchard, Guillermo Corti, Sylvain Delabarre, Ho Jin Kim, Ondrej
Plachy, Marcos Quezada, and Gustavo Santos.
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

Preface xxi
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
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

xxii IBM PowerVC Version 1.2.3: Introduction and Configuration

© Copyright IBM Corp. 2014, 2015. All rights reserved. 1
Chapter 1. PowerVC introduction
IBM® Power Virtualization Center Standard Edition (PowerVC) is the next generation of
enterprise virtualization management tools for IBM Power Systems. PowerVC incorporates a
powerful yet simple and intuitive GUI and deep integration with IBM PowerVM virtualization
technologies. PowerVC simplifies the management of the virtualization for Power Systems
servers that run on IBM AIX and Linux operating systems. It now supports the IBM i operating
system to benefit IBM i clients with various virtualization management functionalities in
PowerVC.
This publication provides introductory and configuration information for PowerVC. After we
present an overview of PowerVC in this first chapter, we cover the following topics in
subsequent chapters:
Release reviews in Chapter 2, “PowerVC versions and releases” on page 9
Planning information in Chapter 3, “PowerVC installation planning” on page 29
Installation guidelines in Chapter 4, “PowerVC installation” on page 77
General configuration and setup that are common to all variants of PowerVC in Chapter 5,
“PowerVC Standard Edition for managing PowerVM” on page 97
Information that is specific to using PowerVC Standard for managing PowerKVM in
Chapter 6, “PowerVC Standard Edition for managing PowerKVM” on page 187
A description of the test environment that was used for the examples in Chapter 7,
“PowerVC lab environment” on page 233
1

2 IBM PowerVC Version 1.2.3: Introduction and Configuration
1.1 PowerVC overview
This publication is for system administrators who are familiar with the concepts included in
these IBM Redbooks publications:
IBM PowerVM Virtualization Introduction and Configuration, SG24-7940
IBM PowerVM Virtualization Managing and Monitoring, SG24-7590
PowerVC simplifies the management of virtual resources in your Power Systems
environment.
After the product code is installed, the PowerVC no-menus interface guides the system
administrator through three simple configuration steps to register physical hosts, storage
providers, and network resources and to start capturing and intelligently deploying AIX, IBM i,
and Linux virtual machines (VMs). PowerVC also helps the system administrator perform the
following activities:
Create VMs and resize their CPU and memory.
Attach disk volumes to those VMs.
Import existing VMs and volumes so that they can be managed by PowerVC.
Monitor the use of resources in your environment.
Migrate VMs while they are running (live migration between physical servers).
Deploy images quickly to create new VMs that meet the demands of ever-changing business
needs. At the time of writing this publication, PowerVC can deploy VMs that use AIX, IBM i, or
Linux operating systems. PowerVC is built on OpenStack, which is open source software that
controls large pools of server, storage, and networking resources throughout a data center.
PowerVC uses IBM Platform Resource Scheduler (PRS) to extend the OpenStack set of
technologies to Power Systems environments with enhanced security, intelligent placement of
VMs, and other advanced policy-based features that are required on enterprise clouds.
PRS is a proven technology that is used in grid and scaled-out computing environments by
more than 2,000 clients. Its open and extensible architecture supports reservations,
over-subscription policies, and user-defined policies. PRS is also energy-aware. For more
information about PRS, see this website:
http://www.ibm.com/systems/platformcomputing/products/rs/
1.1.1 PowerVC functions and advantages
Why PowerVC? Why do we need another virtualization management offering? When more
than 70% of IT budgets is spent on operations and maintenance, IT clients legitimately expect
vendors to focus their new development efforts to reduce this cost and foster innovation within
IT departments.
PowerVC gives IBM Power Systems clients advantages:
It is deeply integrated with Power Systems.
It provides virtualization management tools.
It eases the integration of servers that are managed by PowerVM or PowerKVM in
automated IT environments, such as clouds.
It is a building block of IBM Infrastructure as a Service (IaaS), based on Power Systems.

Chapter 1. PowerVC introduction 3
PowerVC is an addition to the existing PowerVM set of enterprise virtualization technologies
that provide virtualization management. It is based on open standards and integrates server
management with storage and network management.
Because PowerVC is based on the OpenStack initiative, Power Systems can be managed by
tools that are compatible with OpenStack standards. When a system is controlled by
PowerVC, it can be managed in either of two ways:
By a system administrator by using the PowerVC GUI
By higher-level tools that call PowerVC by using standard OpenStack application
programming interfaces (APIs)
PowerVC is an option that is between the Hardware Management Console (HMC) and IBM
SmartCloud® IaaS offerings. It provides a systems management product that enterprise
clients require to effectively manage the advanced features that are offered by IBM premium
hardware. It reduces resource use and manages workloads for performance and availability.
In the following sections, we introduce the concepts of OpenStack to help you understand the
terminology that is used in this book.
1.2 OpenStack overview
PowerVC is based on the OpenStack initiative. The following sections provide an overview of
OpenStack.
1.2.1 The OpenStack Foundation
OpenStack is an IaaS solution that is applied to the cloud computing domain, which is led by
the OpenStack Foundation. The foundation is a non-commercial organization that promotes
the OpenStack project and helps the developers within the OpenStack community. Many
major IT companies contribute to the OpenStack Foundation. Check their website for more
information:
http://www.openstack.org/foundation/
IBM is an active member of the OpenStack community. Multiple IBM divisions have key roles
as members. IBM contributes through code contributions, governance, and support within its
products.
OpenStack is no-charge, open source software that is released under the terms of the
Apache license.
1.2.2 OpenStack framework and projects
The goal of OpenStack is to provide an open source cloud computing platform for public and
private clouds.
OpenStack has a modular architecture. Several projects are underway in parallel to develop
these components:
Nova Nova manages the lifecycle and operations of hosts and compute resources.
Swift Swift covers object-oriented storage. It is meant for distributed high availability
in virtual containers.

Cinder This project covers the management for block storage, such as IBM Storwize®
or IBM SAN Virtual Controller.
Glance Glance is the image service that provides discovery, registration, and delivery
services for virtual disk images.
Horizon This dashboard project is the web service management and user interface to
integrate various OpenStack services.
Neutron Neutron is the network management service for OpenStack. Formerly named
Quantum, Neutron includes various aspects, such IP address management.
Keystone The Keystone focus is on security, identity, and authentication services.
Ceilometer The Ceilometer project is for metering. The Ceilometer provides measurement
and billing across all OpenStack components.
You can find complete descriptions of the main OpenStack projects on the Wiki page of their
website:
https://wiki.openstack.org/wiki/Main_Page
Figure 1-1 shows a high-level view of the OpenStack framework and main components and
how they can be accessed by applications that use the OpenStack computing platform APIs.
Figure 1-1 OpenStack framework
Nova (Compute)
Glance (Image Service)
APIs
OpenStack Shared Services
HARDWARE
Applications
Horizon
(Dashboard)
Neutron (Networking)
Swift (Object Storage)
Cinder (Block Storage)

Figure 1-2 provides details about the main components of the OpenStack framework. It also
contains a few explanations of the roles of these components. The illustration shows that one
of the main benefits of OpenStack is that it provides a standard interface for hardware.
Hardware vendors provide OpenStack compatible drivers for their devices. These drivers can
then be used by the other OpenStack components to act on the hardware devices.
Figure 1-2 OpenStack main components
Higher Level Mgmt Ecosystem
Cloud Mgmt SW
Enterprise
Mgmt SW
Other
Mgmt SW Dashboard (Horizon)
OpenStack API
Security (KeyStone) Scheduler Projects
Images (Glance) Flavors Quotas
AMQP DBMS
drivers drivers drivers
Server
Compute Nova Block Storage
Cinder Network Neutron
Storage Network
Cloud Management APIs
• Focus on providing IaaS
• Broad Eco System
Simple Console
• Built using OS REST API
• Basic GUI for OS functions
Management Services
• Image Management
• Virtual Machine Placement
• Account Management
Foundation (Middleware)
• AMQP Message Broker
• Database for Persistence
Virtualization Drivers
• Adapters to hypervisors
• Server, storage, network
• Vendor Led Drivers

1.2.3 PowerVC high-level architecture
Figure 1-3 shows how PowerVC is implemented on top of the OpenStack framework and how
additional components are inserted within the OpenStack framework to add functions to the
standard set of OpenStack features. It also illustrates that IBM is providing drivers to support
IBM devices by using the OpenStack APIs.
Figure 1-3 PowerVC implementation on top of OpenStack
PowerVC is available in Standard Edition, which is described in the following section.
1.3 PowerVC Standard Edition
PowerVC Standard Edition will manage PowerVM systems that run either IBM POWER6®,
IBM POWER7®, or POWER8 processors that are controlled by an HMC. In addition,
PowerVC can manage PowerKVM Linux scale-out servers.
During installation, PowerVC Standard Edition can be configured to manage VMs that are
virtualized on top of either PowerVM or PowerKVM.
On PowerVM, dual Virtual I/O Servers for each host are supported to access storage and the
network. VMs can be either N_Port ID Virtualization (NPIV)-attached storage or shared
storage pool (SSP) back-end storage and virtual SCSI (vSCSI), which were introduced in
PowerVC 1.2.2. The following hardware products are supported for NPIV:
EMC (VNX and VMAX)
IBM XIV® Storage System
IBM Storwize V3700 system
Block Storage
IBM Power SystemsStorage
IBM and 3r d
Party
Network
IBM and 3r d
Party
OpenStack API
PowerVC Virtualization Management Console
API Additions
Monitoring
Differentiators
AMQP DBMS
Security (KeyStone) Scheduler Platform
EGO
Projects
Images Flavors QuotasOVF
Nova/
Libvirt
Cinder NeutronCompute Network
Storage Drivers PowerVM/KVM Driver Network Drivers
Virtualization Mgmt UI
• Simpleand Intuitive
• Targeting the IT Admin
New Management APIs
• Host & Storage
Registration
• Environment Validation
NewMgmt Capabilities
• More granular VM Mgmt
• Differentiators (DLPAR)
• Power Virtual IO
• OVF image Formats
Platform EGO Provides...
• VirtualMachine
Placement
• WorkloadAware Mgmt
VirtualizationDrivers
• HMC driver for PowerVM
• Libvirt drivers for
PowerKVM
• Leverage ecosystem to
support broad range of IBM
and non-IBM storage and
network attachedto Power
Packaging and Simplification
• Simplified install and
Configuration
• IntuitiveAdministration
Model
• Focus on day 0/1 TTV

IBM Storwize V7000 system
IBM SAN Volume Controller
For storage on an SSP, any SSP-supported storage device is supported by PowerVC.
On PowerKVM, storage is backed by iSCSI devices.
For more information, see 3.1, “IBM PowerVC requirements” on page 30.
For the latest list of requirements, see this website:
http://ibm.co/1jC4Xx0
1.4 PowerVC adoption
Two features are useful for a smooth adoption of PowerVC in an existing environment:
When PowerVC manages a physical server, it can manage the full set or only a subset of
the partitions that are hosted on that server.
When PowerVC is adopted in an environment where partitions are already in production,
PowerVC can discover the existing partitions and selectively start to manage them.
Therefore, the adoption of PowerVC in an existing environment does not require a major
change. It can be a smooth transition that is planned over several days or more.

© Copyright IBM Corp. 2014, 2015. All rights reserved. 9
Chapter 2. PowerVC versions and releases
This chapter describes the evolution of IBM® Power Virtualization Center Standard Edition
(PowerVC) through its versions with special focus on version 1.2.2 and version 1.2.3.
The following topics are covered in this chapter:
Previous versions and milestones
IBM PowerVC version 1.2.2 enhancements and new features
New in IBM PowerVC version 1.2.3
2

2.1 Previous versions and milestones
IBM Systems and Technology Group Cloud System Software developed a virtualization
management solution for PowerVM and PowerKVM, which is called the Power Virtualization
Center (PowerVC). The objective is to manage virtualization on the Power platform by
providing a robust, easy-to-use tool to enable its users to take advantage of the Power
platform differentiation.
This list shows the previous versions:
IBM PowerVC first release (R1)
IBM PowerVC version 1.2.0
IBM PowerVC version 1.2.1
2.1.1 PowerVC release to OpenStack edition cross-reference
Table 2-1 cross-references the PowerVC releases to editions of OpenStack.
Table 2-1 PowerVC releases cross-referenced to OpenStack versions
2.1.2 IBM PowerVC first release (R1)
PowerVC first release was available in certain markets in 2013. The primary objective of this
release was to simplify the task of deploying a single logical partition (LPAR) with operating
system software for new IBM Power System hardware clients. This release presented several
restrictions, requiring virtualization management of the hosts and supporting only limited
resource configurations.
2.1.3 IBM PowerVC version 1.2.0
The second release, PowerVC version 1.2.0, was also available worldwide in 2013. The
primary objective was to simplify the virtualization management experience of IBM Power
Systems servers through the Hardware Management Console (HMC) and build a foundation
for enterprise-level virtualization management.
2.1.4 IBM PowerVC version 1.2.1
The third release of PowerVC, version 1.2.1, was available worldwide in 2014 with the
addition of PowerKVM support that was built on IBM POWER8 servers and shared storage
pool (SSP) support for the PowerVM edition.
PowerVC release Availability OpenStack edition
V1.2 October 2013 Havana
V1.2.1 April 2014 Icehouse
V1.2.2 October 2014 Juno
V1.2.3 April 2015 Kilo

Chapter 2. PowerVC versions and releases 11
2.2 IBM PowerVC version 1.2.2 enhancements and new features
The fourth release of PowerVC, version 1.2.2, was also available worldwide in 2014. This
version focused on adding new features and support to the following components:
Image management
Monitoring
Host maintenance mode
Storage
Network
Security
2.2.1 Image management
This version supports new levels of the Linux distributions (previously supported distribution,
new release):
Red Hat Enterprise Linux (RHEL) 6.6
RHEL 7 (which is supported on IBM PowerKVM only in version 1.2.1)
SUSE Linux Enterprise Server (SLES 12)
New Linux distribution support exists for Ubuntu 14.
Currency support for the Linux operating system can be done on cloud-init. Also, for any new
Linux OS distribution support, only cloud-init is supported, not Virtual Solutions Activation
Engine (VSAE). Any changes that are needed in cloud-init to support the new distribution are
coordinated with the IBM Linux Technology Center (LTC) to distribute the changes to the
cloud-init open source community.
2.2.2 Monitoring
Enhancements and new capabilities are included in PowerVC 1.2.2:
Use the Ceilometer framework to monitor the memory and I/O metrics for instances
Provide the hosts with metrics for CPU utilization and I/O
Provide out-of-band lifecycle operation-related checks
With the new set of health checks and metrics, PowerVC version 1.2.2 monitoring
enhancements include the improved scale and stability of the monitoring functions.
The following major capabilities are available in this version:
Reduce the steady-state CPU utilization of the monitor function
Reduce the redundant health and metric event publication to help improve performance
Use the asynchronous update events and reduce the resource polling
Important: IBM PowerVC Express Edition is no longer supported in this release.
Note: Because Ubuntu is a new distribution, you must update the distribution list that is
used by the image import command-line interface (CLI) and graphical user interface (GUI)
to include Ubuntu.

2.2.3 Host maintenance mode
Virtualization administrators often need to prepare a host system for maintenance, for
example, replace a faulty hardware component or update critical software components. This
act is widely known in the industry as putting a host into maintenance mode. Consider the
following points from a virtualization management perspective:
The host will be prevented from entering maintenance mode if any one (or more) of the
following conditions are true and the user requested automated mobility upon entering
maintenance:
– The host’s hypervisor state is anything other than operating. (For example, the
administrator must address any issues in advance; otherwise, live migrations are
unlikely to succeed.)
– The host has at least one virtual machine (VM) in the error state, and migration cannot
be performed until the administrator resolves the issue.
– The host has at least one VM in the paused state (when one or more VMs in paused
state mean that it resides in memory and the administrator needs to power down the
host).
– The host is based on PowerVM and not licensed for active partition mobility.
No additional virtual machines can be placed on the host while its maintenance state is
either entering, error, or on.
If mobility was requested when the host was entering maintenance mode and an active
VM existed, this VM must be relocated automatically to other hosts within the relocation
domain.
While virtual machines are migrated to other hosts, the host’s Platform Resource
Scheduler (PRS) hypervisor state is entering maintenance. The PRS hypervisor state
automatically transitions to in maintenance when the migrations complete and Nova
notifications will be generated as the state transitions.
After the administrator completes the maintenance, the administrator will remove the host
from maintenance mode. At that point, the PRS hypervisor state transitions back to ok.
Now, virtual machines are able to be scheduled to the host again. VMs that were
previously on the host that were put in maintenance mode need to be migrated back to the
host manually.
2.2.4 Storage
Two additional volume drivers and one fabric driver were added in PowerVC version 1.2.2.
The volume drivers are IBM XIV Storage System and EMC, and the fabric driver is Cisco.
Volume attachment now includes virtual SCSI (vSCSI) connectors. The following uses and
cases apply to these new devices:
Registration of storage arrays and Fibre Channel (FC) switches with the storage template
and storage connectivity groups (SCGs)
Deployment of VMs
Attachment and detachment of volumes in existing VMs
Note: The administrator can take the host out of maintenance mode at any point. PRS
finishes any in-progress migrations and halts afterward.

Image management
Onboarding of VMs and volumes
The new storage and fabric drivers require new registration application programming
interfaces (APIs) to register the new devices.
New storage templates are required for XIV and EMC. Both drivers support additional storage
templates. API and user interface (UI) changes are associated with the storage templates.
Table 2-2 represents how clients are using volumes within PowerVM. For example, when an
N_Port ID Virtualization (NPIV) connection exists to boot a VM, it is not necessary to attach a
vSCSI-connected volume.
When the client sets their connection type for boot and data volumes within an SCG, a client
is limited to two connector types within a single SCG. On deployment or attachment, the SCG
determines the connection type between NPIV and vSCSI for a storage area network (SAN)
device.
Table 2-2 Updated support matrix for SSP, NPIV, and vSCSI storage paths in PowerVC version 1.2.2
The SCG changes allow the creation of a vSCSI on SCG. PowerVC version 1.2.2 provides
the option on the SCG configuration so that the client can specify whether they want dual
Virtual I/O Servers to be guaranteed during deployment and migration. API and UI changes
are associated with these SCG changes.
2.2.5 Cisco Fibre Channel support
This newly added support is for Cisco Multicast Distributed Switching (MDS) Fibre Channel
(FC) switches. This support was developed in collaboration with IBM to ensure compatibility
with PowerVC.
Next, we describe how to enable Cisco support within the PowerVC FC zoning architecture,
which differs significantly from the community architecture.
The relevant components to support Cisco FC are contained within the Cinder-volume
service. One of these services runs for every registered storage provider. Volume manager
invokes the zone manager whenever connections are added or removed. The zone manager
has a pluggable driver model that separates generic code from hardware-specific code. The
following steps describe the flow during the volume attachment or detachment:
1. After the volume driver is invoked, the zone manager flow is invoked.
2. The volume driver returns the initiator that is wanted.
3. The target is mapped from the initialize_connection or terminate_connection method.
4. The returned structure feeds into the zone manager operation.
PowerVC version 1.2.2 supports a maximum of two fabrics. The fabrics can be mixed.
Boot volume/data volume SSPs NPIV vSCSI
SSPs Supported Supported Not supported
NPIV Not supported Supported Not supported
vSCSI Not supported Supported Supported

Function
The Cisco driver has configuration file options that, for each fabric, specify the user name,
password, IP address, and virtual SAN (VSAN) to use for zoning operations. The VSAN is
interesting. Cisco and Brocade switches allow the physical ports on the switch to be divided
into separate fabrics. Cisco calls them VSANs, and Brocade calls them Virtual Fabrics.
Therefore, every zoning operation on a switch is performed in the contact of a VSAN or Virtual
Fabric. However, the two drivers work differently:
For Cisco, a user does not have a default VSAN. So, the VSAN to use is specified in the
configuration file. This method is not ideal. The user needs to be able to determine the
VSAN automatically by looking at where the initiator and target ports are logged in.
For Brocade, every user has a default Virtual Fabric, and the driver creates zones on that
default fabric.
Integration
To extend PowerVC integration, the zone manager class supports an fc_fabric_type option,
which allows the user to select Brocade and Cisco switches.
Zone manager also tolerates slight variations in the behavior of the two drivers. It delivers an
extended Cisco CLI module that is called powervc_cisco_fc_zone_client_cli.py. This
module adds a get_active_zone_map function that is needed by the PowerVC zoning driver.
The Cisco driver is enabled by editing the /etc/cinder/fabrics.conf file.
The fabric registration UI allows to the user to register Brocade and Cisco FC switches.
Mixed fabrics are supported for PowerVC, Brocade, and Cisco Tier1 drivers. Third-party fabric
drivers can be provided and mixed by vendors. However, third-party fabric drivers cannot be
mixed with PowerVC fabric drivers because Cinder supports a single zone manager only and
Tier1 drivers are managed from the PowerVC zone manager.
For Cisco fabrics, the following properties are required for registration:
Display name
IP address
Port
User name
Password
VSAN
The registration API performs a test connection to ensure that the credentials are correct and
the specified VSAN exists.
2.2.6 XIV storage support
Support for IBM XIV Storage System storage arrays is added to PowerVC. The functionality
that is offered by this interface is similar to the functions that are offered through the IBM SAN
Volume Controller (SVC).
Note: IBM PowerVC version 1.2.2 continues to support a maximum of two fabrics that can
be registered.

This interface requires the XIV driver, which is downloaded and included in the build and
installed in the PowerVC environment. The downloaded XIV driver also contains helper
methods to derive a list of volumes in a certain XIV array and its unique identifier. These
methods are used by the corresponding PowerVC registration and extended driver code.
Function
All functions that relate to storage arrays are supported:
Registration by using the default storage template
Storage connectivity group setup
Configuration of the FC port
Onboarding of VMs with XIV volumes that are attached to them
Onboarding of volumes that are already in XIV storage
Creation and deletion of volumes on XIV storage
Deployment of VMs by using volumes from XIV storage
Integration
A new XIV registration code is integrated into PowerVC. As part of the storage registration UI,
this new registration code collects the IP address, user friendly name, user name, and
password to register the XIV Storage System to the PowerVC.
The registration API performs a test connection and retrieves a list of available storage pools
from the XIV system. The list is displayed to the user, so that the user can choose the pool to
use for default provisioning operations.
This approach is similar to how the IBM Storwize registration UI looks today, except that the
Secure Shell (SSH) keys are not supported. Currently, no UI is available for the user to select
the type of storage controller that the user is registering. Storwize is the only option.
A user can use the UI to select between Storwize and Network File System (NFS), and that
selection can be reused to provide the PowerVC user with a Storwize/XIV option.
2.2.7, “EMC storage support” on page 16 shows a choice of SAN Volume Controller, EMC, or
XIV storage during storage registration.
The storage template UI for XIV is similar to Storwize support. The UI needs to recognize the
type of storage provider and display the correct UI.
The storage metadata API is used by the storage template UI to get a list of storage pools and
related information, but first, the XIV driver needs to be enhanced. PowerVC has an extended
XIV driver with the get_storage_metadata function implemented in it. This extended driver is
used by the XIV registration code.
Like the SAN Volume Controller, the XIV has a limit on the number of hosts that can be
defined. During initialize_connection, the host creation fails with a return code of
REMOTE_MAX_VIRTUAL_HOSTS_REACHED. This limit is not determined yet.
The attach operation fails with an appropriate message. However, the TTV validation tool
might expose the total or percent of slots that is used with the same or similar naming scheme
that is used with the SAN Volume Controller for images and volumes. Images start with Image
and volumes start with volume.
Note: The /etc/cinder/cinder.conf file needs to be updated to include xiv as a
supported storage type.

2.2.7 EMC storage support
The EMC storage array is now included in PowerVC version 1.2.2. The support includes EMC
VNX and VMAX storage devices. VNX and VMAX are in two different EMC drivers.
This support is essentially how the PowerVC enables the Storage Management Initiative
Specification (SMI-S) EMC driver. The SMI-S provider proxy applies to the EMC VMAX driver
only, not the VNX driver. The EMC VNX driver uses a remote command tool set that is located
with the cinder driver to communicate to the VNX device rather than through an SMI-S proxy.
The EMC VMAX driver requires that you download the EMC SMI-S provider proxy software
from the EMC website. The EMC VMAX driver also requires that you run on an x86 Linux
system and that you are at version V4.5.1 or higher. The OpenStack EMC driver
communicates with this proxy by using the Web-Based Enterprise Management (WBEM).
The OpenStack EMC driver also has a dependency on the python pywebm package.
The EMC driver supports both iSCSI and FC connectivity. Although the EMC driver has iSCSI
support, only NPIV connectivity is supported in this release.
The configuration of the EMC driver is in two locations. The cinder.conf file contains general
settings that reference the driver and also a link to an external XML file that contains the
detailed settings. The following configuration file settings are valid:
volume_driver = cinder.volume.drivers.emc.emc_smis_fc.EMCSMISFCDriver
cinder_emc_config_file = /etc/cinder/cinder_emc_config.xml
Integration
New EMC registration code is available and enabled in PowerVC version 1.2.2. For
similarities, see “Integration” on page 14.
Like the SAN Volume Controller, the EMC limits the number of hosts that can be defined.
During initialize_connection, the host creation returns a failure. This limit for VNX is 1,024
maximum hosts. The attach operation fails with an appropriate message. TTV might expose
the total number of used slots or the percent of used slots.
The same or similar naming scheme is used with the SAN Volume Controller for images and
volumes. Images start with Image and volumes start with volume.
The EMC low level of design determines any new attributes to be exposed in the default
storage template.
2.2.8 Virtual SCSI support
Current cinder code supports NPIV connectivity from SAN Storage to a VM in the PowerVC
Standard Edition. In this model, the storage volume is mapped directly to the virtual FC
adapter in the VM. PowerVC 1.2.2 adds the support in Standard Edition for mapping the
storage volume to the Virtual I/O Server (VIOS) and for establishing a vSCSI connection from
the VIOS to the VM.
The vSCSI classic model is needed for PureApp where the VM boots from a vSCSI-attached
volume and data volumes are also vSCSI-attached.
Important: This command toolset runs on x86 only, which limits the PowerVC
management server to x86 installations.

Use the updated support matrix, Table 2-2 on page 13, for input to the necessary design
changes to the SCGs. The SGG determines the connection type to the VM during the
attachment and detachment of a volume to a VM. During deployment, the SCG includes
hosts that are compatible with the SCG only.
The SCG has two connectivity types:
One connectivity type for the OS disk
One connectivity type for data volumes
The selection of an NPIV or vSCSI SCG determines the connectivity type for the OS disk.
When a volume is attached to a VM, the connectivity type for volumes determines whether
the volume is connected through NPIV or vSCSI.
vSCSI is supported for all PowerVC tier-1 cinder drivers, which include PowerVC, SAN
Volume Controller, EMC, and XIV drivers. No support is available initially for non-tier-1 volume
drivers.
Two methods exist to establish SAN zoning and storage controller hosts. The first method is
outside of the scope of this section. The administrator establishes all of the zoning and
storage controller hosts before anyone uses the vSCSI connectivity. Most clients already use
this method when they use vSCSI connections from the VIOS. Clients create a zone on the
switch that contains all the VIOS and storage controllers. Live Partition Mobility (LPM)
operations are supported without additional zoning requirements.
Typically, clients also run the rootvg of the VIOS from SAN so an existing host entry is
available on the storage controller. This step also includes the management of the SCG and
the creation of zones and hosts on the storage controller. This duality is evaluated as part of
the design changes that are needed for SCG to support vSCSI.
To enable multiple paths and LPM operations with vSCSI connections, disk reservations must
be turned off for all of the hdisks that are discovered on the VIOS. Use the AIX chdef
command to overwrite configuration attributes when a device is discovered.
For the SAN Volume Controller, the following chdef commands that are shown in Example 2-1
must be executed on the target VIOS before you assign the disks to the vSCSI adapters.
Example 2-1 The chdef commands to set the reserve policy and algorithm on new disks
chdef -a reserve_policy=no_reserve -c disk -s fcp -t mpioosdisk
chdef -a algorithm=round_robin -c PCM -s friend -t fcpother
These chdef commands need to be executed only one time on the Virtual I/O Servers before
you attempt to use vSCSI connections.
Storage controller registration, volume creation, volume deletion, and volume onboard are
unaffected by the addition of the vSCSI connectivity type.
Note: You are required to overwrite the reserve_policy and set the algorithm for the disks
that are discovered. The default algorithm is a failover algorithm.
Note: Consider changing the reserve policy if it was not set to no_reserve. If this setting is
not executed before you allocate the disks to the vSCSI adapter, you are required to
change these settings for each disk.

Ibm power vc version 1.2.3 introduction and configuration

Ibm power vc version 1.2.3 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 power vc version 1.2.3 introduction and configuration

Similar to Ibm power vc version 1.2.3 introduction and configuration (20)

Recently uploaded

Recently uploaded (20)

Ibm power vc version 1.2.3 introduction and configuration