IBM PowerVC Introduction and Configuration

8/12/2019 IBM PowerVC Introduction and Configuration

http://slidepdf.com/reader/full/ibm-powervc-introduction-and-configuration 1/234

ibm.com /redbooks

Draft Document for Review November 20, 2013 5:11 pm SG24-8199-00

IBM PowerVCIntroduction and Configuration

Guillermo Corti

Sylvain Delabarre

Ho Jin Kim

Ondrej Plachy

Marcos Quezada

Gustavo Santos

Installation requires just 20 minutes to

get a virtual machine up and running

Intelligent virtual machine

deployment

Deep integration with

Power Systems

Front cover

http://www.redbooks.ibm.com/








IBM PowerVC Introduction and Configuration

November 2013

International Technical Support Organization

Draft Document for Review November 20, 2013 5:11 pm 8199edno.fm

SG24-8199-00



8199edno.fm Draft Document for Review November 20, 2013 5:11 pm

© Copyright International Business Machines Corporation 2013. All rights reserved.

Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP

Schedule Contract with IBM Corp.

First Edition (November 2013)

This edition applies to Version 1, Release 2 of IBM PowerVC Standard Edition (5765-VCS) and

IBM PowerVC Express Edition (5765-VCX).

This document was created or updated on November 20, 2013.

Note: Before using this information and the product it supports, read the information in“Notices” on page xvii.



iii

Draft Document for Review November 20, 2013 5:11 pm 8199edno.fm

Note: This book is based on a pre-GA version of a product and may not apply when theproduct becomes generally available. We recommend that you consult the productdocumentation or follow-on versions of this redbook for more current information.



8199edno.fm Draft Document for Review November 20, 2013 5:11 pm

iv IBM PowerVC Introduction and Configuration



© Copyright IBM Corp. 2013. All rights reserved. v

Draft Document for Review November 20, 2013 5:11 pm 8199TOC.fm

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xixAuthors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

Now you can become a published author, too! . . . . . . . . . . . . . . . . . . . . . . . . xxi

Comments welcome. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxi

Stay connected to IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

Chapter 1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 IBM PowerVC overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1.2 IBM PowerVC Express Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1.3 IBM PowerVC Standard Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 OpenStack Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.4.1 The OpenStack foundation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.4.2 OpenStack projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 2. Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 PowerVC positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2.2 IBM Power Virtualization Center requirements . . . . . . . . . . . . . . . . . . . . . 10

2.2.1 Hardware and software requirements . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2.2 IBM Power Virtualization Center Express. . . . . . . . . . . . . . . . . . . . . 11

2.2.3 IBM Power Virtualization Center Standard . . . . . . . . . . . . . . . . . . . . 13

2.2.4 Planning Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2.3 IBM PowerVC Storage Access Planning. . . . . . . . . . . . . . . . . . . . . . . . . . 18

2.3.1 Storage Connectivity Groups and Tags in IBM PowerVC Standard . 21

2.3.2 Storage Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.4 Users and groups planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2.4.1 Users management planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.4.2 Groups management planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332.5 Security management planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

2.5.1 Ports used by IBM Power Virtualization Center . . . . . . . . . . . . . . . . 36

2.5.2 Providing a certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37





Contents vii

Draft Document for Review November 20, 2013 5:11 pm 8199TOC.fm

4.7.1 Verification report validation categories . . . . . . . . . . . . . . . . . . . . . . 82

4.8 Compute Templates setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

4.9 Storage Templates Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

4.10 Storage Volumes Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

4.11 IBM PowerVC Standard VM setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4.11.1 Virtual machine onboarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4.11.2 Virtual machine operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Chapter 5. IBM PowerVC Express Edition specifics . . . . . . . . . . . . . . . . 155

5.1 Installation and setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

5.1.1 Installing IBM PowerVC Express . . . . . . . . . . . . . . . . . . . . . . . . . . 155

5.1.2 Setup and preparation of IBM PowerVC Express environment. . . . 156

5.2 Import, capture and deploy ISO images . . . . . . . . . . . . . . . . . . . . . . . . . 165

5.2.1 Import ISO images for deployments . . . . . . . . . . . . . . . . . . . . . . . . 1655.2.2 Deploy a RHEL ISO image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

5.2.3 Image Capture and deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Chapter 6. PowerVC lab environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

6.1 Hardware infrastructure for PowerVC Standard edition . . . . . . . . . . . . . 196

6.2 Hardware Management Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

6.3 Power Systems hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

6.4 Storage infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

6.4.1 Storage SAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1976.5 Software stack for PowerVC Standard lab environment . . . . . . . . . . . . . 197

6.6 Hardware infrastructure for PowerVC Express edition . . . . . . . . . . . . . . 199

6.7 Power Systems hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

6.8 Storage infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

6.8.1 Storage SAN switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

6.9 Software stack for PowerVC Express lab environment. . . . . . . . . . . . . . 199

6.10 Lab environment hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

6.11 IBM PowerVC installation tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Abbreviations and acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

IBM Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Other publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Online resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

Help from IBM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206



8199TOC.fm Draft Document for Review November 20, 2013 5:11 pm

viii IBM PowerVC Introduction and Configuration



© Copyright IBM Corp. 2013. All rights reserved. ix

Draft Document for Review November 20, 2013 5:11 pm 8199LOF.fm

Figures

1-1 IBM PowerVC technology overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

1-2 Openstack framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2-1 IBM PowerVC Express Storage™ Access . . . . . . . . . . . . . . . . . . . . . . . . 20

2-2 IBM PowerVC Standard Storage Access . . . . . . . . . . . . . . . . . . . . . . . . . 21

2-3 Storage Connectivity Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2-4 Storage Connectivity Groups And Tags . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2-5 Examples of Storage Groups Deployments . . . . . . . . . . . . . . . . . . . . . . . 24

2-6 Storage Template definition - Advanced Settings . . . . . . . . . . . . . . . . . . . 26

2-7 Users account view on the IBM PowerVC management host. . . . . . . . . . 282-8 Refresh users account view on the IBM PowerVC management host . . . 29

2-9 Detailed user account information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2-10 View updated user account information . . . . . . . . . . . . . . . . . . . . . . . . . 31

2-11 Users groups view on the IBM PowerVC management host . . . . . . . . . 34

2-12 Detailed view of viewer users group on management host. . . . . . . . . . . 35

2-13 Memory Region Size view on the HMC . . . . . . . . . . . . . . . . . . . . . . . . . 48

3-1 Processors configuration for PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3-2 Memory configuration for PowerVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

3-3 Configure maximum virtual adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534-1 PowerVC login screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

4-2 PowerVC Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4-3 HMC connection info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

4-4 PowerVC Add hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

4-5 PowerVC -Show managed hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

4-6 host information, and the Virtual Machines. . . . . . . . . . . . . . . . . . . . . . . . 69

4-7 IBM PowerVC Standard Add Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

4-8 IBM PowerVC Standard Select Pool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724-9 IBM PowerVC standard Add Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

4-10 IIBM PowerVC Standard Add Fabric 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 73

4-11 PowerVC - Show Storage Providers. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

4-12 PowerVC Fibre Channel Port Configuration . . . . . . . . . . . . . . . . . . . . . . 75

4-13 PowerVC Storage Connectivity Groups . . . . . . . . . . . . . . . . . . . . . . . . . 76

4-14 PowerVC Add Member to Storage Connectivity Group . . . . . . . . . . . . . 78

4-15 PowerVC Defining a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

4-16 IBM PowerVC interface while environment verification in process. . . . . 81

4-17 Verification Results view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824-18 Example of a validation message for an error status . . . . . . . . . . . . . . . 85

4-19 Example of a validation message for a valid status . . . . . . . . . . . . . . . . 86

4-20 PowerVC Create Compute Template . . . . . . . . . . . . . . . . . . . . . . . . . . . 88



8199LOF.fm Draft Document for Review November 20, 2013 5:11 pm

x IBM PowerVC Introduction and Configuration

4-21 PowerVC Compute Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

4-22 PowerVC Create Storage Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

4-23 PowerVC Create Storage Template Advanced. . . . . . . . . . . . . . . . . . . . 92

4-24 PowerVC Storage Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

4-25 PowerVC Create Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

4-26 PowerVC Storage Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4-27 PowerVC management host web interface login screen . . . . . . . . . . . . 96

4-28 PowerVC management host home screen . . . . . . . . . . . . . . . . . . . . . . . 97

4-29 Selecting host view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

4-30 Selected hosts view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

4-31 Collapse and expand buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

4-32 Manage Existing button. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

4-33 Onboarding existing virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . 101

4-34 Example of information pop up message . . . . . . . . . . . . . . . . . . . . . . . 1024-35 Display existing messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

4-36 Existing virtual machine view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

4-37 Virtual machine detailed view with collapsed sections . . . . . . . . . . . . . 104

4-38 Virtual Machine detailed view of expanded information section . . . . . . 105

4-39 Virtual Machine detailed view of expanded specification section . . . . . 107

4-40 Virtual Machine detailed view of expanded network section. . . . . . . . . 108

4-41 Detailed Network view. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

4-42 Detailed view of the tree links to move backwards in the views . . . . . . 109

4-43 Virtual Machine detailed view of expanded details section . . . . . . . . . . 110

4-44 Operations buttons on the virtual machine view . . . . . . . . . . . . . . . . . . 111

4-45 Virtual machine powering on. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

4-46 Virtual machine powered off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

4-47 Verify volume screen when pressing Capture button. . . . . . . . . . . . . . 121

4-48 Information and confirmation window . . . . . . . . . . . . . . . . . . . . . . . . . . 122

4-49 Entering the name for the capture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

4-50 Image snapshot in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

4-51 Image creation in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1244-52 Image view with a finished capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124

4-53 Storage Volumes view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

4-54 Expanded information section of an image capture . . . . . . . . . . . . . . . 126

4-55 Expanded specification section of an image capture . . . . . . . . . . . . . . 128

4-56 Virtual Machines section of an image capture . . . . . . . . . . . . . . . . . . . 129

4-57 Image capture selected for deployment . . . . . . . . . . . . . . . . . . . . . . . . 130

4-58 Information to Deploy an image capture . . . . . . . . . . . . . . . . . . . . . . . . 132

4-59 New virtual machine deployed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

4-60 Virtual Machine resize. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1344-61 Virtual Machine resize. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

4-62 Exceeded value for resizing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

4-63 Virtual machine resize in progress . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137







© Copyright IBM Corp. 2013. All rights reserved. xiii

Draft Document for Review November 20, 2013 5:11 pm 8199LOT.fm

Tables

2-1 Power Systems Virtualization Management Solutions . . . . . . . . . . . . . . . 10

2-2 Hardware and OS requirements for IBM PowerVC Express . . . . . . . . . . 11

2-3 Minimum resource requirements for the IBM PowerVC virtual machine. . 12

2-4 Supported virtualization platforms for IBM PowerVC . . . . . . . . . . . . . . . . 13

2-5 IBM PowerVC-supported network hardware and software . . . . . . . . . . . . 13

2-6 IBM PowerVC-supported storage hardware . . . . . . . . . . . . . . . . . . . . . . . 13

2-7 Hardware and operating system support for IBM PowerVC hosts . . . . . . 14

2-8 Minimum resource requirements for the IBM PowerVC virtual machine. . 15

2-9 HMC requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152-10 Supported virtualization platforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2-11 Supported network hardware and software . . . . . . . . . . . . . . . . . . . . . . 16

2-12 Supported storage hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2-13 Supported security software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

2-14 Ports used for inbound and outbound communication . . . . . . . . . . . . . . 36

2-15 Ports used by HMC, IVM and SVC with IBM PowerVCt . . . . . . . . . . . . . 36

2-16 Additional ports used by IBM PowerVC to connect. . . . . . . . . . . . . . . . . 36

2-17 Processor compatibility Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

4-1 Information section fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044-2 Specifications section fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

4-3 Details section fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

4-4 Description of the fields on the information section. . . . . . . . . . . . . . . . . 126

4-5 Description of the fields on the Specifications section . . . . . . . . . . . . . . 127

6-1 HMC requirements used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

6-2 Hardware test environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

6-3 Storage switch specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

6-4 Software version and releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

6-5 Hardware test environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

6-6 Storage switch specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

6-7 Software version and releases used on PowerVC Express lab . . . . . . . 200



8199LOT.fm Draft Document for Review November 20, 2013 5:11 pm

xiv IBM PowerVC Introduction and Configuration

8199LOE f



© Copyright IBM Corp. 2013. All rights reserved. xv

Draft Document for Review November 20, 2013 5:11 pm 8199LOE.fm

Examples

2-1 Adding admin user account with the useradd command . . . . . . . . . . . . . 282-2 Updating admin user account with the usermod command . . . . . . . . . . . 30

2-3 Delete an user account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3-1 How to set SELINUX mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3-2 How to set repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3-3 yum repolist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3-4 powervc installation command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3-5 Accept the agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3-6 installing powervc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573-7 installation completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3-8 How to install linux in NPIV attachment of SAN volumes . . . . . . . . . . . . . 59

3-9 RSCT installation in Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

4-1 Original scratchpad.txt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

4-2 Edited scratchpad.txt file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

4-3 Specific device names for the /etc/fstab file. . . . . . . . . . . . . . . . . . . . . 117

4-4 Default /etc/lilo.conf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

4-5 Specific devices names for the /etc/lilo.conf file . . . . . . . . . . . . . . . . 117

4-6 Commands to enable activating engine on a previously captured VM . . 1184-7 Output from the /opt/ibm/ae/AE.sh -R command. . . . . . . . . . . . . . . . . 118

8199LOE fm D ft D t f R i N b 20 2013 5 11



8199LOE.fm Draft Document for Review November 20, 2013 5:11 pm

xvi IBM PowerVC Introduction and Configuration

Draft Document for Review November 20 2013 5:11 pm 8199spec fm



Draft Document for Review November 20, 2013 5:11 pm 8199spec.fm

© Copyright IBM Corp. 2013. All rights reserved. xvii

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult yourlocal IBM representative for information on the products and services currently available in your area. Anyreference 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 infringeany IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate andverify 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. Thefurnishing of this document does not grant you any license to these patents. You can send license inquiries, inwriting, 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 suchprovisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS ORIMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer ofexpress 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 theinformation herein; these changes will be incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s) described in this publication at any timewithout 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 materialsfor this IBM product and use of those websites is at your own risk.

IBM may use or distr ibute any of the information you supply in any way it believes appropriate without incurr ing anyobligation to you.

Any performance data contained herein was determined in a controlled environment. Therefore, the resultsobtained in other operating environments may vary significantly. Some measurements may have been made ondevelopment-level systems and there is no guarantee that these measurements will be the same on generallyavailable systems. Furthermore, some measurements may have been estimated through extrapolation. Actualresults 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 publishedannouncements 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 thecapabilities 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 ascompletely as possible, the examples include the names of individuals, companies, brands, and products. All ofthese names are fictitious and any similarity to the names and addresses used by an actual business enterprise isentirely coincidental.

COPYRIGHT LICENSE:This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distr ibute these sample programs in anyform without payment to IBM, for the purposes of developing, using, marketing or distr ibuting application programsconforming 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 orimply reliability, serviceability, or function of these programs. You may copy, modify, and distr ibute these sampleprograms in any form without payment to IBM for the purposes of developing, using, marketing, or distributingapplication programs conforming to IBM's application programming interfaces.

8199spec fm Draft Document for Review November 20 2013 5:11 pm



8199spec.fm Draft Document for Review November 20, 2013 5:11 pm

xviii IBM PowerVC Introduction and Configuration

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International BusinessMachines Corporation in the United States, other countries, or both. These and other IBM trademarkedterms 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 waspublished. Such trademarks may also be registered or common law trademarks in other countries. A currentlist of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml

The following terms are trademarks of the International Business Machines Corporation in the United States,other countries, or both:

AIX®

DB2®

Express Storage™

IBM®

IBM Flex System™IBM SmartCloud®

POWER®

Power Architecture®

Power Systems™

POWER6®

POWER6+™

POWER7®

POWER7+™PowerLinux™

PowerVM®

PureFlex™

Redbooks®

Redbooks (logo) ®

Storwize®

System Storage®

System x® System z®

The following terms are trademarks of other companies:

Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of IntelCorporation or its subsidiaries in the United States and other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, or both.

Java, and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its

affiliates.UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, or service names may be trademarks or service marks of others.

Draft Document for Review November 20, 2013 5:11 pm 8199pref.fm

http://www.ibm.com/legal/copytrade.shtml

http://www.ibm.com/legal/copytrade.shtml



© Copyright IBM Corp. 2013. All rights reserved. xix


Preface

IBM PowerVC is an advanced enterprise virtualization management offering forIBM Power Systems based on the OpenStack technology. This IBM®Redbooks® publication will introduce and position IBM Power Virtualization

Center and will help you understand its positioning, planning, installation, andsetup.

IBM PowerVC is available in two editions, Express Edition to manage smalldeployments through IVM and Standard Edition to manage larger deployments

through the HMC. IBM PowerVC can manage Linux on Power and AIX, running

on POWER hardware including Flex System POWER compute nodes.

PowerVC editions include the following features and benefits:

Virtual Image capture, deployment, and management Policy-based Virtual Machine (VM) placement to improve utilization Targeted VM placement for deployment to reduce complexity Managing real-time optimization and VM resilience to increase productivity VM Mobility with placement policies to reduce burden on IT staff in a

simple-to-install and easy-to-use GUI An open and extensible PowerVM management system that enables you to

adapt as you need and runs in parallel with existing infrastructure, preservingyour investment

A management system that manages existing PowerVM deployments

You will also find all the details on how we set up the lab environment used in thisbook.

This IBM Redbooks publication is intended for experienced IBM PowerVM® and

other virtualization solutions users wanting to understand and implement the nextgeneration of enterprise virtualization management for Power Systems™.

Authors

This book was produced by a team of specialists from around the world working

at the International Technical Support Organization, Poughkeepsie Center.

Guillermo Corti is an IT specialist at IBM Argentina. He has been with IBM since2004, with a 20 years technical background on Power Systems and AIX®. He

has a degree in Systems from Moron University. He also has 10 years






Preface xxi

Dave Archer, Senthil Bakthavachalam, David Bennin, Eric Brown, Rich Conway,Joe Cropper, Rishika Kedia, Yan Koyfman, Samuel D Matzek, John R Niemi,

Geraint North, Atul Patel, Jeff Tenner, Drew Thorstensen, andRamesh Veeramala.

International Technical Support Organization, Poughkeepsie Center

Now you can become a published author, too!

Here’s an opportunity to spotlight your skills, grow your career, and become apublished 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 acceptanceand customer satisfaction, as you expand your network of technical contacts andrelationships. Residencies run from two to six weeks in length, and you can

participate either in person or as a remote resident working from your homebase.

Find out more about the residency program, browse the residency index, and

apply online at:

ibm.com/redbooks/residencies.html

Comments welcome

Your comments are important to us!

We want our books to be as helpful as possible. Send us your comments about

this book or other IBM Redbooks publications in one of the following ways:

Use the online Contact us review Redbooks form found at:

ibm.com/redbooks

Send your comments in an email to:

[email protected]

Mail your comments to:

IBM Corporation, International Technical Support Organization

Dept. HYTD Mail Station P099

2455 South RoadPoughkeepsie, NY 12601-5400

8199pref.fm Draft Document for Review November 20, 2013 5:11 pm

http://www.redbooks.ibm.com/residencies.html




http://www.redbooks.ibm.com/contacts.html

http://www.redbooks.ibm.com/contacts.html







xxii IBM PowerVC Introduction and Configuration

Stay connected to IBM Redbooks

Find us on Facebook:

http://www.facebook.com/IBMRedbooks

Follow us on Twitter:

http://twitter.com/ibmredbooks

Look for us on LinkedIn:

http://www.linkedin.com/groups?home=&gid=2130806

Explore new Redbooks publications, residencies, and workshops with the

IBM Redbooks weekly newsletter:

https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm Stay current on recent Redbooks publications with RSS Feeds:

http://www.redbooks.ibm.com/rss.html

Draft Document for Review November 20, 2013 5:11 pm 8199ch01.fm




https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm



https://www.redbooks.ibm.com/Redbooks.nsf/subscribe?OpenForm






© Copyright IBM Corp. 2013. All rights reserved. 1

Chapter 1. Introduction

IBM PowerVC is the next generation of enterprise virtualization management forPower Systems. With a powerful yet simple and intuitive graphical user interface

(GUI) and a deep integration with IBM PowerVM virtualization technologies, IBMPowerVC enables virtualization without limits for the Power Systems family of

servers running PowerLinux, IBM AIX and IBM i operating systems.

Before you continue you should be familiar and have some practical experiencewith the contents included in the following IBM Redbooks publications: IBM

PowerVM Virtualization Introduction and Configuration , SG24-7940, and IBMPowerVM Virtualization Managing and Monitoring , SG24-7590.

This book provides introduction and configuration information on IBM PowerVC.

