Config Change Report - Filtered (Thinking Green)

Is there a method to filter on and report only those devices where the config has changed?

We need to retain paper reports for 1 year + 90 days all infrastructure devices that have been modified. NCM provides this information well. However the file drawers are filled with daily report where "no changes" is reported. So a positive answer goes a long way into a greener environment.

Find more posts tagged with

Accepted answers

All comments

nrms

I take it setting the "Only save Configs that have changed" option in the "Download Config" tab of the job settings still dumps a message to say that the config hasn't changed? (I don't use that option, hence I'm not sure what its behaviour does.)

rcahill

That's a correct assumption. The device is reported as 'no changes'.

I'd like the option to eliminate the devices that have not changed. I could be wrong but it is a "Config Change Report".

If this can be done, then the report can go directly to QA or Operations for them to file the daily report. Now the network team is required to sit with auditors and describe the process. Besides all of the printed docs with [Node Name] 'No Changes' that go in the paper recycle bins.

nrms

Not sure there is a way then. The Report Writer is a little light on NCM reporting capabilities, and there's no other obviously relevant options in the NCM job config.

Looks like it's either a feature request, or you find a code-monkey to write something that can take a job log from NCM (use the Save Results To File option in the Notifications tab if you're not already doing so) and output just the relevant info!

ds2acrvet

In NCM 7.2.1 this is possible;

Send config change notifications Send a notification if the downloaded config file is different than the:
Last downloaded config file of the selected type
Baseline config file
Startup config file