H3C Technologies H3C SecPath F1000-E - Manual (Page 511)

486
AS-path : 10
Origin : igp
Attribute value : MED 0, pref-val 0, pre 255
State : valid, external, best,
Advertised to such 1 peers:
200.1.3.2
SecPath B has advertised the route to SecPath C in AS 30.
# Display BGP routing table information on SecPath C.
[SecPathC] display bgp routing-table
Total Number of Routes: 1
BGP Local router ID is 3.3.3.3
Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 9.1.1.0/24 200.1.3.1 0 0 20 10i
SecPath C has learned the route to the destination 9.1.1.0/24 from SecPath B.
3. Configure BGP community attribute:
# Configure a routing policy.
[SecPathA] route-policy comm_policy permit node 0
[SecPathA-route-policy] apply community no-export
[SecPathA-route-policy] quit
# Apply the routing policy.
[SecPathA] bgp 10
[SecPathA-bgp] peer 200.1.2.2 route-policy comm_policy export
[SecPathA-bgp] peer 200.1.2.2 advertise-community
# Display BGP routing table information on SecPath B.
[SecPathB] display bgp routing-table 9.1.1.0
BGP local router ID : 2.2.2.2
Local AS number : 20
Paths: 1 available, 1 best
BGP routing table entry information of 9.1.1.0/24:
From : 200.1.2.1 (1.1.1.1)
Original nexthop: 200.1.2.1
Community : No-Export
AS-path : 10
Origin : igp
Attribute value : MED 0, pref-val 0, pre 255
State : valid, external, best,
Not advertised to any peers yet
You can find the No-export community attribute in the output information. In this case, the route of
9.1.1.0/24 is not available in the routing table of SecPath C.