You can go through the pages starting right here or just jump to whatever is thatyou are interested in. The following is a list of chapters describing IBM PowerVC

overview, positioning, planning, installation, and setup, including a labenvironment installation of the product:

IBM PowerVC overview

IBM PowerVC positioning and planning

IBM PowerVC installation

IBM PowerVC setup

1

8199ch01.fm Draft Document for Review November 20, 2013 5:11 pm



2 IBM PowerVC Introduction and Configuration

Note: IBM plans to support IBM Power Virtualization Center (PowerVC) tomanage systems running the IBM i operating system.




Chapter 1. Introduction 3

1.1 IBM PowerVC overview

IBM Power Virtualization Center (PowerVC) is designed to simplify themanagement of virtual resources in your Power Systems environment.

Once the product code is laid out, IBM PowerVC’s no-menus interface will guide

you through three simple configuration steps to register physical hosts, storageproviders, and network resources to start capturing and intelligently deploying

your virtual machines among other tasks shown in the following list:

Create virtual machines and then resize and attach volumes to them. Import existing virtual machines and volumes so they can be managed by

IBM PowerVC. Monitor the utilization of the resources that are in your environment. Migrate virtual machines while they are running (hot migration). Deploy images quickly to create new virtual machines that meet the demands

of your ever-changing business needs.

IBM PowerVC is built on OpenStack. OpenStack is an open source software thatcontrols large pools of server, storage, and networking resources throughout adatacenter. IBM PowerVC leverages IBM Platform Enterprise Grid Orchestrator

(EGO) to extend OpenStack set of technologies into Power Systemsenvironments with enhanced security, intelligent placement of virtual machines

and other advanced policy-based features required on enterprise clouds.

EGO is a proven technology used in Grid and scaled out environments by over2000 clients. Its open, extensible architecture supports policies such as

reservations, energy-aware, and over-subscription, as well as user-definedpolicies.

IBM PowerVC is available in two editions: IBM Power Virtualization CenterExpress Edition and IBM Power Virtualization Center Standard Edition.

Figure 1-1 on page 4 shows a graphic representation for IBM PowerVirtualization Center technology overview.





Figure 1-1 IBM PowerVC technology overview

1.2 IBM PowerVC Express Edition

IBM PowerVC Express Edition is intended for entry environments where virtualmachine hosts are POWER7® and POWER7+™ based IBM Power Systems

Express servers managed by the Integrated Virtualization Manager (IVM).

As a result only a single Virtual I/O Server per host is supported to accessstorage that can be deployed as storage area networks, local storage or a

combination. Supported hardware include:

IBM Storwize® V3700

IBM Storwize V7000

IBM SAN Volume Controller

IBM Integrated Virtualization Manager local storage

P ower SSP*

PowerVC System Admin Console

Nova API Cinder API Quantum API Keystone API Glance API

AMQPMessage Broker

QPID

Scheduler

Platform EGO

Policy Engine

Security Devices Image Registry

DataManagement

Servers Allocations

ImagesUser/Roles

/etc/config

Nova Compute

HMC Driver

Nova Compute

IVM Driver Quantum Service

Cinder DriversCinder Drivers

HMC

Power Systems

PowerVM

V M

Power Systems

PowerVM

Power Systems

PowerVMNetwor k

EMC*

SVC

SAN S witch

R E S T

R E S T

A M Q P

A M Q P

V M

V M

V M

V M

V M

C L I

C on t r ol l i n g S y s t em

M an a g e d S y s t em

Resource Managers Kernel Applications *PlannedKey





1.3 IBM PowerVC Standard Edition

IBM PowerVC is available in two editions: IBM Power Virtualization CenterExpress Edition and IBM Power Virtualization Center Standard Edition.

IBM PowerVC Standard Edition is aimed for enterprise class virtualization

environments where virtual machine hosts are POWER6®, POWER7 andPOWER7+ based IBM Power Systems servers managed by the Hardware

Management Console.

Dual Virtual I/O Server per host are supported to access storage and network.Virtual machines can also use NPIV attached storage. Supported hardware

include:

IBM Storwize V3700 IBM Storwize V7000

IBM SAN Volume Controller

1.4 OpenStack Overview

PowerVC is based on the OpenStack initiative. Before we actually go into the

heart and details of PowerVC, we would like to provide a high level ofunderstanding about OpenStack.

1.4.1 The OpenStack foundation

OpenStack is an Infrastructure as a Service (IaaS) solution applied to the cloudcomputing domain, lead by the OpenStack Foundation.

The OpenStack Foundation is a non-commercial organization, which purpose isto promote the OpenStack project and, help the developers within the OpenStackcommunity.

Many major information technology companies and actors do contribute to the

OpenStack Foundation.

You can find further information about the OpenStack foundation at:

http://www.openstack.org/foundation/

IBM is a major actor in the OpenStack community. Multiple IBM divisions have a

key role as a member of the OpenStack Foundation.







IBM contributes on a large number of levels to the OpenStack ecosystem andprojects via code contributions, governance and support within its products.

OpenStack is a free and open-source software released under the terms of theApache License.

1.4.2 OpenStack projects

OpenStack has a modular architecture based on various components andprojects. The current major components listed below are part of a non fixed andcontinuously extending list. The major projects for OpenStack are listed below.

Nova Manages the lifecycle and operations of hosts and computeresources.

Swift This is the OpenStack project for object oriented storage. It ismeant for distributed and high availability in virtual containers.

Cinder This is the project for the management for block storage within

OpenStack (Such as Storwize or San Virtual Controller in the IBMstorage offering).

Glance Is the image service which provides discovery, registration, and

delivery services for virtual disk images.

Horizon Dashboard project, Horizon is the web service management anduser interface to integrate the various OpenStack services.

Neutron Neutron is the network management service for OpenStack.Formerly named Quantum, Neutron includes various aspects such

has IP addresses management.

You can find a complete description of the main OpenStack projects on:

https://wiki.openstack.org/wiki/Main_Page

Other very important projects from OpenStack implemented in PowerVC arelisted below.

Keystone Security, identity, and authentication services.

ceilometer The ceilometer project is meant for metering, to provide

measurement and billing across all OpenStack components.







Figure 1-2 is an outlook of the OpenStack framework and main components.

Figure 1-2 Openstack framework

Nova (Compute)

Glance (Image Service)

APIs

OpenStack Shared Services

HARDWARE

Applications

Horizon(Dashboard)

Neutron (Networking)Swift (Object Storage)

Cinder (Block Storage)









Chapter 2. Plan

2.1 PowerVC positioning

Why IBM PowerVC? Why is there another virtualization management offering?When more than 70% of IT budgets are spent on operations and maintenance,there are must be new development efforts to reduce this cost and unleashinnovation within IT departments around the world.

IBM is introducing Power Virtualization Center to give Power Systems customers

out of the box virtualization management that accepts most all pre-existingvirtualization configurations as the starting point.

IBM PowerVC joins the PowerVM set of enterprise virtualization technologies toprovide a virtualization management solution that is deeply integrated with PowerSystems, is based on open standards and will be the building block of IBM

Infrastructure as a Service offerings based on Power Systems.

IBM Power Virtualization Center sits right between the Hardware ManagementConsole and IBM SmartCloud® Infrastructure as a Service (IaaS) offerings, to

provide a systems management product that our enterprise customers require toeffectively manage the advanced features offered by our premium hardware,

drive up resource utilization and manage workloads for performance andavailability.

2


Table 2 1 shows the ultimate set of platform and vir tualization management




Table 2-1 shows the ultimate set of platform and vir tualization managementsolutions for Power Systems used as the foundation for IBM SmartCloud

solutions that integrate PowerVM.

Table 2-1 Power Systems Virtualization Management Solutions

2.2 IBM Power Virtualization Center requirements

In this section we describe the hardware and software necessary for the IBMPower Virtualization Center on UNIX AIX and LINUX platforms.

The following are key prerequisites for IBM Power Virtualization Centerinstallation and configuration.

PowerVM Standard edition (5765-PVS); basic function

PowerVM Enterprise edition (5765-PVE); full function

IBM PowerVC will be available as two editions, Express and Standard. Express

will support IVM managed hosts for small deployments and Standard will support

Offering Solution Functions

SmartCloud Cloud management End-user self-service provisioning

Service catalog with virtual systems and

applications

Subscriber and account management

(multi-tenancy)

Delivered as IBM SmartCloud Entry, IBM

SmartCloud Provisioning and IBM

SmartCloud Orchestrator solutions

PowerVC Power Systems

virtualization management

Leadership solution for PowerVM

Intelligent virtual image management

and deployment

Resource pooling and dynamic virtual

management placement

On-going optimization and virtual

machine resilience

HMC Power Systems platform

management

PowerVM configuration and

virtualization setupHardware and firmware configuration

and controls

Service, support and update

management


HMC managed hosts for larger deployments IBM PowerVC can manage Linux



Chapter 2. Plan 11

HMC managed hosts for larger deployments. IBM PowerVC can manage Linuxon Power and AIX, running on Power hardware including Flex System POWER

compute nodes. IBM PowerVC (version 1.2.0) does not allow management ofIVM and HMC managed hosts in a single installation.

2.2.1 Hardware and software requirements

We describe the hardware and software and minimum requirements for the IBMPower Virtualization Center Express and Standard Editions.

2.2.2 IBM Power Virtualization Center Express.

The following information provides a consolidated view of the hardware and

software requirements for your IBM Power Virtualization Center Expressenvironment.

IBM PowerVC management and managed hostsTable 2-2 and Table 2-3 on page 12 describe the hardware, software andminimum requirements for IBM PowerVC Express edition.

Table 2-2 Hardware and OS requirements for IBM PowerVC Express

Host type Supported hardware Supported OperatingSystems (OS)

IBM PowerVC

management host

IBM Power

processor-based models:

IBM PowerLinux 7R1

and 7R2 servers IBM

POWER7 and

POWER7+ servers.

IBM System x®

servers that meet thefollowing minimum

requirements:

Processors - Intel or

AMD x64 processors

with 2 or more logical

cores and a speed of 2

Gigahertz. Memory -

10 Gigabytes. Hard

disk - 40 Gigabytes.

Red Hat Enterprise Linux

(RHEL), version 6.4 for

IBM Power or x86_64.


H S d h d S d O i




Table 2-3 Minimum resource requirements for the IBM PowerVC virtual machine

In addition, all hosts need to have Fibre Channel cards that are suitable forconnecting to the SAN switches.

Virtualization platformTable 2-4 on page 13 includes the vir tualization platform version requirement forIBM PowerVC Express edition.

Managed hosts IBM PowerLinux 7R1 and

7R2 servers. IBM

POWER7 and POWER7+

servers.

Notes: The hosts you

manage should be IBM

PowerLinux, POWER6, or

POWER7 and POWER7+

models and not a

combination.

Red Hat Enterprise

Linux 5.9 and 6.4

SUSE Linux Enterprise

Server (SLES), version

11 SP3

AIX, version 6.1 TL9

and AIX 7.1 TL3

System resource Amount

Processors Minimum: An uncapped shared processor

virtual machine with 1.0 processor unit of

entitled processing capacity and 2 virtual

processors. Recommended (one of the

following): An uncapped shared processor

virtual machine with a minimum of 2.0

processor units of entitled processing

capacity and 2 virtual processors. A virtual

machine with 2 dedicated processors.

Memory 10 Gigabytes

Hard disk 40 Gigabytes if you are using SAN storage

60 Gigabytes if you are using local storage

Tip: You must temporarily store ISO images before you import them into IBM PowerVC.

If you plan to store them temporarily on your IBM PowerVC virtual machine, then youmay need to create the virtual machine with more than the minimum 40 or 60 GB of hard

disk space. Choose the size based on the number and size of the ISO images that you

plan to import.

Host type Supported hardware Supported Operating

Systems (OS)


Table 2-4 Supported virtualization platforms for IBM PowerVC



Chapter 2. Plan 13

pp p

Network resourcesTable 2-5 describes the network infrastructure supported by IBM PowerVC

Express edition.

Table 2-5 IBM PowerVC-supported network hardware and software

Storage providersTable 2-6 shows hardware supported by IBM powerVC Express edition.

Table 2-6 IBM PowerVC-supported storage hardware

2.2.3 IBM Power Virtualization Center Standard

The following information provides a consolidated view of the hardware and

software requirements for IBM Power Virtualization Center Standard version.

Any IBM system that includes an IBM POWER6, POWER7, or POWER7+processor on a Power Server or PureFlex™ Foundation (build to order) that ismanaged through HMC.

Platform Requirement

Virtual I/O Server (VIOS) Version 2.2.2.1 or later

Item Requirement

Network switches that are supported by

IBM PowerVC

Any entry-level IBM or Cisco switch that

supports VLAN tagging

Note: IBM PowerVC does not manage network switches.

Item RequirementStorage systems that can be managed by

IBM PowerVC.

Version 6.4 or higher of IBM Storwize

V3500 (China only), V3700, and V7000,

and SAN Volume Controller (SVC).

Storage area network (SAN) switches that

are supported by IBM PowerVC

IBM System Networking SAN24B-5

Note: IBM PowerVC Express Edition does not manage network switches, but supports

network configurations that use VLAN-capable switches. Standard Edition supportsmanagement of SAN switches.


IBM PowerVC management and managed hosts




g gTable 2-7 and Table 2-8 on page 15 describe the hardware, software, and

minimum requirements for IBM PowerVC Standard edition.

Table 2-7 Hardware and operating system support for IBM PowerVC hosts

Host type Supported hardware Supported operating

systems

IBM PowerVC

management host

IBM Power

processor-based models:

IBM POWER7 and

POWER7+

processor-based

blades.

IBM Flex System™

Power Architecture®

compute nodes.

IBM System x servers

that meet the following

minimum

requirements:

Processors: Intel or

AMD x64 processors

with 2 or more logical

cores and a speed of 2Gigahertz.

Memory: 10

Gigabytes.

Hard disk : 40

Gigabytes.

Red Hat Enterprise Linux

(RHEL), version 6.4 for

IBM Power or x86_64

Managed hosts IBM POWER6,

POWER6+™,

POWER7, and

POWER7+

processor-based

servers.

IBM POWER6 and

POWER7

processor-based

blades. IBM Flex

System Power

Architecture compute

nodes.

Red Hat Enterprise

Linux5.9 and 6.4

SUSE Linux Enterprise

Server (SLES), version

11SP3

AIX, version 6.1 TL9

and 7.1 TL3

Tip: The IBM PowerVC management host will recommend to have at least200 Maximum Virtual Adapters configured on each VIO server.


Table 2-8 Minimum resource requirements for the IBM PowerVC virtual machine



Chapter 2. Plan 15

Hardware Management ConsoleTable 2-9 shows HMC version and release requirements to support IBMPowerVC standard edition.

Table 2-9 HMC requirements

Virtualization platformTable 2-10 includes Virtual I/O version requirement for IBM PowerVC Standard

edition.

Table 2-10 Supported virtualization platforms

Network resourcesTable 2-11 on page 16 describes the network infrastructure supported by IBM

PowerVC Standard edition.

System resource Power Systems System x

Processors Minimum: An uncapped

shared processor virtual

machine with 1.0

processor unit of entitled

processing capacity and 2

virtual processors.

Recommended (one of the

following): An uncapped

shared processor virtual

machine with a minimum of

2.0 processor units of

entitled processing

capacity and 2 virtualprocessors. A virtual

machine with 2 dedicated

processors.

Intel or AMD x64 with two

or more logical cores each

with a speed of 2

Gigahertz.

Memory 10 Gigabytes 10 Gigabytes

Hard disk 40 Gigabytes 40 Gigabytes

Item Requirement

Software level Version 7.7.8 or later

Platform Requirement

Virtual I/O Server (VIOS) Version 2.2.3 or later


Table 2-11 Supported network hardware and software




Storage providersTable 2-12 shows hardware supported by IBM PowerVC Standard edition.

Table 2-12 Supported storage hardware

SecurityTable 2-13 includes security features supported.

Table 2-13 Supported security software

2.2.4 Planning Information

Direct customer support

For technical support or assistance, contact your IBM representative or visithttp://www.ibm.com/support

Item Requirement

Network switches IBM PowerVC does not manage network

switches, but supports network

configurations that use VLAN-capable

switches.

Virtual networks Supports Shared Ethernet Adapters for

virtual machine networking

Item Requirement

Storage systems Version 6.4 or higher of IBM Storwize

V3500 (China only), V3700, V7000, and

SAN Volume Controller (SVC).

Storage area network (SAN) switches Can manage the IBM System Networking

SAN24B-5 and SAN48B-5 switches.

Attachments NPIV-capable Fibre Channel - required for

storage controllers.iSCSI is not

supported.

Item Requirement

Lightweight Directory Access Protocol

(LDAP) server (optional).

All versions of OpenLDAP


Packaging

http://www.ibm.com/support

http://www.ibm.com/support



Chapter 2. Plan 17

The IBM PowerVC Standard and Express Editions contain DVD that include

product installation documentation and files. Your Proof of Entitlement (PoE) forthis program is a copy of a paid sales receipt, purchase order, invoice, or other

sales record from IBM or its authorized reseller from whom you acquired the

program, provided that it states the license charge unit (the characteristics ofintended use of the program, number of processors, number of users) andquantity acquired.

Software MaintenanceThis software license offers Software Maintenance, previously referred to asSoftware Subscription and Technical Support.

Processor core (or processor)Processor Core (or Processor) is a unit of measure by which the program can belicensed. Processor Core (or Processor) is a functional unit within a computing

device that interprets and executes instructions. A processor core consists of atleast an instruction control unit and one or more arithmetic or logic unit. With

multi core technology, each core is considered a Processor Core. Entitlementsmust be acquired for all activated Processor Cores available for use on theserver.

In addition to the entitlements required for the program directly, licensee mustobtain entitlements for this program sufficient to cover the processor coresmanaged by program.

A Proof of Entitlement (PoE) must be acquired for all activated processor cores

available for use on the server. Authorization for the IBM PowerVC Express &Standard Editions program is based on the total number of activated processors

on the machines running the program and the activated processors on themachines being managed by the program.

LicensingIBM International Program License Agreement including the License Informationdocument and Proof of Entitlement (PoE) govern your use of the program. PoEsare required for all authorized use.

This software license includes Software Subscription and Support (also referred

to as Software Maintenance).


2.3 IBM PowerVC Storage Access Planning




To plan for configuration of SAN and storage in IBM PowerVC, the following initialsteps has to be done:

Configuration of the Fibre Channel fabric for the IBM PowerVC environmentshould be planned first - cable attachment, SAN fabrics, redundancy. Bestpractice would be to create at least two independent fabrics to provide best

redundancy.

All Virtual I/O Servers that will be managed by IBM PowerVC will provideshared storage base for Vir tual Machines. In IBM PowerVC Standard, the

storage is accessed via NPIV. In IBM PowerVC Express, the storage accessis by vSCSI LUN mapping.

In IBM PowerVC Standard, it is possible to further distinguish by whichparticular Fibre Channel ports will Virtual I/O Servers access StorageControllers. Proper cable connections to individual fabrics should be in place.

Plan for initial configuration for the SAN switches. Administrator user ID andpassword should be setup to be used by IBM PowerVC.

Plan for initial configuration of the storage controller. This configuration

includes setting up user authentication and creating volumes for first VirtualMachines.

In IBM PowerVC Express, initial zoning should be in place to provide accessfrom Virtual I/O Servers to Storage Controllers.

In IBM PowerVC Standard, initial setup for first VM should be in place. The

preparation steps involve:

– Virtual I/O Server must be setup for NPIV to provide virtual FC accessfrom VM to the SAN (vfcmap command in Virtual I/O Server).

– SAN zoning to provide access from virtual FC ports in VM to StorageControllers must be prepared.

– First LUN for successful installation of OS in the first VM (that will be later

on-boarded to IBM PowerVC Standard) must be prepared on Storage andmasked to virtual FC ports in VM.

With access to storage controllers and switches, IBM PowerVC Standard doesthe following:

collect inventory on fibre channel fabric

collect inventory on storage devices (pools, volumes)

monitor for health

detect misconfigurations


manage zoning

LUN d i



Chapter 2. Plan 19

manage LUNs on storage devices

manage masking of LUNs on storage devices

manage snapshots on storage devices

manage LUN copy operations on storage devices

IBM PowerVC Express manages Storage Controllers but does not manage SAN

switches.

Storage access in IBM PowerVC ExpressThe following Figure 2-1 on page 20 shows how VMs in IBM PowerVC Expressaccess storage. IBM PowerVC Express uses vSCSI for access to storage.

A description of the flow of storage management from physical Storage LUNs to

VMs in IBM PowerVC Express follows:

LUNs are provisioned on a supported Storage Controller

LUNs are masked to IVM Fibre Channel ports and are discovered as hdisk

logical devices in IVM

LUNs are mapped (mkvdev) from IVM to VMs over vSCSI virtual adapter pair


These steps are done automatically by IBM PowerVC Express. No zoning isinvolved, because individual VM do not access physical LUNs directly over SAN.




