Error: Undetected license server due to DNS resolution in VCF Operations 9.1
search cancel

Error: Undetected license server due to DNS resolution in VCF Operations 9.1

book

Article ID: 445428

calendar_today

Updated On:

Products

VCF Operations

Issue/Introduction

In VMware Cloud Foundation (VCF) Operations 9.1, the license server deployment completes on the vCenter, but the newly deployed license server is not detected in the VCF Operations UI.

Symptoms:

  • The license server virtual machine (VM) console may show as Not configured and Disconnected.

  • In specific scenarios where the license server is detected in VCF Operations, stale licenses may be left behind with the error message: This license is no longer associated with this VCF Operations instance, but could not be fully removed. To complete the removal, assign a new license to the vCenter instances which have this license assigned to them.

  • Assigning license to a selected vCenter server may fail with the error: vCenter is unable to resolve the license server host name. Ensure an A record and PTR are added to the DNS servers used by the vCenter.

Environment

  • VMware Cloud Foundation (VCF) 9.1
  • VCF Operations 9.1
  • vCenter 9.1

Cause

Proper communication with the license server depends on functional forward (A) and reverse (PTR) DNS resolution. Mismatched or missing DNS records for license server, as well as failure of the VCF Operations node to resolve its own hostname or IP address, result in registration failure.

Resolution

To allow the VCF Operations to successfully detect the license server and complete the license registration process, follow these steps:

  1. Verify name resolution: Use nslookup to validate both forward and reverse lookups. Ensure these commands successfully return the expected records for both the License Server and VCF operations:

    1. nslookup <license_server_hostname>

    2. nslookup <license_server_IP> 

    3. nslookup <VCF_ops_hostname>

    4. nslookup <VCF_ops_IP> 

  2. Identify Incorrect/ missing DNS Entries: If nslookup fails to return the expected results, identify the incorrect/missing DNS entries for the VCF Operations node or the License Server.

  3. Update DNS Server Records: Update the DNS server records to ensure correct forward (A) and reverse (PTR) resolution. Ensure all DNS naming conventions use lowercase characters to prevent case-mismatch issues.

  4. Retry Detection: Retry the license server detection and configuration workflow from the VCF Operations UI.

Additional Information

In case the issue still persists, redeploy the License Server on the vCenter by following Newly deployed License Server not showing up under the License Server tab in VCF Operations

Powered by Wolken Software