Understanding How Junos Space Automatically Resynchronizes Managed Devices
When configuration changes are made on a physical device that Junos Space manages, Junos Space automatically resychronizes with the device, so that the device inventory information in the Junos Space database matches the current configuration information on the device.
After Junos Space discovers and imports a device, Junos Space enables the auto-resync feature on the physical device by initiating a commit operation.
After auto-resynchronization is enabled, any configuration changes made on the physical device, including out-of-band CLI commits and change-request updates, automatically trigger resychronization on the device. The following diagram shows how a commit operation on the device triggers resynchronization.
When a commit operation is performed on a managed device, Junos Space schedules a re-sync job to run 20 seconds after the commit notification is received. However, by default, if Junos Space receives another commit notification from the device within 25 seconds of the previous commit notification, no additional re-sync jobs are scheduled, but Junos Space will resynchronize both commit operations in one job. This damping feature of automatic resynchronization provides a window of time during which multiple commit operations can be executed on the device, but only one or a few re-sync jobs are required to resynchronize the Junos Space database after multiple configuration changes are executed on the device.
When Junos Space receives the device commit notification, the device status is “Out of Sync”. When the re-sync job begins on the device, the Managed Status for the device displays “Synchronizing” and then “In Sync” after the re-sync job has completed, unless a pending device commit operation causes the device to display “Out of Sync” while it was synchronizing.
When a resync job is scheduled to run but another resync job on the same device is in progress, Junos Space delays the scheduled resync job. The time delay is determined by the damper interval that you can set from the application workspace. By default, the time delay is 20 seconds. The scheduled job is delayed as long as the other resync job to the same device is in progress. When the currently running job finishes the scheduled resync job starts.
You can disable the auto-resync feature in the Application workspace. When auto-resync is turned off, the server continues to receive notifications and will go into the out of sync state; however the auto-resync will not run on the device. To resynchronize a device when the auto-resync feature is disabled, you can use the resync feature to manually resync the device.
For information about setting the damper interval to change the resync time delay and information about disabling the auto-resync feature, see Modifying Application Settings.
