Route-map and Prefix-list - order of preference

From: gladston@br.ibm.com
Date: Tue Aug 09 2005 - 10:34:57 GMT-3


Hi,

This doc is not consistent with the result on C3640-JS-M, Version 12.2(15)T9

===========================
The order of preference varies depending on whether the attributes are applied for inbound updates or outbound updates.
For inbound updates the order of preference is:

   1. route-map
   2. filter-list
   3. prefix-list, distribute-list

http://www.cisco.com/warp/public/459/bgpfaq_5816.shtml

=================================

On the following test I expected, based on the doc, that all routes were permitted because of the order of preference higher for route-map.

The result is that route with mask equal or less than 18 are denied.

Config:

router bgp 5
 no synchronization
 neighbor 150.100.2.254 remote-as 254
 neighbor 150.100.2.254 prefix-list Filter-by-prefix-list in
 neighbor 150.100.2.254 route-map Set-LP-Prepend in

All routes are permitted by route-map.
Prefix with mask equal or less than 18 are denied by prefix-list.

Debug:

.Feb 28 21:39:02: BGP(0): 150.100.2.254 rcvd 60.2.128.0/17 -- DENIED due to: distribute/prefix-list;

More config:

route-map Set-LP-Prepend permit 10
 match ip address 143
 set local-preference 200
 set as-path prepend 254
!
route-map Set-LP-Prepend permit 20
 set local-preference 200
!
access-list 143 permit ip 154.0.1.0 0.254.0.0 host 255.255.255.0
!
ip prefix-list Filter-by-prefix-list seq 5 deny 0.0.0.0/0 le 17
ip prefix-list Filter-by-prefix-list seq 10 permit 0.0.0.0/0 le 32



This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:01:18 GMT-3