Sub-capacity (Virtualization) License Counting...

®

IBM Passport Advantage Software

Sub-capacity (Virtualization) License Counting Rules

IBM Power Systems PowerVM Virtualization Environment

NOTE: Please use these rules in conjunction with the Passport Advantage Agreement

November 1, 2016

http://www-01.ibm.com/software/lotus/passportadvantage/agreementsandforms.html

IBM Passport Advantage Software – Sub-capacity Licensing IBM Passport Advantage Software – Virtualization Capacity Licensing for IBM Power Systems PowerVM Virtualization

2

Index Summary of Virtualization Capacity Licensing Requirements (page 3)

ILMT License Counting - Definitions, Scenarios, Rules (page 4-12) Definitions (page 4-6) Scenarios (page 7-15)

• Dedicated LPAR (page 7)

• Dynamic LPAR (page 8)

• Single Shared Pool with Capped and Uncapped Partitions (page 9-10)

• Micro-Partitioning (Fractional cores) with Single Shared Pool, Capped & Uncapped Partitions (page 11)

− Micro-Partitioning (Fractional cores)– 2 servers (page 12)

• POWER6 or Later Multiple Shared Pool with Capped and Uncapped Partitions (page 13)

• POWER6 or Later Shared Dedicated Partition (page 14)

• POWER6 or Later Live Partition Mobility (page 15)

• PowerKVM (page 16) Licensing Rules (page 17-18)

Manual Calculation of Virtualization Capacity – if allowed (page 19-21) Eligibility Criteria & Requirements (page 19) Rules (page 20) Worksheet Example (page 21)

Other Key Web Links (page 22) Capped & Uncapped Partition Licensing – Settings & Rationale (page 23-25) Processor settings and information for licensing software in a partition (page 26-27)

November 1, 2016


3

Sub-capacity Licensing Requirements Summary

Customers must: Agree to the terms of the Sub-capacity Attachment, and follow Virtualization

Capacity License Counting rules for their Eligible Virtualization Environment(s)

Use Eligible Sub-capacity Products

Use Eligible Virtualization Technologies

Use Eligible Processor Technologies

Use the IBM License Metric Tool (ILMT) and maintain report documentation

• Tivoli Asset Discovery for Distributed (TADd) or IBM BigFix Inventory, may be used in

lieu of IBM License Metric Tool

• Certain ILMT / TADd / BigFix use exceptions may apply

PLEASE NOTE:

The above is only a summary. For details about sub-capacity licensing requirements, see the Sub-capacity Attachment

and other information referred to above, at Passport Advantage Sub-capacity licensing information

Customers are responsible for the installation of the IBM License Metric Tool and for the server it runs on.

November 1, 2016

http://www-306.ibm.com/software/lotus/passportadvantage/subcaplicensing.html



IBM Passport Advantage Software – Virtualization Capacity Licensing for IBM Power Systems PowerVM Virtualization

4

Definitions Dedicated partition (LPAR):

– Processors are always allocated in whole increments (no micro-partitioning)

– Resources are only moved between partitions “explicitly” (e.g. by DLPAR via an operator or a scheduled job)

Entitled Capacity (EC)

– The actual processor core capacity available to a partition. May be changed via DLPAR operation after startup. It is a unit of measure for shared processing capacity. One EC accomplishes approximately the same work as one dedicated processor core. Formerly referred to as PrU.

Virtual Processor (VP)

– Defines the maximum number of physical processor cores that the system can access simultaneously to provide the processing capacity of a shared processors partition

– The processing capacity of a partition is evenly distributed across the virtual processors

Online VP

– The actual VPs available to a partition. May be changed via DLPAR operation after startup.

Shared Pool or Physical Shared Pool

– This is the single shared pool of processor cores that can be available to all partitions that are defined within the shared pool.

– System automatically moves processor core resources between partitions as needed

November 1, 2016


5

Definitions Shared processors Partition (Also known as Micro-partition LPAR)

