Table of Contents
Advertisement
3.RTC configuration:
interface s1/0
ip address 2.0.0.2 255.0.0.0
!
interface s1/1
ip address 3.0.0.2 255.0.0.0
!
router bgp 65010
bgp confederation identifier 200
bgp confederation peers 65020
neighbor 2.0.0.1 remote-as 65010 /*RTA IBGP*/
neighbor 3.0.0.1 remote-as 65010 /*RTB IBGP*/
4.RTD configuration:
interface s1/0
ip address 4.0.0.2 255.0.0.0
!
router bgp 100
neighbor 4.0.0.1 remote-as 200 /*RTA EBGP*/
5.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*/
9. Examples of BGP Community Route Map
This section includes three examples of using route maps of BGP community.
In the first example, route map set-community is used for outbound updates getting to neighbor
171.69.232.50. Special community attribute "no-export" is set on routes passing access list aaa. Other
routes will be advertised normally. This special community attribute will automatically forbid BGP
session parts in AS200 to advertise this route to AS outside.
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 outbound updates getting to
171.69.232.90. All routing configurations generated by AS 70 will add the community attribute value
200 into current values. Other routes will 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
!
Model Name
- 275 -
Hide quick links:
Advertisement
Table of Contents
