Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

"The supplied System Name  is not valid" error upgrading vCenter Server Appliance 6.7 (54682)

Last Updated: 1/21/2021Categories: TroubleshootingTotal Views: 66996Language:
Chinese (Simplified)JapaneseEnglish

25 like this article

Subscribe to get an email
newsletter with new updates

25 people found this helpful Please provide article feedback:

Symptoms

Upgrading vCenter Server Appliance 6.7 fails.

In the firstbootStatus.jason file, you the error:

"failedSteps": "visl-support-firstboot"

In the visl-support-firstboot.py_####_stderr.log file, you see the error:

The supplied System Name <vCenter Server Appliance FQDN> is not valid

GUI Error: Firstboot script execution Error. The supplied System Name vCenter_Server_FQDN is not valid.

Note: Firstboot logs are located at /var/log/firstboot directory.

For more information on:

Firstboot issues, see Firstboot Failed during Install/Deployment, Upgrade or Migration in vCenter Server and vCenter Server Appliance 6.7 (55746​).

Collecting a log bundle or review log files for vCenter Server Appliance install, upgrade, or migration issues, see Triaging a vCenter Server Appliance 6.0 installation, upgrade, or migration (6.0 U2m) failure (2106760).

Cause

This issue occurs when the DNS record for the vCenter Server Appliance 6.7 is incorrect or does not exist.

Resolution

To resolve this issue, verify that the FQDN has a valid (internal) domain name system (DNS) registration before upgrading vCenter Server Appliance 6.7.

For more information about DNS requirements see: DNS Requirements for the vCenter Server Appliance and Platform Services Controller Appliance.

Open the console to the vCenter Server Appliance and press F2 and log in with root credentials.

To enable shell, run this command.

shell.set --enabled true

Enter shell with this command:

shell

Ping the DNS servers to confirm communication with this command:

ping dns.dns_server.com

Use nslookup to make sure the vCenter Server Appliance and DNS Server can be resolved:
nslookup vCenter_Server_Appliance_FQDN
nslookup DNS_Server_FQDN [Note: Run this against all DNS Servers configured in VCSA]

Use the nslookup command to resolve the shortname.

Check the hosts file for invalid dns names

cat /etc/hosts

After underlying networking issue is resolved, deploy/upgrade the vCenter Server Appliance.

Related Information

Related Information: VMware vCenter failed firstboot

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.0.x

Take Our Survey

Support Assistant