Any changes you would make on the device directly would change the Running Configuration, until you save to startup. If we need to detect on the different types of changes. config mode vs tftp new config or image, we would need to highlight that syslog or trap message to start the change detection process, so we get the download and comparison of configurations or just notify that the change has been made.
Loop1 Systems: SolarWinds Training and Professional Services
"When a config change is detected, NCM accesses the device, downloads the modified config file, and compares it to an existing config file to determine what changed."
My question is, is it possible for NCM to monitor both running and startup configuration files? It appears it is only possible to monitor one of two types for change detection.
simon.macpherson The real time change detection is not actually monitoring the config at all. Instead, it is looking for specific syslog messages which pertain directly to a user making a change on the device. When one of those syslog messages is found, it triggers the change tool which identifies and forwards the message. Your NCM environment can be configured to "Act" on these changes, which you could setup to initiate the automatic downloading of a new/current running config.
Aside from the real time change detection, after you have downloaded the current config, you can also configure NCM to check for differences between the running and start up configs. NCM has many tools, some of which seem to overlap slightly, but mostly one simply leads to the next.