Actually its not one of those days. It happens. I have reported issues to engineering before on sync issues. You wont get any assistance from the lower guys and you will need ERT to assist as they have the ability to look at back end sync issues on central.
There was either 1 of 2 problems that existed. Most likely your device was not syncing before you made the change. There was nothing locally with your device that was wrong if it was connected to central and you were getting stats. These are just things that we have to accept with having our services in the cloud by any vendor.
From my understanding there are a couple different services or components to central with AP's and SD-Branch. You have your config sync, monitoring and stats, and then orchestration and routing topology. The switches would not be part of the orchestration and topology as they do not build a vpn tunnel and exchange routes with overlay. Since there are different modules, there are also different groups of public IP's that go with those modules.
You could have had a routing issue going to some of those ip's, the other issue is there could have been a back end service that someone else already reported to ERT and was in the process of fixing.
When I had a config sync issue on some 9012's 1.5 years ago. It took 1-2 weeks to get a resource on the phone form ERT and then get it to engineering. Once it was handed off to them it was fixed pretty quickly.
Next time if there are any sync issues. Just make sure you have basic internet from your gear and its connecting to central and you are getting updated stats.
-------------------------------------------
Original Message:
Sent: Apr 22, 2026 02:52 PM
From: ChristianD
Subject: Switch status hung on "Not in sync - Pushing config"
Well...I was on the phone with someone from TAC for an ticket on another issue, and I wanted to show him the problem with the sync status. Guess what...my switch was now synced ! ... after a few hours.
One of those days...