involved, because individual VM do not access physical LUNs directly over SAN.

Figure 2-1 IBM PowerVC Express Storage™ Access

Storage access in IBM PowerVC StandardThe following Figure 2-2 on page 21 shows how VMs in IBM PowerVC Standardaccess storage.

A description of the flow of storage management from physical Storage LUNs toVMs in IBM PowerVC Standard follows:

access to SAN from VMs is configured on Virtual I/O Servers using FCadapter pair and NPIV (vfcmap)

LUNs are provisioned on a supported Storage Controller

LUNs are masked to VMs virtual Fibre Channel ports

SAN zoning is adjusted so that VMs have access from their virtual FC ports to

Storage Controller host ports. Changes in zoning are done automatically byIBM PowerVC Standard, because individual VM access physical LUNsdirectly over SAN.

IBM PowerVC Express

SAN

IVM (VIOS)

AIX

Linux

Storage

vSCSI

vSCSI

IBM Power Server

PowerVC Express

manages IVM and Storage

PowerVC Express

instructs IVM

to map LUNs to VMs

by vSCSI

Zoning must be

done manualy,

zones are:

Storage host ports

to VIOS FC ports

PowerVC Express

manages LUNs and LUN

masking on storage,

LUNs are masked to VIOS

FC ports


LUNs and are discovered as logical devices in VMs



Chapter 2. Plan 21

These steps are done automatically by IBM PowerVC Standard.

Figure 2-2 IBM PowerVC Standard Storage Access

2.3.1 Storage Connectivity Groups and Tags in IBM PowerVC

Standard

IBM PowerVC Standard uses Storage Connectivity Groups and Tags. IBMPowerVC Express does not include concept of connectivity groups and tags.

Storage Connectivity GroupsA Storage Connectivity Group is a set of Virtual I/O Servers that have access tothe same storage controllers. It can span several host systems in IBM Power

Server landscape managed by IBM PowerVC Standard.

When a new Virtual Machine is deployed from an image, a Storage ConnectivityGroup must be specified and the Virtual Machine will belong to that StorageConnectivity Group. A virtual machine can be deployed only to IBM Power

IBM PowerVC Standard

Brocade SAN

AIX/Linux

Storage

Virtual FC

HMC

IBM Power Server

VIOS 2

Virtual FC

VIOS 1

PowerVC Standardmanages Storage, SAN

and VIOSes (via HMC)

PowerVC Standard

instructs VIOSto map virtual FC

to VMs (NPIV),

dual VIOS config uration

is supported

PowerVC Standard

manages SAN zoning

zones are:

Storage host ports

to VM virtual FC ports

(NPIV)

PowerVC Standard

manages LUNs and LUNmasking on storage,

LUNs are m asked directly

to VM


Systems hosts that contain at least one Virtual I/O Server that is part of thestorage connectivity group. In another words, by using specific SCG, it is




determined which hosts (through its Virtual I/O Servers) are eligible to deploy theVirtual Machine.

Also a Virtual Machine migrate operation is only supported within the specified

storage connectivity group. IBM PowerVC will ensure that the source anddestination servers have access to the required storage controllers and LUNs.

The Figure 2-3 shows an overview of Storage Connectivity Group (SCG)

technology. It shows two IBM Power System servers each with three Virtual I/OServers. Two Virtual I/O Servers from each server are part of Production SCGand one Virtual I/O Server from each server is part of Development SCG.

Figure 2-3 Storage Connectivity Groups

Storage Port TagsA further concept in IBM PowerVC Standard - Storage Port Tags - allows

arbitrary tags to be placed on fibre channel ports. A storage connectivity groupcan be configured to connect only through Fibre Channel ports with a specific

tag.

IBM Power Systems Server A

Hypervisor

VM1 VM2 VM3

vSCSIvSCSI

IBM Power Systems Server B

Hypervisor

VM4 VM5 VM6

vSCSIvSCSI

Production

VIOS A2VIOS A1

FC FC FC F C

Production

VIOS B2VIOS B1

FC FC FC FC

Dev

VIOS A3

FC FC

Dev

VIOS B3

FC FC

Redundant

production SAN Development SAN

Production SCG

Development

SCG


You can also specify which fabric each port is connected to a specific SAN fabricby assigning a tag such name that will be the same as fabric name or purpose

( )



Chapter 2. Plan 23

(for example Production1, Production2, Development_locality, etc.).

The following Figure 2-4 shows possible usage of tags. There are two IBM PowerSystem servers, each having two Virtual I/O Servers. Each Virtual I/O Server has

three Fibre Channel ports. First two FC ports are tagged ProductionSCG and areconnected to redundant production SAN, the third port is tagged DevelopmentSCG

and is connected to development SAN. Client Virtual Machines that belong toboth Storage Configuration Groups (ProductionSCG and DevelopmentSCG)

share the same Virtual I/O Servers but do not share Fibre Channel ports.

Figure 2-4 Storage Connectivity Groups And Tags

The Virtual I/O Servers in a storage connectivity group provide storage

connectivity to a set of Vir tual Machines that have common requirements. Anadministrator can use several approaches to configure Storage Connectivity

Groups, the Figure 2-5 on page 24 shows possible scenarios:

Uniform - all Virtual Machines use all Virtual I/O Server servers and all FibreChannel ports

IBM Power Systems Server A

Hypervisor

VM1 VM2 VM3

vSCSIvSCSI

VIOS A1

FC FC FC

Redundant

production SAN Development SAN

VIOS A2

FC FC FC

IBM Power Systems Server B

Hypervisor

VM4 VM5 VM6

vSCSIvSCSI

VIOS B1

FC FC FC

VIOS B2

FC FC FC

Development

SCG

Production

SCG




2.3.2 Storage Templates

St t l t i t t id d i i t t d fi d t



Chapter 2. Plan 25

Storage template is a concept to provide administrator-defined storage

configuration to use when creating a new disk. Disk size is not part of thetemplate. Storage Template concept is the same in IBM PowerVC Standard and

IBM PowerVC Express. Here is the information that is included in a template: name of the storage template

storage provider

storage pool within storage provider

thin or thick (full) allocation (full allocation can be chosen by selecting Generictype of volume)

If Thin Provisioned is selected, advanced settings will become available:

– Real capacity% of Virtual Capacity - determines how large space for thevolume will be allocated immediately after creating the volume.

– Automatically Expand - check box yes or no. Prevents the volume fromusing up all of its capacity and going offline. As a thin-provisioned volume

uses more of its capacity, this feature maintains a fixed amount of unusedreal capacity, called the contingency capacity.

– Warning threshold - when real capacity reaches given percentage of

virtual capacity a warning alert is sent.

– Thin provisioned grain size - Grain size can be selected in the range 32KBto 256KB. Grain is a chunk used for allocating space. The grain size

affects the maximum virtual capacity for the volume. Generally, smallergrain sizes save space but require more metadata access, which canadversely impact performance. The default grain size is 256 KB, and is the

strongly recommended option. The grain size cannot be changed after thethin-provisioned volume has been created. With grain size of 32KB, the

volume size cannot exceed 260,000 GB.

A storage template is then selectable during volume creation operations.


The following Figure 2-6 on page 26 shows a dialogue that will be presented toan IBM PowerVC administrator when defining advanced settings during a

thin-provisioned storage template definition




thin-provisioned storage template definition.

Figure 2-6 Storage Template definition - Advanced Settings

2.4 Users and groups planning

Default configuration for users and groups are managed by the operating system

and is reflected immediately in IBM PowerVC.


2.4.1 Users management planning

When you install the IBM PowerVC by default it is configured to use the security



Chapter 2. Plan 27

When you install the IBM PowerVC, by default it is configured to use the security

features of the operating system on the management host. This configuration setthe root operating system user account as the only available account with access

to the PowerVC server.

System Administrator must create a new operating system user account toreplace root user account in IBM PowerVC management host configuration. For

more information about how to add, modify or remove users go to “Operatingsystem user account management” on page 27

The user account planning is important to define standard accounts. In additiondefine the process and requirements to manage these accounts. IBM PowerVCmanagement host can manage users account using the operating system

security tools or can be configured to use the services provided by a Lightweight Directory Access Protocol (LDAP)

Operating system user account managementEach user is added, modified or removed by the system administrator on the

operating system and becomes available in IBM PowerVC. It is accomplishedusing the operating system commands.

Users managed by the operating system require some experience using

command lines but are easy to maintain. There is no dependency with otherserver or service and the accounts are shown instantly in the IBM PowerVC

console.

Important: IBM PowerVC management host stores data in IBM DB2®. Whenthe installation of IBM PowerVC is complete, an operating system user

account is created for the main DB2 process to run under. This user account is pwrvcdb. Do not remove or modify this user.


To see user accounts in the IBM PowerVC management hosts click on Users inthe upper black bar with the IBM logo, as shown in Figure 2-7 on page 28.

http://-/?-

http://-/?-

http://-/?-

http://-/?-




Figure 2-7 Users account view on the IBM PowerVC management host

System Administrator of IBM PowerVC management host must replace the

default root user account configuration. After that adding the new user accountto the admin group in the operating system and then removing root from thisgroup.

Adding users accounts with administrator role

To add a new user account to the operating systems on the IBM PowerVC

management host, run as root the command

useradd [options] login_name

Using the command shown in the Example 2-1 you create the user admin, with/home/admin as the home and base directory, the viewer group as the maingroup and a comment with additional information like “PowerVC”

Example 2-1 Adding admin user account with the useradd command

useradd -b /home/admin -c "PowerVC" -d /home/admin -g viewer -madmin


When the user is created, click on the Refresh button inside the Users tab onthe IBM PowerVC management host to see the changes, as shown in Figure 2-8

on page 29.



Chapter 2. Plan 29

Figure 2-8 Refresh users account view on the IBM PowerVC management host


The new user is created with viewer role in the IBM PowerVC management hostbecause it is part of the viewer users group. Double click on the admin user

account to see detailed information, as shown in Figure 2-9.




Figure 2-9 Detailed user account information

Update users accounts

To update an user account in the operating systems on the IBM PowerVCmanagement host, run as root the command

usermod [options] login_name

Using the command shown in the Example 2-2 you update the admin useraccount. The new comment is “IBM Power VC admin user account” and youmove it at the same time to the admin users group

Example 2-2 Updating admin user account with the usermod command

usermod -c "IBM Power VC admin user account" -g admin admin

Note: The useradd command has more options. If you need more informationabout the useradd command, please refer to the manual pages in your linux

distribution.


After this modification is done the admin user account becomes part of theadmin user groups and can manage the IBM PowerVC management host, as

shown in Figure 2-10.



Chapter 2. Plan 31

Figure 2-10 View updated user account information

Disable root user account

Remove the root user account from the admin users group in the IBM

management hosts. To do this run as root the command:

usermod -G root root

Remove users accounts

To remove an user account in the operating systems on the IBM PowerVCmanagement host, run as root the command

userdel [options] login_name

Tip: You can use the Enabled check box to enable or to disable the user

account in the IBM PowerVC management console. This will not affect theuser account to log in to the systems using another method, like telnet or ssh.

Note: The usermod command has more options. If you need more information

about the usermod command, please refer to the manual pages in your linuxdistribution


Using the command shown in the Example 2-3 you remove the admin useraccount from the IBM PowerVC management hosts.

Example 2-3 Delete an user account




Example 2 3 Delete an user account

userdel -r admin

Lightweight Directory Access Protocol (LDAP)

LDAP is an open standard for accessing global or local directory services over anetwork and/or the Internet. A directory can handle as much information as you

need but commonly is used to associate names with phone numbers and mailaddresses.

LDAP is a client server solution. The client request for information and the server

answers this requests. LDAP could be used as an authentication server. Thisapproach need more maintenance and another server to install and configure

LDAP.

IBM PowerVC can be configured to query an LDAP server for authenticationinstead of operating system users accounts authentication

Selecting the authentication methodYou should have to select the authentication method and plan the accounts

needed in advance. We recommend to use the operating system authenticationmethod to manage the users accounts. Most of the IBM PowerVC installations

can be managed using this method.

Use LDAP authentication method only if you already have an LDAP serverinstalled and configured and your domain is complete and accurate. Some

complex and large installation can be benefited using LDAP authenticationmethod. This is part of the security planning. IBM PowerVC do not require LDAP,

it is supported but not mandatory

Note: The userdel command has more options. If you need more informationabout the userdel command, please refer to the manual pages in your linux

distribution

Link: For more information about OpenLDAP visit

