Dear Sven, As far as I can see from your AS20738 aut-num object: aut-num: AS20738 import: from AS2529 action pref=100; accept AS-DEMON AND NOT {0.0.0.0/0} export: to AS2529 announce AS-MAGMOM Your peering description of AS2529 is not detailed enough for RtConfig to select your policy correctly. You may try something like: import: from AS2529 <peerIP> at <localIP> action ... export: to AS2529 <peerIP> at <localIP> announce ... where peerIP and localIP are matching IPs from your inet-rtr object for this peer. The fully specified description of the peering in this case should be: <ASno> [<peerIP> at <localIP>] where [] part is optional. But in case if you use inet-rtr, you should use this more detailed description, so that policy selection can be done properly by RtConfig. If your aut-num doesn't have full specification of the peering, like: import: from AS1 export to AS2 then all possible interface addresses will be selected from your inet-rtr object, as there's no indication which local/remote IP pair you use for the peer. I hope I understood the question correctly and this will be helpful. If you need more details on how policy selection is made (in the software) etc, please let me know. The basics are as usual available in RFC2622. Katie Petrusha Software Engineering Department RIPE NCC
Date: Tue, 13 Jan 2004 09:55:02 +0000 From: sven.huster@hosteurope.com To: irrtoolset@ripe.net Subject: Problem with inet-rtr object
Hello
I got some problems trying to use the inet-rtr object. It creates a lot of route-maps for one peer (8 in this case). I would think it should create just one for in and one for out in a normal (simple) case.
Any suggestions what I do wrong or what's broken here?
Following the input and output used (obviously I removed parts which I consider irrelevant).
Regards Sven
inet-rtr: r01.hosteurope.net local-as: AS20738 ifaddr: 195.66.226.100 masklen 23 ifaddr: 217.199.160.42 masklen 32 ifaddr: 217.199.160.6 masklen 26 ifaddr: 213.248.100.30 masklen 30 peer: BGP4 195.66.226.12 asno(AS2529) [...]
aut-num: AS20738 [...] import: from AS2529 action pref=100; accept AS-DEMON AND NOT {0.0.0.0/0} export: to AS2529 announce AS-MAGMOM [...]
echo "@RtConfig configureRouter r01.hosteurope.net" | RtConfig -cisco_use_prefix_lists ! no ip prefix-list pl100 ip prefix-list pl100 permit 62.49.0.0/16 ip prefix-list pl100 permit 62.56.0.0/17 [...] ip prefix-list pl100 permit 213.222.0.0/19 ip prefix-list pl100 permit 217.22.144.0/20 ip prefix-list pl100 deny 0.0.0.0/0 le 32 ! no route-map MyMap_2529_1 ! route-map MyMap_2529_1 permit 1 match ip address prefix-list pl100 set local-preference 900 ! router bgp 20738 neighbor 195.66.226.12 route-map MyMap_2529_1 in ! no ip prefix-list pl101 ip prefix-list pl101 permit 212.67.192.0/19 ip prefix-list pl101 permit 217.199.160.0/19 ip prefix-list pl101 deny 0.0.0.0/0 le 32 ! no route-map MyMap_2529_2 ! route-map MyMap_2529_2 permit 1 match ip address prefix-list pl101 ! router bgp 20738 neighbor 195.66.226.12 route-map MyMap_2529_2 out ! no route-map MyMap_2529_3 ! route-map MyMap_2529_3 permit 1 match ip address prefix-list pl100 set local-preference 900 ! router bgp 20738 neighbor 195.66.226.12 route-map MyMap_2529_3 in ! no route-map MyMap_2529_4 ! route-map MyMap_2529_4 permit 1 match ip address prefix-list pl101 ! router bgp 20738 neighbor 195.66.226.12 route-map MyMap_2529_4 out ! no route-map MyMap_2529_5 ! route-map MyMap_2529_5 permit 1 match ip address prefix-list pl100 set local-preference 900 ! router bgp 20738 neighbor 195.66.226.12 route-map MyMap_2529_5 in ! no route-map MyMap_2529_6 ! route-map MyMap_2529_6 permit 1 match ip address prefix-list pl101 ! router bgp 20738 neighbor 195.66.226.12 route-map MyMap_2529_6 out ! no route-map MyMap_2529_7 ! route-map MyMap_2529_7 permit 1 match ip address prefix-list pl100 set local-preference 900 ! router bgp 20738 neighbor 195.66.226.12 route-map MyMap_2529_7 in ! no route-map MyMap_2529_8 ! route-map MyMap_2529_8 permit 1 match ip address prefix-list pl101 ! router bgp 20738 neighbor 195.66.226.12 route-map MyMap_2529_8 out