HP 10500 SERIES Configuration Manual page 294

[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
[PE1-bgp] quit
# On PE 2, configure PE 1 as the MP-IBGP peer, and configure a routing policy for the routes
received from PE 1, changing the next hop address of the routes as the loopback interface address
of PE 1.
[PE2] route-policy pe-ibgp permit node 0
[PE2-route-policy] apply ip-address next-hop 1.1.1.9
[PE2-route-policy] quit
[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 route-policy pe-ibgp import
[PE2-bgp-af-vpnv4] peer 1.1.1.9 enable
[PE2-bgp-af-vpnv4] quit
[PE2-bgp] quit
# Issue the display bgp peer command or the display bgp vpnv4 all peer command on the PEs. The
output shows that a BGP peer relationship has been established between the PEs, and has reached
Established state. Take PE 1 as an example:
[PE1] display bgp peer
BGP local router ID : 1.1.1.9
Local AS number : 100
Total number of peers : 1
Peer
3.3.3.9
Verify the configuration:
6.
Issue the display ip routing-table vpn-instance command on the PEs. The output shows the routes
to the peer CEs. Take PE 1 as an example:
[PE1] display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 7
Destination/Mask
4.4.4.9/32
6.6.6.9/32
10.1.1.0/24
10.1.1.2/32
10.3.1.0/24
AS MsgRcvd
100 4
Routes : 7
Proto Pre Cost
BGP 255 0
BGP 255 0
Direct 0 0
Direct 0 0
BGP 255 0
286
Peers in established state : 1
MsgSent OutQ PrefRcv Up/Down
8 0
NextHop
10.1.1.1
3.3.3.9
10.1.1.2
127.0.0.1
3.3.3.9
State
0 00:00:09 Established
Interface
Vlan11
NULL0
Vlan11
InLoop0
NULL0