(http://www.openldap.org/)

http://www.openldap.org/

http://www.openldap.org/




IBM PowerVC management host can display the user accounts belonging toeach group. To see this, log in to the IBM PowerVC management host and click

on Users on the upper black bar with the IBM logo, then click on the Groups tab.See Figure 2-11 for reference




See Figure 2 11 for reference.

Figure 2-11 Users groups view on the IBM PowerVC management host


This view display the three defaults groups. To access detailed information foreach group, double click on the desired group. See Figure 2-12 on page 35 for

reference



Chapter 2. Plan 35

Figure 2-12 Detailed view of viewer users group on management host

2.5 Security management planning

IBM Power Virtualization Center provides security services that support a secure

environment.

IBM Power Virtualization Center provides the following security services:

– LDAP support for authentication and authorization information (users andgroups).– Apache HTTPD configured as the web server provides HTTPS support for

managing resources.– Host key and certificate verification of Hosts, Storage, and Switches– Commands to encrypt and decrypt passwords, tokens, audit records, and

other persisted strings.– Audit logs are recorded and available


2.5.1 Ports used by IBM Power Virtualization Center

This topic lists the ports used by IBM PowerVC management hosts for inbound

and outbound traffic. This topic also lists the local ports used by IBM PowerVC




a d outbou d t a c s top c a so sts t e oca po ts used by o e Cmanagement host. The management host is configured during installation, and

the host should be reserved for IBM PowerVC and the operating system onwhich it runs. No additional software should be installed on the managementhost . When IBM PowerVC is installed, the installation opens ports 80 and 443 forinbound and outbound traffic. If a firewall is configured on the management hostthe installer change the firewall configuration to allow ports 80 and 443 access.

Table 2-14 displays the ports used by Apache Web Server.

Table 2-14 Ports used for inbound and outbound communication

Table 2-15 displays the ports used by the services running on the Hardware

Management Console, the Integrated Virtualization Manager and the StorageVolume Controller.

Table 2-15 Ports used by HMC, IVM and SVC with IBM PowerVCt

Table 2-16 displays additional ports used by the services running on IBM

PowerVC management host.

Table 2-16 Additional ports used by IBM PowerVC to connect

Usage Port Protocol

Apache HTTPD Web Server 80 (optional) HTTP

Apache HTTPD Web Server 443 (required) HTTPS

Usage Port Protocol

IVM 22 SSL

SVC 22 SSL

HMC 12443 HTTPS

Usage Port

EGO 7870

DB2 50110

NOSQL support for DB2 27017

Keystone 443

Keystone admin 443


Glance 9292

Nova 8774

Usage Port



Chapter 2. Plan 37

2.5.2 Providing a certificate

Self-signed certificates are certificates that you create yourself for private use.After you create a self-signed certificate, you can use it immediately. Becauseanyone can create self-signed certificates, they are not considered publicly

trusted certificates. You can replace default, expired, or corrupted certificateswith a self-signed certificate. You must delete the default certificate before you

complete this procedure.

IBM Power VC management hosts is installed with a default self signedcertificate and a key. The certificates are installed in the following locations:

/etc/pki/tls/certs/localhost.crt/etc/pki/tls/private/localhost.key

After you install IBM PowerVC, you can replace the default self-signed certificate

with a certificate of your own. You must restart IBM PowerVC after you replacethe default certificate. This new certificate can be requested from a certificateauthority (CA). The certificate request can include the following information:

– Key size: determines strength of cryptographic keys for certificate.– Certificate label: the certificate with a unique string of characters.– Common name: the fully qualified host name of the server for which the

certificate is being created.– Organization name: the company that uses this certificate.

– Locality or city: the city or a locality designation for your organization.– State or province: the state or province in which you use this certificate.

– Country or region: identifies, with a two-letter designation, the country, orregion in which you use this certificate.

Nova 8774

Cinder 9000

Neutron 9696

Validator 8428

Ceilometer 8777

Bumblebee 5470


2.6 Hosts and clients management planning

When you plan for the hosts in your IBM Power Virtualization Centerenvironment you need to consider the HMCs that manage your hosts and the




environment, you need to consider the HMCs that manage your hosts and thebenefits of using multiple Virtual I/O Servers.

2.6.1 Hardware Management Console Planning

Advanced installations typically use redundant HMCs to manage the hosts.

Consider which HMC and hosts you want IBM PowerVC to manage. IBMPowerVC only supports one HMC managing any particular host. Redundant

HMCs are not supported. If the HMC that you select for IBM PowerVC becomesunavailable, the hosts cannot be managed by IBM PowerVC.

2.6.2 Multiple Virtual I/O Servers planning

Plan more than one Vir tual I/O Server if you want a failover Virtual I/O Server orexpanded Virtual I/O Server functionality. IBM PowerVC provides the option to

utilize more than one Virtual I/O Server. Consider a second redundant Virtual I/OServer to provide redundancy and reliability to the hosts. Having two Virtual I/OServers avoid outages to the hosts when you need to perform maintenance,

updates or changes in the configuration.

2.7 Storage management planning

IBM Power Virtualization Center manages storage volumes, which can beattached to virtual servers. These storage volumes can be on IBM Storwize or

SAN Volume Controller (SVC) devices. PowerVC uses the term storage providerfor any system that provides storage volumes.

2.7.1 Possible storage configurations

PowerVC can manage any number of supported devices. In this example, thereare two storage devices; an external storage device used for development, and

one used for production. It is important that your virtual machines can access thenecessary storage.

IBM PowerVC assumes that all host systems that can access external storagecontrollers have access to the same external storage controllers. Additionally,


when a virtual server is deployed, you can only deploy to a host system that canconnect to the storage on which the deployment image resides.

The administrator can define storage connectivity groups to further constrain theselection of host systems Storage connectivity groups can be used to group host



Chapter 2. Plan 39

selection of host systems. Storage connectivity groups can be used to group hostsystems together, for example, the administrator could define “Production” and

“Development” groups. They can also be used to manage systems that containmultiple VIOS pairs, to direct deployments to a specific pair.

Default storage connectivity groups are automatically created. When a new

virtual machine is deployed from an image, a storage connectivity group must bespecified. The server will be deployed only to a host that contains at least oneVIOS that is part of the storage connectivity group. Similarly, if you want to

migrate a virtual machine, it can only be migrated within the specified storageconnectivity group. This lets you ensure that the source and destination servers

have access to the required storage controllers; for the list of supported storagecontrollers; please see 2.3, “IBM PowerVC Storage Access Planning” on

page 18.

2.7.2 Specifying fibre channel ports

Storage connectivity groups that share a VIOS can use different physical FibreChannel ports on the VIOS. The IBM PowerVC administrator achieves this by

assigning storage port tags to physical fibre channel ports on the desired VIOS.

These tags are labels that can be assigned to specific Fibre Channel ports

across your IBM Power Systems systems. A storage connectivity group can beconfigured to connect only through Fibre Channel ports that have a specific tag

when deploying with NPIV direct connectivity. For further information, refer to2.3.1, “Storage Connectivity Groups and Tags in IBM PowerVC Standard” on

page 21.

2.7.3 Storage volumes planning

When you register a storage provider with IBM PowerVC, a default storage

template is created for that provider. Storage templates let you specify propertiesof a storage volume, such as the storage provider and provisioning method.

When creating a new storage volume, you must select a storage template. All ofthe properties that are specified in the storage template are applied to the newvolume, which is created on the storage provider that is specified in the storage

template.


A storage template must also be specified when deploying a new virtual server tocontrol the properties of the virtual server's boot volume. PowerVC can manage

pre-existing storage volumes. You can select them when registering the storagedevice, or at any later time. Pre-existing storage volumes do not have an

associated storage template




associated storage template.

2.8 Networks management planning

A network represents a set of Layer 2 and Layer 3 network specifications, suchas how your network is subdivided using VLANs, as well as information about thesubnet mask, gateway, and other characteristics. When deploying an image, you

choose one or more existing networks to apply to the new virtual machine.

Setting up networks in advance reduces the amount of information that you needto input during each deployment and helps to ensure a successful deployment.

The first selected network is the management network that provides the primary

system default gateway address. You can add additional networks to divide upthe traffic and provide further functionality

2.8.1 Multiple networks planning

Each virtual machine that you deploy must have one or more networks. Using

multiple networks provides the ability to split traffic. There are commonly three

types of networks that IBM PowerVC management host use when deployingvirtual machines:

Data network This network provides the route over which workload traffic is sent. At least

one data network is required for each vir tual machine, and more than onedata network is allowed.

Management network

This type of network is optional but highly recommended to provide a higherlevel of functionality and security to the virtual machines. A management

network provides the Remote Monitoring and Control (RMC) connection

between the management node and the client LPAR.

Tip: Talk with your network administrator to gather detailed information of yournetworks infrastructure.




The Shared Ethernet Adapter that is chosen as the default is the one that has thesame network VLAN as the new network. If a Shared Ethernet Adapter with the

same VLAN does not exist, IBM PowerVC will choose as default the SharedEthernet Adapter with the lowest primary VLAN ID (PVID) that is in an available

state.




state.

Certain configurations might assure the assignment of a particular SharedEthernet Adapter to a network. For example, if the VLAN that you choose when

creating a network in IBM PowerVC is the PVID of the Shared Ethernet Adapteror one of the additional VLANs of the primary Virtual Ethernet Adapter, then thatShared Ethernet Adapter must back the network. No other options are made

available.

Plan more than one Vir tual I/O Server if you want a failover Virtual I/O Server or

expanded Virtual I/O Server functionality. IBM PowerVC supports the utilizationof virtual switches in the system. Use multiple virtual switches when you want toseparate a single VLAN across multiple distinct physical networks.

2.9 Templates planning and placement policy

IBM PowerVC management host is configured to manage virtual machines,storage and networks. It can be configured to deploy resources using templates.

Tip: Systems that make use of multiple Virtual Switches are supported.

Note: If you create a network, deploy virtual machines to use it, and then

change the Shared Ethernet Adapter to which that network is mapped, yourworkloads will be impacted. The network will experience a short outage while

the re-configuration takes place

Note: If a network is modified to use a different Shared Ethernet Adapter andthat existing VLAN is already deployed by other networks, those other

networks will move to the new adapter as well. To split a single VLAN acrossmultiple Shared Ethernet Adapters, you need to break those Shared EthernetAdapters out onto separate virtual switches.

Note: In environments with dual Virtual I/O Servers, the secondary Shared

Ethernet Adapter is not shown except as an attribute on the primary SharedEthernet Adapter


This templates can be deployed using the policy that best fit your businessrequirements.

2.9.1 Placement policy



Chapter 2. Plan 43

IBM PowerVC management hosts has two policies to deploy virtual machines Distribute virtual machines evenly across all hosts.

– Using this policy the new virtual machines will be distributed across all thephysical machines available in the infrastructure. This is know as striping .

Place virtual machines on a single host until it is fully utilized, then move on to

the next host.

– Using this policy the new virtual machines will be placed on a single host

until it is fully utilized or until the available resources do not met theminimum requested for the new virtual machine. This is also known as packing

2.9.2 Templates planning

IBM PowerVC management host provide standard templates to deploy newvirtual machines. This templates can be customized to accommodate them to

your business needs.

There are two different types of templates:

1. Compute Templates

– This templates are used to define memory, processing units and disk space. See 2.9.2, “Templates planning” on page 43 for further information.

Important: Default placement policy change does not affect existing virtual

machines. It will only take effects for new virtual machines deployed after thepolicy setting was changed

Tip: The following settings might increase the throughput and decrease theduration of deployments:

Use the striping policy instead of the packing policy.

Limit the number of concurrent deployments to match the number of hosts.


2. Storage Templates

– This templates are used to define storage settings such as a specificvolume type, storage pool, and storage provider . See 2.3.2, “Storage

Templates” on page 25 for further information.




Use the templates to deploy new virtual machines. This propagate the values for

all the resources into the vir tual machines, accelerating the deployment processand give a baseline for standardization.

Templates can be defined using the standard view or for more detailed and

specific configuration you can use the advanced view.

Compute Templates planningIBM PowerVC management host provide you five predefined compute templates.

Predefined templates can be edited and removed. In addition you can createyour own templates.

Before you can start creating templates check the resource availability. Forexample, you can have different templates for development, test and production

or may be you can have different templates for small, medium or high-endsystems or a mix of all.

Basic Templates planning

The information needed to plan basic templates is: Template Name: The name to show for the template

Virtual Processors: Amount of virtual processors. A virtual machinegenerally performs best if the number of virtual processors is close to the

number of processing units available to the virtual machine.

Memory (MB): Amount of memory in MB. The value for Memory must be amultiple of the memory region size configured on your host. Minimum value is

16. To see the region size for your host, open the properties windows for the

selected host into the Hardware Management Console, then open thememory tab and record the Memory Region Size. Figure 2-13 on page 48

display an example view for the memory region size.

Processing Units: Amount of entitled processing units. A processing unit is

the minimum amount of processing resource that the virtual machine is ableto consume. For example, a value of 1 (one) processing unit corresponds to

100% use of a single physical processor. Processing units are split betweenvirtual processors, so that a virtual machine with two virtual processors and

one processing unit would appear to the virtual machine user as a systemwith two processors, each running at 50% speed.

Disk (GB): Disk space needed in GB.


Compatibility mode: Select the compatibility needed for your virtualmachine. Table 2-17 on page 45 describes each processor compatibility

mode and the servers on which the virtual machines that use each processorcompatibility mode can successfully operate.



Chapter 2. Plan 45

Table 2-17 Processor compatibility Modes

Processor

compatibility modes

Description Supported servers

POWER5 The POWER5 processor

compatibility mode allows you

to run operating-system

versions that use all the

standard features of the

POWER5 processor.

Virtual machines that use

the POWER5 processor

compatibility mode can run

on POWER5, POWER6,

and POWER6+

processor-based servers.






POWER6 processor.

Virtual Machines that use

the POWER6 processor


on POWER6, POWER6+,

and POWER7


POWER6+ The POWER6+ processor





POWER6+ processor.


the POWER6+ processor


on POWER6+ and

POWER7


POWER6 enhanced The POWER6 enhanced

processor compatibility mode

allows you to run

operating-system versions

that use all the standard

features of the POWER6

processor and also providesadditional floating-point

instructions to applications

that use the POWER6

processor.


the POWER6 enhanced

processor compatibility

mode can run on POWER6



POEWER6+ enhanced The POWER6+ enhanced

processor compatibility mode

allows you to run


the POWER6+ enhanced


Processor

compatibility modes

Description Supported servers




allows you to run

operating-system versionsthat use all the standard

features of the POWER6+

processor and also provides

additional floating-point

instructions to applications

that use the POWER6+

processor.


mode can run onPOWER6+



compatibility mode allows youto run operating-system



POWER7 processor.


the POWER7 processorcompatibility mode can run

on POWER7


default The default processor

compatibility mode is a

preferred processor

compatibility mode that

enables the hypervisor todetermine the current mode

for the virtual machine. When

the preferred mode is set to

default, the hypervisor sets the

current mode to the most fully

featured mode supported by

the operating environment. In

most cases, this is the

processor type of the server

on which the virtual machine isactivated. For example,

assume that the preferred

mode is set to default and the

virtual machine is running on a

POWER7 processor-based

server. The operating

environment supports the

POWER7 processor

capabilities so the hypervisor

sets the current processorcompatibility mode to

POWER7.

The servers on which

virtual machines with the

preferred processor

compatibility mode of

default can run depend onthe current processor

compatibility mode of the

virtual machine. For

example, if the hypervisor

determines that the current

mode is POWER7, the

virtual machine can run on

POWER7



Restriction: A POWER6 processor cannot emulate all features of a POWER5

processor. Similarly, a POWER7 processor cannot emulate all features of a POWER6

or a POWER5 processor. For example, certain types of performance monitoring might

not be available for a virtual machine if the current processor compatibility mode of a

virtual machine is set to the POWER5 mode.



Chapter 2. Plan 47

Advanced Templates planning

The information required to plan advanced templates are:

Template Name: The name to show for the template

Virtual Processors: Amount of virtual processors. A virtual machinegenerally performs best if the number of virtual processors is close to the

number of processing units available to the virtual machine. You can specifythe following values:

– Minimum: The smallest number of virtual processors that you will accept

for deploying a virtual machine. If this value of virtual processor is notavailable, the deploy will not occur.

– Desired: The number of virtual processors that you want for deploying a

virtual machine.

– Maximum: The largest number of virtual processors that you will allow

when resizing a virtual machine. This value is the limit to resizedynamically. When it is reached you need to power off the virtual machine,

edit the profile, change the maximum to a new value and start de virtualmachine.

Memory (MB): Amount of memory expressed in MB. The value for Memory

must be a multiple of the memory region size configured on your host.

Minimum value is 16Mb. To see the region size for your host, open the properties windows for the selected host into the Hardware ManagementConsole, then open the memory tab to view the Memory Region Size.Figure 2-13 on page 48 display an example view for the memory region size.

– Minimum: The smallest amount of memory that you want for deploying avirtual machine. If the value of minimum memory is not available, the

deploy will not occur.

– Desired: The total memory that you want in the virtual machine. The

deploy will occur with an amount of memory less or equal than desiredand greater or equal than minimum

Note: For detailed explanation about processor compatibility modes see IBMPowerVM Virtualization Introduction and Configuration , SG24-7940


– Maximum: The largest value for memory that you will allow when resizinga virtual machine. This value is the limit to resize dynamically. When it is

reached you need to power off the virtual machine, edit the profile, changethe maximum to a new value and start de virtual machine




Figure 2-13 Memory Region Size view on the HMC

Processing Units: Amount of entitled processing units. A processing unit is

the minimum amount of processing resource that the virtual machine is ableto consume. For example, a value of 1 (one) processing unit corresponds to100% use of a single processor.

– Minimum: The smallest number of processing units that you will accept fordeploying a virtual machine. If this value of virtual processor is not

available, the deploy will not occur.– Desired: The number of processing units that you want for deploying a

virtual machine. The deploy will occur with an amount of processing unitsless or equal than the desired value and greater or equal than the

minimum value

– Maximum: The largest number of virtual processors that you will allow

when resizing a virtual machine. This value is the limit to resizedynamically. When it is reached you need to power off the virtual machine,

edit the profile, change the maximum value to a new value and start devirtual machine.


Important: Processing units and vir tual processor are values that workclosely and must be calculated carefully. For more information about virtual

processor and processing units refer to IBM PowerVM Virtualization Managingand Monitoring , SG24-7590



Chapter 2. Plan 49

Disk (Gb): Disk space needed in Gb.

Compatibility mode: Select the computability needed for your virtual

machine. Table 2-17 on page 45 describes each processor compatibilitymode and the servers on which the virtual machines that use each processor

compatibility mode can successfully operate.

Shared processors or dedicated processor: You need to plan if the virtualmachine uses processing resources from a shared processor pool or uses

dedicated processor resources.

– Shared processors settings

• Uncapped: Uncapped virtual machines can use processing units that

are not being used by other vir tual machines, up to the number ofvirtual processors assigned to the uncapped virtual machine.

• Capped: Capped virtual machines can use only the number of

processing units that are assigned to them.

• Weight (0-255): If multiple uncapped virtual machines require unused

processing units, the uncapped weights of the uncapped vir tualmachines determine the ratio of unused processing units that areassigned to each virtual machine. For example, an uncapped virtual

machine with an uncapped weight of 200 receives two processing unitsfor every processing unit that is received by an uncapped virtual

machine with an uncapped weight of 100.

– Dedicated processors setting

• Idle sharing: This setting enable this virtual machine to share its

dedicated processors with other virtual machines when this virtualmachine is powered on and idle

Availability priority (0-255): To avoid shutting down mission-critical

workloads when your server firmware de-configures a failing processor, setavailability priorities for the virtual machines. A virtual machine with a failing

processor can acquire a replacement processor from a virtual machine with alower availability priority. The acquisition of a replacement processor allows

the virtual machine with the higher availability priority to continue running aftera processor failure.








3.1 Setting up the IBM Power Virtualization CenterStandard environment

Before you install IBM Power Virtualization Center, you must install Red HatEnterprise Linux into the management virtual machine Also PowerVC requires




Enterprise Linux into the management virtual machine. Also, PowerVC requires

certain packages to be installed. If the Red Hat Enterprise Linux “yum” repositoryis configured and enabled on the host, PowerVC installation will find and installthe required packages. Otherwise, you must manually install them.

3.1.1 Creating the virtual machine to host PowerVC

Figure 3-1 and Figure 3-2 on page 53 shows two screens with the profile

information needed for the creation of the IBM PowerVC virtual machine.

PowerVC 1.2 also supports the x86_64 environment.

Figure 3-1 Processors configuration for PowerVC

Important: The management vir tual machine must be reserved for PowerVC

and the operating system on which it runs. Do not install other software into it.




Chapter 3. Install 53

Figure 3-2 Memory configuration for PowerVC

3.1.2 Changing Maximum Virtual Adapters in VIOS server

The PowerVC management host will recommend to have at least 200 Maximum

Virtual Adapters configured on each VIO server.

Figure 3-3 Configure maximum virtual adapters

3.1.3 Downloading the RHEL 6.4 package

You can download the file on the website at:

http://www.redhat.com


3.1.4 Red Hat Linux Base Install

Note: Download the ppc file such as RHEL-6.4-ppc64-dvd.iso

http://www.redhat.com/

http://www.redhat.com/




When Installing Red Hat Enterprise Linux 6.4, install linux text mode to installbase rpms. For information, see the website

https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/index.html

3.1.5 Verify SELinux is Permissive or Disabled

IBM PowerVC will not run on a system that has SELinux set to enforcing mode.

you must have SELinux set to permissive or disabled mode. To verify yourselinux setting, check the /etc/selinux/config file (see Example 3-1) andensure the SELinux setting is not set to Enforcing. Otherwise, change the line as

shown here:

SELINUX=permissive

Example 3-1 How to set SELINUX mode

[root@localhost ~]# cat /etc/selinux/config"/etc/selinux/config" 13L, 458C# This file controls the state ofSELinux on the system.# SELINUX= can take one of these three values:# enforcing - SELinux security policy is enforced.

# permissive - SELinux prints warnings instead of enforcing.# disabled - No SELinux policy is loaded.SELINUX= permissive# SELINUXTYPE= can take one of these two values:# targeted - Targeted processes are protected,# mls - Multi Level Security protection.SELINUXTYPE=targeted

Note: RHEL installation Guide consists of three parts. see Chapter 2.

Chapter 1. x86, AMD64, and Intel64 - Installation and Booting

Chapter 2. IBM Power Systems - Installation and Booting

Note: You must reboot the server in order for the change to take effect


3.1.6 Setting default network interface

IBM PowerVC uses the default network interface: eth0. To use a different network

interface such as eth1, set the environment variable, HOST_INTERFACE , priorto running the install script. For example:








#export HOST_INTERFACE=eth1

3.1.7 Setting DNS, and host name

There are two options, either using DNS or working without DNS. but attentionmust be paid to correct setting of name resolution of all components that will be

managed by PowerVC.

No DNS environment present, make sure to that all hardware components are

correctly defined in you /etc/hosts file including the information for all thecomponents including vir tualization infrastructure, for example, SAN switcheshost name.

Domain Name Server (DNS) present environment, you must have all the mostnames for all the hardware components that you make your infrastructure on the

DNS, and both forward and reverse resolution need to work correctly. and hostname have to be consistent with the DNS. When we say all, means storage SANswitches, HMCs host name, and so on.Also, after setting the host name on

PowerVC, It is difficult to change the host name. Confirm the host name beforeinstalling PowerVC.

3.1.8 IBM Installation toolkit

IBM installation Toolkit is not a requirement for PowerVC installation.

3.2 Installing IBM Power Virtualization Center frommedia

This section describes how to install IBM PowerVC on your management hostusing install media.

Note: During writing this book, there were some problems running IBM

installation toolkit together with PowerVC. Therefore, our demo lab was setupwithout IBM installation toolkit in PowerVC management server.


3.2.1 Configuring the yum repository for the IBM PowerVC install

This section is an example illustrating how to configure the local yum repository

using Red Hat Enterprise Linux installation media so that the IBM PowerVCinstallation finds the required packages

1. Create the directory where the iso image will be mounted.




#mkdir -p /media/iso

2. Mount the Red Hat Enterprise Linux 6.4 iso image

#mount -o loop [your iso file location] /media/iso

3. Create a repo file that points to the Red Hat Enterprise Linux repo file on theiso image.

Example 3-2 How to set repository

# cat /etc/yum.repos.d/rhel64-media.repo

[rhel64media]name=RHEL 6.4 mediabaseurl=file:///media/isoenabled=1gpgcheck=0

4. Verify that yum is seeing the new repo file

Example 3-3 yum repolist

[root@powervca iso]# yum repolistrhel-source | 3.9 kB 00:00 ...rhel-source/primary_db | 2.9 MB 00:00 ...repo id repo name statusrhel-source Red Hat Enterprise Linux 6.4 3,357repolist: 3,357

3.2.2 Installing IBM PowerVC

1. Change the directory to the location of the installation script

2. Install PowerVC. use the commands shown in Example 3-4.

3. type 2 in here.

Example 3-4 powervc installation command

[root@powervcstd powervc-1.2.0.0]# ls /tmp/powervc-1.2.0.0/


bin install lap liblicense packages powervc.rsp[root@powervcstd powervc-1.2.0.0]# ./install

Select the offering type to install: 1 - Express (IVM support) 2 - Standard (HMC support)




9 - Exit

4. Accept license. type 1 in here.

Example 3-5 Accept the agreement

Extracting license contentInternational Program License Agreement

Part 1 - General Terms

BY DOWNLOADING, INSTALLING, COPYING, ACCESSING, CLICKING ON AN "ACCEPT"BUTTON, OR OTHERWISE USING THE PROGRAM, LICENSEE AGREES TO THE TERMS OFTHIS AGREEMENT. IF YOU ARE ACCEPTING THESE TERMS ON BEHALF OF LICENSEE,YOU REPRESENT AND WARRANT THAT YOU HAVE FULL AUTHORITY TO BIND LICENSEETO THESE TERMS. IF YOU DO NOT AGREE TO THESE TERMS,* DO NOT DOWNLOAD, INSTALL, COPY, ACCESS, CLICK ON AN "ACCEPT" BUTTON,OR USE THE PROGRAM; AND* PROMPTLY RETURN THE UNUSED MEDIA, DOCUMENTATION, AND

Press Enter to continue viewing the license agreement, or enter "1" toaccept the agreement, "2" to decline it, "3" to print it, "4" to readnon-IBM terms, or "99" to go back to the previous screen.

5. Installation script processing, as shown Example 3-6

Example 3-6 installing powervc

#######################################################################Starting the IBM PowerVC 1.2.0.0 Installation on:2013-10-23T12:35:22-04:00#######################################################################LOG file is /opt/ibm/powervc/log/powervc_install_2013-10-23-123514.logCleaning up temporary and support files.

6. Installation completed, as shown Example 3-7

Example 3-7 installation completed**********************************************************************


PowerVC installation successfully completed at2013-10-22T15:54:50-04:00. Refer to /opt/ibm/powervc/log/powervc_install_2013-10-22-151956.logfor more details.********************************************************************** Use a web browser to access IBM PowerVC at

h // ib




https://powervca.pwrvc.ibm.com

3.3 Uninstalling IBM Power Virtualization Center

This topic describes how to uninstall IBM PowerVC from your management host.The following procedure removes IBM PowerVC from the management host. It

does not remove or change anything in your environment that you created duringyou were using IBM PowerVC. Any Red Hat Enterprise Linux prerequisitepackages that are installed during the IBM PowerVC installation remain. Run the

following command with some options to uninstall IBM PowerVC.

/ opt/ibm/powervc/bin/powervc-uninstall -y -s

-y The optional -y parameter indicates that you are answering yes,confirming that you want to uninstall the product. Including -y willperform a silent uninstall.

-s The optional -s printer indicates that you want to save

configuration files. During the uninstall, configuration files will besaved to the following location:

/etc/opt/ibm/powervc/saved-data-<time stamp>.tgz

if there are some problem using powervc-uninstall, you run

[powervc install file folder]/install -u -f

-u Uninstall to attempt clean up of failed installation and exit.

-f Force uninstall in attempt to bypass failures.

Note: If you have some problems during installation, check the log at/opt/ibm/powervc/log/powervc_install_ [install date] .log


3.4 Consideration of installing virtual machinesmanaged by PowerVC

Now, PowerVC support only NPIV attachment of SAN volumes to virtualmachines. You must install the OS in NPIV attachment of SAN volumes. OS

specific install recommendations




specific install recommendations

3.4.1 Linux virtual machines

If you install linux, you can install as Example 3-8.

Example 3-8 How to install linux in NPIV attachment of SAN volumes

System has 256 Mbytes in RMA

Config file read, 221 bytesWelcome to the 64-bit Red Hat Enterprise Linux 6.4 installer!Hit <TAB> for boot options.Welcome to yaboot version 1.3.14 (Red Hat 1.3.14-41.el6)Enter "help" to get some basic usage informationboot: linux mpath

After installing a Linux operating system on virtual machines, install the IBM

Installation Toolkit. especially install the “RSCT utilities” and “RSCT core” tools.you can install all rpm package when you install “ibm-power-managed-rhel6” withits dependencies.

1. Install the IBM Installation Toolkit

[IBM Installation Toolkit directory]/install.sh

2. Make the repository for linux

3. install ibm-power-managed-rhel6.ppc64

yum install -y ibm-power-managed-rhel6.ppc64

4. check the rmc status, as shown in Example 3-9

Example 3-9 RSCT installation in Linux

[root@vmlnx01 ~]# lssrc -aSubsystem Group PID Status ctcas rsct 4352 active ctrmc rsct 4353 active

IBM.ServiceRM rsct_rm 4453 active IBM.DRM rsct_rm 4455 active IBM.ERRM rsct_rm inoperative




4




Chapter 4. IBM PowerVC Set up

The IBM PowerVC Setup chapter provides all required steps to define objects inIBM PowerVC and guides you how to manage IBM PowerVC Standard. It goes

through the steps to add hosts, storage, storage connectivity groups and tags,SAN, networks. Verification of IBM PowerVC environment is also covered.

It also describes in detail how to manage Virtual Machines. It describes IBMPowerVC Standard Virtual Machine onboarding, image capturing, deployment,Virtual Machine operations.

This chapter includes the following sections:

IBM PowerVC setup

Hosts setup

Storage and SAN Fabric setup

Storage port tags setup

Storage Connectivity Group setup

Networks setup

Storage templates setup

Storage volumes setup

Virtual machines onboarding Virtual machines operations


The information contained in this chapter is related to IBM PowerVC Standardbut most of the steps are common both for IBM PowerVC Standard and Express.

There are some differences in IBM PowerVC Express and they are covered inChapter 5., “IBM PowerVC Express Edition specifics” on page 155.





4.1 PowerVC setup

4.1.1 Introduction

Before you can start performing tasks in IBM PowerVC, you have to register the

resources that you want to manage. You can register a storage system and



Chapter 4. IBM PowerVC Set up 63

y g g g yhosts, and create networks to use when you deploy images. When you registerresources with IBM PowerVC, you make them available for use in performing

tasks within PowerVC, such as hosting vir tual machines or storing images ofcaptured virtual machines. It is very important that your environment meets all of

the hardware and software requirements and is configured correctly before youregister your resources.

4.1.2 Connecting to PowerVC

1. Access IBM PowerVC by opening your browser and typing

https://<ipaddress or hostname>/

Figure 4-1shows how to login to IBM PowerVC, given IP address is the IP

address of your PowerVC management host.


2. Log in as administrative user to IBM PowerVC.




Figure 4-1 PowerVC login screen

4.2 Hosts setup

When you add the hosts in your IBM Power Virtualization Center environment,you need to connect to the HMCs that manage your hosts. and, After hosts,storage and networks have been correctly configured in PowerVC, it is possible

to add a Vir tual Machine. Refer to 2.2.3, “IBM Power Virtualization CenterStandard” on page 13 for further references about supported hosts in IBM

PowerVC Standard Edition

To configure the hosts, follow these preliminary steps:

Configure IBM system that is managed through HMC.

Setup users accounts with administrator role in PowerVC. Refer to 2.4, “Usersand groups planning” on page 26 for further details.

Setup the host name, IP and an Operator userid for HMC.


After successful installation of PowerVC and first login as administrator user, theuser will be presented with Main page of IBM PowerVC. At the Main page, first

step is to add a host.

1. On the Main page, click Add Hosts to register a host with IBM PowerVC. TheFigure 4-2 shows the window.




Figure 4-2 PowerVC Login


2. When you register a host, you provide the name and credentials for HMC thatmanages the host. Click Add Connection and PowerVC will connect to HMC,

and read hosts information from it. The dialogue is shown in Figure 4-3.




Figure 4-3 HMC connection info

Note: Do not specify hscroot for the user ID. Instead, specify a user ID in the

Operator role.




4. The Figure 4-5 shows how powerVC window look like after successfullyadding hosts. To show host properties, click desired host.

Additional hosts can be added by clicking Hosts Add Host, the dialogue

about adding a new host will be the same like for the first host in steps 2) and3). If there are hosts in same HMC, you can choose the same HMC name.




