I have noticed that NCM is collecting an extra configuration after correctly downloading a changed configuration. We run a nightly configuration job that includes most of our devices. If a change is found the configuration is saved. Then the next day, even though there is not another change, another copy of the configuration is downloaded. Then on the third day, when there is no change, the configuration is not saved. We wind up with one extra configuration saved each time there is a change.
Is anyone else seeing this behavior?
Example:
March 1 Downloaded and discarded Running config - no change
March 2 Downloaded and discarded Running config - no change
March 3 Downloaded and saved Running config - change found
March 4 Downloaded and saved Running config - no change (identical config to previous day)
March 5 Downloaded and discarded Running config - no change
March 6 Downloaded and discarded Running config - no change
March 7 Downloaded and discarded Running config - no change
March 8 Downloaded and saved Running config - change found
March 9 Downloaded and saved Running config - no change (identical config to previous day)
March 10 Downloaded and discarded Running config - no change
So two changes, but four configurations saved.
