[AusNOG] Route filter update management advice.

[Matthew Moyle-Croft]

On 26/05/2010, at 12:49 PM, David Hughes wrote:

> 
> For your own sanity, generating your BGP and filtering config from an RPSL specification is a good step forward.  I've been working on that for a while now.  The old  IRR Toolset ( irrtoolset.isc.org) has been horrible to work with over the years but is getting better.

FWIW, our EBGP policy is entirely driven from IRRToolset.  It's a little ugly, but you can generate all filtering etc at a higher level and never have to hand code EBGP again.  Does need some automation wrapped around it.  One nice thing -> it can generate IOS and JunOS amongst other things.  So, aside from the glue to generate some stuff, you can move from vendor to vendor with no issue.   

(it can also be used to generate filters -> so knowing what's on net or not is really easy).

Highly recommended.

We also automate iBGP completely.   DB has router descriptions (functions, rr details, etc) and generates entire IBGP stack for every router in about 30sec.   

MMC

>  If it wasn't written in c++ I'd be helping maintain and enhance it.  Shame about the choice of language really.  But, it's getting more portable and reliable so it's a good starting point.  That and IRRd (www.irrd.net) should help remove some of the manual aspects.
> 
> 
> David
> ...
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog