Conflict: Running configs and startup configs do not match

Overview

The following results appear when viewing Overall Running vs. Startup Configs Conflicts:

Conflict: Running configs and startup configs do not match

Environment

NCM 7.2.2 and later

Cause 

This occurs when devices highlight certificate lines in config comparison.

Resolution

1. On the Web Console, go to Settings > NCM Settings > Comparison Critieria.
2. Select Ignoring hex data and click Edit.
3. Remove the ^ and click OK.
   
   [ \t\r\n\v\f]*[A-Fa-f0-9][A-Fa-f0-9][A-Fa-f0-9][A-Fa-f0-9][A-Fa-f0-9][A-Fa-f0-9][A-Fa-f0-9][A-Fa-f0-9]
    
4. Deselect Ignoring hex data.
5. Select Ignoring quit word line and click Edit.
6. Remove the ^ and click OK. 
   
   [ \t\r\n\v\f]*quit[ \t\r\n\v\f]*

If issue persists, add the following regex in Comparison Criteria:

^[ \t\r\n\v\f]*[A-Fa-f0-9]

Note: When using a job to download the configs, verify that it does not use the Only save configs that have changed option.

NCM only updates that chart when a new config is stored to the database. if you created a new comparison rule, it doesn't re-evaluate the configs that made up the 'Overall Running vs. Startup' chart. 

Please download startup config and running config for the node in question again after following the procedure above.

Also, if you want to Ignore the '!Last Configuration change' and '! NVRAM' Last write time line in cisco configs, you can check the below checkboxes and ENABLE them under Comparison Criteria page on your NCM Settings:

• Cisco '! Last Updated' line (Part 1)
• Cisco '! Last Updated' line (Part 2)