Filter
Top Products
Use Route Maps and Other Filters to Filter and Alter BGP and OSPF Routes | Page 41
Examples
add ip routem=mixed entry=1 match prefixlist=com
add ip routem=mixed entry=1 set com=89:89
add ip routem=mixed entry=2 match prefixlist=as
add ip routem=mixed entry=2 set aspath=34599
set bgp peer=45.45.45.45 outroutemap=mixed sendcommunity=yes
When the route 156.23.4.144/28 is checked on the AlliedWare Plus switch, its ASPath
contains 34599.
3. On the AlliedWare Plus switch, create an ASPath-list that drops AS paths containing
34599, but allows all others.
ip as-path access-list list1 deny 34599
ip as-path access-list list1 permit .*
4. Create a community-list that includes the community 89:89, among others.
ip community-list 78 permit 55:66
ip community-list 78 permit 89:89
ip community-list 78 permit 9999:89
5. Create a route map that drops updates that match this community-list, but allows all other
updates.
route-map com deny 1
match community 78
route-map com permit 2
6. Apply both the aspath-list and the route map as in-filters on the neighbor:
router bgp 34567
redistribute connected
neighbor 45.45.45.46 remote-as 34568
neighbor 45.45.45.46 route-map com in
neighbor 45.45.45.46 filter-list list1 in
BGP#show ip bgp 156.23.4.144/28
BGP routing table entry for 156.23.4.144/28
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
34568 34599
45.45.45.46 from 45.45.45.46 (45.45.45.46)
Origin incomplete metric 0, localpref 100, valid, external, best
Last update: Wed Oct 1 08:54:10 2008