Hi,
Could you please attach replication logs.
C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tomcat\Logs
The ReplicationLocal-0.log contains Replication events initiated from the Local SEPM and the ReplicationRemote-0. log contains events received from the Replication partner
Also could you please try these steps
Add to the following to the conf.prop on all the SEPMs
scm.replication.keepalive=1
Reboot, Test, If that fails
Change scm.replication.keepalive=10 in the conf.properties file
Followings are the fixes in SEP 12.1 RU3.
Do you see any of this error message?
1) Replication fails with a Java error: "GC overhead limit exceeded"
Fix ID: 2920217/3055586
Symptom: After upgrading to Symantec Endpoint Protection Manager 12.1.2, replication fails with the exception message "OutOfMemoryError: GC overhead limit exceeded."
Solution: Modified the replication function to avoid a scenario where object references could be recursively checked.
2) Replication failed
Fix ID: 2810324
Symptom: The replication fails continuously. The data.zip file is generated and transferred, but replication is not successful.
Solution: Fixed this issue by cloning the default management server list in the Enforcer's policy.
SEP 12.1 RU2 MP1 has also one fix related to replication, here it is.
AgentSweepingTask fails to clean the SEM_CONTENT table, leading to replication issues
Fix ID: 2956524
Symptom: Symantec Endpoint Protection Manager replication fails, and the AgentSweepingTask logs contain reported deadlocks. Multiple applications or processes attempting to access the database at the same time appear to trigger these deadlocks.
Solution: Added additional retries and failsafes to ensure that the AgentSweepingTask is given a higher priority in the event of multiple failures and failed retries to ensure it can run.
I hope you have performed system reboot after the SEPM upgrade.