User's Manual

468
!
router bgp 100
neighbor 4.0.0.1 remote-as 200 /*RTA EBGP*/
RTE configuration:
interface s1/0
ip address 5.0.0.2 255.0.0.0
!
router bgp 65020
bgp confederation identifier 200
bgp confederation peers 65010
neighbor 5.0.0.1 remote-as 65010 /*RTA EBGP*/
61.5.9 Example of Route Map with BGP Group Attribute
This section includes three examples of using route map with BGP community attribute.
In the first example, “route map set-community” is applied on the outcoming update of neighbor 171.69.232.50.
Set the special community attribute with value “no-export” for the routes passing access list aaa, while other
routes are broadcasted normally. This special community attribute will automatically prevent BGP speakers in
AS200 from advertising the route outside of the autonomous system.
router bgp 100
neighbor 171.69.232.50 remote-as 200
neighbor 171.69.232.50 send-community
neighbor 171.69.232.50 route-map set-community out
!
route-map set-community 10 permit
match ip address aaa
set community no-export
!
route-map set-community 20 permit
In the second example, “route map set-community” is used for the outcoming update of neighbour
171.69.232.90. All routes orgining from AS70 will insert value 200 into the community attribute 200, all other
routes will just be advertised normally.
route-map bgp 200
neighbor 171.69.232.90 remote-as 100
neighbor 171.69.232.90 send-community
neighbor 171.69.232.90 route-map set-community out
!
route-map set-community 10 permit
match as-path test1
set community-additive 200 200
!
route-map set-community 20 permit
match as-path test2
!
ip aspath-list test1 permit 70$
ip aspath-list test2 permit .*
In the third example, selectively set the MED and local preference value of routes from neighbor
171.69.232.55 according to the commumity attribute value of the routes. All routers matching with community
list com1will be set with MED as 8000, this may include routes with community value “100 200 300” or “900