Assigning ESXi license to ESXi host fails
search cancel

Assigning ESXi license to ESXi host fails

book

Article ID: 381426

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

When attempting to assign an ESXi license to an ESXi host through the host UI, the license check shows a positive check to show it is a valid license key. Upon assigning the license key to the ESXi host, the screen refreshes like it to apply the key, but upon looking at the license on the ESXi host it doesn't match the key that it was assigned.

Environment

ESXi 7.X

ESXi 8.X

Using a vSphere ESXi 7/8 Subscription key

Cause

ESXi host license key CPU core count is less than the CPU core count on the physical host.

Open an SSH session into the ESXi host and run the following command:

  • vim-cmd vimsvc/license --show | grep 'serial' -w
    • That command should display the license key the ESXi host is currently using.

Then run the following command to assign the license key to the ESXi host:

  • vim-cmd vimsvc/license --set=LICENSE KEY HERE
    •  The command should provide an output. Please see the following 2 lines “[diagnostic] and Results”
      •  serial: LICENSE KEY HERE
           vmodl key: esx.standard.cpuCoreMin
           name: vSphere 8 Standard (Subscription)
           total: 0
           used: 0
           unit:
           Properties:
             [diagnostic] = Insufficient number of per cpu core licenses. At least 32 are currently required, but only 16 provided.
             [ProductName] = VMware ESX Server
             [ProductVersion] = 8.0
             [license_not_set] = 1
             [expirationHours] = 23288
             [expirationMinutes] = 0
             [expirationDate] = 2027-07-04T00:00:00Z
             [system_time] = 2024-11-05T15:59:38.445047Z
             [feature] = vsmp:0 ("Unlimited virtual SMP”)
             [feature] = h264remote ("H.264 for Remote Console Connections”)
             [feature] = esxHost ("vCenter agent for VMware host”)
             [feature] = vimapi ("vSphere API”)
             [feature] = contentlib ("Content Library”)
             [feature] = vstorage ("Storage APIs”)
             [feature] = vmotion ("vSphere vMotion”)
             [feature] = xswitchvmotion ("X-Switch vMotion”)
             [feature] = das ("vSphere HA”)
             [feature] = dr ("vSphere Data Protection”)
             [feature] = endpoint ("vShield Endpoint”)
             [feature] = replication ("vSphere Replication”)
             [feature] = vshield ("vShield Zones”)
             [feature] = hotplug ("Hot-Pluggable virtual HW”)
             [feature] = svmotion ("vSphere Storage vMotion”)
             [feature] = smartcard ("Shared Smart Card Reader”)
             [feature] = ft:2 ("vSphere FT (up to 2 virtual CPUs)”)
             [feature] = vvolumes ("Virtual Volumes")
             [feature] = storageawarenessapi ("APIs for Storage Awareness")
             [feature] = spbm ("Storage-Policy Based Management")
             [feature] = vaai ("vSphere Storage APIs for Array Integration")
             [feature] = serialuri:2 ("Remote virtual Serial Port Concentrator")
           Result: FAILURE
    • As you can see the license key failed to be applied to the ESXi host because the CPU core count exceeds the license key is configured for.

Resolution

Make sure the license key meet the ESXi physical host CPU core count. Please reach out to Broadcom Global Support and create a non-technical case for assistance to determine if the correct license key was purchase and assigned to your account. 

https://knowledge.broadcom.com/external/article/145364/create-a-non-technical-case-for-support.html

 

Additional Information

Powered by Wolken Software