– A logical partition that utilizes processor resources from the shared processing pool using Micro-Partitioning technology are referred to as shared processor partitions.

– The processing unit assigned to a shared processors partition is known as processor entitlement, or entitled capacity. A shared processors partition can be defined as “capped” or “uncapped”

– The POWER Hypervisor automatically moves processor core resources among partitions based on each partition’s entitled capacity, “capped or uncapped” attributes, and its load

Capped partition:

– This type of shared processor partition can never be allocated processing capacity that is more than its Entitled Capacity

Uncapped partition:

– This type of shared processor partition can be allocated processing capacity that can exceed its Entitled Capacity. It can access the unused processor cores in the shared pool, when available, up to the Online VP value (VP).

Micro-partitioning:

– The ability to divide a physical processor’s computing power into fractions of a processing unit and share them among multiple logical partitions.

– To obtain the number of license entitlements the customer should acquire, add up the total number of cores per server then round up to the next whole number of processor cores (aggregate and round up, by server)

– Processor units are allocated in increments of 0.01 processor core

November 1, 2016


6

Definitions

Multiple Shared Pools

– A POWER6 or later capability that allows the physical shared processor pool to be subdivided into multiple virtual pools. LPARs that are part of a shared pool are limited by the number of processor resources in that pool. There is only one level of pool nesting, the virtual shared pools are always a child to the physical shared processor pool. POWER5 systems only have the physical shared processor pool.

Shared Dedicated Partition

– Is a dedicated partition that can potentially donate all its capacity, when unused, to the physical shared pool when the "shared dedicated capacity" is enabled. The entire capacity of such a partition is counted both in the shared pool and as a dedicated partition.

Live Partition Mobility

– Allows the movement of an entire running LPAR (including the OS and any applications) from one physical server to another without loss of service

PowerKVM

– An open source server virtualization that is based on the IBM POWER processor technology. It includes the Linux open source technology of KVM virtualization.

Hardware Management Console (HMC)

– Hardware Management Console is used in establishing the partition settings. Processing Unit settings determine the Entitled Capacity of a partition. The VP settings determine the Online VP that a partition obtains.

November 1, 2016


7

License Counting – Dedicated LPAR

License entitlements required are based on processor core capacity available to the software in the partition

For the example below:

– WebSphere Application Server (WAS): PVUs for 10 cores need to be licensed

– DB2 Enterprise Server Edition (DB2): PVUs for 4 cores need to be licensed

i5/OS

WAS

AIX

WAS

DB2

Linux

DB2

1 2 3 4 5 6 7 8 1 2 1 2

Server with 12 Processor cores

Partitions

November 1, 2016


8

License Counting – Dynamic LPAR System i and System p provide the capability to dynamically move processor core resources

between partitions

Customer must acquire PVUs for the highest actual* processor core capacity available to the

IBM software

Example: i5/OS

WAS

AIX

WAS

DB2

Linux

DB2

1 2 3 4 5 6 7 8 1 2 1 2

Customer’s basic

configuration:

i5/OS

WAS

AIX

WAS

DB2

Linux

DB2

1 2 3 4 5 6 7 8 9 1 1 2

Changed during

batch peak:

i5/OS

WAS

AIX

WAS

DB2

Linux

DB2

1 2 3 4 5 6 1 2 3 4 1 2

Changed for

simulation work:

License PVUs for: 10 WAS cores (consistent throughout) + 6 DB2 cores (from simulation peak)

* greater of a) what the partition starts with or b) the result of a DLPAR operation

November 1, 2016


9

License Counting – Single Shared Pool with Capped and Uncapped Partitions

A

i5/OS

B

AIX

C

Linux

Shared Pool (9 processor cores)

1 1 1 1 2 3 4 5 6 7 8 9

D

Capped

AIX

DB2

VP = 6

EC = 4.00

E

Uncapped

i5/OS

WAS

VP = 7

EC = 5.00

WAS cores to license: • 7 from VP for uncapped

partition E

DB2 cores to license: • 4 from EC for capped

partition D

