For those who take advantage of sflow on the newer powerconnect firmware (3.x supports it), you might find that the running-config now has a new timeout value, which is a countdown. Countdowns make babies cry. While I hate to see crying babies, sflow is way too useful to let a few whiny infants get in my way of using it, so instead I decided to modify rancid to stop informing me of this countdown reduction.<br>
<br>3c3<br>< ## $Id: drancid,v 1.2 2010/07/29 14:42:56 rancid Exp $<br>---<br>> ## $Id: drancid,v 1.1 2010/07/29 14:09:22 rancid Exp $<br>229,237d228<br>< # -------------------------------<br>< # custom lines here<br>
< # -------------------------------<br>< #<br>< # ignore sflow countdown timer<br>< if (/(sflow\s+\d+.*timeout)/) {<br>< ProcessHistory("","","","$1 4294967295\n"); next;<br>
< }<br><br>I'm putting in that high number because that is the highest the command allows, and if you're wanting to paste it into a config again later, better it to be a usable command and not an <ignored> or <removed> type of message.<br>
<br>My thanx to <b>john heasley </b>on the post at <a href="http://www.shrubbery.net/pipermail/rancid-discuss/2010-July/005065.html">http://www.shrubbery.net/pipermail/rancid-discuss/2010-July/005065.html</a> for the hints I needed. <br>
<br>This is my first filter, so be kind.<br><br><br>