Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

How to add a host to a VMware Cloud Foundation workload domain when the build number does not match (66835)

Last Updated: 1/25/2019Categories: How toTotal Views: 2596Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

When adding an ESXi host to a VMware Cloud Foundation workload domain, a check is made against the ESXi host's build number. If the build number does not match the build number of the ESXi hosts already in the workload domain, the operation will not be permitted. This article provides instructions that allow for the expansion of a workload domain with hosts whose build number does not exactly match.

Impact / Risks

Ensure that the host being added is of a compatible version with the vCenter Server in the workload domain...i.e. only add an ESXi 6.5 host to a vCenter Server also running at version 6.5.

Ensure that the host being added is of a version that aligns with rest of the VMware Cloud Foundation installation. Reference Correlating VMware Cloud Foundation version with the versions of its constituent products (52520).

If a host is added that has a newer build number than the existing ESXi hosts, the appropriate LCM update must be applied to bring the rest of the workload domain up to the same build number.

Resolution

Log in to the SDDC Manager Controller VM as the root user.

Issue the following command to create and edit the /home/vrack/VMware/vRack/feature.properties file:

vi /home/vrack/VMware/vRack/feature.properties

Add the following to the file:

feature.sddcmanager.unmanagedhostupgrade=false

Save and close the file.

Issue the following commands to set the appropriate ownership and permissions on the /home/vrack/VMware/vRack/feature.properties file:

chown vrack:users /home/vrack/VMware/vRack/feature.properties
chmod 755 /home/vrack/VMware/vRack/feature.properties

Issue the following command to restart the vcfmanager service:

systemctl restart vcfmanager

Note: The value of feature.sddcmanager.unmanagedhostupgrade in the /home/vrack/VMware/vRack/feature.properties file can be set to true after the expansion is completed or the /home/vrack/VMware/vRack/feature.properties file can be removed (if desired). In either instance, the vcfmanager service will need to be restarted for the change to be active.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
无法使用 Horizon Client 启动应用程序或无法启动 AppBlast 门户，用户会收到以下错误：“此桌面的显示协议当前不可用。 错误: AGENT_ERR_PROTOCOL_FAILURE” (66784)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Foundation

Related Versions:

VMware Cloud Foundation 2.3.x

Take Our Survey

Support Assistant