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

477
{
To enable SecPath C to access the network 8.1.1.0/24 connected directly to SecPath A, inject
network 8.1.1.0/24 to the BGP routing table of SecPath A.
# Configure SecPath A.
<SecPathA> system-view
[SecPathA] bgp 65008
[SecPathA-bgp] router-id 1.1.1.1
[SecPathA-bgp] peer 3.1.1.1 as-number 65009
[SecPathA-bgp] network 8.1.1.1 24
[SecPathA-bgp] quit
# Configure SecPath B.
[SecPathB] bgp 65009
[SecPathB-bgp] peer 3.1.1.2 as-number 65008
[SecPathB-bgp] quit
# Display BGP peer information on SecPath B.
[SecPathB] display bgp peer
BGP local router ID : 2.2.2.2
Local AS number : 65009
Total number of peers : 2 Peers in established state : 2
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
3.3.3.3 65009 12 10 0 3 00:09:16 Established
3.1.1.2 65008 3 3 0 1 00:00:08 Established
The output shows that SecPath B has established an IBGP peer relationship with SecPath C and an
EBGP peer relationship with SecPath A.
# Display the BGP routing table on SecPath A.
[SecPathA] display bgp routing-table
Total Number of Routes: 1
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
*> 8.1.1.0/24 0.0.0.0 0 0 i
# Display the BGP routing table on SecPath B.
[SecPathB] display bgp routing-table
Total Number of Routes: 1
BGP Local router ID is 2.2.2.2
Status codes: * - valid, ^ - VPNv4 best, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale