Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Network Configuration Manager (NCM) > NCM compliance rule to find a string for a RegEx does not work

NCM compliance rule to find a string for a RegEx does not work

Table of contents

Updated March 22, 2017

Overview

When using a find string in a compliance/policy rule for a line in a configuration that is literally a regular expression, it fails to find a match.

Environment

All NCM versions

Detail

By default, when using a ‘Find String' in a compliance/policy rule, some characters are still interpreted as patterns in a regular expression; for device configuration lines that contain these characters, the policy will not match without escaping (‘\’) these characters.

From NCM 7.6 onwards, this behavior can be changed to process strings exactly as they appear without interpreting any characters. To change the default behavior:

  1. Open the Orion Platform Advanced Configuration Global Settings page.
  2. Scroll to the NCM.BusinessLayer category and select the ComplianceRegexEscapeEnabled checkbox.
  3. Save to apply the settings.

Please note, that if there have already been workarounds where one has escaped out the special characters/regular expression to work, enabling this feature will break these rules so they will need to be adjusted accordingly.

 

 

Last modified
16:31, 21 Mar 2017

Tags

Classifications

Public