Hide this message
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.
Updated March 22, 2017
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.
All NCM versions
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:
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.