Apologies if this has been asked before, I looked through the archives and the only similar cases was solved by exciting sync-from first<—not in our case
When performing device check-sync we get result unsupported, we did sync-from before issuing check-sync. We are using NSO 4.0.3, XR NED and XRv in VIRL. Customer claims that with 4.0.1, check-sync was fine.
Compare-config doesn’t report anything i.e. Everything is actually in sync
From the user guide:
check-sync Check if the NSO copy of the device configuration is in sync with the actual device configuration. This operation is cheap as it only compares a signature of the configuration from the device rather than comparing the entire configuration. Depending on the device the signature is implemented as a transaction-id, time-stamp, hash-sum or not at all. The capability must be supported by the corresponding NED. The output might say unsupported, and then the only way to perform this would be to do a full device compare-config command.
How do we know exactly what’s causing this behaviour and if there is a way to troubleshoot?