christopher.a.thornton

Oh I see, sorry I though it was for the same rule that you had in the original image. From the more recent one I think it should be working as intended. You can try to change your rule to this for regular expression and see if that will help get it to show up correctly. ^mab[\r\n]*$

Thanks Craig. I see an error in my previous response as it has a must contain instead of must not contain (I removed quite a few lines from my actual rule and missed that part). But your link should give him the correct guidance.

Hey noobes​, after you run the compliance report you will see your violations listed out when you click on the report. If you open one of the violations you will get a window like the below. You can run the remediation script on just the node you are looking at or on all nodes in violation as you see below. Let me know if…

Thanks wluther​, I was going to do up something like that but I didn't have enough time this morning.

Hey noobes​, I think I see the issue in the first try that you were doing. You were missing a \ in front of the s here so it was not actually matching anything because it was looking for a line that started with "interfaces" and not a line that started with "interface" and had a space after it. Your new config block match…

What I did for my ACL's is broke them down into separate lines where each approved permit or deny gets it's own check. Once I have all those in there I make another check at the end for a must not contain of something like the below. ^access\-list 1 permit (?!(1\.1\.1\.1|2\.2\.2\.0 255\.255\.255\.0)).*[\r\n]$ That will…

If you click on the test button what output does it have in there?

No problem awcrane​, glad to help out.

I made some tweaks to Malik's. The below will save the running configs to a folder structure like the below. Let me know if this will work for you. @TFTP (Defined when you run the template) @DIRECTORY (Defined when you run the template) @ContextNode.NodeCaption (The name of the Node in SolarWinds) Files are stored under…

Not a problem at all. If you run into any issues with Regex feel free to ask on the forums, a lot of people on here will be able to assist. I had to learn it a few months ago myself to better leverage NCM. Check out the post below as it may help you a bit with what you are trying to do. Everything You Ever Wanted to Know…

Ok I see what is happening I think. The way you have you rule set up is that it checks each one individually. If you want to be alerted for all at once if they are present or not present try to remove all of the parentheses "(" or ")" from the rule. You could leave the one before the start and the one at the very end as…

No problem Jeff. If those options don't work out for you jump back in this thread and provide an update so that we can engage again and see what is going on.

It is located in Settings -> NCM Settings -> Configs and then under the Config Transfer area.

I think that I may have found a way to do this, but it is not elegant. Can you start a new thread for this part so that others can comment as well. They may not come into this one as it has been marked resolved. Once it is open I will put my proposed solution in there. Thanks.

You can separate the ACL lines into different lines on the rule, that way it will show you exactly which lines are missing in your ACL so you know which ones to add in.

It should look like the below when you are creating the rule.

No need for parenthesis in the rule at all aside from in the regex part. It will apply both rules at the same time and flag them as failures accordingly. If you are still having issues get a screen grab of the rule and error and post it here so I can take a look.

Ah ok I see what it's doing now. Take out the @TFTP and @filename in the CLI portion and that will remove the lines that it is adding in while running. Give that a shot and see if that works for you.

Actually the method that jkrenzien​ posted is a better way of doing it.

Hi Mike, I would try to add maybe a second slash to the sequence and see if that works out, usually when you have a // the first one is escaped and the second one is a literal /. If that doesn't work you may have to play around with the combination at the @String_CLI variable and see if you can get a combination that will…

You can have it saved to a file as well, though I have never done that. I usually view the results via the job history or have NCM send me an email with the results.

Ok I get what you are saying now. I am not sure of an easy way to select just the nodes that have a configuration mismatch to perform a write on them. If it were me I would just make a job to write the config and push it out to all of the devices so that way I know all of them were good. Not sure if that is something you…

Ok great glad you were able to get it to work. With RegEx there are some weird quirks that you have to figure out sometimes and that was going to be my next guess was to look at the match statement. I think what may have been happening is that when you pasted the line in there you may not have had any additional lines…

Found some of it myself, still a work in progress but at least I have the SWQL table sections. They are listed here. SolarWinds Information Service v3.0 Schema Documentation Index

No problem at all, glad it worked for you.

Ina, I thought for sure that would work. It didn't dawn on me that it was part of the login prompt and could not be bypassed by the script that I made. I am not experienced with Config Change Templates which may be able to help with this, but maybe someone else would no better. Sorry it didn't work for you.

Ok I see what you are trying to do and that is fairly straightforward actually. For the remediate script you do not need to include the conf t or interfance in there or anything else. I would just leave it as the ${ConfigBlockStartLine}. The rule I think that would work best is like the below. The rule above will match all…

Hey Muhammed, I am actually not sure on that answer, we currently have NCM 7.4.1 right now. I believe the options should be fairly close though as I think they just added some more features in the new versions. I do not believe they changed the options around too much. Hopefully it will be mostly similar for you so that…

Try to change the deny line to this and see if that works. This is what I have for my deny line and it works. ^\s?deny\s{1,5}any log[\r\n]*$ For the Config Block End I use this on mine. It will find either ! or the deny any at the end. (!|^\s?deny\s{1,5}any log[\r\n]*$)

One thing that you could try is to match each line individually in the rule instead of matching it all at once. This would allow you to see what of the lines are causing the errors and then you can correct it. I would try having the rule broken into 5 different lines like this. ^\s?ip access\-list standard XXX[\r\n]$…