![HP 12500 Series Configuration Manual Download Page 270](http://html.mh-extra.com/html/hp/12500-series/12500-series_configuration-manual_162786270.webp)
262
NOTE:
The configurations for the other three CEs (CE 2 through CE 4) are similar to those for CE 1. (Details not
shown)
# On PE 1, configure the CE 1 and CE 2 as the iBGP peers, and configure PE 1 as the route
reflector.
[PE1] bgp 100
[PE1-bgp] ipv4-family vpn-instance vpn1
[PE1-bgp-vpn1] peer 10.1.1.1 as-number 100
[PE1-bgp-vpn1] peer 10.1.1.1 reflect-client
[PE1-bgp-vpn1] import-route direct
[PE1-bgp-vpn1] quit
[PE1-bgp] ipv4-family vpn-instance vpn2
[PE1-bgp-vpn2] peer 10.2.1.1 as-number 100
[PE1-bgp-vpn2] peer 10.2.1.1 reflect-client
[PE1-bgp-vpn2] import-route direct
[PE1-bgp-vpn2] quit
[PE1-bgp] quit
NOTE:
The configurations for PE 2 are similar to those for PE 1. (Details not shown)
Issue the
display bgp vpnv4 vpn-instance peer
command on the PEs. The output shows that BGP
peer relationships have been established between the PEs and CEs, and have reached the
Established state. Take the BGP peer relationship between PE 1 and CE 1 as an example:
[PE1] display bgp vpnv4 vpn-instance vpn1 peer
BGP local router ID : 1.1.1.9
Local AS number : 100
Total number of peers : 1 Peers in established state : 1
Peer AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
10.1.1.1 100 26 21 0 2 00:11:08 Established
5.
Configure an MP-iBGP peer relationship between PEs.
# On PE 1, configure PE 2 as the MP-iBGP peer, and configure a routing policy for the routes
received from PE 2, changing the next hop address of the routes as the loopback interface address
of PE 2.
[PE1] route-policy pe-ibgp permit node 0
[PE1-route-policy] apply ip-address next-hop 3.3.3.9
[PE1-route-policy] quit
[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 route-policy pe-ibgp import
[PE1-bgp-af-vpnv4] peer 3.3.3.9 enable
[PE1-bgp-af-vpnv4] quit