[rancid] asr 920 noisy dir bootflash:

[Mikhail]

Hello. I have a lot of such configuration changes.

tracelogs size changes are skipped but it is not, how can i get rid of it?

Thank you :)


- !Flash: bootflash: 1339412480 bytes total (869 MB free)
+ !Flash: bootflash: 1339412480 bytes total (868 MB free)

- !Flash: bootflash: 1339412480 bytes total (868 MB free)
+ !Flash: bootflash: 1339412480 bytes total (869 MB free)

- !Flash: bootflash: 1339412480 bytes total (869 MB free)
+ !Flash: bootflash: 1339412480 bytes total (868 MB free)

- !Flash: bootflash: 1339412480 bytes total (868 MB free)
+ !Flash: bootflash: 1339412480 bytes total (869 MB free)



Mit freundlichen GrÌßen, Mikhail.

[heasley]

Post by Mikhail
Hello. I have a lot of such configuration changes.
tracelogs size changes are skipped but it is not, how can i get rid of it?
Thank you :)
- !Flash: bootflash: 1339412480 bytes total (869 MB free)
+ !Flash: bootflash: 1339412480 bytes total (868 MB free)
- !Flash: bootflash: 1339412480 bytes total (868 MB free)
+ !Flash: bootflash: 1339412480 bytes total (869 MB free)
- !Flash: bootflash: 1339412480 bytes total (869 MB free)
+ !Flash: bootflash: 1339412480 bytes total (868 MB free)
- !Flash: bootflash: 1339412480 bytes total (868 MB free)
+ !Flash: bootflash: 1339412480 bytes total (869 MB free)
Mit freundlichen Grüßen, Mikhail.

Grüße, You can can define a new device type that omits collection
of flash information (see rancid.types.conf(5)), or try rancid 3.8
or the current alpha which both have been altered to further reduce
fluctuation in flash info, or create a new module with a version of
DirSlotN() that filters this altogether, or complain to Cisco about
leaving debug code in production images. :)

I do not recall if the 900 runs XE or XR, but an example from XE:

!Flash: bootflash: 7 GB total (83% free)

[Emille Blanc]

We encountered this, and in some cases they would tick over the multi-megabyte mark, so the built-in function heasly mentions here didn't eliminate the noise adequately.
Our solution was to hack in a function that when an ASR920 is encountered, display the free space in ">500MB free". This still generated a diff if space dropped below 500, which happens occasionally when one of the ASR's maintenance tasks goes haywire.

-----Original Message-----
From: Rancid-discuss [mailto:rancid-discuss-***@shrubbery.net] On Behalf Of heasley
Sent: Friday, September 14, 2018 10:22 AM
To: Mikhail

Post by Mikhail
Hello. I have a lot of such configuration changes.
tracelogs size changes are skipped but it is not, how can i get rid of it?
Thank you :)
- !Flash: bootflash: 1339412480 bytes total (869 MB free)
+ !Flash: bootflash: 1339412480 bytes total (868 MB free)
- !Flash: bootflash: 1339412480 bytes total (868 MB free)
+ !Flash: bootflash: 1339412480 bytes total (869 MB free)
- !Flash: bootflash: 1339412480 bytes total (869 MB free)
+ !Flash: bootflash: 1339412480 bytes total (868 MB free)
- !Flash: bootflash: 1339412480 bytes total (868 MB free)
+ !Flash: bootflash: 1339412480 bytes total (869 MB free)
Mit freundlichen Grüßen, Mikhail.

Grüße, You can can define a new device type that omits collection of flash information (see rancid.types.conf(5)), or try rancid 3.8 or the current alpha which both have been altered to further reduce fluctuation in flash info, or create a new module with a version of
DirSlotN() that filters this altogether, or complain to Cisco about leaving debug code in production images. :)

I do not recall if the 900 runs XE or XR, but an example from XE:

!Flash: bootflash: 7 GB total (83% free)