Server with 12 processor cores

License Rules:

For Capped Partitions: The highest actual* level of Entitled Capacity (EC);

EC was formerly referred to as Processing Unit (PrU).

For Uncapped Partitions: The highest actual* number of Online VP (Virtual

Processors)

Shared Pool: the lower of the sum of each partition for a product or the processor

capacity of the shared pool

* The greater of what the partition starts with or the result of a DLPAR operation

November 1, 2016


10

A

i5/OS

B

AIX

DB2

C

Linux


1 1 1 1 2 3 4 5 6 7 8 9

D

Capped

i5/OS

VP = 1

EC= 1.00

E

Capped

AIX

DB2

VP = 4

EC = 2.00

F

Capped

Linux

WAS

DB2

VP = 4

EC = 2.00

G

Uncapped

i5/OS

WAS

VP = 7

EC = 3.00

H

Uncapped

AIX

WAS

DB2

VP = 3

EC = 1.00


DB2 cores to license: 1 from dedicated partition B

4 from EC for capped partitions E

and F

3 from VP for uncapped partition H

8 total

WAS cores to license: 2 from EC for capped partition F

10 from VP for uncapped partitions G

and H

12 total reduced to 9, maximum

cores available in the shared pool

License Counting – Single Shared Pool with Capped and Uncapped Partitions

License Rules:

For Capped Partitions: The highest actual* level of Entitled Capacity (EC);

EC was formerly referred to as Processing Unit (PrU).


Processors)

Shared Pool: the lower of the sum of each partition for a product or the

processor capacity of the shared pool


November 1, 2016


11

License Counting - Micro-Partitioning (Fractional cores) with Single Shared Pool, Capped & Uncapped Partitions

A

i5/OS

B

AIX

DB2

C

Linux


1 1 1 1 2 3 4 5 6 7 8 9

D

Capped

i5/OS

VP = 3

EC = 2.10

E

Capped

AIX

DB2

VP = 4

EC = 1.60

F

Capped

Linux

WAS

DB2

VP = 4

EC = 1.30

G

Uncapped

i5/OS

WAS

VP = 7

EC = 3.00

H

Uncapped

AIX

WAS

DB2

VP = 3

EC = 1.00

WAS cores to license: 1.3 from EC for capped partition F

10 for uncapped partitions G and H

11.3 total, rounded up to 12

Reduced to 9, maximum cores

available in the shared pool


DB2 cores to license: 1.0 from dedicated partition B

2.9 from EC for capped partitions

E and F

3.0 from VP for uncapped

partition H

6.9 rounded up to 7.0

7.0 total cores to license

License Rules:

For Capped Partitions: The highest actual* level of Entitled Capacity (EC)

• EC was formerly referred to as PrU (Processing Units).

For Uncapped Partitions: The highest actual* number of Online VP (Virtual Processor Cores)

Shared Pool Capping Rule: the lower of the sum of each partition for a product or the processor

core capacity of the shared pool

Aggregate fractional processor cores, apply shared pool capping rules, and round up at the

server level to the next whole processor core.


November 1, 2016


12

License Counting - Micro-Partitioning (Fractional cores) with Single Shared Pool, Capped & Uncapped Partitions – 2 servers

A

Capped

AIX

DB2

VP = 3

EC= 1.3

Server #1 with 8 processor cores

Physical Shared Pool

(8 processor cores)

1 2 3 4 5 6 7 8

D

Uncapped

AIX

VP = 3

EC= 2



(10 processor cores)

1 2 3 4 5 6 9 10 7 8

E

Capped

AIX

VP = 3

EC = 2

B

Capped

AIX

DB2

VP = 3

EC= 0.2

C

Capped

AIX

DB2

VP = 3

EC= 2.4

DB2 cores to license: 2.0 Server 1 ( 1.5 from capped

partitions A (1.3) & B (0.2),

rounded up to a whole core )

3.0 Server 2 ( 2.4 from capped

partition C, rounded up to a

whole core )

__

5.0 total cores to license

