General Licensing Notes:
The following tables describe how to determine the required subscription capacity for VCF, vSphere Foundation and vSAN.
VCF with vSAN Capacity Table
VCF with vSAN Capacity Licensing Notes:
# of Hosts ********** |
CPUs / Host ********** |
Cores / CPU ********** |
TiBs / Host *********/ |
TiBs / Cluster ********** |
Entitled TiBs from Foundation |
Subscription Capacity Required for VCF (Core) |
Subscription Capacity Required for vSAN (TiB) |
Calculation |
3 | 1 | 8 | 3.840 | 11.520 | 48 | 48 | -36 |
VCF: Though the number of cores is 8 on each CPU, customers must purchase 48 because the minimum subscription capacity is 16 cores per CPU and there is 1 CPU on each of the 3 ESXi host. |
3 | 2 | 16 | 1.840 | 5.520 | 96 | 96 | -90 | VCF: Subscription capacity is the total number of cores × number of CPUs × number of ESXi hosts. vSAN: Customers will receive 96 TiBs of vSAN, which exceeds their desired amount of capacity and there will be 90 TiBs left over. No additional capacity is needed. |
3 | 2 | 16 | 49.920 | 149.760 | 96 | 96 | 54 | VCF: Subscription capacity is the total number of cores × number of CPUs × number of ESXi hosts. vSAN: Customers will receive 96 TiBs of vSAN and need to purchase an additional 54 TiBs of vSAN capacity. |
3 | 2 | 24 | 61.440 | 184.320 | 144 | 144 | 41 | VCF: Subscription capacity is the total number of cores × number of CPUs × number of ESXi hosts. vSAN: Customers will receive 144 TiBs of vSAN and need to purchase an additional 41 TiBs of vSAN capacity. |
3 | 1 | 6 | 8.393 | 25.178 | 48 | 48 | -22 | VCF: Though the number of cores is 6 on each CPU, customers must purchase 48 because the minimum subscription capacity is 16 cores per CPU and there is 1 CPU on each of the 3 ESXi hosts. vSAN: Customers will receive 48 TiBs of vSAN, which exceeds their desired amount of capacity and there will be 22 TiBs left over. No additional capacity is needed |
4 | 2 | 20 | 4.473 | 17.893 | 160 | 160 | -142 | VCF: Subscription capacity is the total number of cores × number of CPUs × number of ESXi hosts. vSAN: Customers will receive 160 TiBs of vSAN, which exceeds their desired amount of capacity and there will be 142 TiBs left over. No additional capacity is needed. |
vSphere Foundation with vSAN Capacity Licensing Notes:
# of Hosts ********** |
CPUs / Host ********** |
Cores / CPU ********** |
TiBs / Host ********** |
TiBs / Cluster ********** |
Entitled TiBs from Foundation | Subscription Capacity Required for vSphere Foundation (Core) |
Subscription Capacity Required for vSAN (TiB) **************** |
Calculation |
3 | 1 | 8 | 3.840 | 11.520 | 4.688 | 48 | 12 | vSphere Foundation: Though the number of cores is 8 on each CPU, customers must purchase 48 cores because the minimum subscription capacity is 16 cores per CPU and there is 1 CPU on each of the 3 ESXi hosts. vSAN: There is insufficient trial capacity from VVF. Therefore, subscription capacity is the total number of TiBs x number of ESXi hosts in each vSAN cluster. |
3 | 2 | 16 | 1.840 | 5.520 | 9.375 | 96 | 0 | vSphere Foundation: Subscription capacity is the total number of cores × number of CPUs × number of ESXi hosts. vSAN: Since the trial capacity (9.375 TiBs) from VVF is greater than or equal to the number of TiBs in vSAN cluster (5.520), customers have sufficient vSAN trial capacity and do not need to purchase additional vSAN capacity. |
3 | 2 | 16 | 49.920 | 149.760 | 9.375 | 96 | 150 | vSphere Foundation: Subscription capacity is the total number of cores × number of CPUs × number of ESXi hosts. vSAN: There is insufficient trial capacity from VVF. Therefore, subscription capacity is the total number of TiBs x number of ESXi hosts in each vSAN cluster. |
3 | 2 | 24 | 61.440 | 184.320 | 14.063 | 144 | 185 | vSphere Foundation: Subscription capacity is the total number of cores × number of CPUs × number of ESXi hosts. vSAN: There is insufficient trial capacity from VVF. Therefore, subscription capacity is the total number of TiBs x number of ESXi hosts in each vSAN cluster. |
3 | 1 | 6 | 8.393 | 25.178 | 4.688 | 48 | 26 | vSphere Foundation: Though the number of cores is 6 on each CPU, customers must purchase 48 because the minimum subscription capacity is 16 cores per CPU and there is 1 CPU on each of the 3 ESXi hosts. vSAN: There is insufficient trial capacity from VVF. Therefore, subscription capacity is the total number of TiBs x number of ESXi hosts in each vSAN cluster. |
4 | 2 | 20 | 4.473 | 17.893 | 15.625 | 160 | 18 | vSphere Foundation: Subscription capacity is the total number of cores × number of CPUs × number of ESXi hosts. vSAN: There is insufficient trial capacity from VVF. Therefore, subscription capacity is the total number of TiBs x number of ESXi hosts in each vSAN cluster. |
Symptoms:
VMware has created a tool to identify the number of Core licenses (with a minimum of 16 cores per physical CPU) and TiB licenses that are required to properly license the following VMware products – VMware Cloud Foundation (VCF), VMware vSphere Foundation (VVF), and VMware vSAN for current environments.
The number of core licenses (with a minimum of 16 cores per physical CPU) required for vSphere Foundation and VCF and TiB licenses required for vSAN can be identified in one of two ways:
Use:
Connect-VIServer -Server <Server_FQDN/IP>
Import-Module .\FoundationCoreAndTiBUsage.psm1
Get-FoundationCoreAndTiBUsage -DeploymentType VCF
Get-FoundationCoreAndTiBUsage -DeploymentType VVF
4.Disconnect from vCenter Server:
Disconnect-VIServer -Server <Server_FQDN/IP>
Here is an example output after running the PowerCLI tool
VCF with vSAN Example
VVF with vSAN Example
The table below describes each of the columns in the Compute Usage and vSAN Usage sections. At the bottom of the output shows the total quantity of VCF or VVF cores and vSAN TiB licenses required.
Column Name | Description |
Compute Usage Information |
|
CLUSTER | This column displays the name of the cluster. If there is no value in this column, this means the host is not part of the cluster. |
VMHOST | This column displays the host IP address. |
NUM_CPU_SOCKETS | This column displays the quantity of CPU sockets in the host. |
NUM_CPU_CORES_PER_SOCKET | This column displays the quantity of cores in each CPU socket in the host. |
FOUNDATION_LICENSE _CORE_COUNT |
This column displays the quantity of core licenses required for VCF or VVF licensing in the cluster. |
vSAN Usage Information |
|
CLUSTER | This column displays the name of the cluster. |
NUM_HOSTS | This column displays the quantity of hosts in the cluster. |
NUM_CPU_SOCKETS | This column displays the quantity of CPU sockets in the cluster. |
NUM_CPU_CORES | This column displays the quantity of cores in the cluster. |
FOUNDATION_LICENSE_CORE_COUNT | This column displays the quantity of core licenses from the Foundation offer in the cluster. |
ENTITLED_VSAN_LICENSE_TIB_COUNT | This column displays the quantity of TiB licenses received from the Foundation offer in the cluster. |
REQUIRED_VSAN_TIB_CAPACITY | This column displays the required TiB capacity for the cluster. |
VSAN_LICENSE_TIB_COUNT | This column displays the number of TiB licenses required for the cluster after taking into account any TiB entitlement received from the Foundation offer. • If the figure is negative or 0, this represents that the quantity of TiBs received from the Foundation offer is greater than or equal to the quantity of TiBs that require licenses. No additional licensing is required and excess capacity can be aggregated. • If the figure is positive, this represents that the quantity of TiBs that require licenses is greater than the quantity of TiBs received from the Foundation offer. Additional licensing is required. |
Get-FoundationCoreAndTiBUsage -ClusterName “Cluster_Name” – DeploymentType VCF
Get-FoundationCoreAndTiBUsage -ClusterName Cluster_Name – DeploymentType VCF -CSV
Get-FoundationCoreAndTiBUsage -ClusterName Cluster_Name – DeploymentType VCF -CSV -Filename “name.csv”
Get-FoundationCoreAndTiBUsage -ClusterName Cluster_Name – DeploymentType VCF -CollectLicenseKey
Note: You will receive two files. The one with -vsan appended includes the TiB count information, while the other file includes the core count information.
Related Information
Figure 1 - Core Count
Figure 2 – TiB Count
Note: If when attempting to run this script you receive an error similar to: "cannot be loaded. The file xxxx.psm1 is not digitally signed. You cannot run this script on the current system. For more information abut running scripts and setting execution policy, see about_Execution_Policies at htt;s//microsoft...."
Run the following command to bypass the execution policy, then run the script again:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass