From alex at teleportsv.net Thu Oct 2 15:35:12 2003 From: alex at teleportsv.net (Alexander Moskalenko) Date: Thu, 02 Oct 2003 16:35:12 +0300 Subject: Some questions Message-ID: <3F7C2990.9020307@teleportsv.net> Hello ! I'm trying to automate cisco prefix-lists configuration. 1. Is it possible to set name for prefix-list ? 2. I have a strange situation In RIPE DB: import: from AS3261 action pref=400; accept ANY export: to AS3261 announce AS-TeleportSV remarks: . import: from AS6849 action pref=400; accept ANY export: to AS6849 announce AS-TeleportSV RtConfig gives the following: !Fticom Warning: filter matches ANY/NOT ANY ! no ip prefix-list pl106 ip prefix-list pl106 permit 0.0.0.0/0 le 32 ! !UkrTelecom Warning: filter matches ANY/NOT ANY ! ^^^^^^ There is no prefix-list for second upstream but the routing policy is the same Here is my template: @RtConfig set cisco_access_list_no = 0 ! ! !Fticom @RtConfig import AS15785 AS3261 ! !UkrTelecom @RtConfig import AS15785 AS6849 ! From katie at ripe.net Fri Oct 3 09:58:51 2003 From: katie at ripe.net (Katie Petrusha) Date: Fri, 3 Oct 2003 09:58:51 +0200 Subject: Some questions In-Reply-To: <3F7C2990.9020307@teleportsv.net> References: <3F7C2990.9020307@teleportsv.net> Message-ID: <20031003075851.GC1983@ripe.net> On Thu, Oct 02, 2003 at 04:35: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. > 2. I have a strange situation > In RIPE DB: > import: from AS3261 action pref=400; accept ANY > export: to AS3261 announce AS-TeleportSV > remarks: . > import: from AS6849 action pref=400; accept ANY > export: to AS6849 announce AS-TeleportSV > > RtConfig gives the following: > > !Fticom > Warning: filter matches ANY/NOT ANY > ! > no ip prefix-list pl106 > ip prefix-list pl106 permit 0.0.0.0/0 le 32 > ! > !UkrTelecom > Warning: filter matches ANY/NOT ANY > ! > > > ^^^^^^ > There is no prefix-list for second upstream but the routing policy is the > same 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 RtConfig caches the access-lists (and in the future ip as-path access-lists and route- maps) that it generates so that the same access-list number can be reused instead of generating a new access list. If you do not want RtConfig to consume much memory, -dis- able_access_list_cache option can be used to turn off this feature. However, if you are short on memory on your cisco box, you should leave this feature enabled. Then RtConfig will print for you another list as well. So your output may then look like: no ip prefix-list pl100 ip prefix-list pl100 permit 0.0.0.0/0 le 32 ! no route-map MyMap_3261_1 ! route-map MyMap_3261_1 permit 1 match ip address prefix-list pl100 set local-preference 600 ! router bgp 15785 neighbor 2.2.2.2 route-map MyMap_3261_1 in !UkrTelecom Warning: filter matches ANY/NOT ANY ! no ip prefix-list pl101 ip prefix-list pl101 permit 0.0.0.0/0 le 32 ! no route-map MyMap_6849_2 ! route-map MyMap_6849_2 permit 1 match ip address prefix-list pl101 set local-preference 600 ! router bgp 15785 neighbor 4.4.4.4 route-map MyMap_6849_2 in (Notice that pl101 and pl100 are identical, but I've used -disable_access_list_cache option). Don't hesitate to ask if you have any further questions. > > Here is my template: > > @RtConfig set cisco_access_list_no = 0 > ! > > ! > !Fticom > @RtConfig import AS15785 AS3261 > ! > !UkrTelecom > @RtConfig import AS15785 AS6849 > ! -- Kind regards, Katie Petrusha RIPE NCC From alex at teleportsv.net Fri Oct 3 12:09:12 2003 From: alex at teleportsv.net (Alexander Moskalenko) Date: Fri, 03 Oct 2003 13:09:12 +0300 Subject: Some questions In-Reply-To: <20031003075851.GC1983@ripe.net> References: <3F7C2990.9020307@teleportsv.net> <20031003075851.GC1983@ripe.net> Message-ID: <3F7D4AC8.9060907@teleportsv.net> Katie Petrusha wrote: Dear Katie, > On Thu, Oct 02, 2003 at 04:35: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 = @RtConfig import @RtConfig cisco_prefix_acl_name = @RtConfig import > > > 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 From katie at ripe.net Wed Oct 8 15:45:18 2003 From: katie at ripe.net (Katie Petrusha) Date: Wed, 8 Oct 2003 15:45:18 +0200 Subject: Some questions In-Reply-To: <3F7D4AC8.9060907@teleportsv.net> References: <3F7C2990.9020307@teleportsv.net> <20031003075851.GC1983@ripe.net> <3F7D4AC8.9060907@teleportsv.net> Message-ID: <20031008134517.GA16645@ripe.net> 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 = > @RtConfig import > @RtConfig cisco_prefix_acl_name = > @RtConfig import 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 From katie at ripe.net Thu Oct 23 15:14:50 2003 From: katie at ripe.net (Katie Petrusha) Date: Thu, 23 Oct 2003 15:14:50 +0200 Subject: Prototype release of RPSLng IRRToolSet Message-ID: <20031023131450.GC6823@ripe.net> [ Apologies for multiple messages ] Dear Colleagues, The RIPE NCC is pleased to announce version 4.8.1 prototype release of IRRToolSet. RPSLng is an effort to extend RPSL language, enabling the language to document routing policies for the IPv6 and multicast address families currently used on the Internet. The prototype of IRRToolSet implements the Internet Draft Document draft-blunk-rpslng-01 (http://www.ietf.org/internet-drafts/draft-blunk-rpslng-01.txt). The prototype release contains peval, rpslcheck and RtConfig that already work with a new dictionary (you can also try the Web prototype for peval and RtConfig). Currently work is in progess to make other tools RPSLng compatible. More details can be found at: http://www.ripe.net/db/irrtoolset Please contact irrtoolset at ripe.net for any comments. -- Best regards, Katie Petrusha RIPE NCC