Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > Unable to compare configuration files most likely caused by broken regular expressions

Unable to compare configuration files most likely caused by broken regular expressions

Updated August 23, 2017

Overview

This article describes issues related to the following error:
Unable to compare configuration files, most likely caused by broken regular expressions. Inspect your logs for details.

 

Environment

  • NCM 7.6

 

Cause 

 

The configuration differences engine doesn’t accept some regular expression characters or tokens.

Resolution

  1. Click Settings > All Settings.
  2. Under Product Specific Settings, click NCM Settings. 
  3. Under Configs, click Comparison Criteria.
  4. Replace all ‘\s’ occurrences to ‘[ \t\r\n\v\f]’ in the RegEx column.
    Example: ‘\s*crypto.*certificate’ -> ‘[ \t\r\n\v\f]*crypto.*certificate’
  5. Replace all ‘error’ occurrences to ‘er[r]or’ in the RegEx column.
    Example: ‘errors*’ -> ‘er[r]ors*’
 

 

Last modified

Tags

Classifications

Public