Adding License Server in VCF Operations redirects back to License & Registration page
search cancel

Adding License Server in VCF Operations redirects back to License & Registration page

book

Article ID: 441251

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

  • Deployed a new License Server as part of the upgrade of SDDC manager as per documentation Upgrading to VMware Cloud Foundation 9.1
  • Adding newly deployed License Server in VCF operations fails with no error but redirects to the License & Registration page in the UI. 
  • License Server does not appear under Manage Licenses & Registration 
  • VCF License Server appliance shows status DISCONNECTED and VCF Ops Hosts: Not configured on the DCUI screen
  • Manual deployment of the License Server appliance using a valid JWT token results in an unconfigured state.

Environment

  • VCF Operations 9.1
  • SDDC Manager 9.1
  • VCF License Server Appliance 9.1

Cause

This issue occurs due to one of the following reasons:

  • Time Drift: A significant time difference exists between the VCF Operations VM and the License Server appliance, preventing successful token validation and registration.
  • DNS Resolution: VCF Operations does not return its FQDN correctly, or proper forward and reverse lookup entries are missing for the VCF Operations FQDN and short name.
  • Uppercase Hostnames/DNS: VCF 9.1 components fail to communicate if DNS records or hostnames contain uppercase characters
  • Incorrect Deployment Method: Deploying the OVA via standalone ESXi UI instead of vCenter Server UI prevents vApp/OVF property injection
  • Proxy Configuration: The License Server fails to connect if a proxy is configured but not required for internal traffic

Resolution

  1. Ensure the License Server OVA is deployed exclusively through the vCenter Server UI to ensure vApp options are correctly injected.
  2. Verify that the License Server hostname and DNS records (Forward/PTR) contain only lowercase characters.
  3. Verify that TCP port 443 is open bi-directionally between VCF Operations and the License Server.
  4. If a proxy is in use, ensure it is bypassed for internal communication or redeploy without proxy settings.
  5. Confirm NTP synchronization between VCF Operations, the License Server VM, and the ESXi host.
  6. Generate a fresh One-Time Token (OTK) in VCF Operations and update the VM's vApp options if registration continues to fail.
  7. If issue continues restart the VCF Operations cluster by navigating to https://<VCF-Operations-FQDN-or-IP> then taking the cluster offline and online.
  8. Redeploy license server.