Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > NCM job is expected to download configs only if a change is detected, but it downloads configs even if no change is detected

NCM job is expected to download configs only if a change is detected, but it downloads configs even if no change is detected

Table of contents

Updated April 27, 2018

Overview

When the job runs and a change is found, NCM downloads and saves the configuration file. The next time the job runs, even though there is not another change, a new configuration is downloaded and saved. During subsequent runs of the job, when there is no change, the configuration is not saved. NCM downloads one extra configuration each time there is a change.

 

Environment

  • NCM 7.0 through NCM 7.7

Detail

NCM behavior is as follows:

  1. Once a change is detected, NCM will download a new config, since it differs than the one before.
  2. The next time the job runs, NCM downloads the config again and saves it to the database, even though a change has not been detected. (A difference is not noted in the last XX changes.) 
  3. The following downloads will honor the expected behavior of the job until a real difference is detected.

 

The reason for the one additional config being downloaded is so the Charts on NCM do not always show conflicts, where there really are none on the devices. 

 

This is expected behavior and is by design. This behavior was implemented because the charts were showing conflicts because the user was only saving configs for devices that were different.

 

 

 

 

 

Last modified

Tags

Classifications

Public