On 10/10/16, Jay Hennigan <j...@west.net> wrote: > On 10/6/16 1:26 PM, Jesse McGraw wrote: >> Nanog, >> >> (This is me scratching an itch of my own and hoping that sharing it >> might be useful to others on this list. Apologies if it isn't) >> >> When I'm trying to comprehend a new or complicated Cisco router, >> switch or firewall configuration an old pet-peeve of mine is how >> needlessly difficult it is to follow deeply nested logic in route-maps, >> ACLs, QoS policy-maps etc etc >> >> To make this a bit simpler I’ve been working on a perl script to convert >> these text-based configuration files into HTML with links between the >> different elements (e.g. To an access-list from the interface where it’s >> applied, from policy-maps to class-maps etc), hopefully making it easier >> to to follow the chain of logic via clicking links and using the forward >> and back buttons in your browser to go back and forth between command >> and referenced list. > > Way cool. Now to hook it into RANCID....
It looks like what I did in 2.3.8 should still work - control_rancid puts the diff output into $TMP.diff so add this bit: grep "^Index: " $TMP.diff | awk '/^Index: configs/{ if ( ! got1 ) { printf("/usr/local/bin/myscript.sh "); got1=1; } printf("%s ", $2) } END{ printf("\n") } ' >$TMP.doit /bin/sh $TMP.doit >$TMP.out if [ -s $TMP.out ] ; then .. send mail / whatever rm $TMP.doit $TMP.out fi Regards, Lee