[rancid] Re: Cisco ASA 8.2 software - changes....

[john heasley]

Fri, May 29, 2009 at 02:56:33PM -0500, Justin Shore:
> Here's the contents of mine:
>
> ASA# more disk0:/coredumpinfo/coredump.cfg
> CD_ENA=no
> CD_FILESYSTEM=disk0:
> CD_COMP=yes

looks useless to me; seems that info is either in the config or the
file contents should be displayed by rancid, and filter the file from
the flash listing.

Index: rancid.in
===================================================================
RCS file: /home/rancid/.CVS/rancid/bin/rancid.in,v
retrieving revision 1.255
diff -d -u -r1.255 rancid.in
--- rancid.in	20 Apr 2009 19:56:27 -0000	1.255
+++ rancid.in	29 May 2009 21:20:41 -0000
@@ -705,6 +705,8 @@
 	}
 
 	/\s+(multiple-fs|nv_hdr|vlan\.dat)$/ && next;
+	# filter coredumpinfo/coredump.cfg
+	/\s+oredumpinfo\/coredump.cfg$/ && next;
 	ProcessHistory("FLASH","","","!Flash: $_");
     }
     ProcessHistory("","","","!\n");

> It looks like some developer decided to store configuration parameters  
> in a file on the disk rather than in the running-config.  I downgraded  
> last night but I fully expect the file to be updated with other config  
> if I were to actually enable the coredump feature.  I don't know where  
> the actual coredumps would be stored however.  It could be in the  
> coredumpinfo directory so excluding the directory and all its contents  
> might not be a good thing.  Excluding the coredump.cfg file wouldn't be  
> such a bad thing though.
>
> Justin
>
>
> john heasley wrote:
>> Fri, May 29, 2009 at 08:11:47AM -0400, Sam.Holley at gtri.gatech.edu:
>>> We to were having the same issue, we did the following to Rancid to keep it from reporting on the file every time it was updated. So far, working like a champ.
>>>
>>>
>>>
>>> The correct part to edit is the ShowFlash function between ~lines 564 and 577.  I added one line under this one:
>>>
>>>
>>>
>>> /\s+vlan\.dat$/ && next;
>>>
>>>
>>>
>>> to look like this:
>>>
>>> /\s+vlan\.dat$/ && next;
>>>
>>> /.*coredumpinfo.*/ && next;
>>
>> still, what is the file?  is it configuration, which exists in the
>> show conf, and therefore can just be filtered?  or is a coredump, which
>> you'd want to know about changes.
>>
>> ie: should rancid filter it, or say here's the DDTS (Thanks Justin)?
>>
>>>
>>> It now ignores any lines in the flash drive directory listing that contain "coredumpinfo".  The '.*' before and after are probably not necessary but it was added.
>>>
>>>
>>>
>>> Sam
>>>
>>>
>>>
>>> From: rancid-discuss-bounces at shrubbery.net [mailto:rancid-discuss-bounces at shrubbery.net] On Behalf Of Peter Serwe
>>> Sent: Thursday, May 28, 2009 10:59 PM
>>> To: Justin Shore
>>> Cc: rancid-discuss at shrubbery.net
>>> Subject: [rancid] Re: Cisco ASA 8.2 software - changes....
>>>
>>> Anybody running a configuration management system that checks the same things is going to log the change,
>>> it just so happens that rancid is particularly complete about checking for differences.
>>>
>>> For that matter, rancid isn't really a full-fledged configuration management system, but most of what anyone really
>>> wants to use one for is encompassed in rancid's functionality.  Any functioning configuration differ that is as complete
>>> as rancid would pick up the changes, it just so happens that most people don't run one, or look at the diffs, because
>>> the rest of them don't email out the changes like rancid does out of the box.
>>>
>>> I haven't noticed, FWIW, the same behavior in the 7.2.4 branch.
>>>
>>> Peter
>>>
>>> On Thu, May 28, 2009 at 7:17 PM, Justin Shore <justin at justinshore.com<mailto:justin at justinshore.com>> wrote:
>>> Justin Shore wrote:
>>>> I'll put a call into TAC next week and raise hell about this.  There's
>>>> no excuse for this file's timestamp to be hit every time someone does a
>>>> 'show run' (which is apparently the trigger for this "feature").
>>> I opened my case with TAC last week and asked for it to be escalated to
>>> the DE folks.  My TAC engineer ran the case up the flagpole for me and
>>> this issue is now acknowledged to be and is officially logged as a bug.
>>>  The BugID is CSCsz85597.
>>>
>>> http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsz85597
>>>
>>> My engineer suggested downgrading to the latest 8.0.4 interim release as
>>> a temporary workaround while the DE folks address the bug and work it
>>> into a maintenance release, hopefully for 8.2.  It should be a really
>>> simple fix so hopefully it doesn't take too long.  The engineer said
>>> that at least one other person is now attached to this bug and they too
>>> were running RANCID.
>>>
>>> Justin
>>>
>>> _______________________________________________
>>> Rancid-discuss mailing list
>>> Rancid-discuss at shrubbery.net<mailto:Rancid-discuss at shrubbery.net>
>>> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss
>>>
>>>
>>>
>>> --
>>> ????
>>
>>> _______________________________________________
>>> Rancid-discuss mailing list
>>> Rancid-discuss at shrubbery.net
>>> http://www.shrubbery.net/mailman/listinfo.cgi/rancid-discuss