User's Manual

BGP route table
Flags: >=Best route for the given prefix, *=Unreachable next hop,
W=Withdrawn
m=Community, a=Aggregate route, s=Aggregate Suppressed, D=Damped
Learned from: L=Local, e=eBGP Peer, i=iBGP Peer, c=Confederate
Peer
---------------------------------------------------------------------
Fl Prefix Next hop Origin MED Local pref
Path
Originator Cluster List
---------------------------------------------------------------------
<SNIP>
> 64.0.0.0/4 45.45.45.45 INCOMPLETE - 100
SEQ 34567 11 22 33 44 55 66 77 88 99 1010 1111 1212 1313 1414 1515
1616;
e - -
---------------------------------------------------------------------
Use Route Ma
ps and Other Filters to Filter and Alter BGP and OSPF Routes | Page 39
Examples
Example G A community-list based filter dropping incoming updates based on community
number
1. Configure the AW peer to send out a community number 89:89
add ip routem=com entry=1 set commmun=89:89
set bgp peer=45.45.45.45 outroutemap=com sendcommunity=yes
The routes coming from that peer has community 89:89
1. Then, on the AlliedWare Plus switch, create a community-list that matches on some
community values.
ip community-list 78 permit 55:66
ip community-list 78 permit 89:89
ip community-list 78 permit 9999:89
2.
Create a prefix-list that matches the route 52.0.0.0/8
ip prefix-list test1 permit 52.0.0.0/8
3.
Set the community-list to be the match criterion on a deny entry in a route map
route-map com deny 1
match community 78
BGP#show ip bgp 52.0.0.0/8
BGP routing table entry for 52.0.0.0/8
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Not advertised to any peer
34568
45.45.45.46 from 45.45.45.46 (45.45.45.46)
Origin IGP metric 0, localpref 100, valid, external, best
Community: 89:89 ----------------------------
Last update: Wed Oct 1 06:47:01 2008