[Infrastructures] using IA methodologies to build network element configuration

[Matt S Trout]

On Wed, Apr 06, 2005 at 10:51:49AM +1000, Andrew Fort wrote:
> For the routing policy example Daniel gave, this problem is "solved" in 
> terms of building multi-vendor configuration.  It amazes me that only 1 
> in 20 network engineers I talk to have heard of it (or 'have heard about 
> it' but have no idea what it is).
> 
> RPSL (see rfc 2622, 2650) is the policy language.
> IRRToolSet is the toolset for configuration building and data management 
>    (originally a ISI/Merit? development, then RIPE, now ISC)..
> 
> However, IRRToolSet doesn't give you any way to upload your 
> configurations, and as of RtConfig (the config builder) v4.7, it still 
> doesn't support some of the most useful abstractions in RPSL (such as as 
> router objects properly).  Also, some problems are most easily handled 
> by simply awk'ing the output of it..

Looks very cool, but so far as I can see is only designed for inter-AS
routing rather than intra-AS routing? IME most organisations get into
trouble due to ad-hoc configuration of their internal network far sooner
than they do from ad-hoc peering configuration.

-- 
    Matt S Trout            Brag sheet:    http://trout.me.uk/services.html
LAMP, Infrastructure        Contact:       services@trout.me.uk
   and Automation
     specialist                                       Do it once. Do it right.