Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM - Knowledgebase Articles > NCM Compliance Rule RegEx at the end of the line

NCM Compliance Rule RegEx at the end of the line

Table of contents
Created by Bill Corgey, last modified by MindTouch on Jun 23, 2016

Views: 1,097 Votes: 0 Revisions: 5

Updated June 6, 2016


This article provides  brief information on how Policy Rule validations can be written:

  • Find a string
  • RegEx

Using \r  to match the CRLF can produce inconsistent  results.



All NCM versions


Using the \r in NCM is not necessary and could produce inconsistent results due to the format the configuration is received from the device.  

One config may have the CRLF returned directly after the line and the next config from the same device may have white space between the end of the line and the CRLF, so no matter where the \r is placed, results may be varied and logically it is correct.

Example:  hostname bas-3750CRLF  vs.  hostname bas-3750 CRLF

Note:  the CRLF is not visible in NCM. A text editor that allows the view of all characters must be used. 


SInce NCM examines line by line the use of the \r is not needed unless one is specifically looking for the CRLF to be in a specific position.


It is not recommended to use  \r for Policy Rules in NCM.



Last modified