NSX cluster remains in a degraded state after implementing a solution that includes start search resync all

Products

• VMware NSX

Issue/Introduction

• An issue has been encountered in NSX such that the manager node cluster is in a degraded state.
• Drilling down into each node in the cluster shows that the search service is degraded on each of them.
• There is a documented resolution for the issue and part of that resolution includes running the command, start search resync all, on each node in the manager cluster.
• After running start search resync all on one node, the original issue remains but one node in the manager cluster does not show as degraded.
• Logging into the UI for the one node that does not show as degraded shows that the original issue appears to be resolved on that node.

Environment

• VMware NSX-T Data Center
• VMware NSX

Cause

Until start search resync all is run on a manager node, it will continue to reflect the original issue. 

Resolution

Run start search resync all on all affected manager nodes in the cluster. 

Additional Information

• "Failed to get "INVENTORY OVERVIEW" report" error displayed when trying to view inventory on local manger in Federated NSX Environment
• NSX Manager is reporting search sync issues
• Inconsistencies within NSX UI 
• NSX System Overview Not Loading 
• NSX-T UI Displays Edge Associated with Logical Router After Edge Removal 
• Resolving NSX-NCP Pod Stuck in CrashLoopBackOff due to NSX Search Service Error 
• NSX Manager upgrade fails with error “alb_policy_deactivate_check failed” due to stale ALB objects in NSX-T database
• The certificates displayed on the screen are different in each NSX Manager UI. 
• VMware NSX "Operations DB Disk Usage Very High" Alarm Triggered due to large search index 
• Cannot fetch inventory details: Search service is currently unavailable
• DFW rule Services field has the error Not able to fetch entity details. This entity may belong to other location.
• NSX Manager reports INDEXING_FAILURES for a long time
• Only CBM (Cluster Boot Manager) certificates are visible in the NSX Manager UI after upgrade to 4.2.X
• NSX UI reporting rules are deactivated and DFW is turned off
• [HCX] Network Extension task fails with the error : "Failed to resolve vc backing network moref for network <logical-switch path>"
• NSX Manager is reporting search sync issues after upgrade to 4.2.3
• NSX-T Search stops functioning after upgrading from 3.2.2 to 4.2.1.1
• Following an upgrade to VMware NSX 4.1.x, index is out of sync
• /nonconfig  high on NSX managers due to  IDS/IPS signature search index
• NSX-T alarm about disk usage for the Manager node disk partition /nonconfig has reached 10%
• "Control Channel To Transport Node Down Long" or "Management Channel to Transport Node Down Long" alarms for removed Transport Nodes
• Logical Switches in failed state upon upgrade to VMware NSX 4.1.x
• vROps alarm: "Logical Switch State has failed" for NSX segments
• NSX-T Manager alert '/' disk partition has reached 80% which is at or above the high threshold value of 80%
• Unable to add ESXI host as a host transport node.
• NSX Upgrade State Shows Previous Upgrade Still in Progress, During Host Upgrade Phase.