In NSX federation setup, local site status is SUSPENDED.

Products

• VMware NSX

Issue/Introduction

• Remote sites may report state as SUSPENDED 

• Bidirectional connectivity between the Global Manager (GM) and Local Manager (LM) has been verified and is confirmed to be good over ports 443 and 1236.
• The following log entries from the Global Manager indicate that the remote site (ID: #######-################) is rejecting full state updates from the GM due to a persistence error:

2025-08-12T12:36:14.495Z  INFO nsx-rpc:APH_provider:user-executor-3 Replicator 77767 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] receiveFullStateStatusUpdate: Received Full State Update. requestId = 21fdd14e-3d2a-431c-bdd6-deebb10333ba, site = bc2db220-################, flow = FlowIdentifier{role='Policy', nameSpace='LM_2_GM_NOTIFICATION'}, status = FullStateStatus [status=REJECTED, fromReceiver=false, failureReason=PERSISTENCE_ERROR, appDataProcessingTime=null]
2025-08-12T12:36:14.495Z  WARN nsx-rpc:APH_provider:user-executor-3 ReplicationFlow 77767 - [nsx@6876 comp="global-manager" level="WARNING" subcomp="async-replicator"] Full state sync request rejected by site #######-################ for flow FlowIdentifier{role='Policy', nameSpace='LM_2_GM_NOTIFICATION'} with reason Persistence error encountered
2025-08-12T12:36:14.495Z  INFO nsx-rpc:APH_provider:user-executor-3 ReplicationFlow 77767 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] Flow FlowIdentifier{role='Policy', nameSpace='LM_2_GM_NOTIFICATION'} local site=################, remote site=################ local state moves from RECOVERY to ERROR, reason = Full state sync request was rejected by remote site
2025-08-12T12:36:14.496Z  INFO nsx-rpc:APH_provider:user-executor-3 StatusPersistenceService 77767 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] StatuePersistenceService::UpdateFlowStatus for entryKey flow_id: "RECEIVER.Policy.LM_2_GM_NOTIFICATION"
site_id: "################"
 and value timestamp: 1755002174495
site_id: "################"
flow_id: "RECEIVER.Policy.LM_2_GM_NOTIFICATION"
local_state: "ERROR"
remote_state: "SUSPENDED"

Environment

VMware NSX 4.x

Resolution

Workaround

Restart the async-replicator service on all LM nodes:

#systemctl stop async-replicator-service
#systemctl start async-replicator-service

If the above does not work/further assistance is needed, open an SR with Broadcom Support  and provide relevant data below:

1. NSX Global Manager log bundle
2. NSX Local Manager log bundle