Error: vSAN add-on license assignment fails due to TiB capacity mismatch in VCF Operations 9.x
search cancel

Error: vSAN add-on license assignment fails due to TiB capacity mismatch in VCF Operations 9.x

book

Article ID: 411654

calendar_today

Updated On:

Products

VCF Operations VMware vCenter Server

Issue/Introduction

In VMware Cloud Foundation (VCF) 9.x environments, attempting to assign a vSAN add-on license via the VCF Operations portal may fail with a grayed-out "Assign" button. This occurs when the licensed capacity does not meet the total raw physical storage requirements of the cluster.

Symptoms

  • The Assign button for the vSAN add-on license is grayed out in the VCF Operations portal.
  • Clicking the red exclamation icon reveals an error: Used Capacity – #### TiB, Allocated Capacity #### TiB – ‘To assign this license, it must have allocated capacity of #### TiB’.
  • The issue occurs even when actual logical usage is below the licensed limit.

Environment

  • VMware Cloud Foundation 9.x
  • VCF Operations Manager
  • vSAN Add-on Licensing

Cause

VCF 9.x validates vSAN add-on licenses against the Total Raw Physical Storage (TiB) contributed by all hosts in the cluster, rather than logical data usage. A rounding discrepancy (e.g., 1 TiB difference) between the hardware's reported raw capacity and the entitlement provided in the license file will block the assignment. This is frequently observed in air-gapped or disconnected deployments where licenses are manually generated.

Resolution

  1. Verify the exact Total Raw Physical Storage reported by VCF Operations for the cluster.
  2. Compare this value against the Allocated Capacity in the current license file.
  3. If a discrepancy exists, contact the Broadcom Account Team or Licensing TAM to adjust the entitlement to match the hardware's raw reported TiB.
  4. Once the updated entitlement is processed, download the new license file from Download Broadcom products and software.
  5. Import the revised license into VCF Operations and assign it to the affected vCenter.

Additional Information

To speak with a customer representative or a Support Engineer, see . Scroll to the bottom of the page and click on your respective region.