RE: RANCID filter_audit

> No, I'm thinking of something that (gasp) I had with the IBM=20
> 360 assembler and
> other compilers and assemblers.
>=20
> At the end of a configuration (to start), it would list an=20
> address (or a
> subnet), and tell you all the statements that referenced it.=20
> For example,
>         ip address
>         access-list (and probably indirect references in maps)
>         ospf network statements
>         server references
>         static routes
> as a starting point.  In other words, it tells you EVERYWHERE=20
> you need to make
> changes when you change an address or something affecting it.
>=20
> The next step would be to extend the scope beyond a single=20
> router, grabbing the
> hostname to prefix the cross-reference. Again, the idea is=20
> that if an address
> changes, you have a positive confirmation of every=20
> configuration that may need
> to be changed.  It's also a debugging tool, because you know=20
> which routers
> affect that address.
>

I don't think it's something I can have use for very often. (IP address
changes).
this also sounds it could be tricky to program
I use primitive checks like: "sh run | inc x\.y\.z\." to catch config
that might refer to the subnet.
also on clean config I think you should refere to ip address as least as
possible. (f.e. static route point to interface will not require any
changes)