get site-replicator remote-sites' the remote site shows 'data synced' and If the alarm is manually resolved, it retriggers again.VMware NSX
After a synchronization alarm validly triggers, if the leader of the ArAlarmService changes from an NSX Manager to another NSX Manager before the alarm resolves then the alarm stays uncleared
To resolve the alarm, restart the Async Replication service on the Local NSX Manager
> get cluster status verbose | find ArAlarmServiceIn the section ASYNC_REPLICATOR, check for the UUID of the Ar Alarm Service ArAlarmService 1 SMALL <node UUID> 1641194# systemctl stop async-replicator-service# systemctl start async-replicator-serviceIf the issue persists even after following the above steps, feel free to open a case with Broadcom Support Team