Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Policy -> Rule Regex -> behavior not working correctly (seemingly)

I use http://gskinner.com/RegExr/ as a tool to test my regex.

I'm using this expression as part of a "block" check for interface description:

description [a-zA-Z]*(/s)* HSRP (PRI|SEC) V=(([2]([0-4][0-9]|[5][0-5])|[0-1]?[0-9]?[0-9])[.]){3}(([2]([0-4][0-9]|[5][0-5])|[0-1]?[0-9]?[0-9]))

the above would fail if: the descr for F0 had R-XRT-O.... or the IP was only 2 octets, etc..

it shows as matching in the tool, but I'm getting policy errors "not matching" in NCM policy report.

does NCM not support full regex?
Is there plans to support that in future?

thanks

Find more posts tagged with

Accepted answers

njoylif

can't use "/s" in NCM which equates to space(s) like tab, spaces, etc..

just hope there are no double spacebar taps in description.

All comments

njoylif

can't use "/s" in NCM which equates to space(s) like tab, spaces, etc..

just hope there are no double spacebar taps in description.

fcaron

Hi Larry,

We don't have a plan to make significant change in our regex "interpretor" but we have requests for a better documentation of the syntax we support and not (63049).

I'm adding your vote on this item, because I think it would help you.

njoylif

yep, great...thx