Avaya 1000 Series Configuration Manual page 325

All routes received from 3rdPartyRouter having a community of 200:100 are filtered. The bgp
table shows all of those routes as INACTIVE.
Avaya1> show ip route
Show ip route does not show any BGP routes in its table. Change the routemap in
3rdPartyRouter to set community value of 200:100 , only for routes in 18.1.x.x range.
3rdPartyRouterA>conf term
3rdPartyRouterA(config)>ip access-list standard 1
3rdPartyRouterA(config-std-nacl)>permit 18.1.0.0
0.0.255.255
3rdPartyRouterA(config-std-nacl)>exit
3rdPartyRouterA(config)>route-map AS-100Community
permit 10
3rdPartyRouterA(config-route-map)>match ip address 1
3rdPartyRouterA(config-route-map)>set community 200:100
3rdPartyRouterA(config)>route-map AS-100Community
permit 20
3rdPartyRouterA>clear ip bgp *
3rdPartyRouterA>
Route map From200 on Avaya1 will filter everything in 18.1.x.x range and allow 15.1.x.x range
to be installed in to the routing table.
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 above shows that all 18.1.x.x range has the community of 200:100 set, but all of them are
marked INACTIVE which means got filtered properly.
Avaya1> show ip bgp table
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
15.1.2.0/24
15.1.3.0/24
18.1.1.0/24
18.1.5.0/24
18.1.6.0/24
Avaya Secure Router 1000 Series Configuration Guide
Next Hop Metric
30.30.30.3 100
30.30.30.3 100
30.30.30.3 100
30.30.30.3 100
Next Hop Metric
30.30.30.3 100
30.30.30.3 100
30.30.30.3 100
30.30.30.3 100
30.30.30.3 100
Configuring BGP Policies
LocPrf Path
0 200 ?
0 200 ?
0 200 ?
0 200 ?
LocPrf Path
170 200 ?
170 200 ?
0 200 ?
0 200 ?
0 200 ?
December 2010 325