Figure 4-5 PowerVC -Show managed hosts


5. The Figure 4-6 on page 69 shows the detailed host information.

After hosts, storage and networks have been correctly configured inPowerVC, it is possible to add a Virtual Machine by expanding the Virtual

machines section. Now, you can see the Manage Existing button inFigure 4-6 on page 69




Figure 4-6 host information, and the Virtual Machines

4.3 Storage and SAN Fabric Setup

When using external SAN storage with PowerVC, some preliminary steps need

to be done to prepare storage controllers and Fibre Channel switches before theycan be managed by IBM PowerVC.

PowerVC needs management access to the storage controller. When using user

authentication, the administrative user name and password for the storagecontroller must be setup. There is another option which is using cryptographickey pairs. For instructions to generate an use key pairs, see the documentation

for your device.


To configure the storage controller and SAN switch, follow these preliminarysteps:

Configure the Fibre Channel SAN fabric for the IBM PowerVC environment.

Connect the required Fibre Channel ports that are owned by the Virtual I/OServer (VIOS) and the storage controllers to the SAN switches.

Setup the hostnames, IP and administrator user ID and password for SANswitches.




Setup the hostnames, IP and the administrator user ID and password for

storage controllers.

Create volumes for initial Virtual Machines that will be later imported

(on-boarded) to PowerVC.

For reference about supported storage in PowerVC Standard and Express

editions, please see 2.2.1, “Hardware and software requirements” on page 11.

Basically, the following storage controller models are supported at the time of

writing this book:

IBM Storwize V3500 or Storwize V3700 external storage systems

IBM Storwize V7000

IBM System Storage® SAN Volume Controller

IBM System Networking Brocade switches are supported to be managed by

PowerVC Standard, the switches must support NPIV technology. PowerVCExpress does not manage Fibre Channel switches.

4.3.1 Add storage controller and SAN Fabric to PowerVC

After successful installation of PowerVC and first login as administrative user, theuser is presented with main page of PowerVC.

Note: Attention must be paid to correct setting of name resolution of

hostnames of fibre channel switches, storage controllers, HMC, and Virtual I/OServers that will be managed by PowerVC. Hostnames of those components

must exactly match names defined in DNS. Both forward and reverse DNSresolutions should work correctly before initial setup of PowerVC.


Here is a step by step walk through setting up storage and SAN fabric setup.

1. To add a storage controller, click Add Storage hot link and you will bepresented with dialogue that is shown in Figure 4-7 on page 71.

The required information is:

– Storage Controller name or IP address

– User ID/Password or Encryption key

Click Add Storage and PowerVC connects to the storage controller and




Click Add Storage and PowerVC connects to the storage controller andretrieve setup information from it.

Figure 4-7 IBM PowerVC Standard Add Storage

2. Next you are presented with information about pools that are configured onthe storage controller, you have to select the default pool for PowerVC tocreate LUNs. Figure 4-8 on page 72 shows the dialogue.

The required information is to select default pool

Click Add Storage and PowerVC finishes adding storage controller.





Figure 4-8 IBM PowerVC Standard Select Pool

3. Next step is to add fabric. IBM PowerVC automatically asks about fabric, clickAdd Fabric as shown in Figure 4-9.

Figure 4-9 IBM PowerVC standard Add Fabric

You have to fill information about first SAN switch that is to be added under

PowerVC control.

The required information is:

– Storage Controller name or IP address

– User ID/Password or Encryption key


Click Add Fabrics and PowerVC connects to the switch and retrieves setupinformation from it. The dialogue is shown in Figure 4-10




Figure 4-10 IIBM PowerVC Standard Add Fabric 2

The Figure 4-11 shows how PowerVC Storage screen looks like after

successfully adding first SAN storage controller and SAN switch (tab StorageProviders). To show managed SAN switches, click on Fabrics tab.

Figure 4-11 PowerVC - Show Storage Providers


Additional storage controllers can be added by clicking Storage StorageProviders tab Add Storage, the dialogue about adding a new storage

controller is the same like for the first storage controller in steps 1) and 2).

Additional SAN switches can be added by clicking Storage Fabrics tab Add Fabric, the dialogue about adding a new switch is the same like for the first

switch (Fabric) in step 3).

S




4.4 Storage port tags setup

The next step is the definition of IBM PowerVC Standard Fibre Channel port tags,

it is an optional setting. Individual FC ports in Virtual I/O Servers that aremanaged by PowerVC can be tagged with named labels. For discussion about

PowerVC Tags and Storage Connectivity Groups please refer to 2.3.1, “Storage

Connectivity Groups and Tags in IBM PowerVC Standard” on page 21.

For setting up tagging, please start from PowerVC main page and selectConfiguration Fibre Channel Port Configuration. You will be presented

with a dialogue shown in Figure 4-12 on page 75.

Note: Tagging is optional and not necessary if you do not plan to use thisfeature.


For each Fibre Channel adapter in all Virtual I/O servers managed by PowerVCyou are able to select a port tag (arbitrary name) and a switch to which this port is

connected (Fabric).




Figure 4-12 PowerVC Fibre Channel Port Configuration

4.5 Storage Connectivity Groups setup

The next step is to define IBM PowerVC Standard Storage Connectivity Groups

(SCG). A storage connectivity group is a set of Virtual I/O Server that haveaccess to the same storage controllers. For discussion about PowerVC Storage

Connectivity Groups please refer to 2.7, “Storage management planning” onpage 38. Setting up Storage Connectivity Groups is a mandatory step fordeployment of Virtual Machines in PowerVC.


For setting up Storage Connectivity Groups, please start from PowerVC mainpage and select Configuration Storage Connectivity Groups. You will be

presented with a dialogue shown in Figure 4-13 on page 76.




Figure 4-13 PowerVC Storage Connectivity Groups

Click Create and you will be presented with a dialogue. For the new StorageConnectivity Group, you have to input:

Name of the Storage Connectivity Group

Automatically add eligible Virtual I/O Servers to this group check box. Ifchecked, from now on, newly added Virtual I/O Servers are added to thisgroup if they have access to the same storage (Fabrics, Tags) as other

members of the group.




When the above information is completed, click Add Member, you will bepresented with the dialogue in Figure 4-14. You have to select which Virtual I/O

servers become members of the group. If a tag was previously selected, onlyeligible Virtual I/O Servers are available to select. After selecting Virtual I/O

servers, click Add Member. Selected Virtual I/O Servers are added to StorageConnectivity Group, then click Add Group and the group is created. Now thegroup is available for Virtual Machine deployment.




Figure 4-14 PowerVC Add Member to Storage Connectivity Group

4.6 Networks Setup

When creating a new Virtual Machine, you have to select a network. If thenetwork use static IP assignment, you have to select also a new IP address for


the Virtual Machine. For full description about networks in PowerVC, please referto 2.8, “Networks management planning” on page 40.

Here is how to create a network definition in PowerVC. From PowerVC mainpage, click Networks Add Network . You will be presented with the dialogueshown in Figure 4-15 on page 80.

The requested data to fill in when creating a network are: Network name

VLAN ID




VLAN ID

Dynamic or Static (select Dynamic if the IP addresses is to be assigned

automatically by DHCP server)

Subnet mask

Gateway

Primary/Secondary DNS

Shared Ethernet Adapter Mapping - select SEAs within Virtual I/O Serversthat have access to the given network and are configured with the proper

VLAN ID

After you click Add Network the network is created. From the Networks page thenetwork can be also Edit network (change networks parameters) and Delete network.

Keep in mind:

PowerVC will intelligently detect which SEA to use per host. Ypu simply needto verify that PowerVC made the right choice.

In the event that PowerVC made an incorrect choice about the SharedEthernet Adapter to use for a given host, you may change it at a later time.





Figure 4-15 PowerVC Defining a Network

Important: The Primary VLAN is the PVID attached to the SEA in the list.The VLAN you specify does not need to match the Primary VLAN

select SEA pair


4.7 Environment verification

Once you have finished adding hosts, storage providers and networks it is a goodtime to verify your PowerVM environment before trying to capture, deploy oron-board virtual machines.

Virtualization management function failures may occur when dependencies andprerequisite configurations are not met.

IBM PowerVC is designed to reduce the overall complexity of virtualization and




IBM PowerVC is designed to reduce the overall complexity of virtualization and

cloud management. It can check for all required dependencies and prerequisiteconfigurations and clearly communicate the failures. It can also accurately

pinpoint validation failures and remediation actions when possible. Figure 4-16 shows IBM PowerVC interface where you will start the verification process by

clicking the Verify Environment button and access the verification report clicking

on View Results.

Figure 4-16 IBM PowerVC interface while environment verification in process.


The environment validation function architecture allows to add and evolvevalidators to check solution specific environment dependencies and prerequisite

configurations. This architecture is intended to allow the evolution of the tool toimprove on performance, reliability and scalability of validation execution with

increase in number of endpoints, their configurations and their inter-connectivity.

4.7.1 Verification report validation categories

Once the validation process is done you will be able to access a report of the

results as shown in Figure 4-17 This report consists of a table with four columns




results as shown in Figure 4-17. This report consists of a table with four columnswhere you see the following values:

Status

System

Validation Category

Description

Figure 4-17 Verification Results view


The following list shows the validation categories you can see on this report anda description for the type of messages you should expect from each one those

categories:

Access and CredentialsValidation of reachability and credentials from the management

server to the PowerVC domain, including userid, passwords

and SSH keys for all resources.File System, CPU and Memory on Management Server

Minimum processing and storage requirements for the

PowerVC management server




PowerVC management server.

OS, Services, DatabaseThis category groups all messages regarding to the availability

of the service daemons needed for the correct operation andmessage passing on the PowerVC domain. Including operatingsystem services, OpenStack services, Platform EGO services

and DB2 configuration.

HMC Version Hardware Management Console software level and K2services are up and running.

Power Server resourcesPower Systems hosts when managed by the IBM. This

category is viewable from IBM PowerVC Express Edition.

HMC managed Power Server resources

Power Systems hosts when managed by an HMC. Validationmessages include operating state, PowerVM EnterpriseEdition enablement, PowerVM Live Partition mobility

capabilities, ability to run a VIOS, maximum number ofsupported Power Systems servers, firmware level and

processor compatibility. This category is viewable from IBMPowerVC Standard Edition.

Virtual I/O Server access, license, IVM Power Systems hosts when managed by the IVM. Validation

messages include operating state, PowerVM EnterpriseEdition enablement, PowerVM Live Partition mobilitycapabilities, ability to run a VIOS, maximum number of

supported Power Systems servers, firmware level andprocessor compatibility. This category is viewable from IBM

PowerVC Express Edition.

Virtual I/O Server count, level and RMC StateMinimum number of configured VIOSs on each managed host,

software level, RMC connection and state to the HMC, Licenseagreement state and maximum number required for virtual


adapter slots. This category is viewable from IBM PowerVCStandard Edition.

Virtual Network - Shared Ethernet Adapter

Shared Ethernet Adapter is configured on the PowerVCmanagement server network and in Active state. Maximum

number required of virtual slots. This category is viewable fromIBM PowerVC Express Edition

Virtual I/O Server SEA count, stateThis category is related for the validation of at least one SEA

on one Virtual I/O Server This category is viewable from IBM




on one Virtual I/O Server. This category is viewable from IBMPowerVC Standard Edition.

Host-Storage LUN Visibility

LUN Visibility test. LUNS are created on storage providers andare visible to VIOSs. This category is viewable from IBMPowerVC Express Edition.

Host Storage FC ConnectivityMessages related to the enabled access to the storage areanetwork fabric by the VIOSs and correct WWPN to validate

VIOS - Fabric - Storage connectivity is established. Thiscategory is viewable from IBM PowerVC Standard Edition.

Storage Model Type and Firmware LevelMessage related to the minimum SVC and storage providers

firmware levels and the allowed MTMs.

Brocade Fabric ValidationsValidation for the switch presence, zoning enablement and

firmware level.

Figure 4-18 on page 85 and Figure 4-19 on page 86 show the depth ofinformation provided that you should expect to find when clicking or hovering

your mouse pointer over each row of the verification report.





Figure 4-18 Example of a validation message for an error status





Figure 4-19 Example of a validation message for a valid status

4.8 Compute Templates setup

Compute template is a concept to provide a predefined compute configuration touse when creating a virtual machine. and it let you specify settings for images

that are deployed with the template. You can customize processor, memory, andother features. You will select a compute template when you add an host. You

can change the compute template associated with a virtual machine when youresize and add the virtual machine. You can also create new compute templates

on the Configuration page.

For full description about compute templates, refer to 4.8, “Compute Templatessetup” on page 86.


The following Figure 4-22 on page 91 shows a dialogue that you will bepresented when creating a compute template. To access compute templates

configuration from PowerVC main page, click Configuration ComputeTemplates Create. You will have to:

Select Template settings

Provide Compute template name

Provide Virtual processors

Provide Processing units

Provide Memory




y

Select the Compatibility mode

If you click Advanced Settings, an additional dialogue will be presented.

Advanced settings are:

• Provide Virtual processors value of minimum, desired, maximum• Provide Processing units value of minimum, desired, maximum

• Provide Memory value of minimum, desired, maximum





Figure 4-20 PowerVC Create Compute Template


After clicking Add the Compute template will become available for use whencreating Virtual machine. The page summarizing available Compute Templates

in presented in Figure 4-21 on page 89.




Figure 4-21 PowerVC Compute Templates

4.9 Storage Templates Setup

Storage template is a concept to provide a predefined storage configuration touse when creating a new disk. For full description about storage templates,please refer to section 2.3.2, “Storage Templates” on page 25.


The following Figure 4-22 on page 91 shows a dialogue that you are presentedwhen creating a storage template. To access storage templates configuration

from PowerVC main page, click Configuration Storage Templates Create. Next, you have to:

Select storage provider.

Select pool within selected storage provider.

Provide storage template name.

Select the type of provisioning:

– Generic means full space allocation




– Thin provisioned is self-explanatory

If you select Thin provisioned, Advanced settings button becomesavailable (see Figure 4-20 on page 88). If you click Advanced Settings, an

additional dialogue is presented. Advanced settings are:

• Real Capacity% of Virtual storage

• Automatically expand

• Warning threshold

• Thin-provisioned grain size

For detailed discussion about how these settings affect PowerVC disk

allocation, please refer to section 2.3.2, “Storage Templates” on page 25 of this book.


Storage Controller

Pool




Figure 4-22 PowerVC Create Storage Template

Thick (full) provisioned





Figure 4-23 PowerVC Create Storage Template Advanced


After clicking Create the storage template is created a becomes available for usewhen creating Storage Volumes. The page summarizing available Storage

Templates in presented in Figure 4-21 on page 89.




Figure 4-24 PowerVC Storage Templates

4.10 Storage Volumes Setup

After adding storage providers and defining storage templates, storage volumes

can be created. When you create a volume, you have to select a template that

determines where (which storage controller and pool) and what are theparameters (thin or thick provisioning, grain size, etc.) of newly created volume.

When creating a volume, you have to input:

Storage Template

Volume name

Volume size

Write a short description of the volume (optional).


When creating a volume follow these steps from PowerVC main page: StorageVolumes Volumes tab Create, you will be presented with dialogue shown

in Figure 4-25 on page 94.




Figure 4-25 PowerVC Create Volume

After clicking Create Volume, the volume is created and you will be presentedwith a list of existing volumes, as shown in Figure 4-26 on page 95. From that

page you can manage volumes, valid operations are:

Create

Delete





Figure 4-26 PowerVC Storage Volumes

4.11 IBM PowerVC Standard VM setup

The following section explain the step by step needed to onboard an existingvirtual machine and the management tasks related to virtual machines.

4.11.1 Virtual machine onboarding

IBM PowerVC Standard Edition management host can manage existing virtualmachines and capture them for future deployments. The steps to onboard an

existing virtual machine ar described below

Connect to the PowerVC management host web interface. See Figure 4-27 on

page 96 for reference.







Figure 4-28 P owerVC management host home screen


Double click on the hosts picture in the main frame or click on the host in the leftside bar. See Figure 4-29 on page 98 for references




Figure 4-29 Selecting host view.

Host view button


Select the host which the virtual machines that you want to import into thePowerVC management host. Its background color will change to light blue. Then

double click on it. See Figure 4-30 on page 99 for reference.




Figure 4-30 Selected hosts view.

This opens the detailed host view. We have collapsed all the section for viewingpurposes. To collapse and expand the sections click on the small grey arrow

beside the section names. In the Figure 4-31 on page 100 you see the collapseand expand buttons. The Capacity section is expanded.

Selected host


Collapse and expand buttons




Figure 4-31 Collapse and expand buttons

Expand the Virtual Machines section, and then click on the Manage Existingbutton. See Figure 4-32 for details

Figure 4-32 Manage Existing button


The Manage Existing button open a new window with two options:

a. Manage any supported virtual machines that are not currently beingmanaged by PowerVC.

b. Select specific virtual machines.

Check the option Select specific virtual machines.After loading data, it willdisplay all the virtual machines available to be onboarded to the PowerVC

management host. Select the one you want to onboard. The background colorwill change to light blue for the selected vir tual machine. Click on Manage. See

Figure 4-33 for reference.

Note: Checking the option Manage any supported virtual machines that




Figure 4-33 Onboarding existing virtual machines

After you click on Manage, the PowerVC management host display an

