F3215-HP Load Balancing Module Network Management Configuration Guide-6PW101

286
{ The EBGP peers, Router A and LB (usually belong to different ISPs), 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 Router B to access the network 8.1.1.0/24 connected directly to Router A, inject
n e t w ork 8 .1.1.0/24 t o t h e B G P r ou t i n g t a b l e o f R ou t e r A .
# Configure Router A.
<RouterA> system-view
[RouterA] bgp 65008
[RouterA-bgp] router-id 1.1.1.1
[RouterA-bgp] peer 3.1.1.1 as-number 65009
[RouterA-bgp] network 8.1.1.1 24
[RouterA-bgp] quit
# Configure LB.
[LB] bgp 65009
[LB-bgp] peer 3.1.1.2 as-number 65008
[LB-bgp] quit
# Display BGP peer information on LB.
[LB] 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 LB has established an IBGP peer relationship with Router B and an EBGP
peer relationship with Router A.
# Display the BGP routing table on Router A.
[RouterA] 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 LB.
[LB] display bgp routing-table
Total Number of Routes: 1