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

478
Origin : i - IGP, e - EGP, ? - incomplete
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 8.1.1.0/24 3.1.1.2 0 0 65008i
# Display the BGP routing table 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
i 8.1.1.0/24 3.1.1.2 0 100 0 65008i
NOTE:
From the outputs, you can find SecPath A has learned no route to AS65009, and SecPath C has learned
network 8.1.1.0 but the next hop 3.1.1.2 is unreachable, and thus the route is invalid.
4. Redistribute direct routes:
Configure BGP to redistribute direct routes on SecPath B, so that SecPath A can obtain the route to
9.1.1.0/24 and SecPath C can obtain the route to 3.1.1.0/24.
# Configure SecPath B.
[SecPathB] bgp 65009
[SecPathB-bgp] import-route direct
# Display the BGP routing table on SecPath A.
[SecPathA] display bgp routing-table
Total Number of Routes: 4
BGP Local router ID is 1.1.1.1
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
*> 2.2.2.2/32 3.1.1.1 0 0 65009?
* 3.1.1.0/24 3.1.1.1 0 0 65009?
*> 8.1.1.0/24 0.0.0.0 0 0 i
*> 9.1.1.0/24 3.1.1.1 0 0 65009?
Two routes 2.2.2.2/32 and 9.1.1.0/24 have been added in SecPath A's routing table.
# Display the BGP routing table on SecPath C.