286
Advertised to peers (1 in total):
200.1.3.2
The output shows that Router B can advertise the route with the destination 9.1.1.0/24 to other
ASs through BGP.
# Display the BGP routing table on Router C.
[RouterC] display bgp routing-table ipv4
Total number of routes: 1
BGP local router ID is 3.3.3.3
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
* >e 9.1.1.0/24 200.1.3.1 0 20 10i
Router C has learned the route to the destination 9.1.1.0/24 from Router B.
3.
Configure BGP COMMUNITY attribute:
# Configure a routing policy.
[RouterA] route-policy comm_policy permit node 0
[RouterA-route-policy-comm_policy-0] apply community no-export
[RouterA-route-policy-comm_policy-0] quit
# Apply the routing policy.
[RouterA] bgp 10
[RouterA-bgp] address-family ipv4 unicast
[RouterA-bgp-ipv4] peer 200.1.2.2 route-policy comm_policy export
[RouterA-bgp-ipv4] peer 200.1.2.2 advertise-community
Verifying the configuration
# Display the BGP route 9.1.1.0 on Router B.
[RouterB] display bgp routing-table ipv4 9.1.1.0
BGP local router ID: 2.2.2.2
Local AS number: 20
Paths: 1 available, 1 best
BGP routing table information of 9.1.1.0/24:
From : 200.1.2.1 (1.1.1.1)
Rely nexthop : 200.1.2.1
Original nexthop: 200.1.2.1
OutLabel : NULL
Community : No-Export
AS-path : 10
Origin : igp
Attribute value : pref-val 0