Community List Filters - Avaya 1000 Series Configuration Manual

18.1.5.0/24
18.1.6.0/24
18.1.7.0/24
The above routes appear in the bgp table but not in the route table. Only active routes are
pushed on to the FIB. In the above *> 18.1.0.0/21 is the only one active.
Avaya2> show ip route
18.1.0.0/21 is the only route that got installed in the routing table.

Community List Filters

One other way filtering routes is to use community filters and decide based on the community
whether to permit/deny routes. Add a community of 100:200 to all routes announced by
3rdPartyRouter.
3rdPartyRouterA(config)>route-map AS-100Community permit
3rdPartyRouterA(config-route-map)>set community 200:100
3rdPartyRouterA(config)>router bgp 200
3rdPartyRouterA(config-router)>neighbor 30.30.30.1
route-map AS-100Community out
3rdPartyRouterA(config-router)>neighbor 30.30.30.1
send-community
3rdPartyRouterA>clear ip bgp *
View Avaya1's bgp table to check whether it has received all the routes with community
200:100 from 3rdPartyRouter. Perform a show using x:x format.
Avaya1> show ip bgp community aa_nn 200:100
BGP route table, local router ID is 30.30.30.1 Status codes: * valid, > best, i -
internal Origin codes: i - IGP, e - EGP, ? - incomplete
Network
18.1.1.0/24
18.1.5.0/24
18.1.6.0/24
18.1.7.0/24
The same can be obtained by giving an absolute number 13107300 in the show ip bgp
community , which is equal to 200:100
Avaya1> show ip bgp community number 13107300
BGP route table, local router ID is 30.30.30.1 Status codes: * valid, > best, i -
internal Origin codes: i - IGP, e - EGP, ? - incomplete
Avaya Secure Router 1000 Series Configuration Guide
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
Next Hop Metric
30.30.30.3 100
30.30.30.3 100
30.30.30.3 100
30.30.30.3 100
Configuring BGP Policies
100 200 ?
100 200 ?
100 200 ?
LocPrf Path
170 100 200 ?
170 100 200 ?
170 100 200 ?
170 100 200 ?
December 2010 323