|
Description |
Assign Licenses to vSan, Wcp, vCenter, Esxi |
|
Progress Messages |
A problem has occurred on the server. Please retry or contact the service provider and provide the reference token. |
|
Error |
Message: A problem has occurred on the server. Please retry or contact the service provider and provide the reference token. Remediation Message: Reference Token: TEUOO3 Cause: Unable to update assets |
During an SDDC Workflow like adding a domain - the workflow stops with the above error:
VCF 5.x
This is caused by a licensing capacity error. The log /var/log/vmware/vcf/operationsmanager/operationsmanager.log can show the failing license key and the capacity it has and the requirements it needs.
A host license capacity in the operationsmanager log looks like this and explicitly declares what is the capacity issue with the license. This can be further verified within the vCenter.
Caused by: com.vmware.vcf.licensemanager.common.exception.LicenseManagerException: License Key 12345-XXXXX-XXXXX-XXXXX-5678 has available cores 4, but required core for hosts are 176.
Other licenses may not be explicit - "License assignment cannot be completed due to not enough license capacity" can show for vSAN and other license types.
Above this in the logging - it mentions the license key number.
This license key can be verified within vCenter to reveal more details about the license (Example of vSAN - TB capacity error below)
Verify any existing deployments that is using capacity on the license such as cores or tb.
Next calculate requirements of the domain to be added and see if the capacity is sufficient.
For ex - Domain1 is using 100TB and Domain2 is 500TB - but license only has capacity for 200TB.
If there is a clear capacity issue - engage our licensing/sales team (Create a Non Technical case for Support Portal / License / Contract related issues)
Alternatively to raise a case with GS support if the capacity does not add up.