Piegorsch, Weylin William
2017-05-24 20:51:07 UTC
For those who are curious, I opened a TAC case about this last December (681520039). I asked four questions; here’s the response:
“Is this expected behavior?”
The switch will update the bootvar_debug.log file as part of its normal operation. This data is intended for Cisco engineering and TAC.
edit: of note, I’ve observed that updating those files also updates a number of other things in rancid’s output:
debug filesystem:
- bootvar_debug.log
- bootvar_debug.meta
logflash filesystem:
- debug_logs/
- the lines that show logflash: size used/free
“What I would need to do to disable it?”
Preventing these logs from updating is not an option as it is part of the switch's normal operation.
“[Do] I need to be worried about exhausting storage capacity?”
The debug directory will have a dedicated amount of flash storage for the file, as such, it will not have an impact on the other functions of the switch. You will not need to be worried about exhausting the capacity.
“Is this documented anywhere?”
This isn’t documented externally, however, these [TAC case notes] can be treated as official documentation if required.
weylin
-----Original Message-----
From: heasley <***@shrubbery.net>
Date: Wednesday, May 24, 2017 at 15:05
To: Nick Hilliard <***@foobar.org>
Cc: <***@nttdata.com>, <***@hbcs.org>, <rancid-***@shrubbery.net>
Subject: Re: [rancid] Nexus 7k & bootvar_debug churn
should work against nxos.pm too.
Index: lib/nxos.pm.in
===================================================================
--- lib/nxos.pm.in (revision 3646)
+++ lib/nxos.pm.in (working copy)
@@ -487,6 +487,9 @@
# Drop ee.log
/\s+ee\.log(?:\..*)?$/ && next;
+ # Drop bootvar_debug log files
+ /\s+bootvar_debug\./ && next;
+
# Drop accounting.log
/\s+accounting\.log$/ && next;
“Is this expected behavior?”
The switch will update the bootvar_debug.log file as part of its normal operation. This data is intended for Cisco engineering and TAC.
edit: of note, I’ve observed that updating those files also updates a number of other things in rancid’s output:
debug filesystem:
- bootvar_debug.log
- bootvar_debug.meta
logflash filesystem:
- debug_logs/
- the lines that show logflash: size used/free
“What I would need to do to disable it?”
Preventing these logs from updating is not an option as it is part of the switch's normal operation.
“[Do] I need to be worried about exhausting storage capacity?”
The debug directory will have a dedicated amount of flash storage for the file, as such, it will not have an impact on the other functions of the switch. You will not need to be worried about exhausting the capacity.
“Is this documented anywhere?”
This isn’t documented externally, however, these [TAC case notes] can be treated as official documentation if required.
weylin
-----Original Message-----
From: heasley <***@shrubbery.net>
Date: Wednesday, May 24, 2017 at 15:05
To: Nick Hilliard <***@foobar.org>
Cc: <***@nttdata.com>, <***@hbcs.org>, <rancid-***@shrubbery.net>
Subject: Re: [rancid] Nexus 7k & bootvar_debug churn
Thank you, Nick. On my deployment, I don't have an nxrancid file anywhere, but found the same logic in nxos.pm which I applied this to. I suspect this will resolve it.
er yeah, sorry this came from a rancid 2 deployment, but the patchshould work against nxos.pm too.
===================================================================
--- lib/nxos.pm.in (revision 3646)
+++ lib/nxos.pm.in (working copy)
@@ -487,6 +487,9 @@
# Drop ee.log
/\s+ee\.log(?:\..*)?$/ && next;
+ # Drop bootvar_debug log files
+ /\s+bootvar_debug\./ && next;
+
# Drop accounting.log
/\s+accounting\.log$/ && next;