information pop up message on the lower right corner of the window. SeeFigure 4-34 on page 102

g p g y ppare not currently being managed by PowerVC and then clicking Manage

make the onboarding of all candidate vir tual machines without asking forconfirmation.





Figure 4-34 Example of information pop up message

Figure 4-35 Display existing messages

Click on the Host view to return to the Manage Existing view. Select the recentlyadded virtual machine. The background color will change to light blue and. The

Tip: You can display the messages again by licking Messages on the black

bar with the IBM logo at the top of the screen. See Figure 4-35 for reference


Remove button is enabled when a virtual machine is selected. Clicking Remove on this view, will remove this virtual machine from the IBM PowerVC

management hosts. IBM PowerVC management hosts will not be able to performtasks on that virtual machine until you manually add it again. See Figure 4-36

Note: Removing a virtual machine from the Virtual Machine section in theHost view will only remove the virtual machine management out the PowerVC

management host. The Virtual Machine and its resources will remainconfigured and working




Figure 4-36 Existing virtual machine view

Double click on the recently added virtual machine to display detailedinformation. Virtual machines detailed view can be accessed by double clickingHome Hosts Host name Virtual Machine Name. Where Host name is

the name of the server containing the Virtual Machine that you want to view andVirtual Machine Name is the proper Virtual Machine

For viewing purposes we have collapsed all the sections. You can collapse andexpand each section by clicking on the small grey arrow beside any sectionname. See Figure 4-37 on page 104 for reference.





Figure 4-37 Virtual machine detailed view with collapsed sections

Click on the small grey arrow beside Information to expand the section. This

sections display information about the virtual machine status, health and creationdates. See Table 4-1 for more information

Table 4-1 Information section fields

Field Description

Name The name of the virtual machine

State The actual state for the virtual machine.

Health The actual health status for the virtual machine. The

possible health status are:

OK: The target resource, all related resources, and the

PowerVC management services for the resources report

zero problems. Warning: The target resource or a related resource

requires user attention.

Attention: Nova or cinder host services that manage the

resources report problems and require user attention.

Critical: The target resource or a related resource is in an

error state.

Unknown: PowerVC is unable to determine the health

status of the resource.











Figure 4-40 Virtual Machine detailed view of expanded network section

Double clicking on the Network will display the Network Detailed information,

including the VLAN id, the Virtual I/O servers involved, the Shared EthernetAdapters and other useful information. See Figure 4-41 on page 109 for adetailed network view

Note: For more detailed information about Network Setup into IBM PowerVC

management host see 4.6, “Networks Setup” on page 78.





Figure 4-41 Detailed Network view

Click on VM: virtual machine name on the line below the black bar with the IBMLogo to return to the Virtual Machine Sections View. See Figure 4-42

Figure 4-42 Detailed view of the tree links to move backwards in the views

Expand the Details Section to see some details about the status and the

hypervisor names for the Virtual Machine. The Table 4-3 on page 110 explainseach field on the view.

Links to go backwards


Table 4-3 Details section fields

Field Description

Power state Actual power status for the Virtual

Machine

Task status If there is a task running on the Virtual

Machine, here you see the status of the

task

Disk config How was the disk configured into the

Virtual Machine

Hypervisor host name The name of the host in the hypervisor

and the HMC




The Figure 4-43 displays Details section of the selected virtual machine.

Figure 4-43 Virtual Machine detailed view of expanded details section

Hypervisor partition name The name of the Virtual Machine in the

hypervisor and the HMC


4.11.2 Virtual machine operations

This sections explain the operations that can be performed on a Vir tual Machine

already managed by IBM PowerVC management host. The sections explainingthe operations allowed are:

• “Refresh virtual machine view”

• “Start the virtual machine” on page 113

• “Stop the virtual machine” on page 114

• “Prepare the virtual machine for capture” on page 114

• “Capture the virtual machine” on page 121

• “Deploy a new virtual machine” on page 129

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-




• “Resize the virtual machine” on page 134

• “Migrate virtual machines” on page 138

• “Reset State of a virtual machine” on page 147

• “Delete Images” on page 148

• “Delete a virtual machine” on page 151

The Figure 4-44 shows the buttons for each task except for the volumesmanagement. To see more about attaching an detaching volumes view sections:

• “Attach volume to the virtual machine” on page 141

• “Detach volume from the virtual machine” on page 144

Figure 4-44 Operations buttons on the virtual machine view

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-

http://-/?-




Start the virtual machineThe Start button power on the current selected virtual machine. Once the virtual

machine finish the startup process it is available for operations made with IBMPowerVC management host. The process take more time than the usual boot

process of the operating system. IBM PowerVC wait until the RMC servicebecame available to start communicating with the virtual machine. Even though

the status will show as active because the virtual machines is powered on, but

the health will show a message warning similar to “Reason: RMC state ofVirtual Machine vmaix01 is Inactive”. Wait for a few minutes and the health

should become to OK state. The Figure 4-45 on page 113 displays a virtualmachine powering on.




Figure 4-45 Virtual machine powering on


Stop the virtual machineThe Stop button will silently power off the vir tual machine. There is no

confirmation dialog. Be carefully with the Stop button because you can suddenlypower off the wrong virtual machine. When the vir tual machine complete the

shutdown process and is powered of the status change to Shutoff (Reset State).This take a few minutes to complete. See Figure 4-46 on page 114 for reference.




Figure 4-46 Virtual machine powered off

Prepare the virtual machine for capture

You can capture a virtual machine that you created or deployed. You must firstenable a virtual machine to be captured and then capture it. This enablement isrequired just the first time you do the capture for the specific partition. If you plan

to capture several different partitions you need to enable each one before youcan capture them.

There are requirements that the virtual machine must meet before it can becaptured.


Capture requirements

This topic describes the support and requirements for capturing a virtual

machine in your IBM Power VC management host.

Sources that you can capture

You can create an image by capturing a virtual machine that is running any of theoperating systems that are supported by IBM PowerVC, as described in 2.2.1,

“Hardware and software requirements” on page 11.

Requirements

Before you can capture a virtual machine, you should ensure that the followingrequirements are met:

Your IBM PowerVC environment is configured as described in 4.1, “PowerVCsetup” on page 63.




setup on page 63.

The host that the virtual machine resides on is registered in IBM PowerVC.

The virtual machine uses virtual I/O and virtual storage.

The /var directory on the IBM PowerVC management hosts have enoughspace

– When you capture virtual machines that use local storage, the /var

directory on the management server is used as the repository for storingthe images. The file system containing the /var directory needs to have

enough space to store the captured images.

The virtual machine is powered off.– When you power off a virtual machine, the status will appear as Active

until the virtual machine has completely shut down. You can select thevirtual machine for capture while the status is still displayed as Active.

For SUSE Linux 11 virtual servers, devices names should be literal names

rather than symbolic links. By default, devices are mounted by -id, which

means that they are represented by symbolic links. You need to change thedevices so they are mounted by device name or UUID, not by -id. Thefollowing steps describe how to do this using device name.

– Search the file system table /etc/fstab for the presence of symboliclinks.

– They will look like this: /dev/disk/by-*

– Store the mapping of /dev/disk/by-* symlinks to their target devices in ascratch file. For example:

ls -l /dev/disk/by-* > /tmp/scratchpad.txt

– The contents of the scratchpad.txt file may look something like theExample 4-1


Example 4-1 Original scratchpad.txt file

/dev/disk/by-id:total 0lrwxrwxrwx 1 root root 9 Apr 10 12:07scsi-360050768028180ee380000000000603c -> ../../sdalrwxrwxrwx 1 root root 10 Apr 10 12:07scsi-360050768028180ee380000000000603c-part1 -> ../../sda1

lrwxrwxrwx 1 root root 10 Apr 10 12:07scsi-360050768028180ee380000000000603c-part2 -> ../../sda2lrwxrwxrwx 1 root root 10 Apr 10 12:07scsi-360050768028180ee380000000000603c-part3 -> ../../sda3lrwxrwxrwx 1 root root 9 Apr 10 12:07wwn-0x60050768028180ee380000000000603c -> ../../sdalrwxrwxrwx 1 root root 10 Apr 10 12:07wwn 0x60050768028180ee380000000000603c part1 > / /sda1




wwn-0x60050768028180ee380000000000603c-part1 -> ../../sda1lrwxrwxrwx 1 root root 10 Apr 10 12:07

wwn-0x60050768028180ee380000000000603c-part2 -> ../../sda2lrwxrwxrwx 1 root root 10 Apr 10 12:07wwn-0x60050768028180ee380000000000603c-part3 -> ../../sda3total 0lrwxrwxrwx 1 root root 9 Apr 10 12:07 scsi-0:0:1:0 -> ../../sdalrwxrwxrwx 1 root root 10 Apr 10 12:07 scsi-0:0:1:0-part1 -> ../../sda1lrwxrwxrwx 1 root root 10 Apr 10 12:07 scsi-0:0:1:0-part2 -> ../../sda2lrwxrwxrwx 1 root root 10 Apr 10 12:07 scsi-0:0:1:0-part3 -> ../../sda3/dev/disk/by-uuid:

total 0lrwxrwxrwx 1 root root 10 Apr 10 12:073cb4e486-10a4-44a9-8273-9051f607435e -> ../../sda2lrwxrwxrwx 1 root root 10 Apr 10 12:07c6a9f4e8-4e87-49c9-b211-89086c2d1064 -> ../../sda3

– Edit /etc/fstab, replacing the /dev/disk/by-* entries with the device

names that the symlinks point to, as laid out in your scratchpad.txt file.The Example 4-2shows how look the lines before you edit them.

Example 4-2 Edited scratchpad.txt file

/dev/disk/by-id/scsi-360050768028180ee380000000000603c-part2 swap swapdefaults 0 0/dev/disk/by-id/scsi-360050768028180ee380000000000603c-part3 / ext3acl,user_xattr 1 1

– In this example, those lines are changed to refer to the specific devicenames. See Example 4-3 for reference.


Example 4-3 Specific device names for the /etc/fstab file.

/dev/sda2 swap swap defaults 0 0/dev/sda3 / ext3 acl,user_xattr 1 1

– Edit /etc/lilo.conf, making the boot and root l ines correspond to the

device names. The Example 4-4 shows how look the lines before you editthem:

Example 4-4 Default /etc/lilo.conf file

boot = /dev/disk/by-id/scsi-360050768028180ee380000000000603c-part1root = /dev/disk/by-id/scsi-360050768028180ee380000000000603c-part3

– In Example 4-5, those lines are changed to refer to the specific devicenames.




Example 4-5 Specific devices names for the /etc/lilo.conf file

boot = /dev/sda1root = /dev/sda3

– Run lilo

– Run mkinitrd

Installing the activation engine

Before you capture a virtual machine for the first time, you must install theactivation engine that is shipped with IBM Power Virtualization Center on thevirtual machine.

Follow these steps to Install and enable the activation engine:

1. Get the activation engine package vmc.vsae.tar from the IBM PowerVCmanagement host on /opt/ibm/powervc/activation-engine.

2. Transfer the vmc.vsae.tar file to the virtual machine that you are going tocapture.

Note: You have to do this step each time you deploy the SUSE Linux image.After that, you can capture and deploy an image of the resulting virtual

machine as many times as you like without having to perform this step.


3. On the virtual machine that you are going to capture, extract the contents ofthe .tar file.

a. For AIX, ensure that the JAVA_HOME environment variable is set and points

at a Java runtime environment (JRE), for example:

# export JAVA_HOME=/usr/java5/jre

Run the activation engine installation command

– For AIX run the following command, which is included in the .tar file:

aix-install.sh

– For Linux, run the following command, which was included in the .tar file:

linux-install.sh

Enabling the activation engine




Before you capture a virtual machine, you must enable the activation engine thatis installed on it. This topic describes how to enable the activation engine.

If you previously captured the virtual machine and want to capture it again,

run the commands shown in Example 4-6

Example 4-6 Commands to enable activating engine on a previously captured VM

