V sphere5計價

vSphere 5 Licensing and Packaging

VMware, August 2011

© 2009 VMware Inc. All rights reserved

vSphere 5 licensing: Evolution Without Disruption

vSphere 4.x vSphere 5

Licensing Unit Processor = Processor

!
Core per proc Restricted < Unlimited

Physical RAM
Restricted < Unlimited
per host
Amt of vRAM pooled
Pooled vRAM
NA ≠ across entire
entitlement
environment

2

What is vRAM?

 vRAM is the memory configured to a virtual machine
 Assigning a certain amount of vRAM is a required step in the
creation of a virtual machine

3

Key vRAM Concepts

1 Each vSphere 5 processor license comes with certain
amount of vRAM entitlement

2 Pooled vRAM Entitlement Sum of all
processor license
Consumed vRAM entitlements
3
Sum of vRAM
configured into all
powered on VMs

4
Compliance =
12 month rolling average of Consumed vRAM < Pooled vRAM Entitlement

4

Key concepts - Example

4 licenses of vSphere
Each vSphere Enterprise
Enterprise Edition
Edition license entitles
vRAM Pool (256GB) provide a vRAM pool of
to 64GB of vRAM.
256GB (4 * 64 GB)
Consumed vRAM = 80 GB

64GB 64GB 64GB 64GB
Customer creates
20 VMs with 4GB
vRAM each

vSphere Ent vSphere Ent

1 1 1 1
CPU CPU CPU CPU

Host A Host B

Compliance =
12 month rolling average of Consumed vRAM < Pooled vRAM Entitlement

5

vSphere 5 Licensing
Detail

6

vSphere 5.0 Licensing Model in More Detail
vSphere 4.1 and prior vSphere 5.0 and later
Per CPU with Core and Physical Per CPU with
Memory Limits vRAM Entitlements
Licensing Unit CPU = CPU

SnS Unit CPU = CPU

Restrictions by vSphere editions
Core per proc • 6 cores for Standard and Enterprise, Ess, Ess+ < Unlimited
• 12 core for Advanced and Ent. Plus

Restrictions by vSphere edition
Physical RAM • 256GB for Standard, Advanced and Enterprise.
capacity per host Ess, Ess+
< Unlimited
• Unlimited for Enterprise Plus

Entitlement by vSphere edition
• 32GB vRAM for Essentials Kit
vRAM entitlement per
proc
Not applicable ≠ •
•
32GB vRAM for Essentials Plus Kit
32GB vRAM for Standard
• 64GB vRAM for Enterprise
• 96GB vRAM for Enterprise Plus

YES – vRAM entitlements are pooled
Pooling of entitlements Not applicable < among vSphere hosts managed by a
vCenter or linked vCenter instance

Max amount of vRAM per 96GB – a powered on VM will count for a
VM counted
Not applicable ≠ maximum of 96GB against the pool
regardless of its actual configured amount
• Purchase in advance of use
• Purchase in advance of use
Compliance policies = • 12 months rolling average of daily
• High Watermark
high watermark

Monitoring tool Not applicable ≠ YES – built-into vCenter Server 5.0
7

vSphere 5 Licensing In Action

How does it work? vSphere 5.0
 Each CPU must have at least one vSphere license
assigned
vRAM Pool
• Cores and physical RAM do not matter
(using 80 GB out of 256GB)
 Each processor license managed by a vCenter or
multiple vCenters in Linked mode contributes an
amount of vRAM capacity to the total vRAM pool
• Example: 4 vSphere Ent. Licenses create a vRAM pool
of 256GB of vRAM (4 x 64GB)
• Each vSphere Edition creates a separate pool that
must be kept in licensing compliance
 vRAM pool is shared among powered-on VMs
running on all hosts in a vCenter
• Example: 20 VMs with 4GB of configured vRAM VMware vCenter Server
consume a total of 80GB vRAM
• It doesn’t matter how many VMs you run and on which vSphere Ent vSphere Ent
hosts you run them.
• vMotion, DRS, HA do not require additional licenses 1 1 1 1
 At any point in time the 12 month rolling average of
