Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Network Configuration Manager (NCM) > Apply a compliance rule with config block using RegEx to selected interface types

Apply a compliance rule with config block using RegEx to selected interface types

Table of contents
Created by Bill Corgey, last modified by Bill Corgey on Aug 23, 2017

Views: 1,905 Votes: 0 Revisions: 6


There are times when a compliance rule needs to be confined to a subset of interfaces already in group and needs to be dealt with differently than a standard Config Block.


NCM 7.4


Create the policy rule in the web

  1. In the advanced section, set the criteria you are searching for.
  2. in the search Config File/Block, select the Config Block.
  3. Lay out the criteria of the section(s) of the config where NCM needs to look at.

For this example, I want to search several different interfaces, but not all

I want to look at any block that starts with interface serial, interface test1, interface test2 or interface multilink

  1. The RegEx for the config block start would be:
    interface serial*.*|interface test1*.*|interface test2*.*|interface multilink*.*
  2. The RegEx for the config block end would be:



Note:  RegEx patterns used in the Config block is a single line expression.  Multi-line expressions used will not be fully recognized.  

Example of a Non-supported Regex:

In this case I would like to check all Gigabit ethernet ports on VLAN 104 that have flowcontrol receive on.


^interface GigabitEthernet.*\n(.*\n)*.*switchport access vlan 104.*\n(.*\n)*.*flowcontrol receive on



Also note it is possible to test with desired results from the rule page, but not get the results in the actual run of the rule.  (this is with the development team as a item of concern) 


Last modified