NCM Configuration Change Report

We are running SSH on our switches and the Change Report keeps showing the "certificate self-signed" portion of the config as a change for every switch:

Example: thwack.com/.../original.aspx

I tried to have this portion of the configs ignored using the RegEx exemption feature to no avail and this false change make the reports hugh.

We're downloading both running and start-up configs every night and then generating a change report.

Any help on the correct syntax to ignore this portion would be greatly appreciated.

Thanks

Find more posts tagged with

certificate_self-signed

Accepted answers

All comments

chris.lapoint

This appears to be a bug and similar to case 53559. Can you please open a support ticket on this one to help us prioritize the fix?

rseitzinger

Case # 62140 Created: NCM Configuration Change Report

emorys

I am having this same problem. Will the case resolution be posted here?

AlbanyNYMike

Same here. My Change Reports are full of Crytpo Key changes that no one wants to see. I attempted to filter but to no avail/

The_Cisco_Kid

Concur with this sentiment to the furthest extent. Daily change reports that are 20+ pages long make the whole report pretty useless. Its way to easy to overlook a real change between all the crypto changes. Also the purpose of this software is to make our life easier and save us time, this is counter productive to that effort. I would consider this a priority up very close to the priority of making the user tracking portion function properly, both very important piece of the equation of network management.

chris.lapoint

This has been fixed in 5.1

andyty

I'm sorry but we're running 5.1.1 and the issue is still outstanding. I've tried even to filter it through Comparison Citeria but without any result.

chris.lapoint

Hmmm...I've verified we made two code changes in 5.1 to automatically ignore the crypto self-signed cert lines in the config.

Did 5.1 fix this issue for anyone on this thread?

In any case, we're very committed to getting this resolved. If you're still seeing this issue and are runninng 5.1 or later, please open a support ticket and reference this thread.