H3C Technologies H3C S10500 Series Switches - Manual (Page 250)

235
BGP local router ID : 3.3.3.3
Local AS number : 65009
Total number of peers : 1 Peers in established state : 1
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
2.2.2.2 65009 2 2 0 0 00:00:13 Established
The output information shows that Switch C has established an iBGP peer relationship with Switch B.
3. Configure eBGP.
• The eBGP peers, Switch A and Switch B (usually belong to different carriers), are located in different
ASs. Typically, their loopback interfaces are not reachable to each other, so directly connected
interfaces are used for establishing BGP sessions.
• To enable Switch C to access the network 8.1.1.0/24 connected directly to Switch A, inject network
8.1.1.0/24 to the BGP routing table of Switch A.
# Configure Switch A.
<SwitchA> system-view
[SwitchA] bgp 65008
[SwitchA-bgp] router-id 1.1.1.1
[SwitchA-bgp] peer 3.1.1.1 as-number 65009
[SwitchA-bgp] network 8.1.1.1 24
[SwitchA-bgp] quit
# Configure Switch B.
[SwitchB] bgp 65009
[SwitchB-bgp] peer 3.1.1.2 as-number 65008
[SwitchB-bgp] quit
# Display BGP peer information on Switch B.
[SwitchB] 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 4 4 0 0 00:02:49 Established
3.1.1.2 65008 2 2 0 0 00:00:05 Established
The output shows that Switch B has established an iBGP peer relationship with Switch C and an eBGP
peer relationship with Switch A.
# Display the BGP routing table on Switch A.
[SwitchA] 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,