Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Counting CPU licenses needed under new VMware licensing policy (77098)

Last Updated: 3/1/2021Categories: InformationalTotal Views: 72474Language:
Chinese (Simplified)JapaneseEnglish

37 like this article

Subscribe to get an email
newsletter with new updates

37 people found this helpful Please provide article feedback:

Details

VMware has created a tool to identify the number of per-CPU licenses (supporting up to 32 physical cores per CPU) required for existing deployments when upgrading to new major versions of VMware products. This tool will also be useful for VMware products purchased after changes to the licensing model announced on Feb 3, 2020.

Solution

To identify the number of CPU licenses (supporting up to 32 physical cores per CPU) required for upgrading to a new major version of vSphere and vSAN (starting Apr 2, 2020 as described in the blog post ) in one of two ways:

For small deployments and ESXi hosts not connected to a vCenter Server: Navigate to Host > Hardware > CPU and check the value of Cores per socket to determine if your host has more than 32 physical cores per CPU.

For larger deployments: VMware has developed the attached PowerCLI tool that collects and consolidates information on the quantity of CPU licenses (supporting up to 32 physical cores per CPU) required for each host connected to a vCenter Server.

Prerequisite:

VMware PowerCLI 10.x or greater installed

Download and extract the attached 77098_vSphereCPUSocketToCoreUsage.zip

Connect to vCenter Server:

Connect-VIServer -Server vCenter_Server

Import PowerCLI function:

Import-Module .\vSphereCPUSocketToCoreUsage.psm1

Run Get-vSphereCPUSocketToCoreUsage function to retrieve results. By default, the script will iterate through all vSphere Clusters.

CPU_LICENSE_COUNT: The current Licensing method's CPU count
LIMITED_CPU_CORE_LICENSE_COUNT: CPU count under the new licensing model.

If the CPU_LICENSE_COUNT and LIMITED_CPU_CORE_LICENSE_COUNT values are equal, there will be no change in licensing. If LIMITED_CPU_CORE_LICENSE_COUNT is larger than CPU_LICENSE_COUNT, the licensing will need to be changed.

To specify a specific vSphere Cluster, you can use -ClusterName option:

Get-vSphereCPUSocketToCoreUsage -ClusterName Cluster_Name

To output the results into a CSV file, you can use -Csv option:

Get-vSphereCPUSocketToCoreUsage -Csv

To name the CSV file, you can use -Filename option:

Get-vSphereCPUSocketToCoreUsage -Csv -Filename name.csv

Additional Information
Licensing ESXi 6.x/7.0.x and vCenter Server 6.x/7.0.x

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

77098_vSphereCPUSocketToCoreUsage

Additional Resources

KB
•
コンテンツ ライブラリから複数の仮想マシンをデプロイすると、ユーザー インターフェイスに別の vCenter Server のカスタム仕様が表示される (77172)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCloud Director 10.0 に仮想マシンの監視チャートが表示されない (77055)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere

VMware vSAN

Related Versions:

VMware vSphere 6.7.x

VMware vSphere 6.5.x

VMware vSAN 6.x

Take Our Survey

Support Assistant