Some questions
Katie Petrusha katie at ripe.net
Wed Oct 8 15:45:18 CEST 2003
On Fri, Oct 03, 2003 at 01:09:12PM +0300, Alexander Moskalenko wrote: Dear Alexander, > >>Hello ! > >> > >>I'm trying to automate cisco prefix-lists configuration. > >> > >>1. Is it possible to set name for prefix-list ? > > > > > >Not for now but will be implemented soon. Now you can only set the start > >number by > >@RtConfig set cisco_prefix_acl_no = 0 > >if you're using prefix lists. > >'pl' prefix is hardcoded but I'll make it configurable in the next > >release. > > > > Now I made a template per peer and using sed to replace 'pl100' by the > name i want. > If there will be a possibility to configure this thing the way like: > > @RtConfig cisco_prefix_acl_name = <prefix-name> > @RtConfig import <ASN-1> <rtr-1> <ASN-2> <rtr-2> > @RtConfig cisco_prefix_acl_name = <another prefix-name> > @RtConfig import <ASN-1> <rtr-1> <ASN-2> <rtr-2> Yes, that's how it will look like in the future. > >As you may have noticed, the identical prefix/access lists are not > >printed for optimization by default. > >However, if you want the identical prefix/access lists to be printed, > >you may turn on this option: > > > > -disable_access_list_cache > > ok, thanx, I'll use it > my BGP configuration requires prefix list per peer > > and another question: > if there is a tool to automaticaly change router's configuration? > for example something changes in RIPE DB, my script compares new > prefix-list with the previous, mails diff > then human reads mail and, if all ok, reply with password and string > 'OK', configuration automaticaly changes Not that I know. Mostly people use their own scripts. -- Kind regards, Katje