NSX Federation Full Sync completed but time reported as older time
search cancel

NSX Federation Full Sync completed but time reported as older time

book

Article ID: 422933

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

NSX Global Manager sync status reported local site sync is completed with an old sync time. Rebooting GM/LM does not update the sync time. 

Global Manager data-log reported the full sync time as 2024 and only delta syncs after the full sync.

2024-06-25T16:08:54.156Z INFO nsx-rpc:AsyncReplicatorService1:user-executor-1 log 150833 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] FullStateMessage Table=Span Key=/global-infra/span/global-infra-domains-#### message number= 11
2024-06-25T16:08:54.156Z INFO nsx-rpc:AsyncReplicatorService1:user-executor-1 log 150833 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] FullStateMessage Table=Span Key=/global-infra/span/global-infra-domains-#### message number= 12

...

2025-12-04T11:31:15.156Z INFO QueuePoller log 1307386 - [nsx@6876 comp="global-manager" level="INFO" subcomp="async-replicator"] Sent delta messages for flow FlowIdentifier{role='Policy', nameSpace='GM_2_LM'} to site ####. Messages

 

Environment

VMware NSX

Cause

Last full sync happened in 2024, which is right, and that is expected. Restarting nodes/services or network restoration will not trigger a full sync between GM and LM.  Only when the system detects there is a loss of data then full sync be triggered. 

Resolution

This is expected and can be ignored.