Discussion:
[rancid] ignoring flash memory changes
Saulo Zimbaro
2013-06-19 18:04:34 UTC
Permalink
ItŽs possible to ignoring memory changes in rancid backups?

Index: configs/csfw-asa-office01
===================================================================
retrieving revision 1.239
diff -U 4 -r1.239 csfw-asa-office01
@@ -30,9 +30,9 @@
!Flash: 123 11348300 Feb 21 2011 16:17:54 asdm-621.bin
!Flash: 3 4096 Dec 31 2002 22:03:48 log
!Flash: 10 4096 Dec 31 2002 22:03:58 crypto_archive
!Flash: 11 4096 Dec 31 2002 22:04:32 coredumpinfo
- !Flash: 12 43 Jun 19 2013 09:00:27 coredumpinfo/coredump.cfg
+ !Flash: 12 43 Jun 19 2013 12:00:33 coredumpinfo/coredump.cfg
!Flash: 125 12105313 Feb 21 2011 16:15:12 csd_3.5.841-k9.pkg
!Flash: 126 4096 Feb 21 2011 16:15:14 sdesktop
!Flash: 133 1462 Feb 21 2011 16:15:14 sdesktop/data.xml
!Flash: 127 2857568 Feb 21 2011 16:15:16
anyconnect-wince-ARMv4I-2.4.1012-k9.pkg
--
*Saulo Zimbaro*

Mobile ) (+55) 21 9800-0100

****@gmail.com

****@zimbaro.com
Alan McKinnon
2013-06-19 21:39:31 UTC
Permalink
It´s possible to ignoring memory changes in rancid backups?
Index: configs/csfw-asa-office01
===================================================================
retrieving revision 1.239
diff -U 4 -r1.239 csfw-asa-office01
@@ -30,9 +30,9 @@
!Flash: 123 11348300 Feb 21 2011 16:17:54 asdm-621.bin
!Flash: 3 4096 Dec 31 2002 22:03:48 log
!Flash: 10 4096 Dec 31 2002 22:03:58 crypto_archive
!Flash: 11 4096 Dec 31 2002 22:04:32 coredumpinfo
- !Flash: 12 43 Jun 19 2013 09:00:27 coredumpinfo/coredump.cfg
+ !Flash: 12 43 Jun 19 2013 12:00:33 coredumpinfo/coredump.cfg
!Flash: 125 12105313 Feb 21 2011 16:15:12 csd_3.5.841-k9.pkg
!Flash: 126 4096 Feb 21 2011 16:15:14 sdesktop
!Flash: 133 1462 Feb 21 2011 16:15:14 sdesktop/data.xml
!Flash: 127 2857568 Feb 21 2011 16:15:16
anyconnect-wince-ARMv4I-2.4.1012-k9.pkg
I don't know of a way to do this that is already built into shipped rancid.

I've always held the view that some things are just not generic enough
or detectable enough to be shipped out to everyone, so you get to
maintain a few forks with your own customization. And there are nowadays
so many IOSes with different behaviours....

You probably want to add something like this to ShowFlash:

next if (/coredumpinfo\/coredump.cfg\$/);

Untested of course so double check my regexes :-)

Rancid could really benefit from some kind of call-out mechanism where
we can add our own local tweaks and keep them out of the main code, but
unfortunately 2.3.x doesn't have this.

Perhaps a worthy addition to the 3.0 series!
--
Alan McKinnon
***@gmail.com
heasley
2013-06-27 22:18:12 UTC
Permalink
Post by Alan McKinnon
Rancid could really benefit from some kind of call-out mechanism where
we can add our own local tweaks and keep them out of the main code, but
unfortunately 2.3.x doesn't have this.
Perhaps a worthy addition to the 3.0 series!
What do you mean 'call-out mechanism'? in 3.0 you can tell rancid which
module to include (need to add functionality to include multiple modules)
and tell it what function to use to parse the output.
Alan McKinnon
2013-06-28 05:54:08 UTC
Permalink
Post by heasley
Post by Alan McKinnon
Rancid could really benefit from some kind of call-out mechanism where
we can add our own local tweaks and keep them out of the main code, but
unfortunately 2.3.x doesn't have this.
Perhaps a worthy addition to the 3.0 series!
What do you mean 'call-out mechanism'? in 3.0 you can tell rancid which
module to include (need to add functionality to include multiple modules)
and tell it what function to use to parse the output.
Yes, something like that.

The problem I face is I've forked every parser script I use, and it's
always to add or remove entire commands or individual regexes. These
things work best when the regex definition is treated as data out of a
config, not as pure code

