Custom Config Collection
Has anyone created custom modules to collect configs without having to log in and out of a switch/router as much? Right now, when I have configs getting collected from a switch via SSH, it logs in and out twice for each type of thing I'm collecting. We have it collecting configs and a few other commands the NOC folks asked if it could grab, so there are eight entries every time a collection is done. We also have these devices set up to log all sign ins and outs, so this fills the logs quite a bit every time it is run and makes it difficult to read other activity being logged. The active discovery and collection scripts on these config sources (for example SSH_Interactive_Dynamic) seem very similar so I don't understand why there is a need to have both. Ideally, one script would login, collect the four things I want it to collect, and sign out. I'm looking through the developer documentation a bit now, it's been a long time since I've written any code at this level though so any help would be appreciated Thank you!
ConfigSource to compare to a known template (PoC)
LM Config is awesome - but until now you've not been able to compare a config to a "known good" template. Now you can... Edit for v1.4.0+: Now gives a MUCH cleaner output (in my humble opinion) - see comments below for details. v1.4.0: 2GTW7W If you really want the earlier version with its more expansive output, v1.3.0 as detailed in this first post is at XHDDP4 Edit for v1.3.0+: The groovy check that picks up on the change-from-template flags is now more flexible, in that it looks at each line in turn (rather than the entire config object) so you can more carefully identify matches to be alerted on. This is very much only a proof-of-concept, which will show the method to use. As written it will do nothing in your account as it looks for a couple of test files I created specifically for this in my account. Suppose you have this template file (configTestTemplate.txt) for a config: # Config test file:# Here's a config test fileSetting1=1Setting2=2Setting3=3# The above must never be changed Now, suppose the actual config (in configTestConfig.txt) is like this: # Config test file:# Here's a config test fileSetting1=1Setting2=2Setting3=4# The above must never be changed If you can't see it, 'Setting3' has been changed... This ConfigSource will read in both the config (from file in this example, but it could be from SSH, etc) and the template from file, then run through the template and compare each line to the equivalent line in the config. Where it finds a discrepancy between the two, these are listed in the output after the actual config, marked with 'DISCREPANCY', as in the screenshot below. The template used for comparison is also returned: Config Checks then pick up on changes as you'd normally expect, and also if the output contains 'DISCREPANCY'. Notes: You must have LM Config to use this The template file must contain the EXACT same text in the EXACT same format as the config will be produced, because this PoC only checks line 1 against line 1, line 2 against line 2, etc. If your template contains 'DISCREPANCY' you'll have to come up with some other keyword to print and alert on, obviously.