SDDC Manager UI login re-routes FQDN to short name
search cancel

SDDC Manager UI login re-routes FQDN to short name

book

Article ID: 445808

calendar_today

Updated On:

Products

VMware SDDC Manager / VCF Installer

Issue/Introduction

  • Logging into the SDDC Manager via a web browser automatically reroutes the session to a short name (e.g., https://sddc-manager/ui ) instead of the expected Fully Qualified Domain Name (FQDN).

  • This occurs even when you have configured the FQDN in your environment. (eg: sddc-manager.domain.com)

  • Validating the logs /var/log/vmware/vcf/domainmanager/domainmanager.log points all the API calls to the short name instead of the FQDN.

Environment

VCF 9.1

SDDC Manager

Cause

This behavior occurs when the internal system name is set to a short name instead of the FQDN during the initial VCF installation or configuration.
The SDDC Manager picks up this 'System Name' for login redirections and internal log URL generation.

Resolution

To resolve this issue, you must manually update the system hostname to the FQDN using the command-line interface on the SDDC Manager appliance.

1. Log in to the SDDC Manager appliance as the 'vcf' user via SSH.

2. Switch to the root user using su -
       
3. Verify the current system status and hostname by running:

      nmctl status

Expected output as below:

root@sddc-manager [ ~ ]# nmctl status
              System Name: sddc-manager
              Kernel: Linux (6.1.164-2.ph5)
            Systemd Version: v253.19-17.ph5
  

4. Confirm if the 'System Name' field displays the short name (e.g., ####).

5. Set the system name to the correct FQDN by executing the following command:
  
nmctl set-hostname <FQDN_of_SDDC_Manager>
 
   *(Example: nmctl set-hostname sddc-manager.domain.com)*

6. Verify the change by running `nmctl status' again to ensure the System Name now reflects the FQDN.

7. Clear your browser cache and attempt to log in to the SDDC Manager URL. The session should now correctly route to the FQDN.

Additional Information

  • Contact Broadcom Support article if the manual update does not resolve the issue.