License Rules:




Processor Cores)

Shared Pool Capping Rule: the lower of the sum of each partition for a product or

the processor core capacity of the shared pool

Aggregate fractional processor cores, apply shared pool capping rules, and

round up at the server level to the next whole processor core.


November 1, 2016


13

DB2 cores to license: • 1.0 from dedicated partition B

• 1.7 from EC for capped partition E

• 3.0 from VP for uncapped partition H

= 5.7 rounded up to 6

License Counting – POWER6 or Later Multiple Shared Pool with Capped and Uncapped Partitions

A

i5/OS

B

AIX

DB2

C

Linux

Physical Shared Pool (9 processor cores)

1 1 1 1 2 3 4 5 6 7 8 9

D

Capped

i5/OS

VP = 2

EC= 1.80

E

Capped

AIX

DB2

VP = 4

EC= 1.7

F

Capped

Linux

WAS

VP = 4

EC = 2.00

G

Uncapped

i5/OS

WAS

VP = 7

EC = 2.00

H

Uncapped

AIX

WAS

DB2

VP = 3

EC = 1.00

WebSphere cores to license: • 2 from EC for capped partition F

• 7 from VP for uncapped partition G

• 3 from VP for uncapped partition H

= 12 but reduced to 5 (maximum

cores available to virtual shared pool #2)

Virtual Shared pool #1

7 processor cores

Virtual Shared pool #2

5 processor cores

License Rules:



For Uncapped Partitions: The highest actual* number of Online VP (Virtual Processor Cores)

Shared Pool Capping Rule: the lower of the sum of each partition for a product or the processor

core capacity of the shared pool

Aggregate fractional processor cores, apply shared pool capping rules, and round up at the

server level to the next whole processor core.



November 1, 2016


14

WebSphere cores to license: • 2 from EC for capped partition F

• 7 from VP for uncapped partition G

• 3 from VP for uncapped partition H

= 12, but reduced to 11 (maximum cores

available to the shared pool with the

donated capacity from partition B)

DB2 cores to license: • 2 from dedicated partition B

• 2 from EC capped partition E

• 2 from EC capped partition F

• 3 from VP for uncapped

partition H

= 9 cores

License Counting – POWER6 or Later Shared Dedicated Partition

A B

DB2

Physical Shared Pool (9 processor cores + 2 donated) =11

1 2 1 2 3 4 5 6 7 8 9

F

Capped

Linux

WAS

DB2

VP = 4

EC = 2.00

E

Capped

AIX

DB2

VP = 4

EC= 2.00

H

Uncapped

AIX

WAS

DB2

VP = 3

EC = 1.00

G

Uncapped

i5/OS

WAS

VP = 7

EC = 3.00

D

Capped

i5/OS

VP = 1

EC= 1.00


Partition B is a Shared Dedicated Partition.

2 processor cores of unused capacity from Partition B

are donated to the physical shared pool

License Rules: For Capped Partitions: The highest actual* level of Entitled Capacity (EC); formerly referred to

as Processing Unit (PrU).

For Uncapped Partitions: The highest actual* number of VP (Virtual Processors)

License rule: the lower of the sum of each partition for a product or the processor core

capacity of the shared pool (including the donated capacity from a shared dedicated partition)

Aggregate fractional processor cores, apply capping rules and round up to the next whole

number at server level


November 1, 2016


15

License Counting – POWER6 or Later Live Partition Mobility

B

Uncapped

AIX

DB2

VP = 10

EC= 2

A

Capped

AIX

DB2

VP = 1

EC= 1



(8 processor cores)

1 2 3 4 5 6 7 8

C

Uncapped

AIX

VP = 3

EC= 2



(10 processor cores)

1 2 3 4 5 6 9 10

Movement

of LPAR to

a different

server with

no loss of

service

B’

Uncapped

AIX

DB2

VP = 10

EC= 2

7 8

D

Capped

AIX

VP = 3

EC = 2

• Sub-capacity Licensing After Mobility

Event

DB2 cores to license = 11

Server#1

1 - LPAR A (EC=1)

Server#2

10 – LPAR B (VP=10)

License Rule for Qualified Mobility:

Count the maximum processor core capacity for each program concurrently within an

ILMT Region.

Requirements:

Using ILMT 9.2.2 or later version: A single ILMT server can be used to manage each

ILMT Region using IBM sub-capacity region functionality

Using ILMT 9.2 or earlier version: A minimum of one ILMT server must be installed per

ILMT Region where sub-capacity programs are installed

ILMT Regions:

Region 1: North America & South America

Region 2: Europe & Africa

Region 3: Asia & Australia

Count the maximum

peak capacity for each

program at any point in

time:


• Sub-capacity Licensing Prior

to Mobility Event:


Server#1 (capped at 8)

1 - LPAR A (EC=1)

10- LPAR B (VP=10)

November 1, 2016


16

License Counting – PowerKVM

VM 1

WAS

DB2

VM 2

WAS

VM 3

WAS

DB2

4 4 1

12


License counting for KVM

• Eligible Virtualization Technology can be used to create Virtual Machines

(VMs) Each VM is assigned a quantity of virtual cores

• Each virtual core is equal to one core for PVU licensing.

• License PVUs for the maximum number of virtual cores in the VM(s)

available to the product

• the lower of the sum of virtual cores or full capacity of the server

For above example, the PVU Virtualization Capacity licensing requirement

is based on the maximum number of virtual cores in the VM(s) available to

a product

License Rule: lower of the Virtualization Capacity or Full (Physical) Capacity

available in the Server

November 1, 2016

Virtual Cores

Software Products

Physical Cores

Virtual Machine (VM)

WAS cores to license:

4 from VM1

4 from VM2

1 from VM3

9 Total

DB2 cores to license:

4 from VM1

1 from VM3

5 Total


17

License Rules for Partitions, Shared Pools, and Micro-partitioning for each product:

for a Dedicated or Shared Dedicated LPAR, the highest actual* number of cores allocated to the LPAR

for a Capped Partition, the highest actual* amount of Entitled Capacity (EC)

Note: Recommend licensing to the Desired Processing Units from HMC, or a higher amount to be reached through a

DLPAR

for a Uncapped Partitions, the highest actual* amount of online VP (Virtual Processor Cores)

Note: Recommend licensing to the Desired VP from HMC, or a higher amount to be reached through a DLPAR

for a Shared Processor Pool, the lower of the sum of each partition for a product or the processor core

capacity of the shared pool (including the donated capacity from a shared dedicated partition)

Aggregate fractional processor cores, apply shared pool capping rules, and round up at the server level to

the next whole processor core

(lower of the sum of the virtual cores or the server capacity)


ILMT Licensing Counting Rules – for Single Server Environments

License Rule for Qualified Mobility:

Count the maximum processor core capacity for each program concurrently within an ILMT Region.

Requirements:

Using ILMT 9.2.2 or later version: A single ILMT server can be used to manage each ILMT Region using IBM sub-capacity region

functionality

Using ILMT 9.2 or earlier version: A minimum of one ILMT server must be installed per ILMT Region where sub-capacity programs

are installed

ILMT Regions:

Region 1: North America & South America

Region 2: Europe & Africa

Region 3: Asia & Australia

November 1, 2016


18

The licensing rules in the preceding pages reflect how ILMT will operate to calculate PVUs

If ILMT does not yet support a Eligible Virtualization Environment, or you qualify for an exception to use ILMT, you will need to follow the Manual Calculation of Virtualization Capacity.

The Manual Calculation of Virtualization Capacity rules can be found in the following pages (slides 18-20) in the deck

To find out if a Eligible Virtualization Technology is supported by ILMT visit Passport Advantage Sub-capacity licensing information

November 1, 2016





19

Manual Calculation of Virtualization Capacity

Eligibility Criteria: Customers must use the IBM License Metric Tool, with the

following exceptions ILMT does not support the Eligible Virtualization Environment

Customer has fewer than 1000 employees and contractors - Tool recommended

Customer server Full Capacity licensing for a PVU product is less than 1000 PVUs

(on servers with an Eligible Virtualization Environment) - Tool recommended

Requirements: For the above exceptions, customers must manually manage,

track and prepare Audit Reports An Audit Report must be prepared at least once per quarter and identify the

following detail: Each Eligible Sub-Capacity Product deployed in each Eligible

Virtualization Environment

An Eligible Virtualization Environment can be a Single Server or a Group of Servers

(Server Cluster)

In addition to the above detail, the report should provide a summary total of the

required number of PVUs by and for each Eligible Sub-Capacity Product

Audit Reports must be prepared as frequently as is required to maintain a history of

increases to Virtualization Capacity and Full Capacity

Each Audit Report must be generated, at least once per quarter

The above is only a summary. For detailed terms please see the Sub-capacity licensing attachment

November 1, 2016

http://www-306.ibm.com/software/lotus/passportadvantage/subcapacityattachments.html




20

Manual Calculation of Virtualization Capacity – Rules

License Rules for a partition, shared pools and micro-partitioning for each product:

for a Dedicated LPAR, the highest actual* number of cores allocated to the LPAR

for a Capped Partition, the highest actual* amount of Entitled Capacity (EC)

for a Uncapped Partition, the highest actual* amount of Online VP (Virtual Processor Cores)

*The greater of what the partition starts with or the result of a DLPAR operation (in whole cores)

The PVU licensing requirement is based on the maximum number of virtual processor cores in the partitions available to a product (lower of the sum of the virtual cores or the server capacity)

If you want to use sub-capacity licensing for any other PowerVM technology, including shared processor pool, multiple shared processor pool, shared dedicated partition or Live Partition Mobility, you must use the ILMT tool

For Single Server Environments:

November 1, 2016


21

Manual Calculation of Virtualization Capacity - Worksheet Example

Worksheet has 3 tabs;

use the following tabs

Instructions & Information

Single Server

Web Link: Worksheet for Manual Calculation of Virtualization Capacity

VIRTUALIZATION ENVIRONMENT - SINGLE SERVER- This worksheet is for one standalone server for one Software Product

- Per the Instructions on the first tab, you may choose to leverage this approach or develop / leverage

your own processes and reporting format so long as you capture all the mandatory information below

- Enter data in input fields below (shaded area) * Mandatory

Date of this Audit Report *

Product Name *

Program Identification Number (57xx-xxx)

P/N Description

Part Number

Server ID / Location

Server Vendor / Brand

Server Model

Virtualization Technology used *

Processor Technology (Vendor, Brand,Type,Model#) * (A)

PVUs per core * (A)

Total Activated Cores on Server * (C)

Full Capacity PVUs for Server * (C)

12 DO NOT DELETE ROW

VM, Partition ID * (whatever identifier used for any subdivision of a server such as

LPAR #, IP address, hostname, etc.)

Cores (B) per

Partition or

VM * User Comments

A 4

B 4

C 2

D 2

Sum of Virtual Cores * 12

PVUs per core * 70

Virtualization Capacity PVUs by Product for Server * 840

PVU Licenses required by Product for Server * (C) 560

* Mandatory Field

http://www-01.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customers.html

(C) Lower of Full Capacity or Virtualization Capacity

8

560

70

D55WJLL

IBM System x

xxxxx

Intel Xeon Quad Core Model 35XX

March 31, 2009

(A) PVU's required for each physical processor core are listed on the PVU table (see link below, including vendor/brand designations)

VMware ESX 3.5

(B) For purposes of 'Manual Calculation' of Virtual Capacity, 1 virtual core (or CPU) is equivalent to 1 physical core. Enter values in whole cores.

IBM WEBSPHERE APPLICATION SERVER NETWORK DEPLOYMENT

5724-H88

IBM WEBSPHERE APPLICATION SERVER NETWORK DEPLOYMENT

PROCESSOR VALUE UNIT (PVU)

Server ID # F6015; Bldg 1, Room 1, Somers, NY

November 1, 2016

ftp://ftp.software.ibm.com/software/passportadvantage/SubCapacity/Manual_Calculation_of_Virtualization_Capacity.xls




22

PVU

PVU table and other information

Sub-capacity

Passport Advantage Sub-capacity licensing Information

Virtualization Capacity License Counting Rules

Passport Advantage Sub-capacity licensing terms

Key Web Links

November 1, 2016

http://www-306.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customers.html




http://www-306.ibm.com/software/lotus/passportadvantage/Counting_Software_licenses_using_specific_virtualization_technologies.html

http://www-01.ibm.com/software/lotus/passportadvantage/pa_agreements.html




23

Partition Settings

Processor Capacity setting:

Determines the amount of ECs assigned to the partition. Customers

specify the minimum, desired, and maximum values

• Minimum: Amount of EC required to start up the partition

• Desired: The desired amount of EC for the partition to start with

• Maximum: Used as an upper limit for future Dynamic LPAR (DLPAR)

operations that customers execute to increase entitled capacity.

Virtual Processor setting:

Determines the amount of VPs assigned to the partition. Customers

specify the minimum, desired, and maximum values.

• Minimum: Amount of VPs required to start up the partition.

• Desired: The desired amount of VPs for the partition to start with

• Maximum: Used as an upper limit for future dynamic LPAR (DLPAR)

operations that customers execute to increase the number of virtual

processors.

November 1, 2016


24

Capped & Uncapped Partition License Counting Rationale

Capped partition:

This type of shared processor partition can never be allocated processing capacity that is more than its Entitled Capacity.

Entitled Capacity: The actual processor core capacity available to a partition. May be changed via DLPAR operation after startup.

Virtual Processor (VP): Defines the number of physical processor cores that the system can access to provide the processing capacity of a shared processors partition.

License the highest actual* amount of Entitled Capacity. A partition may start up with a certain Entitled Capacity (between Minimum and Desired ) but through a DLPAR

operation, this Entitled Capacity may be increased (up to the Maximum) or decreased. Hence, the license must cover the greater of the Entitled Capacity the partition starts with or the result of a DLPAR operation

Note: Recommend licensing to the Desired Processing Units from HMC or a higher amount to be reached through a DLPAR

Uncapped partition:

This type of shared processor partition can be allocated processing capacity that can exceed its Entitled Capacity.

The Entitled Capacity defines the basic or ‘start up’ processor capacity

The VP defines the number of physical processor cores that the partition can access to grab idle processor capacity available. It can access the unused processor cores in the shared pool, when available, up to the Online VP value (VP).

Online VPs: The actual VPs available to a partition. May be changed via DLPAR operation after startup.

License VP equal to the highest actual* amount of Online VPs. A partition may start up with a certain Online VP (between Minimum and Desired ) but through a DLPAR

operation, this Online VP may be increased (up to the Maximum) or decreased. Hence, the license must cover the greater of the Online VPs a partition starts with or the result of a DLPAR operation.

Note: Recommend licensing to the Desired VP from HMC or a higher amount to be reached through a DLPAR

* greater of a) what the partition starts with or b) the result of a DLPAR operation

November 1, 2016


25

HMC Processor settings for a Partition for all OS

HMC Panel provides

information on “Min”,

"Desired" and “Maximum”.

Recommend licensing to:

a) Desired - as a partition

will start with these

resources if available or

b) a higher amount (up to

Max), if customer plans to

do a DLPAR to a higher

level than Desired

Determine EC (Entitled Capacity)

Determine Online VP

November 1, 2016


26

Information for Licensing a partition - AIX

November 1, 2016


27

Information for Licensing a partition – i OS

This slide is for i OS contains similar information as the prior 2 slides

November 1, 2016

Sub-capacity (Virtualization) License Counting...

Documents

Transcript of Sub-capacity (Virtualization) License Counting...