H3C SR8800 10G Mpls Configuration Manual page 297

Configure an MP-IBGP peer relationship between PEs
5.
# Configure PE 1.
[PE1] bgp 100
[PE1-bgp] peer 3.3.3.9 as-number 100
[PE1-bgp] peer 3.3.3.9 connect-interface loopback 0
[PE1-bgp] ipv4-family vpnv4
[PE1-bgp-af-vpnv4] peer 3.3.3.9 enable
[PE1-bgp-af-vpnv4] quit
[PE1-bgp] quit
# Configure PE 2.
[PE2] bgp 100
[PE2-bgp] peer 1.1.1.9 as-number 100
[PE2-bgp] peer 1.1.1.9 connect-interface loopback 0
[PE2-bgp] ipv4-family vpnv4
[PE2-bgp-af-vpnv4] peer 1.1.1.9 enable
[PE2-bgp-af-vpnv4] quit
[PE2-bgp] quit
After completing the configuration, issue the display bgp peer command or the display bgp vpnv4
all peer command on the PEs. The output shows that BGP peer relationship has been established
between the PEs, and has reached the Established state.
[PE1] display bgp peer
BGP local router ID : 1.1.1.9
Local AS number : 100
Total number of peers : 1
Peer AS
3.3.3.9 100
Verify your configurations
6.
Issue the display ip routing-table vpn-instance command on the PEs. The output shows the routes
to the CEs. The following takes PE 1 as an example:
[PE1] display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 5
Destination/Mask
10.1.1.0/24
10.1.1.2/32
10.3.1.0/24
127.0.0.0/8
127.0.0.1/32
[PE1] display ip routing-table vpn-instance vpn2
Destinations : 5
Destination/Mask
10.2.1.0/24
10.2.1.2/32
10.4.1.0/24
127.0.0.0/8
127.0.0.1/32
Peers in established state : 1
MsgRcvd MsgSent OutQ
2 6
Routes : 5
Proto Pre Cost
Direct 0 0
Direct 0 0
BGP 255 0
Direct 0 0
Direct 0 0
Routes : 5
Proto Pre Cost
Direct 0 0
Direct 0 0
BGP 255 0
Direct 0 0
Direct 0 0
286
PrefRcv Up/Down
0 0 00:00:12 Established
NextHop
10.1.1.2
127.0.0.1
3.3.3.9
127.0.0.1
127.0.0.1
NextHop
10.2.1.2
127.0.0.1
3.3.3.9
127.0.0.1
127.0.0.1
State
Interface
GE4/1/1
InLoop0
NULL0
InLoop0
InLoop0
Interface
GE4/1/2
InLoop0
NULL0
InLoop0
InLoop0