After upgrading to NSX 4.2.4 NSX UI shows error "Search index out of sync" (Error MP60516) for ServiceConfig

Products

• VMware NSX

Issue/Introduction

• GUI and API search capabilities are impaired or completely unavailable, preventing the retrieval of configuration data.

• The issue begins immediately after upgrading NSX to version 4.2.4.x

• The following error messages are continuously logged in /var/log/search/search-manager.log on the NSX Manager:
  
  

963055:YYYY-MM-DDTHH:MM:SS.MS+HH:MM ERROR http-nio-###.#.#.#-7440-exec-1 SearchSyncManagerImpl 77623 - [nsx@6876 comp="nsx-manager" errorCode="MP60516" level="ERROR" reqId="########-####-####-####-############" subcomp="manager" username="[USER@DOMAIN]"] [QueryExecution: ConsistencyCheck] Search index is out of sync for ServiceConfig.
963126:YYYY-MM-DDTHH:MM:SS.MS+HH:MM ERROR http-nio-###.#.#.#-7440-exec-26 SearchSyncManagerImpl 77623 - [nsx@6876 comp="nsx-manager" errorCode="MP60516" level="ERROR" reqId="########-####-####-####-############" subcomp="manager" username="[USER@DOMAIN]"] [QueryExecution: ConsistencyCheck] Search index is out of sync for ServiceConfig.

 

Environment

• VMware NSX 4.2.4.x

Cause

NSX 4.2.4 introduces a stricter data consistency model for the search service.

This issue occurs if there is a stale ServiceConfig entry in the Corfu tables that retains an applied-to reference pointing to a Logical-Router that was previously deleted. Because of the new strict consistency model in 4.2.4, these legacy stale entries are now flagged as invalid object paths during index consistency checks. This halts the search resync process and triggers the MP60516 error.

Note: Moving forward, this stricter consistency model prevents user from deleting a Logical-Router if it is still actively being referenced by other components.

Resolution

Broadcom prepared a python script to delete the references to stale logical-router entries and thus resolve the problem. 

If you are facing this error, please open a support request with Global Support (GS) and reference this Knowledge Base article.

Please check below KB for opening a support request with Global Support (GS):

Creating and managing Broadcom cases

Additional Information

Broadcom is actively working to integrate a pre-check into future VCF versions. This pre-check will proactively flag these stale referenced entries before an upgrade is allowed to proceed, preventing the issue from surfacing post-upgrade.