Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Configuration Manager (NCM) > Running and Startup config comparisons show a difference where there are none

Running and Startup config comparisons show a difference where there are none

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 90 Votes: 1 Revisions: 12

Overview

Startup and running configuration comparisons show there is a difference, but there should not be any. The process is not ignoring hexadecimal data even after enabling 'Ignoring hex data' criteria in NCM Settings > Comparison Criteria. 

Environment

All NCM versions

Cause

The startup config for Cisco devices do not display the hex data but the running config will

Standard hex keys are in blocks of 8 per line:

^[ \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]

Config file comparisons may not ignore the hex data, if you use shorter blocks, like the sample given below:

^[ \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]

the word quit at the end of the Hex data is not at the beginning of the line in the config. It can be random on the line but generally close.

Resolution

If your hex keys are not in blocks of 8, you need to modify the 'Ignore quit word line' criteria: 

from: ^[ \t\r\n\v\f]*quit[ \t\r\n\v\f]*

to: [ \t\r\n\v\f]*quit[ \t\r\n\v\f]*

1. Log into the Orion Webconsole 

2. Click Settings > NCM Settings > Comparison Criteria 

3. Select 'Ignoring quit word line' and click 'Edit'.

4. Edit RegEx pattern screen appears as shown in the sample screen below: 
kb 5319.jpg

5. Edit the RegEx pattern as highlighted in the above screen and click 'OK'. 

6. Verify by comparing two configs being displayed as different previously.

7. If the above comparison is corrected, Download a new set of configs to NCM regardless if a change is detected or not.  This will update the charts on the web page.  They will not be automatically reconciled by simply correcting the Comparison Criteria



 
 

Last modified
21:29, 22 Jun 2016

Tags

Classifications

Public