I still haven't fully read the 3.0 code yet, so I could well be asking
for something you've already done
--
Alan McKinnon
***@gmail.com
Alan McKinnon
2013-06-30 23:37:10 UTC
Permalink
I do the same: modify each parser to ignore various lines (such as
timestamped items) -- is this the wrong method for ignoring certain
config diffs?
I'd say it's the only way
-- Eric Cables
Post by heasley
Post by Alan McKinnon
Rancid could really benefit from some kind of call-out mechanism
where
Post by heasley
Post by Alan McKinnon
we can add our own local tweaks and keep them out of the main
code, but
Post by heasley
Post by Alan McKinnon
unfortunately 2.3.x doesn't have this.
Perhaps a worthy addition to the 3.0 series!
What do you mean 'call-out mechanism'? in 3.0 you can tell rancid
which
Post by heasley
module to include (need to add functionality to include multiple
modules)
Post by heasley
and tell it what function to use to parse the output.
Yes, something like that.
The problem I face is I've forked every parser script I use, and it's
always to add or remove entire commands or individual regexes. These
things work best when the regex definition is treated as data out of a
config, not as pure code
I still haven't fully read the 3.0 code yet, so I could well be asking
for something you've already done
--
Alan McKinnon
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
--
Alan McKinnon
***@gmail.com
heasley
2013-07-01 15:55:22 UTC
Permalink
Post by Alan McKinnon
Post by heasley
Post by Alan McKinnon
Rancid could really benefit from some kind of call-out mechanism
where
Post by heasley
Post by Alan McKinnon
we can add our own local tweaks and keep them out of the main
code, but
Post by heasley
Post by Alan McKinnon
unfortunately 2.3.x doesn't have this.
Perhaps a worthy addition to the 3.0 series!
What do you mean 'call-out mechanism'? in 3.0 you can tell rancid
which
Post by heasley
module to include (need to add functionality to include multiple
modules)
Post by heasley
and tell it what function to use to parse the output.
Yes, something like that.
The problem I face is I've forked every parser script I use, and it's
always to add or remove entire commands or individual regexes. These
things work best when the regex definition is treated as data out of a
config, not as pure code
I still haven't fully read the 3.0 code yet, so I could well be asking
for something you've already done
3.0 does not offer a manner of altering the regexes by configuration,
only the module, commands and functions used for the given device type. I
do not see the former being practical, there are simply too many; you'd
practically define the entire module in a configuration file and the value
would be lost.
Alan McKinnon
2013-07-01 19:37:19 UTC
Permalink
Post by heasley
Post by Alan McKinnon
Post by heasley
Post by Alan McKinnon
Rancid could really benefit from some kind of call-out mechanism
where
Post by heasley
Post by Alan McKinnon
we can add our own local tweaks and keep them out of the main
code, but
Post by heasley
Post by Alan McKinnon
unfortunately 2.3.x doesn't have this.
Perhaps a worthy addition to the 3.0 series!
What do you mean 'call-out mechanism'? in 3.0 you can tell rancid
which
Post by heasley
module to include (need to add functionality to include multiple
modules)
Post by heasley
and tell it what function to use to parse the output.
Yes, something like that.
The problem I face is I've forked every parser script I use, and it's
always to add or remove entire commands or individual regexes. These
things work best when the regex definition is treated as data out of a
config, not as pure code
I still haven't fully read the 3.0 code yet, so I could well be asking
for something you've already done
3.0 does not offer a manner of altering the regexes by configuration,
only the module, commands and functions used for the given device type. I
do not see the former being practical, there are simply too many; you'd
practically define the entire module in a configuration file and the value
would be lost.
I can't get the first, but I can get 2, 3 & 4?

Deal, you have a sale. The check is in the mail :-)
--
Alan McKinnon
***@gmail.com
Eric Cables
2013-06-30 23:09:15 UTC
Permalink
I do the same: modify each parser to ignore various lines (such as
timestamped items) -- is this the wrong method for ignoring certain config
diffs?

-- Eric Cables
Post by Alan McKinnon
Post by heasley
Post by Alan McKinnon
Rancid could really benefit from some kind of call-out mechanism where
we can add our own local tweaks and keep them out of the main code, but
unfortunately 2.3.x doesn't have this.
Perhaps a worthy addition to the 3.0 series!
What do you mean 'call-out mechanism'? in 3.0 you can tell rancid which
module to include (need to add functionality to include multiple modules)
and tell it what function to use to parse the output.
Yes, something like that.
The problem I face is I've forked every parser script I use, and it's
always to add or remove entire commands or individual regexes. These
things work best when the regex definition is treated as data out of a
config, not as pure code
I still haven't fully read the 3.0 code yet, so I could well be asking
for something you've already done
--
Alan McKinnon
_______________________________________________
Rancid-discuss mailing list
http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
Loading...