rm /opt/ibm/ae/AP/*cp /opt/ibm/ae/AS/vmc-network-restore/resetenv/opt/ibm/ae/AP/ovf-env.xml

Prepare the virtual machine to be captured by running the followingcommand:

/opt/ibm/ae/AE.sh -R

Wait until the virtual machine is powered off. See Example 4-7 for reference

on the output for the /opt/ibm/ae/AE.sh -R command.

Example 4-7 Output from the /opt/ibm/ae/AE.sh -R command

# /opt/ibm/ae/AE.sh -R

Important: This command finishes preparing the virtual machine for captureand then powers off the virtual server. Run this command only when you are

sure that you no longer need to be logged into the vir tual server beforecapturing it.

Note: When this commands finishes the virtual machines is powered off andready to be captured


JAVA_HOME=/usr/java5/jre[2013-11-01 16:44:55,831] INFO: Looking for platform initializationcommands[2013-11-01 16:44:55,841] INFO: OS: AIX Version: 7.1[2013-11-01 16:44:56,315] INFO: No initialization commandsfound....continuing[2013-11-01 16:44:56,319] INFO: Base PA: /opt/ibm/ae/ovf-env-base.xml[2013-11-01 16:44:56,322] INFO: VSAE Encryption Level: Disabled[2013-11-01 16:44:56,323] INFO: CLI parameters are '['AE/ae.py', '-R']'[2013-11-01 16:44:56,325] INFO: AE base directory is /opt/ibm/ae/[2013-11-01 16:44:56,345] INFO: Resetting system. AP file: None.Interactive: False[2013-11-01 16:44:56,513] INFO: In reset[2013-11-01 16:44:56,513] INFO: Resetting products[2013-11-01 16:44:56,515] INFO: Start to reset

ib f t l t




com.ibm.ovf.vmcontrol.system0821-515 ifconfig: error loading /usr/lib/drivers/if_eth: A file ordirectory in the path name does not exist.[2013-11-01 16:44:56,846] INFO: Start to resetcom.ibm.ovf.vmcontrol.restore.network0821-515 ifconfig: error loading /usr/lib/drivers/if_eth: A file ordirectory in the path name does not exist.[2013-11-01 16:44:59,917] INFO: Resetting the operating system[2013-11-01 16:44:59,947] INFO: Cleaning AR and AP directories[2013-11-01 16:44:59,957] INFO: Shutting down the system

SHUTDOWN PROGRAMFri Nov 1 16:45:01 CDT 2013

Broadcast message from root@vmaix01 (tty) at 16:45:01 ...

shutdown: PLEASE LOG OFF NOW !!!System maintenance is in progress.All processes will be killed now.

Broadcast message from root@vmaix01 (tty) at 16:45:01 ...

shutdown: THE SYSTEM IS BEING SHUT DOWN NOW

JAVA_HOME=/usr/java5/jre


[2013-11-01 16:45:10,040] INFO: Looking for platform initializationcommands[2013-11-01 16:45:10,049] INFO: OS: AIX Version: 7.1

[2013-11-01 16:45:10,424] INFO: No initialization commandsfound....continuing[2013-11-01 16:45:10,428] INFO: Base PA: /opt/ibm/ae/ovf-env-base.xml[2013-11-01 16:45:10,430] INFO: VSAE Encryption Level: Disabled[2013-11-01 16:45:10,433] INFO: CLI parameters are '['AE/ae.py', '-d','stop']'[2013-11-01 16:45:10,434] INFO: AE base directory is /opt/ibm/ae/[2013-11-01 16:45:10,453] INFO: Stopping AE daemon.[2013-11-01 16:45:10,460] INFO: AE daemon was not running.0513-044 The sshd Subsystem was requested to stop.

Wait for ' Halt completed ' before stopping




Wait for '....Halt completed....' before stopping.Error reporting has stopped.

Uninstalling the activation engine

If you need to uninstall the activation engine from a virtual machine run the

following commands:

For AIX:

– aix-install.sh -u

For Linux:

– linux-install.sh -u


Capture the virtual machine

After you finish installing and preparing the virtual machine for capture click on

Virtual Machines Virtual machine name to capture? Capture Button.After pressing the Capture button you see the Verify Boot Volume screen. See

Figure 4-47 on page 121 for reference.




Figure 4-47 Verify volume screen when pressing Capture button

The dialog in Figure 4-47 only appears the first time you capture a VM.

Verify boot volume

One or more volumes can be attached to a virtual machine when it is brought

under management by IBM PowerVC. Therefore, you must identify the name ofthe boot volume for the virtual machine the first time an operation, such as

capture, resize, and delete, is performed on the virtual machine.

A copy of the boot volume will be included as part of the image when the virtualmachine is captured. The operating system information ensures that the vir tual

machine can be activated when the captured image is deployed.

The boot volume must also be verified when the vir tual machine is resized ordeleted. This ensures that the correct volume is resized or deleted along with thevirtual machine.

Select the correct boot volume from the Boot Volume drop down menu and nextselect the operating system from the Operating Systems drop down menu too.

Finally click continue. The IBM PowerVC management hosts display an


information and confirmation window to ensure you have installed and enabledthe activation engine. See Figure 4-48 on page 122 for reference




Figure 4-48 Information and confirmation window

After reading the message in the information and confirmation window, click

Continue. The next screen allow you to write the name for the capture and showyou the default resources required. See Figure 4-49 for reference





Figure 4-49 Entering the name for the capture

Write the desired name for the capture and then press Capture the process start

and the Task column display the Image Snapshot message an icon. In addition,a pop up message appears for a few seconds in the lower right corner on the

screen. See Figure 4-50 for reference

Figure 4-50 Image snapshot in progress


When the image snapshot is running click on the Images icon to view theImages. you will see the Queued State message which means that the snapshot

is currently been created. See Figure 4-51 on page 124 for reference.




Figure 4-51 Image creation in progress

When the image snapshot finishes the State in the Images view change toActive, and the Operating System show aix. See Figure 4-52 for reference.

Figure 4-52 Image view with a finished capture


If you click on the Storage Icon on the left bar you can see the storage relatedinformation about the Image Capture recently created. See Figure 4-53 for

reference.




Figure 4-53 Storage Volumes view

IBM PowerVC management hosts manage the image capture the same way itmanage another volume into the system but adding information to use this

volume as an image. This information enable the image to appear in the imageview to do deployments of new virtual machines.

Click on the Image icon on the left bar to return to the Images view. Select theimage to display in details and double click on it. Expand the Information

section. The Figure 4-54 on page 126 displays the information section expanded.

Tip: To collapse and expand a section click on the small grey arrow beside the

section name.


Note: For viewing purposes all the sections in the book captures arecollapsed.




Figure 4-54 Expanded information section of an image capture

The Table 4-4 explains each field on the Information section.

Table 4-4 Description of the fields on the information section

Field Description

Name Name of the image capture

State Current state of the image capture

ID Unique identifier number for the resource

Checksum Verification sum for the resource.

Size Storage space used by the partition

Created Created date and time

Last updated Last updated date and time


Collapse the Information section and expand the Specifications section. TheTable 4-5 explains each field on the view.

Table 4-5 Description of the fields on the Specifications section

Field Description

Image Type Description of the image type

Container Format Type of container for the data

Disk Format The specific format for the disk

Operating system The operating system on the image

Hypervisor type The name of the hypervisor managing the

image

Architecture Architecture of the image




The Figure 4-55 on page 128 displays the information section expanded.

Volume name Name of the volume containing the image

Storage provider The name of the storage device providing

the storage space

Storage template The name of the storage template used to

create the volume







Figure 4-56 Virtual Machines section of an image capture

Deploy a new virtual machine

You can deploy images that are created when you capture a virtual machine. Youcan deploy to a specific host or let the placement policy choose for you the best

location for the new virtual machine. See 2.9.1, “Placement policy” on page 43 for more information.

PowerVC has the following limits on deploys:

PowerVC supports a maximum of 10 concurrent deploys, the express edition

a maximum of 5

Important: Before you deploy an image, you can set a default domain for the

resulting virtual image by editing the nova.conf file. If you do not set a defaultdomain name in the nova.conf file, PowerVC uses the domain that is set for

the Virtual I/O Server on the host you are deploying to. If it is unable to retrieve

that value, it will use the domain name of the PowerVC management host. If itis unable to retrieve that value, no domain name is set and you will have to setit manually after you deploy the image.


PowerVC supports a maximum of 10 deploys per minute. If you exceed thislimit, you receive an error with an error code of 413.

The storage connectivity group that you select determines which hosts are

available as target hosts in the deploy operation. For more information, seethe Storage connectivity groups topic.

Start a new deploy by clicking on the Images button on the left bar to see theImages Captures. Then select the Image Capture that you want to use to

deploy your new Virtual Machine. The selected image background will changeto light blue. Then click on the Deploy button. See Figure 4-57 for reference

Deploy button




Figure 4-57 Image capture selected for deployment

Then click on the Deploy button to start deploying the new virtual machine. TheIBM PowerVC management hosts open a new windows to complete basic

information about the new vir tual machine. You need to prepare in advance thefollowing information:

Virtual Machine name Instances:

– If you have a DHCP server configured and a network created in IBM

PowerVC management host with this DHCP, you will be able to deploysimultaneously several virtual machines at the same time. There is a limitof 10 deploys per minute.

Host

– Manually select the host where the new virtual machine will be placed or

choose Selected by placement policy to let IBM PowerVC management


host to decide the best place based on the configured policy. To see howto configure, refer to 2.9.1, “Placement policy” on page 43.

Storage connectivity group

– Select the specific connectivity group for the storage access used by thenew virtual machine. For further details, refer to 4.5, “Storage Connectivity

Groups setup” on page 75.

Compute template

– Select the desired compute template to deploy the new virtual with

standard resource definitions. For further details, refer to 4.8, “ComputeTemplates setup” on page 86.

Storage template

– Select the desired storage template to deploy the new virtual withpredefined storage capacity. For further details, refer to 4.9, “Storage

Templates Setup” on page 89.




Primary network (system default gateway):

– Select the desired network. If the network select does not have a DHCP

configured, you have to write an IP address manually. For further details,refer to 4.6, “Networks Setup” on page 78.

The Figure 4-58 on page 132 displays the information window to Deploy animage capture.

Note: Selecting manually a host will change the graphics bar on the right partof the window to adjust the values to the new selection.

Tip: You can select a compute template to deploy a virtual machine with

standard predefined values for processing units, virtual processor andmemory. Even though you can change any value by clicking in the highlighted

number beside the resource. In the Figure 4-58 on page 132 you will see thememory value opened to enter the new desired value instead of the value

provided by the template.





Figure 4-58 Information to Deploy an image capture

Click on the Deploy blue button on the lower part of the screen to start deploying

the new virtual machine. This process may take a few minutes to finish.


When the deploy finish you will see a new virtual machine in the virtual machinesview. This new virtual machine is a clone of image capture and is already

configured and powered on. See Figure 4-59 on page 133 for reference




Figure 4-59 New virtual machine deployed


Resize the virtual machineIBM PowerVC management host can resize dynamically the managed vir tual

machines. Click on the Virtual Machines button on the left bar of the screen.Then select the desired virtual and finally click the Resize button on the upper

bar on the screen. See Figure 4-60 for reference




Figure 4-60 Virtual Machine resize




Important: To refresh the profile you need to shutdown and startup the vir tualmachine instead of reboot it. Rebooting the virtual machine will keep the

current values no matter how many times do you change them in the profile.




Figure 4-62 Exceeded value for resizing


After completing this screen click Resize. The resizing process start, and you willsee a popup message window in the lower right part of the screen. Also you can

see the complete messages in the message view. See Figure 4-63 on page 137 for reference.




Figure 4-63 Virtual machine resize in progress

Figure 4-64 Display and review existing messages

Tip: You can display again the messages by clicking Messages on the black

bar with the IBM logo at the top of the screen. See Figure 4-35 for reference


The resize process can take a few minutes. When it is finished you can see thenew sizes in the Specifications section of the virtual machine. Refer to

Figure 4-39 on page 107 for reference.

Migrate virtual machinesIBM PowerVC management server can mange the Live Partition Mobility feature.This allow you to migrate virtual machines from one host to another.

Migration requirements To successfully migrate vir tual machines using IBM Power VC managementserver, you have to make sure that the source and destination hosts and thevirtual machines are configured properly.

To migrate a vir tual machine, the following requirements must be met:

The virtual machines is in Active status in IBM PowerVC management host.

The PowerVM Enterprise Edition or PowerVM for IBM PowerLinux hardware

feature is activated on your hosts This enables you to use the Live Partition




feature is activated on your hosts. This enables you to use the Live PartitionMobility feature. For further details, refer to 2.2.1, “Hardware and softwarerequirements” on page 11.

The networks for both source and target hosts must configured upon a

Shared Ethernet Adapters using same Virtual Ethernet Switch.

It is recommended that the maximum number of virtual resources (virtual

adapters) is set to at least 200 on all of the hosts in your environment. Thisensures that you are able to create a sufficient number of virtual machines on

your hosts.

The logical-memory block size on the source host and the destination hostmust be the same.

Both the source and destination hosts must have Virtual I/O Server virtual

machines defined that are members of the same storage connectivity group.

The processor compatibility mode on the vir tual machine that you want to

migrate must be supported by the destination host.

The virtual machine must have a Resource Monitoring and Control (RMC)connection enabled. For instructions on how to set up the RMC connection,

see Configuring VLANs on the network switch.

Note: For more information about this and other topics refers to IBM Power

Systems Information center on the web.


Following restrictions apply when migrating a virtual machine:

You cannot exceed the maximum number of concurrent migrationsdesignated for the source and destination hosts. The maximum number of

concurrent migrations depends on the number of migrations supported by theVirtual I/O Servers that are associated with each host.

A source host in a migration operation cannot concurrently serve as a targethost in a separate migration operation.

If you deployed a virtual machine with a processor compatibility mode ofPOWER7 and later changed the mode to POWER6, you cannot migrate thevirtual machine to a POWER6 host. The MAC address for a POWER7 virtual

machine is generated by PowerVC during deploy. To migrate to a POWER6host, the MAC address of the vir tual machine must be generated by the HMC.

To migrate from a POWER7 to a POWER6 host, you must initially deploy to aPOWER7 system with the processor compatibility mode set to a POWER6derivative, or you must initially deploy to a POWER6 host.

Migrate the virtual machine




Migrate the virtual machine Click on the Virtual Machines icon on the left bar on the screen. Then select the

desired virtual machine to be migrated. The background change to light blue.Click the Migrate button located on the black upper bar with the IBM Logo. See

Figure 4-65 for reference

Figure 4-65 Migrate selected virtual machine




Note: Warning messages in the Health column is normal. It will take a fewminutes to change to OK.

Target host after migration




Figure 4-68 Virtual machine migration finished

Attach volume to the virtual machine

IBM PowerVC management server can handle storage volumes. Using IBMPowerVC management serve you can attach a new or existing volume to a virtualmachine. To do this, click on the Virtual Machines icon on the left bar on thescreen. Then select the vir tual machine you want to add a volume. The

background color change to light blue. Click on the Attach Volume button. Youwill see a pop up window. This window allow you to attach an existing volume or

to create a new volume and attach it in one step.

Select Attach a new volume to this virtual machine. See Figure 4-69 on

page 142 for reference.

Tip: For more information about creating volumes refer to 4.10, “StorageVolumes Setup” on page 93.





Figure 4-69 Attaching a new volume to a virtual machine

Then complete the volume name, the size required in Gb and a description for

the new volume. The storage bar in the right part of the screen will changedynamically when you change the size. You can use a predefined storage

template. To review storage template go to 4.9, “Storage Templates Setup” onpage 89.

Click on Attach when ready. This process will create a new volume an after thatwill attach it to the server. You will see an information message in bottom part of

the screen. See Figure 4-70 on page 143 for reference.





Figure 4-70 Volume attaching in progress


To see the new added volume, double click on the virtual machine from theprevious step, then click on the Attached Volumes tab. This tab display the

current volumes attached to the virtual machine. See Figure 4-71 on page 144 for reference.




Figure 4-71 Attached volumes view

To complete the process you must execute the following command on the virtualmachine command line

For AIX operating systems execute as root:– cfgmgr

For Linux operating systems execute as root:

– echo “- - -” > /sys/class/scsi_host/host_N /scan

– Where host_N is the controller managing the disks on the virtual machine.

Detach volume from the virtual machine

To detach a volume from the virtual machine you need to remove it first from theoperating system.

For AIX operating system execute as root:

– rmdev -dl hdisk_N

– Where hdisk_N is the disk you want to remove.

For Linux operating system you need to reboot after detaching the volume.




After that, click on the Detach Button. IBM PowerVC management serverdisplay a confirmation dialog. Click accept to finish removing the volume. See

Figure 4-73 on page 146 for reference




Figure 4-73 Confirmation dialog

You will see a Detaching status in the State column. When the process finishesthe volume is detached from the virtual machine.

Important: After detaching a volume from the virtual machine it is stillmanaged by IBM PowerVC management host. To completely remove thevolume after detaching it you need to Delete it using the Storage view.


Reset State of a virtual machineThere are some situations when a vir tual machine become unavailable or in an

unrecognized state for the IBM PowerVC management server. It this happens toyou, it is possible to run the Reset State procedure. This process will try to

reconnect the virtual machine to the IBM PowerVC management server. To dothis double click on the vir tual machine with problems, then on the Reset State

link beside the State on the Information section. See Figure 4-74 on page 147 for reference




Figure 4-74 Virtual machine reset state

IBM PowerVC management server display a confirmation window.Click OK tocontinue. See Figure 4-75 for reference


Figure 4-75 Reset state confirmation window




Delete Images

To delete an image that is not in use click on the Image icon located on the leftbar in the main screen on the IBM Power management server. Then select the

image that you want to delete. The background color will change to light blue.Finally click on the Delete button. See Figure 4-76 for reference.

Important: This process can take from a few minutes to a couple of hours. Ifthe state do not change, try to restore the virtual machine or deploy it again

from an image.


Figure 4-76 Image selected




IBM PowerVC management server display a confirmation window. If you want topermanently delete the image from the storage mark the check box and click OK.

See Figure 4-77 on page 149 for reference.

Figure 4-77 Delete an image confirmation dialog

You will see a pop up message and the image is deleted from the IBM PowerVC

management server. See Figure 4-78 for reference


Tip: You can delete images from the IBM PowerVC management serverkeeping them in the storage for future usage.




Figure 4-78 Image deleted message


Delete a virtual machineIBM PowerVC can delete virtual machines completely from your systems. To do

that click on the Virtual Machines icon located on the left bar on the mainscreen. After that select the virtual machine that you want to remove. The

background color change to light blue. Finally click on the delete button. SeeFigure 4-79 for reference.




Figure 4-79 Delete virtual machine


IBM PowerVC management server display a confirmation window. If you want topermanently delete the virtual machine click OK. See Figure 4-80 on page 152

for reference




Figure 4-80 Delete virtual machine confirmation window

You will see a pop up message and the image is deleted from the IBM PowerVC

management server. See Figure 4-81 for reference.

Y

Figure 4-81 Pop up message after a virtual machine is deleted








Chapter 5. IBM PowerVC ExpressEdition specifics

5




IBM PowerVC Express Edition as specific aspects regarding the setup, thestorage management, and the way it handles the ISO images capture. In this

chapter, we cover the installation and setup specifics as well as the basic steps to

import, capture and deploy ISO images.

5.1 Installation and setup

In this setup, we cover the installation and setup differences with the IBMPowerVC Standard Edition.

5.1.1 Installing IBM PowerVC Express

This section outlines the slight difference with the installation of IBM PowerVCStandard edition. Before to install PowerVC, it is necessary to have a Linux

Installation ready, as described in Chapter 3, “Install” on page 51.


Since the IBM PowerVC can be hosted either on Linux x86 or in a Linux onPower hosted on a different Power System, we do not cover the Linux installation

in this section. You can refer to 3.2, “Installing IBM Power Virtualization Centerfrom media” on page 55 for complete installation details. Once the Linux for

PowerVC Express Edition is ready, we follow the steps below:

1. Change the directory to the location of the installation script

2. Install PowerVC Express Edition, use the commands shown below:

[root@powervcexp powervc-1.2.0.0]# ls /tmp/powervc-1.2.0.0/bin install lap liblicense packages powervc.rsp[root@powervcexp powervc-1.2.0.0]# ./install

Select the offering type to install: 1 - Express (IVM support) 2 - Standard (HMC support) 9 - Exit

Type “1” to process with the IBM PowerVC Express Edition.

5 1 2 Setup and preparation of IBM PowerVC Express environment




5.1.2 Setup and preparation of IBM PowerVC Express environment.

In this section, we cover the steps to add an Integrated Virtualization Manager

host (IVM), a storage array, and a network. We want the reader to keep in mindthat an IVM is a Virtual I/O server with HMC-like functionality embedded.

We give an example of the three basic step to integrate:

An IVM host.

An IBM SAN Volume Controller (Same steps for a Storwize).

A network.

We want to remind the fact that IBM PowerVC Express Edition does not manageSAN fabrics/switch. It uses virtual scsi storage mapping only, in the other handthe Standard Edition does use NPIV storage mapping. It also does map the

storage luns mapping from the SAN Volume Controller (SVC) or Storwize to the

IVM, in order to have them mapped to the client vir tual machine’s (vm) vscsiadapter.


Add the IVM hostThe following Figure 5-1 on page 157 shows the IBM PowerVC Express login

window from a browser.



Chapter 5. IBM PowerVC Express Edition specifics 157

Figure 5-1 IBM PowerVC Express Edition login window




As shown in Figure 5-3, add the hostname or IP address of the target IVM host.

Figure 5-3 PowerVC “Add Host” box

After the add is successful, the Figure 5-4 shows the home page with then newIVM host available (Hosts: 1).




Figure 5-4 IBM PowerVC Express Edition after host is added


Add a storage arrayNext step is to add the storage, clicking the “Add Storage” plus sign. The

Figure 5-5 on page 160 shows a popup window to specify the storage array ipaddress and credentials. With our lab setup, we use an IBM SAN Volume

Controller.




Figure 5-5 Add a storage to IBM PowerVC Express Edition

After providing the IP connections settings and credentials, it is necessary to

specify the SVC storage pool assigned to the lab environment. In Figure 5-6 the

SVC shows up with two different pools. The pool DS4800_site2_p01 is selected.

Figure 5-6 SVC Storage Pool choice


Once the SVC and Storage Pool are successfully added, a new storage providerappears onto the PowerVC home page, as shown in Figure 5-7 on page 161

(Storage Providers: 1) with no managed volume yet.




Figure 5-7 The new SVC storage provider is successfully added


Add a network The next step is now to add a network using the Add network button. The menu

window shown in Figure 5-8 on page 162 is offered to add the proper networkname, VLAN ID, subnet mask, default gateway, Domain Name Server (DNS),

address deployment choice (DHCP/Static), and the Share Ethernet Adapter(SEA) automatically retrieved from the IVM’s configuration.




Figure 5-8 Add a network to PowerVC configuration


Once the network is successfully added to the configuration, the home page isupdated as shown on Figure 5-9 on page 163 (Network: 1).




Figure 5-9 Network is now configured


Environment verificationOnce those three initial steps have been achieved it is also possible to check the

overall PowerVC configuration like shown Figure 5-10 on page 164 by using the“Verify Environment” button.




Figure 5-10 Verify Environment in progress


In this lab configuration, the code used is not at general availability level. Theverification does fail as shown in Figure 5-11 on page 165, because of the SVC

compatibility. This would not be the case with the official released code.




Figure 5-11 Failed verification caused by SVC compatibility

5.2 Import, capture and deploy ISO images

IBM PowerVC Express edition offers the possibility to use ISO images to createAIX and Linux virtual machines from scratch. The setup is slightly different

compared to PowerVC Standard Edition.

5.2.1 Import ISO images for deploymentsOnce the environment is verified, it is time to import ISO images to PowerVC.

It is necessary to have the ISO image files uploaded to PowerVC vm prior to

import them to the repository. This is a three step procedure:

1. Upload/transfer the ISO image files into PowerVC home directory.

2. Import the ISO image into the Glance repository. Once this step is finished,you can delete the original ISO image file.




[admin@powervcexp Downloads]$ ls -altrtotal 7273372-rwxr-xr-x 1 admin admin 4175724544 Oct 30 16:07 AIX.710.iso-rwxr-xr-x 1 admin admin 3272192000 Oct 30 16:25 rhel-6.4-ppc64.isodrwxr-xr-x 2 admin admin 4096 Oct 30 17:02 .drwx------ 4 admin admin 4096 Oct 30 17:09 ..[admin@powervcexp Downloads]$ which powervc-iso-import/usr/bin/powervc-iso-import[admin@powervcexp Downloads]$ powervc-iso-import \--name AIX_710 --os-distro aix --location ./AIX.710.isoPassword:******

+----------------------------+--------------------------------------+| Property | Value |+----------------------------+--------------------------------------+| Property 'architecture' | ppc64 || Property 'hypervisor_type' | powervm || Property 'os_distro' | aix || checksum | c0e30fdab56b4346f75ac55a1eeb9c45 || container_format | bare || created_at | 2013-10-30T21:13:00.147141 || deleted | False || deleted_at | None || disk_format | iso || id | 025dee79-05a2-430d-b1b9-63a021f96115 || is_public | True |

| min_disk | 0 || min_ram | 0 || name | AIX_710 || owner | 7d20f71bcd6540538cda8875e5ef7e3d || protected | False || size | 4175724544 |




Figure 5-12 Import an AIX ISO image into IBM PowerVC Express

| size | 4175724544 || status | active || updated_at | 2013-10-30T21:13:59.148223 |+----------------------------+--------------------------------------+






By double clicking the RHEL64 image, it is possible to get further details on theimage such as its id as shown in Figure 5-16.

Figure 5-16 RHEL ISO image details

Those images are located in the /var/lib/glance/images/ directory. The




Figure 5-17 on page 170 shows the ISO images files named accordingly to theID found shown in the images interface shown in Figure 5-16.

Figure 5-17 File list of the glance images directory

[admin@powervcexp ~]$ ls -1 /var/lib/glance/images/

025dee79-05a2-430d-b1b9-63a021f96115ea9b6c5a-7b90-4eff-8ee4-f6dbd8cd68f7[admin@powervcexp ~]$




5.2.2 Deploy a RHEL ISO image

Once the ISO images are imported, we can now proceed to deployment onto an

initial virtual machine. This virtual machine will be the basic image, ready forfuture automatic deployments. From the image window left navigation panel, as

shown in Figure 5-20, we select the RHEL64 image and click “deploy” which isnow enabled.

Figure 5-20 Select the RHEL64 image for deployment

Once the image is selected for deployment, the parameters for the target virtual




g p y , p gmachine have to be specified as shown in Figure 5-21 on page 173 before any

deployment can start. Those parameters are:

The virtual machine name.

The target host. The computer template.

The following default values can be overridden when they are available:

– Processors.

– Processor units.– Memory size.

– Disk Size.

The storage template.

The network template.

The virtual machine’s IP address.


Figure 5-21 Virtual machine deployment parameters.




It is now possible to select the deploy button, and start the virtual machine’s

deployment. We can monitor the virtual machine’s deployment from the left panelnavigation area, as shown in Figure 5-22

Figure 5-22 Virtual machine building.


The next Figure 5-23 on page 174 shows the virtual machine as built, with an“active” status. Even if this status seems definitive, the initial Linux installation

has to be done manually by booting the ISO image.

Figure 5-23 First active status for virtual machine

Once the building is finished, the machine is prepared, and shutdown for manualinstallation of the Linux ISO images, as shown in Figure 5-24.

Note: This extra manual installation step is only necessary for ISO imagedeployment, not for captured virtual machines.




Figure 5-24 Virtual is shutdown after building

y


Linux installation for the virtual machine.In the following steps, we describe the manual installation of a Linux VM using an

ISO image.

1. Open the console to vm vmlnx02.In order to proceed to the manual installation steps we have to open a remote

connection from the IBM PowerVC Express command line through the IVM tothe vm using the powervc-console-term command, as shown in Figure 5-25

on page 175.

Figure 5-25 Open the vm’s console from IBM PowerVC Express

2. Start the virtual machine from PowerVC. As shown in Figure 5-26, select the

virtual machine, then click the “start” button.

[root@powervcexp ~]# powervc-console-term vmlnx02Password: *******Starting terminal.

Red Hat Enterprise Linux Server release 6.4 (Santiago)Kernel 2.6.32-358.el6.ppc64 on an ppc64

vmlnx02 login:




Figure 5-26 First boot of virtual machine vmlnx02




5. On the main SMS menu, we choose option “5” to access the boot optionmenu, as shown in Figure 5-29 on page 177

Figure 5-29 Select boot option

6 Select the option “1” to go to the boot installation device menu as shown in

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Main Menu 1. Select Language 2. Setup Remote IPL (Initial Program Load) 3. Change SCSI Settings 4. Select Console

5. Select Boot Options

------------------------------------------------------------------------------- Navigation Keys:

X = eXit System Management Services ------------------------------------------------------------------------------- Type menu item number and press Enter or select Navigation key:5




6. Select the option 1 to go to the boot installation device menu, as shown in

Figure 5-30.

Figure 5-30 Boot options menu

Version AL730_122

SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Multiboot 1. Select Install/Boot Device 2. Configure Boot Device Order 3. Multiboot Startup <OFF> 4. SAN Zoning Support

------------------------------------------------------------------------------- Navigation keys: M = return to Main Menu ESC key = return to previous screen X = eXit System Management Services ------------------------------------------------------------------------------- Type menu item number and press Enter or select Navigation key:1


7. Select the option “7” to list all the available boot devices, as shown inFigure 5-31 on page 178.

Figure 5-31 Select boot devices menu

8. From the boot device list, Figure 5-32, we select option “2” in order to boot the

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Select Device Type 1. Diskette 2. Tape 3. CD/DVD 4. IDE

5. Hard Drive 6. Network 7. List all Devices





8. From the boot device list, Figure 5 32, we select option 2 in order to boot the

virtual CD-ROM which has been propagated by PowerVC into the IVM vir tualmedia repository and mapped to the vm.

Figure 5-32 Select the CD-ROM device for boot

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Select Device Device Current Device Number Position Name 1. 2 Interpartition Logical LAN ( loc=U8233.E8B.061AB2P-V3-C63-T1 ) 2. 1 SCSI CD-ROM ( loc=U8233.E8B.061AB2P-V3-C2-T1-L8100000000000000 )



9. On the next menu shown in Figure 5-33, select option “2” to boot in normalmode.

Figure 5-33 SMS boot mode

10 To boot the vm in Figure 5-34 we select option “1”

SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Select Task

SCSI CD-ROM ( loc=U8233.E8B.061AB2P-V3-C2-T1-L8100000000000000 )

1. Information 2. Normal Mode Boot 3. Service Mode Boot

------------------------------------------------------------------------------- Navigation keys: M = return to Main Menu

ESC key = return to previous screen X = eXit System Management Services ------------------------------------------------------------------------------- Type menu item number and press Enter or select Navigation key:2




10.To boot the vm, in Figure 5 34 we select option 1 .

Figure 5-34 Exit SMS and boot

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.

------------------------------------------------------------------------------- Are you sure you want to exit System Management Services? 1. Yes 2. No

------------------------------------------------------------------------------- Navigation Keys:



11.The vm does now boot from the select CD-ROM device, as shown inFigure 5-35.

Figure 5-35 The vm boots from the chosen device

12.Once the linux boot prompt is shown, we proceed to the classical RHEL

IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM STARTING SOFTWARE IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM PLEASE WAIT... IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM/




installation.

Figure 5-36 Boot the Linux installation media

You can refer to the Linux on Power information center for further help with Linuxinstallation:

http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/topic/liaab/concepts/installsetupparent.htm

Welcome to the 64-bit Red Hat Enterprise Linux 6.4 installer!Hit <TAB> for boot options.

Welcome to yaboot version 1.3.14 (Red Hat 1.3.14-41.el6)Enter "help" to get some basic usage informationboot:


13.Once the basic RHEL installation is complete, we reboot the vm as shown inFigure 5-37, and proceed to alter the default bootlist by pressing the “enter”

key.

Figure 5-37 Reboot the installed vm

Welcome to Red Hat Enterprise Linux for ppc64

+---------------------------¦ Complete +----------------------------+ ¦ ¦ ¦ Congratulations, your Red Hat Enterprise Linux installation is ¦ ¦ complete. ¦ ¦ ¦ ¦ Please reboot to use the installed system. Note that updates may ¦ ¦ be available to ensure the proper functioning of your system and ¦ ¦ installation of these updates is recommended after the reboot. ¦ ¦ ¦ ¦ +--------+ ¦ ¦ ¦ Reboot ¦ ¦ ¦ +--------+ ¦ ¦ ¦ ¦ ¦ +-------------------------------------------------------------------+

<Enter> to exit









Set the vm default boot deviceOnce the Linux RHEL is installed, we need to set the disk in the vm’s default boot

list for future activations or restarts.

1. The initial banner displays immediately after typing “enter” on the previousstep. We need again, to quickly hit “1” to proceed to the SMS menu as shown

on Figure 5-38 on page 182.

IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMIBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

1 = SMS Menu 5 = Default Boot List 8 = Open Firmware Prompt 6 = Stored Boot List

M K b d




Figure 5-38 Initial start banner after installation

Memory Keyboard


2. Select option “5” for boot options like in Figure 5-39.

Figure 5-39 Select boot options from SMS menu

3. Select option 2 in the boot menu as shown in Figure 5-40 on page 183 toconfigure the boot device order.

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Main Menu 1. Select Language 2. Setup Remote IPL (Initial Program Load) 3. Change SCSI Settings 4. Select Console 5. Select Boot Options

------------------------------------------------------------------------------- Navigation Keys:





Figure 5-40 Configure boot device order


------------------------------------------------------------------------------- Multiboot 1. Select Install/Boot Device 2. Configure Boot Device Order 3. Multiboot Startup <OFF> 4. SAN Zoning Support



4. Select option “1” in the boot device order list, Figure 5-41.

Figure 5-41 Configure boot device order

5. Select option “5” to identify the bootable hard drives as shown in Figure 5-42on page 184.

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Configure Boot Device Order 1. Select 1st Boot Device 2. Select 2nd Boot Device 3. Select 3rd Boot Device 4. Select 4th Boot Device 5. Select 5th Boot Device 6. Display Current Setting

7. Restore Default Setting

------------------------------------------------------------------------------- Navigation keys: M = return to Main Menu ESC key = return to previous screen X = eXit System Management Services -------------------------------------------------------------------------------

Type menu item number and press Enter or select Navigation key:1




Figure 5-42 Select boot device type menu

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.-------------------------------------------------------------------------------

Select Device Type 1. Diskette 2. Tape 3. CD/DVD 4. IDE 5. Hard Drive 6. Network 7. None 8. List All Devices



6. From the Media type, we choose option “1” as shown in Figure 5-43, to selectthe virtual scsi adapter.

Figure 5-43 Select media type menu

Note: IBM PowerVC Express does use virtual scsi disk mappings on IVM.

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.-------------------------------------------------------------------------------

Select Media Type 1. SCSI 2. SSA 3. SAN 4. SAS 5. SATA 6. USB 7. IDE 8. ISA 9. None10. List All Devices





Figure 5 43 Select media type menu


7. We select the existing virtual scsi from the media adapter menu with option“1” as shown in Figure 5-44.

Figure 5-44 Select Media Adapter menu

8. Select the virtual scsi disk previously installed in “Linux installation for the

virtual machine.” on page 175, from the select device menu, Figure 5-45. This

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Select Media Adapter 1. U8233.E8B.061AB2P-V3-C2-T1 /vdevice/v-scsi@30000002 2. None 3. List all devices

------------------------------------------------------------------------------- Navigation keys: M = return to Main Menu ESC key = return to previous screen X = eXit System Management Services

------------------------------------------------------------------------------- Type menu item number and press Enter or select Navigation key:1

http://-/?-

http://-/?-

http://-/?-

http://-/?-




p g , , gdevice would not show in the menu before it is actually bootable.

Figure 5-45 Select device menu

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Select Device Device Current Device Number Position Name 1. - SCSI 19 GB Harddisk ( loc=U8233.E8B.061AB2P-V3-C2-T1-L8200000000000000 ) 2. None



9. We now set this bootable disk as 1st boot device in the bootlist, Figure 5-46.

Figure 5-46 Set boot sequence menu

10.The bootlist is now ready, as shown in Figure 5-47, and we can proceed to

boot the Linux disk with option “x”.

Version AL730_122SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Select Task

SCSI 19 GB Harddisk ( loc=U8233.E8B.061AB2P-V3-C2-T1-L8200000000000000 )

1. Information 2. Set Boot Sequence: Configure as 1st Boot Device

------------------------------------------------------------------------------- Navigation keys: M = return to Main Menu ESC key = return to previous screen X = eXit System Management Services


http://-/?-

http://-/?-




Figure 5-47 Exit SMS and boot


------------------------------------------------------------------------------- Current Boot Sequence 1. SCSI 19 GB Harddisk ( loc=U8233.E8B.061AB2P-V3-C2-T1-L8200000000000000 ) 2. Interpartition Logical LAN ( loc=U8233.E8B.061AB2P-V3-C63-T1 ) 3. None 4. None 5. None

------------------------------------------------------------------------------- Navigation keys: M = return to Main Menu ESC key = return to previous screen X = eXit System Management Services ------------------------------------------------------------------------------- Type menu item number and press Enter or select Navigation key:X


11.Last confirmation to exit the SMS menu, and boot the disk, Figure 5-48,option “1”.

Figure 5-48 Confirm boot and exit SMS

12.Once booted, the virtual machine console will propose the default first boot

login prompt, Figure 5-49.

Version AL730_122 SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.------------------------------------------------------------------------------- Are you sure you want to exit System Management Services? 1. Yes 2. No

------------------------------------------------------------------------------- Navigation Keys:

X = eXit System Management Services





Figure 5-49 First boot prompt

Welcome to Red Hat Enterprise Linux!

Hit <TAB> for boot optionsWelcome to yaboot version 1.3.14 (Red Hat 1.3.14-41.el6)Enter "help" to get some basic usage informationboot:


localhost.localdomain login: rootPassword:********


Basic Linux setupAfter the base Linux image installation is ready. The following list provides basic

steps to make the base image ready for deployments:

Configure the IP address on eth0.

Configure the hostname.

Configure the /etc/resolv.conf for name resolution.

Add the ip address and hostname to /etc/hosts if necessary.

Configure a yum repository for RHEL is a plus and will help in most cases forfurther packages installation.

Once this is done, we encourage you to install the IBM Power Linux toolsrepository. The IBM PowerLinux Tools provide access to the following tools:

IBM PowerLinux hardware diagnostic aids and productivity tools.

IBM Software Development Toolkit for PowerLinux servers.

IBM Advance Toolchain for PowerLinux servers.

For the lab setup needs, we have setup a yum repository for the IBM PowerLinux

hardware diagnostic aids and productivity tools. Then, installed the rpm package“ibm-power-managed-rhel6” with its dependencies.

Further information on the IBM PowerLinux Tools can be found at the following

URL:




URL:

http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/yum.html

Note: The “ibm-power-managed-rhel6” installs the Reliable Scalable Cluster

Technology (RSCT) layer packages. It is important to install RSCT to have theResource Monitor Control (RMC) active for Live Partition Mobility andPowerVC monitoring on the vir tual machines.


After the Linux’s initial setup, along with the ibm-power-managed-rhel6 packageinstalled, we can reboot the vm with the Linux reboot command. The vm is now

up and running. Since the tcp/ip connectivity is now available, we can disconnectfrom the virtual machine console using the special keys sequence “~.” as shown

in Figure 5-50 on page 190.

Figure 5-50 Exit the virtual machine console

Once rebooted with the RMC communication active the vm (vmlnx02) should


vmlnx02 login: ~.

login: Connection to ivmc closed.






Once rebooted with the RMC communication active, the vm (vmlnx02) should

look like Figure 5-51 with an active state and OK health status.

Figure 5-51 vmlnx02 is deployed and active.


5.2.3 Image Capture and deployment

Install the Activation Engine for image capture.In order to prepare the initial vm for capture, we have to install and run the IBMActivation Engine on the Linux vm using the following orders:

1. Logon to the Linux installed image, and transfer the Activation Engine

package from the IBM PowerVC Express management host:

mkdir /tmp/ActivationEngine

cd /tmp/ActivationEnginescp powervcexp:/opt/ibm/powervc/activation-engine/vmc.vsae.tar .

2. Uncompress and install the Activation Engine:

tar -xf vmc.vsae.tar./linux-install.sh

3. Run the Activation Engine and HALT the vm to enable the capture:

rm /opt/ibm/ae/AP/*

rm: remove regular file `/opt/ibm/ae/AP/ovf-env.xml'? y

cp /opt/ibm/ae/AS/vmc-network-restore/resetenv/opt/ibm/ae/AP/ovf-env.xml

/opt/ibm/ae/AE.sh -R --->The system is going down for halt NOW!




y g g

HALT and ready to capture

This step will actually halt the vm which is now available for PowerVC capture

and deployment.


Capture the vm imageThe vm is now ready, and we can now select the vm for capture by selecting the

vm and click the capture button as shown

1. Select the vm, and click the capture button from the top navigation bar asshown in Figure 5-52.

Figure 5-52 Start the vm capture

2. Enter the new image name, and click the capture button on the popup windowshown Figure 5-53 on page 192.




Figure 5-53 Capture a vm based on an ISO image


3. Figure 5-54 show the verification window to confirm that the

Figure 5-54 Choose name and capture

4. The vm is now set for capture, as shown in Figure 5-55 on page 193 asqueued, with a type of snapshot, not as an image.




Figure 5-55 Capture queued


5. After a moment, the image is ready for deployment as shown in Figure 5-56.

Figure 5-56 The vm image is ready for deployment

For vm based deployment, please refer to 4.11.1, “Virtual machine onboarding”

on page 95







6.1 Hardware infrastructure for PowerVC Standardedition

This section describes the hardware components used in the test environment.

6.2 Hardware Management Console

HMC used for testing and configuration in Table 6-1 shows the hardwarespecifications used to manage the Power Systems infrastructure for the lab

environment.

Table 6-1 HMC requirements used.

6.3 Power Systems hardware

Table 6-2 shows the IBM Power Systems servers used in the IBM PowerVC

Hardware Type Model Version Release

HMC 7042 CR6 Version 7 Build

Level:20131010

Release: 7.8

service pack: 0




Table 6 2 shows the IBM Power Systems servers used in the IBM PowerVC

Standard lab environment.

Table 6-2 Hardware test environment

6.4 Storage infrastructure

This section details storage components used for testing.

Hardware Model Type Firmware level

IBM Power7 740 8205 E6C AL740-110

IBM Power7 750 8233 E8B AL730-122






6.6 Hardware infrastructure for PowerVC Expressedition

We describes in this section all the components used during the IBM PowerVCexpress version installation and setup.

6.7 Power Systems hardwareTable 6-5 shows the IBM Power Systems hardware used in the IBM PowerVC

Express lab environment.

Table 6-5 Hardware test environment

6.8 Storage infrastructure

Basically the storage infrastructure used for both editions of PowerVC installation

have the same requirements. We use this section to mention the componentsused for testing also for this edition.

Hardware Model Type Firmware level

IBM Power7 750 8233 E8B AL730-122



Chapter 6. PowerVC lab environment 199

g

6.8.1 Storage SAN switch

Table 6-6 shows the switch specifications used in this lab

Table 6-6 Storage switch specifications.

6.9 Software stack for PowerVC Express labenvironment

This section shows the software used in this lab, as you can the see samesoftware requirement were used for both editions.

Manufacturer Type Model

IBM 2498 B40


In the Table 6-7 is a detailed list of software used during all the lab testsperformed on PowerVC Express installation.

Table 6-7 Software version and releases used on PowerVC Express lab

Software Operating system or firmware version

IVM / Virtual I/O server 2.2.3

RedHat Enterprise 6.4

IBM PowerVC Express edition 1.2.0.0

Storage SAN switch 7.1.1 (Not managed in Express edition)

SAN Volume Controller 6.4.0.0 (build 64.9.1206132000)

Note: There are not specific requirements from Network switch perspective so

its configuration was not updated during the lab tests.







PowerVC domain is the set of LPARs managed by PowerVC (set of hosts,storage, and LPARs managed).

On-boarding is the process by which an existing virtual machines (VM) is

added to a PowerVC managed domain.

Existing virtual machines are left out, by default, from the PowerVC domain.

There are two ways to add a VM to the IBM PowerVC Standard Editiondomain:

– Deploy a VM created from a captured image of an existing VM from your

environment.

– Import and existing LPAR created with the HMC.

6.11 IBM PowerVC installation tips

This is a brief list about some trouble faced while installing PowerVC,

– Import a PowerVC LPAR into the PowerVC domain is not allowed,because RSCT tools are not supported on existing LPAR outsidePowerVC domain.

– IBM PowerLinux Toolkit is not a requirement for PowerVC installation.

– In this release of IBM PowerVC editions (Standard and Express) IBM

PowerVM Live Partition Mobility is not supported.

– Shared Storage Pools is not supported on this version.




– VSCSI is not supported by IBM PowerVC Standard Edition, only NPIV issupported.

– VSCSI is supported by IBM PowerVC Express Edition.

– Disable Security Enhancement Linux for IBM PowerVC installation.

– In an environment without Domain Name Server (DNS), make sure tohave all hardware components correctly defined in the /etc/hosts file

through the environment, including the information for all the components,for instance, SAN switches hostnames, HMC, and so on.

– In an environment with DNS present environment you must have allnames for the hardware components that make your infrastructure defined

on the DNS, and both forward and reverse resolution have to workcorrectly. When we say all, means storage SAN switches, HMCshostname, and so on.

Draft Document for Review November 20, 2013 5:11 pm 8199abrv.fm

This abbreviations

and acronyms file is

optional.

Use this file by adding names

and descriptions to it. Sort

these names: highlight

rows Table Sort Sort

By: Column 1 Sort

oroptionally add names and

descriptions to the Index file

instead of this file by indexing

the first use of an abbreviation

or acronym: highlight text

Special Marker

Index New Marker

abbreviation1 Description1

abbreviation2 Description2IBM International Business

Machines Corporation

ITSO International Technical

Support Organization



Abbreviations and acronyms




8199abrv.fm Draft Document for Review November 20, 2013 5:11 pm




Draft Document for Review November 20, 2013 5:11 pm 8199bibl.fm

Related publications

The publications listed in this section are considered particularly suitable for a

more detailed discussion of the topics covered in this book.

IBM Redbooks

The following IBM Redbooks publications provide additional information about

the topic in this document. Note that some publications referenced in this listmight be available in softcopy only.

????full title???????, xxxx-xxxx

????full title??????? , SG24-xxxx

????full title??????? , REDP-xxxx ????full title??????? , TIPS-xxxx

You can search for, view, download or order these documents and otherRedbooks, Redpapers, Web Docs, draft and additional materials, at the followingwebsite:

ibm.com/redbooks








Other publications

These publications are also relevant as further information sources:




Online resources

These websites are also relevant as further information sources:

Description1

http://????????.???.???/





T o d e t er mi n e t h e s pi n ewi d t h of a b o ok , y o u d i v i d e t h e p a p er P P I i n t o t h en um b er of p a g e s i n t h e b

s m o o t h wh i c h h a s aP P I of 5 2 6 .Di v i d e d 2 5 0 b y 5 2 6 wh i c h e q u al s a

s pi n ewi d t h of .4 7 5 2 " .I n t h i s

t h e b o

ok an d h i d e t h e o t h er s : S p e ci al > C on d i t i on al T ex t > S h ow / Hi d e > S pi n e S i z e ( - - >Hi d e: ) > S e t

b o ok b y o p eni n g t h e b o ok f i l ewi t h

t h e s pi n e.f m s t i l l o p en an d

F i l e >I m p or t >F or m a t s t h e

Dr af t

D o c um en t f or R ev i ew

N ov em b er 2 0 ,2 0 1 3 5 : 1 1 pm

I B M P

o w e r V

I n t r o d u c t i o n

C o n f i g u r a t i o

I B M P

o w e r V

I n t r o d u c t i o n

C o n f i g u r a t i o



( 2 . 0 ” s pi n e )

2 . 0 ” <->

2 .4 9 8 ”

1 0 5 2 <->1 3

1 4 p a g e s

( 2 . 5 ” s pi n e )

2 . 5 ” <->nnn.n”

1 3 1 5 <->nn

nn p a g e s

b

o ok .A n ex am pl ei s a2 5 0 p a g e b o ok u s i n gP l ai nf i el d o p a q u e

5 0 #

c a s e , y o uw o ul d u s e t h e. 5 ” s pi n e.N ow

s el e c t t h e S pi n ewi d t h

f or

.M ov e t h e c h an g e d C on d i t i on al t ex t s e t t i n g s t o al l f i l e s i n y o u

r

C on d i t i on al T ex t S e t t i n g s ( ONL Y ! ) t o t h e b o ok f i l e s .

8 1 9 9 s pi n e.f m

2 0 8

C a n d

n C a n d

n



® Draft Document for Review November 20, 2013 5:11 pm

INTERNATIONALTECHNICALSUPPORTORGANIZATION

BUILDING TECHNICALINFORMATION BASED ONPRACTICAL EXPERIENCE

IBM Redbooks are developed bythe IBM International TechnicalSupport Organization Experts

®

IBM PowerVCIntroduction andConfiguration

Installation requires

just 20 minutes to

get a virtual machine

up and running

Intelligent virtualmachine deployment

Deep integration

with Power Systems

IBM PowerVC is an advanced enterprise virtualization

management offering for IBM Power Systems based on the

OpenStack technology. This IBM® Redbooks® publication

will introduce and position IBM Power Virtualization Center

and will help you understand its positioning, planning,

installation, and setup.PowerVC editions include the following features and benefits:

Virtual Image capture, deployment, and management

Policy-based Virtual Machine (VM) placement to improve

utilization

Targeted VM placement for deployment to reduce

complexity

Managing real-time optimization and VM resilience to

Back cover



SG24-8199-00 ISBN

Support Organization. Expertsfrom IBM, Customers andPartners from around the worldcreate timely technicalinformation based on realisticscenarios. Specificrecommendations are providedto help you implement ITsolutions more effectively inyour environment.

For more information:ibm.com /redbooks

increase productivity VM Mobility with placement policies to reduce burden on

IT staff in a simple-to-install and easy-to-use GUI

An open and extensible PowerVM management system

that enables you to adapt as you need and runs in

parallel with existing infrastructure, preserving your

investment

A management system that manages existing PowerVM

deployments







Documents

IBM PowerVC Introduction and Configuration