Service Check-Sync behavior: Steps:1. Make headend router unreachable2. Provision service with async commit queue  provision in failed state as expected3. run device check-sync for headend router on nso   result is error as expected4. run service check-sync  the result is "in-sync true"  Is this expected?In what condition will service check-sync returns "in-sync false"?admin@ncs> request devices device xrv9k-PE7 check-sync result errorinfo Failed to connect to device xrv9k-PE7: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new stateadmin@ncs> *** ALARM connection-failure: Failed to connect to device xrv9k-PE7: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new stateadmin@ncs> request sr-te policies policy SRv6-702-igp-relative-segments check-syncin-sync true
Hi Crystal,The difference between the two is that one is a "device check-sync" and the other is a "service check-sync". The "service check-sync" only compares to local CDB and returned true since everything was in sync. As for "device check-sync" this is mainly dependent on how the NED handles this case and for the most part it checks the remote device but in this case it failed because the remote device was not reachable.Thanks Reginald. For "service check-sync", what is local CDB compare with? For "service check-sync", the comparison is done between the service output and underlying service/devices on NSO.Had webex and explained the difference between service and device check-sync to the submitter