CPU CPU CPU CPU
daily high watermark of consumed vRAM must be
equal or less to the vRAM pool capacity
• Compliance is at the vCenter level not the host level
 vRAM pool can be extended by: Host A Host B
• Upgrading all CPUs to higher end vSphere Edition
1
• Adding processor licenses to the same set of CPUs VM Processor
• Adding a new host with new licenses (4GB vRAM) License

8

Tools for Tracking vRAM Entitlement vs Usage

 Before upgrading to vSphere 5, customers can use a
separate free utility that analyzes a VI3 or vSphere 4
environment, and determines vRAM consumed
• The tool will be available later in Q3 2011
 After upgrading to vSphere 5:
1. vRAM licensing monitoring and reporting tool built into vCenter 5
2. Free add-on to vCenter for in-depth historical trending analysis

9

When Does the vSphere 5 Licensing Model Apply?

For ELA customers

 Customers with active ELA will continue to be subject to the terms of their
contracts for the duration of their contract, independent of which vSphere
version they deployed
• ELA customers may contact their VMware sales representatives to update the
terms of their ELAs to the new vSphere 5 licensing model
For customers without ELAs
 The new model applies only to vSphere 5 licenses. Prior versions of
vSphere will continue to be based on their respective licensing model

 The new vSphere 5 licensing model will apply upon acceptance of the
vSphere 5 EULA (necessary condition to upgrade to vSphere 5)

 Customers who purchase vSphere 5 licenses and decide to downgrade to
older versions of vSphere will be subject to the EULA terms and licensing
model of the vSphere version they downgrade to

10

