Has anyone attempted to modify the NCM Config Change Report? I would like to suppress the "no configs to compare" message on the daily report we run "Show changes made over the past [2] days."
Currently running NCM v6.0 SP1
Thanks
"No configs to compare" are you downloading configs on a nightly basis?
I too an having a similar issue. I am running NCM v6.1 (tried v7 to find out SW integrated NCM with NPM, rolled back. Heads up SW, not everyone wants an integrated product like that.)
Anyway, my daily config change report is showing "no configs" most of the time. The download job is setup to only download a config when it sees a change. The config change job is setup to only check the last 1 day, or if there is no config from the last day to compare the running against the last one downloaded ( a checkbox in the job settings I believe). Before in version 5 the job used to say " no changes". How can I get it to say No Changes or if there is truely no changes for the timeperiod, omit it from the report? Any suggestions? Thanks
Hi whitejcdc,
the option to omit "no changes" from change report is already tracked as feature request #90604.
Regards,
Jiri
"No Changes" was not what I was pointing out, its was the "No Configs" that it is displaying instead.
The job clearly is setup to look at the currently and any last known saved config and check for differences. The job then should display "No changes" if the configs are not different, otherwise show the differences. But instead its displaying "No Configs" instead of "No Changes". That needs to be looked as to why its doing that.
"No Configs" should be used for when there truly is not a previous config to compare against, but there are. All of my nodes have at least one downloaded. So really the job should never currently say "No Configs" unless I add a new node or if I delete all of the current configs for one.
Please look into this.
Actually, "no configs" would show up unless you had 2 configs that meet the criteria. One being the last downloaded and the other being the last known. It does not treat one config as both.
I do have two configs that meet the criteria, since I am using the option for the last known if no config has been downloaded in the last 24 hrs. I did not say that it was using the one for both.
Anyway, I do have two configs for it to compare (the last downloaded and the current running) for each node, but it still gives me "No configs" even in this case. This is the issue I have been trying to convey. Not sure when it started doing this issue, but before it would give me "No changes" when it compared the two, now its giving "No configs" instead and shouldn't be.
BUMP
Do you have maintenance? If so, you can create a case and send me the screenshots showing the issue so I can take a look and give you a call to help you figure it out.
Hey Lorenzo. Here is a screenshot of my daily config check email and a SS of the Node list in NCM showing the Config Change Job information (removed screenshots). As you can see the job is setup to look at the last 1 days for changes, but also compare against the last downloaded if no configs found within the period specified. Which shouldn't that compare the running with the last downloaded on record?? The job still outputs "no config" for that though. Thanks for your help.
Jeff
the only problem with this is that there is no way for me to know that there is a current download as of today.
For example: In your gbserversk2.apac.local node, the last download was on 4/21/12 and the last download for lac1sk1.apacteleservices.com was 4/19
This would be considered the last downloaded config and there is no current config to compare against. So the no configs to compare would correct in both cases.
As a test: download a current config from a device and run the report. What are the results?
If you don't download daily, you may want to consider setting a baseline config, then using the Compare most recent Download to Baseline option.
