Compare Running configuration to written when captured on LM
In my instance of LM I have captured the written configuraiton and running configuration. Any suggestions to do a diff comparison and create an alert against it?
-=CB=-
The_Bhattman
Posted 4 years ago·Last reply 4 years ago
6 comments
Antony Hawkins
·4 years agoThen my startup vs running custom ConfigSource, as linked above, may be of assistance.
mnagel
·4 years agoFWIW, we do use a Unsaved Config DS we wrote for IOS that compares the saved time and last config change time. It _mostly_ works, but there are some annoyances. One is uptime counter rollover, a general problem with timestamp comparisons. The other is that IOS reports config changed the second you enter config mode even if you change nothing.
The_Bhattman
OP4 years agoHow about this article
/topic/2027-running-vs-startup-comparison-configsource-poc/mnagel
·4 years agoNot only that, but comparing in some cases is very painful. When we used to use Nagios, we had checks that worked very well for the ASA since they use a cryptochecksum (this was trivial since we just scanned all the files in one pass, compared and submitted passive check results for any problems -- LM needs something similar, probably via the API). For IOS there are a bunch of elements instantiated at startup that are not in the saved config, so while you could perhaps fashion a suitable filter, it would be brittle. Other platforms might be OK, just depends.
LM User
·4 years agoIf they are separate instances no. You'd have to do that kind of work inside a groovy based config check, collecting both the configs within a single configsource, then using groovy to compare them.