Avaya 1000 Series Configuration Manual page 318

Configuring BGP Features
18.1.5.0/24
18.1.6.0/24
18.1.7.0/24
Check whether Avaya2 has any routes with community value of 100 in it.
Avaya2> show ip bgp community number 100
No routes have got a community set with value 100.
In order to set a community value of 100 to the aggregated address 18.1.0.0/21 in Avaya1,
use an attribute_map. Attribute_map also uses a route map to select a set of routes and then
set some attribute values to it.
In this case, set community value 100 to aggregated address 18.1.0.0/21. Use a route map
called ToAvaya2 which matches all routes and sets community 100.
Avaya1/configure> policy route_map ToAvaya2 1 permit
Avaya1/configure/policy/route_map ToAvaya2 1> set community aa_nn
0:10
Apply that route map to our aggregate address using attribute_map:
Avaya1/configure> router bgp 100
Avaya1/configure/router/bgp 100> aggregate_address 18.1.0.0
255.255.248.0 attribute_map ToAvaya2 Avaya1 should have advertised 18.1.0.0/21
with a community value of 0:100 or 100. View the bgp table of Avaya2:
Avaya2> show ip bgp table
BGP route table, local router ID is 100.1.1.3 Status codes: * valid, > best, i -
internal Origin codes: i - IGP, e - EGP, ? - incomplete
Network
18.1.1.0/24
18.1.2.0/24
18.1.3.0/24
18.1.0.0/21
18.1.5.0/24
18.1.6.0/24
18.1.7.0/24
Avaya2 has received the aggregate address 18.1.0.0/21.
318 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
Orig Next Hop Next Hop
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
20.1.1.1 20.1.1.1
Metric LocPrf Path
100 200 ?
100 200 ?
100 200 ?
100 i
100 200 ?
100 200 ?
100 200 ?
100 200 ?
100 200 ?
100 200 ?
December 2010