Quantcast
Channel: THWACK: All Content - All Communities
Viewing all articles
Browse latest Browse all 13537

NCM Config Comparison.. Frustrating.... :(

$
0
0

Good afternoon NCM Community.... 

 

I am still finding config comparison in NCM is frustrating and illogical....  Every RegEx expression I try to create as an exclusion fails.  The end result is to call the SolarWinds support desk and wait for someone to help.  Each time we have been able to get the RegEx to finally work but I have never been given a reason why it is working or why the original RegEx expression failed.  

 

I have read through the admin guide, read through the NCM product BLOG, I have even purchased a couple of RegEx expression notpads to test with, and while the expressions work in the Notepads they never work in NCM and I am trying to figure out why...  With that I am reaching out with my most recent RegEx expression that doesn't work to see if someone can point me in the right direction. 

 

Below is a screen shot of the comparison that is incorrect....

clip_3.png

 

There are 2 usernames with this system.  I want to exclude a match on the first username (admin).  however everything I have tried with NCM fails.  I have tried...

1. ^username admin 

2. ^*username admin*

3. ^*username\sadmin*

4. username admin

5. ^(username admin).*?\n

Everyone of those expressions fail.  NCM still shows that there is a change in the username which is not true....  The statup config file (left side) show the username one way but the same username is displayed differntly when using the show running config command (right side).

 

The only RegEx command that works is  ^username.*ord  But this command will match on both username lines which is not the intended result.  I need this to match on just the first user name line.... 

 

Any thoughts or suggestions on where I am missing some logic would be greatly appreciated.

 

 


Viewing all articles
Browse latest Browse all 13537

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>