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

Preparing Cluster with Transport Node Profile Fails With This Operation Has a Different Version Than The Current System Version. (77192)

Last Updated: 5/12/2022Categories: InformationalTotal Views: 1815Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When applying a Transport Node Profile to a cluster of unprepared ESXi hosts, the following error occurs:

"The object TransportNodeCollection/<UUID> used in this operation has different version 1 than the current system version. Fetch the latest copy of the object and retry operation. (Error code: 604)"

See Photo Below:

Hosts will remain in a 'not configured' state after this error is triggered.

Cause

There are four variables that must all be present in order to encounter this issue:

1) The profile has vmkernel adapter and/or physical NIC migration mapping in the Transport Node Profile

2) The TN profile is applied on a VC cluster in which some or all hosts are not TN. If all hosts in the cluster are already transport nodes, this issue will not occur. A host becomes a transport node once it has been prepared for NSX T.

3) There must be a host that is not the last one to become a transport and its validation fails. Validation can fail due to a powered-on VM on the host or a vmkernel adapter that's not found.

4) There must be another host that will become a TN and its validation passes (EX: A host in maintenance mode). If both a host that passes validation and a host that does not pass validation are present in the same cluster, it will trigger a version mismatch host-to-error map that's tracked for the cluster.

Resolution

This is a known issue effecting NSX T.  This issue will be fixed in a future version of NSX T.

Workaround

There are two primary workarounds for this issue:

1.) You may detached the transport node profile from the vCenter Cluster. Place one ESXi host into vCenter maintenance mode.  This host will be installed with NSX T.  Then, re-attach the transport node profile to the cluster.  This will install a single ESXi host per iteration.

2.) You may remove the vmkernel adapter and/or physical NIC migration mapping in the Transport Node Profile for initial NSX T VIB install.  Then, once all hosts are installed, add the desired vmkernel adapter and/or physical NIC migration mapping into the Transport Node Profile which will trigger this configuration change across the cluster once all transport nodes are already installed.

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
•
RDSH でオーディオ デバイスの USB リダイレクトがサポートされていない (78284)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX Transformers

Related Versions:

Take Our Survey

Support Assistant