vSphere 5 Editions
Essentials Essentials Enterprise
`  New in vSphere 5.0 Essentials Essentials Standard Standard
Advanced Enterprise
Plus Plus Plus

vRAM Entitlement per proc 32 GB +
32GB 32 GB 64 GB 96 GB
vCPU 8 way 8 way 8 way 8 way 32 way
vSphere
Features Storage
Hypervisor Appliance
High Availability
Data Recovery
vMotion
Virtual Serial Port Concentrator
Hot Add
vShield Zones
Fault Tolerance
Storage APIs for Array Integration
Storage vMotion
Distribute Resource Scheduler &
Distributed Power Management
Distributed Switch
I/O Controls (Network and Storage)
Host Profiles
Auto deploy 
Profile-Driven Storage 
Storage DRS 

All editions include: Thin Provisioning, Update Manager, Storage APIs for Data Protection, Image Profile, and SLES (except Ess and Ess +)

12

vSphere 5 Acceleration Kits
Essentials Standard Enterprise Enterprise
 New in vSphere 5.0
Essentials
Plus AK AK Plus AK

Entitlements per CPU license
• vRAM Entitlement 32 GB 32 GB 32 GB 64 GB 96 GB
(192 GB max) (192 GB max) (256GB per kit) (384 per kit) (576 per kit)
• vCPU 8 way 8 way 8 way 8 way 32 way
Features
Hypervisor
High Availability
Data Recovery
vMotion
Virtual Serial Port Concentrator
Hot Add
vShield Zones
Fault Tolerance
Storage APIs for Array Integration
Storage vMotion
Distribute Resource Scheduler &
Distributed Power Management
Distributed Switch
I/O Controls (Network and Storage)
Host Profiles
Auto deploy 
Profile-Driven Storage 
Storage DRS 

All editions include: Thin Provisioning, Update Manager, Storage APIs for Data Protection, Image Profile, and SLES (except Ess and Ess +)
13

Entitlement Paths for current vSphere 4.x customers

vSphere 4.x vSphere 5.0

Enterprise Plus Enterprise Plus

Enterprise Enterprise

Advanced

Standard Standard

Essentials Plus Essentials Plus

Essentials Essentials

14

Upgrade Paths for vSphere Editions and Kits

Enterprise Enterprise Plus

Enterprise Plus

Standard Enterprise

Any one of the
Essentials Plus
Acceleration Kits

Any one of the
Acceleration Kits

Essentials Essentials Plus

15

VMware vSphere Hypervisor 5

Entry level free product for single server virtualization
Full-featured hypervisor
 Based on VMware’s next generation hypervisor architecture, ESXi
 Provides the same performance, reliability and robustness of the
ESXi included with paid versions of VMware vSphere

Basic virtualization capabilities for a single host
 Cannot be centrally managed with vCenter Server
 Individual vSphere Hypervisor hosts can be remotely managed
with the vSphere Client
 Provides only basic server consolidation capabilities

Free
 Entitles to 32GB of vRAM per server and can be used on servers
with up to 32GB of physical RAM

 Can be easily upgraded to paid vSphere editions for central
management and advanced capabilities

16

vSphere Storage Appliance 1.0
Packaging

17

vSphere Storage Appliance - Shared Storage for Everyone

vSphere Storage Appliance
vSphere Storage Appliance
Shared storage capabilities,
without the cost and complexity

Licensing Per instance
(up to 3 nodes)

+ vSphere Essentials Plus w/
 Install in minutes vSphere Storage Appliance
1 Five click simplicity  Easy to use
 Saves money

High Availability without  Survive server failures vSphere Storage Appliance
2 the need for shared  No more planned
available at cost down
storage hardware downtime
when purchased with
vSphere Essentials Plus
World-class datacenter  Set and forget
3 capabilities – even for automation
small environments  Get more out of your
hardware

18

VMware vCenter
Site Recovery Manager 5.0
Packaging

19

SRM 5 Editions Lineup

SRM 5

Standard Enterprise

Scalability Limits

(1)
• Maximum protected VMs 75 virtual machines Unlimited(2)

Features

• Support for storage-based replication

• Centralized recovery plans

• Non-disruptive testing

• Automated DR failover

• vSphere Replication

• Automated failback

• Planned migration

1. Maximum of 75 VMs per site and per SRM instance
2. Subject to the product’s technical scalability limits
New in SRM 5.0
US pricing only. Pricing outside the US might vary

20

vSphere 5.0 Licensing -
Detailed Examples

21

Customer Scenario

 How do I license a host with vSphere 5?
 How much vRAM do I get with my vSphere 5 licenses?
 What is the vRAM pool?
 How many VMs can I run with my vRAM pool?
 How many VMs can I power on a host?
 What if my VMs move to a different host with vMotion or DRS?
 What is my vRAM pool if I have multiple vCenter Servers?
 What is my vRAM pool if I have more than one vSphere edition?
 How do I expand my vRAM pool?
 How do I license an new host and join it to my vRAM pool?
 What are the benefits of the vSphere 5 licensing model?
 Will vSphere 5 be more expensive for vSphere 4.x customers?

22

How Many vSphere Licenses Do I Need?

Answer
In this example:  Like in vSphere 4.x, each CPU requires at
• Licensing Host A with vSphere 5 requires the least one license
same number of licenses as with vSphere 4.x  vSphere 5 licensing does not impose limits
• Licensing Host B with vSphere 5 requires half on number of cores per processor and
the licenses of vSphere 4.x (2 vs. 4) because physical RAM per server
vSphere 5 does not limit the number of cores
per processor

Example
vSphere Ent vSphere Ent Summary

1 1 1 1 Hosts 2
CPUs 4
CPU CPU CPU CPU
vSphere Licenses 4

Host A Host B
Host A
2 sockets, 4 cores per CPU, 48GB RAM 1
Host B VM Powered-off Processor
2 sockets, 12 cores per CPU, 64GB RAM (4GB vRAM) VM License

23

How Much vRAM Do I Get with My vSphere Licenses?

Answer
Each vSphere Enterprise Edition license
entitles to 64GB of vRAM. Each vSphere 5 processor license
includes a vRAM entitlement

Edition vRam per License

Enterprise Plus 96GB
64GB 64GB 64GB 64GB
Enterprise 64GB

Standard 32GB

32GB
Essentials Plus
(192GB max)
vSphere Ent vSphere Ent 32GB
Essentials
(192GB max)
1 1 1 1
CPU CPU CPU CPU

Host A Host B
Host A

24

What is the vRAM pool?

Answer
4 licenses of vSphere Enterprise Edition
provide a vRAM pool of 256GB (4 * 64 GB)
 When managing vSphere hosts with
vCenter, vRAM entitlements are pooled
 vRAM pool capacity is the max capacity
that can be used with the current set of
licenses
64GB
vRAM Pool (256GB) 64GB
64GB 64GB

VMware vCenter Server
Example
vSphere Ent vSphere Ent License the following servers with vSphere
Enterprise Edition:
1 1 1 1
Summary
CPU CPU CPU CPU
CPUs 4
vSphere Licenses 4
Host A Host B
Pooled vRAM (GB) 256
Host A

25

How Many VMs Can I Run with My vRAM pool?
 24 powered on VMs each with 4GB of configured
vRAM consume a total of 96GB Answer
 Powered off VMs do not consume vRAM capacity
 You can run as many VMs as you want as
long as the consumed vRAM capacity is
equal or less than the vRAM pool
 Only powered on VMs consume vRAM
capacity

Example
vSphere Ent vSphere Ent  User creates 32 VMs with 4GB of
configured vRAM and powers on only 24
1 1 1 1
Summary
CPU CPU CPU CPU
CPUs 4
vSphere Licenses 4
Host A Host B
Host A
Consumed vRAM (GB) 96

26

How Many VMs Can I Power-on a Host?
 By running 36VMs on host B the user consumes
a total of 144GB on Host B
Answer
 The two Enterprise Ed. Licenses used for Host B
contributes a total of 128GB of vRAM to the pool
 You can power on as many VMs as you as
you want on a host as long as the total
consumed vRAM is less or equal to
available vRAM pool
 If necessary, you can increase the available
vRAM pool capacity by adding more proc.
… licenses to a CPU

Example
VMware vCenter Server  User deploys 40 VMs each with 4GB of
configured vRAM distributing 4 VMs on Host
A and 36 on Host B
1 1 1 1 Summary

CPU CPU CPU CPU A B Pool

vSphere Lic. 2 2 4

Host A Host B VMs 4 36 40

Host A Consumed vRAM (GB) 16 144 160
Host B VM Powered-off Processor vRam Pool (GB) 128 128 256

27

What if My VMs Move to a Different Host with vMotion or DRS?

Answer

Any VM can run on any host within a vRAM
pool. Since vRAM is pooled across all hosts of
the same vSphere edition under a vCenter
Server, the movement of VMs cannot cause
more vRAM to be needed.

Example

VMs on one host can vMotion to another without
impacting the consumed or available vRAM
vSphere Ent vSphere Ent capacity.
All VMs can even run on a single host, in effect
1 1 1 1 borrowing the vRAM capacity of the other host.
CPU CPU CPU CPU Summary
CPUs 4
Host A Host B vSphere Licenses 4
Host A
2 sockets, 4 cores per CPU, 48GB RAM 1 Pooled vRAM (GB) 256
2 sockets, 12 cores per CPU, 64GB RAM (4GB vRAM) VM License Consumed vRam (GB) 128

28

What is My vRAM Pool if I Have Multiple vCenter Servers?

You must link the vCenter Servers to form a single Answer
vRAM pool. The resulting vRAM capacity is the
sum of the two site’s vRAM capacity.
The vRAM pool can extend across multiple
linked vCenter Servers. vCenter Servers
Site 1 Site 2 (Standard Edition) can be linked together using
Linked Mode.

Example
Site 1 and Site 2 each contain a host with two
licenses of Enterprise. Each site has 128GB of
pooled vRAM capacity in a separate pool.
VMware vCenter VMware vCenter When the vCenter Servers at each site are linked
Server Server
together, one vRAM pool is created with 256 GB
vSphere Ent vSphere Ent of pooled vRAM capacity.
1 1 1 1 Summary
Summary
Site 1 1 and 2 2
Site Site
CPU CPU CPU CPU

CPUs
CPUs 2 4 2
vSphere Licenses
vSphere Licenses 2 4 2
Host A Host B
Host A
Pooled vRAM (GB)
Pooled vRAM (GB) 128 256 128
Host B VM Powered-off Processor Consumed vRam (GB)
Consumed vRam (GB) 64 128 64

29

What is My vRAM Pool if I Have More Than One vSphere
Edition?
Answer

Each edition of vSphere has a separate vRAM
pool. Adding licenses for one edition will not
add vRAM to other edition’s vRAM pool.

Example
Host X is licensed with two licenses of Enterprise
VMware vCenter Server Plus. There are two separate vRAM pools: one
for Enterprise with 256 GB, another for Enterprise
vSphere Ent +
Plus with 192 GB.
1 1 1 1 1 1 Summary

CPU CPU CPU CPU CPU CPU Ent Ent+

CPUs 4 2

Host A Host B Host X vSphere Licenses 4 2

Host A Pooled vRAM (GB) 256 192
Host B VM Powered-off Processor Consumed vRam (GB) 128 96

30

I Need More vRAM Capacity. How Do I Expand my vRAM Pool?

Answer

There are two ways you can expand your
vRAM pool:
1) Upgrade all licenses to an edition with a
higher vRAM entitlement
2) Add more licenses of the current edition

… …
Example

VMware vCenter Server All 256GB of vRAM capacity is consumed.
Another 16 GB is needed for 4 additional VMs.

1 1 1 1
Summary
CPU CPU CPU CPU
CPUs 4
vSphere Licenses 4
Host A Host B
Host A
Consumed vRam (GB) 256

31

Enterprise Plus is entitled to 96GB of vRAM.
4 licenses * 96GB = 384GB vRAM Answer

vRAM pool:

… …
Example

vSphere Ent
vSphere Ent + vSphere Ent
vSphere Ent +
Upgrading all 4 licenses to Enterprise Plus would
1 1 1 1 raise the Pooled vRAM capacity to 384GB.
Summary
Summary
CPU CPU CPU CPU
CPUs
CPUs 4
4
vSphere Licenses
vSphere Licenses 4
4
Host A Host B
Pooled vRAM (GB)
384
Host A
Consumed vRam (GB)
272

32

One additional license of Enterprise will increase
the vRAM pool by 64GB, yielding a total pooled Answer
vRAM capacity of 320GB.
vRAM pool:

… …
Example

Adding one additional license of Enterprise would
1 1 1 1 1 increase the pooled vRAM capacity to 320GB.
Summary
CPU CPU CPU CPU
CPUs 4
vSphere Licenses 4
5
Host A Host B
320
Host A
272

33

How Do I License a New Host and Join It to My vRAM Pool?

Answer
There are two ways to add a host:
1) Add additional licenses of the same edition.
2) If you have more licenses than CPUs, you
can deploy those licenses to the new host.
Pooled vRAM capacity will remain
unchanged.

Example
VMware vCenter Server A new host, Host C, needs to be licensed.

1 1 1 1 1
Summary
CPU CPU CPU CPU CPU
CPUs 4
vSphere Licenses 5
Host A Host B Host C
Host A

34


Pooled vRAM capacity is increased
by 64GB. As before, VMs can run
Answer
on any of the three hosts.
1) Add additional licenses of the same edition
2) If you have more licenses than CPUs, you can
deploy those licenses to the new host. Pooled
vRAM capacity will remain unchanged.

Example
vSphere Ent vSphere Ent vSphere Ent One additional license of Enterprise is added. This
increases the pooled vRAM capacity to 384GB.
1 1 1 1 1 1
Summary
CPU CPU CPU CPU CPU
CPUs 4
5
vSphere Licenses 5
6
384
Host A

35

Pooled vRAM capacity remains
unchanged at 320GB. As before, the
Answer
VMs can run on any of the three hosts.
1) Add additional licenses of the same edition.
2) If you have more licenses than CPUs,
you can deploy those licenses to the
new host. Pooled vRAM capacity will
remain unchanged.

Example

vSphere Ent vSphere Ent vSphere Ent No additional vRAM is needed and there are more licenses
than CPUs. A license can be redeployed to Host C. Pooled
vRAM capacity remains unchanged.
1 1 1 1 1
Summary
CPU CPU CPU CPU CPU
CPUs 5
4
vSphere Licenses 5
Host A

36

V sphere5計價

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie V sphere5計價

Ähnlich wie V sphere5計價 (20)

Mehr von 零壹科技股份有限公司

Mehr von 零壹科技股份有限公司 (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

V sphere5計價