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

Replication errors during NSX upgrade in Cross vCenter environment (56512)

Last Updated: 7/11/2018Categories: InformationalTotal Views: 3609Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After upgrading the Primary NSX Manager, and before upgrading the Secondary NSX Manager(s):

You see the following sync issues in vSphere Web Client under Networking & Security / Installation and Upgrade:

Requested URL /api/2.0/services/application/dpi/discovered-appguid could not be found. This may be caused by mismatch in NSX manager versions or missing object ID.

To further identify this condition, the following matches can be found in the NSX Manager logs:

In localhost_acess_log_date.txt:

127.0.0.1 - - [07/Jun/2018:09:58:27 +0200] "POST /api/2.0/services/application/dpi/discovered-appguid HTTP/1.1" 404 1018 16

In replicator.log:

​2018-06-07 09:58:30.578 CEST ERROR pool-4-thread-1 ReplicatorUtils:84 - - [nsxv@6876 comp="nsx-manager" errorCode="MP160307" subcomp="manager"] Error in calling POST for object <?xml version="1.0" encoding="UTF-8"?>
<appguid><appGuidId>1697</appGuidId><appGuidName>GITHUB</appGuidName></appguid> on VSM 10.140.0.220
org.springframework.web.client.HttpClientErrorException: 404 Not Found
at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:85) ~[spring-web-4.3.14.RELEASE.jar:4.3.14.RELEASE]
at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:708) ~[spring-web-4.3.14.RELEASE.jar:4.3.14.RELEASE]
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:661) ~[spring-web-4.3.14.RELEASE.jar:4.3.14.RELEASE]
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:621) ~[spring-web-4.3.14.RELEASE.jar:4.3.14.RELEASE]
at org.springframework.web.client.RestTemplate.postForObject(RestTemplate.java:388) ~[spring-web-4.3.14.RELEASE.jar:4.3.14.RELEASE]
at com.vmware.vshield.replicator.utils.VsmRestClient.post(VsmRestClient.java:148) ~[classes/:?]
at com.vmware.vshield.replicator.utils.ReplicatorUtils.executeRestApi(ReplicatorUtils.java:53) [classes/:?]
at com.vmware.vshield.replicator.providers.DefaultReplicationProvider.executeRestApi(DefaultReplicationProvider.java:302) [classes/:?]
at com.vmware.vshield.replicator.providers.DefaultReplicationProvider.handleCreate(DefaultReplicationProvider.java:74) [classes/:?]
at com.vmware.vshield.replicator.providers.DefaultReplicationProvider.handleCreateInternal(DefaultReplicationProvider.java:348) [classes/:?]
at com.vmware.vshield.replicator.providers.DefaultReplicationProvider.handleFullSync(DefaultReplicationProvider.java:187) [classes/:?]
at com.vmware.vshield.replicator.queuemgmt.SecondaryReplicationQueue$SecondaryEventDispatcher.run(SecondaryReplicationQueue.java:156) [classes/:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_161]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_161]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_161]

Note: This log excerpt is an example. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article is to highlight the documentation in regards to the sync issues displayed.

Cause

The sync issues occur because the REST API call used for the specific object exists in the upgraded Primary NSX Manager but not in the non-upgraded Secondary NSX Manager(s).

Impact / Risks

This does not cause any impact.

Resolution

As documented in NSX 6.4 Upgrade Guide:

If you are logged in to the vSphere Web Client during the upgrade, you will see synchronization issue warnings on the Networking and Security > Installation and Upgrade > Management page. This is because you have NSX Manager appliances with different versions of NSX. You must upgrade the secondary NSX Manager appliances before proceeding with any other part of the upgrade.

Proceed with the upgrade of the Secondary NSX Manager(s). The sync issues will be automaticall cleared after all Secondary NSX Managers are upgraded.

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

Take Our Survey

Support Assistant