HP HSR6800 Configuration Manual page 316

[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
Execute 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 the 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 AS
3.3.3.9 100
6. Verify the configuration:
# Execute 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
127.0.0.0/8
127.0.0.1/32
[PE1] display ip routing-table vpn-instance vpn2
Peers in established state : 1
MsgRcvd MsgSent OutQ
2 6
Routes : 7
Proto Pre Cost
BGP 255 0
BGP 255 0
Direct 0 0
Direct 0 0
BGP 255 0
Direct 0 0
Direct 0 0
308
PrefRcv Up/Down
0 0 00:00:12 Established
NextHop
10.1.1.1
3.3.3.9
10.1.1.2
127.0.0.1
3.3.3.9
127.0.0.1
127.0.0.1
State
Interface
GE2/1/1
NULL0
GE2/1/1
InLoop0
NULL0
InLoop0
InLoop0