Discussion:
[rancid] Disabling commands without altering rancid.types.base
Howard Jones
2017-06-19 14:07:54 UTC
Permalink
I have a few nexus 7000 switches where the contents of bootflash changes
very regularly, causing spurious changes. For now, I've commented out
some commands in etc/rancid.types.base, against the advice of the
manpage. Is there a way to remove commands in rancid.types.conf for an
existing device type?

# cisco-nx;command;nxos::DirSlotN;dir bootflash:
#cisco-nx;command;nxos::DirSlotN;dir debug:
#cisco-nx;command;nxos::DirSlotN;dir logflash:
#cisco-nx;command;nxos::DirSlotN;dir slot0:
#cisco-nx;command;nxos::DirSlotN;dir usb1:
#cisco-nx;command;nxos::DirSlotN;dir usb2:
#cisco-nx;command;nxos::DirSlotN;dir volatile:
heasley
2017-06-19 16:10:09 UTC
Permalink
Post by Howard Jones
I have a few nexus 7000 switches where the contents of bootflash changes
very regularly, causing spurious changes. For now, I've commented out
some commands in etc/rancid.types.base, against the advice of the
manpage. Is there a way to remove commands in rancid.types.conf for an
existing device type?
only by creating a different device definition, such as cisco-nx-thingie,
in rancid.types.conf.

These changes in the next version (and in the current alpha) might help:

nxos.pm: drop bootvar_debug.* log files reported on the ML

nxof.pm: Filter vtp_debug.log and vtp_debug_old.log CDETS bug CSCuy87611
- Mark Felder

Loading...