HP 10500 Series Configuration Manual page 227

[PE3-bgp-vpn1] peer 2001:1::1 as-number 65410
[PE3-bgp-vpn1] ipv6-family unicast
[PE3-bgp-ipv6-vpn1] peer 2001:1::1 enable
[PE3-bgp-ipv6-vpn1] import-route direct
[PE3-bgp-ipv6-vpn1] quit
[PE3-bgp-vpn1] quit
[PE3-bgp] quit
# Configure PE 4 and CE 4 in the same way that PE 3 and CE 3 are configured. (Details not
shown.)
Establish an MP-IBGP peer relationship between PEs of the customer carrier to exchange the VPN
5.
routes of the customer carrier's customers:
# Configure PE 3.
[PE3] bgp 100
[PE3-bgp] peer 6.6.6.9 as-number 100
[PE3-bgp] peer 6.6.6.9 connect-interface loopback 0
[PE3-bgp] ipv6-family vpnv6
[PE3-bgp-vpnv6] peer 6.6.6.9 enable
[PE3-bgp-vpnv6] quit
[PE3-bgp] quit
# Configure PE 3 in the same way that PE 3 is configured. (Details not shown.)
Verify the configuration:
6.
# Execute the display ip routing-table command on PE 1 and PE 2. The output shows that only
routes of the provider carrier network are present in the public network routing table of PE 1 and
PE 2. Take PE 1 as an example:
[PE1] display ip routing-table
Routing Tables: Public
Destinations : 7
Destination/Mask
3.3.3.9/32
4.4.4.9/32
30.1.1.0/24
30.1.1.1/32
30.1.1.2/32
127.0.0.0/8
127.0.0.1/32
# Execute the display ip routing-table vpn-instance command on PE 1 and PE 2. The output shows
that the internal routes of the customer carrier network are present in the VPN routing tables. Take
PE 1 as an example:
[PE1] display ip routing-table vpn-instance vpn1
Routing Tables: vpn1
Destinations : 11
Destination/Mask
1.1.1.9/32
2.2.2.9/32
5.5.5.9/32
Routes : 7
Proto Pre Cost
Direct 0 0
ISIS 15 10
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Direct 0 0
Routes : 11
Proto Pre Cost
ISIS 15 20
ISIS 15 10
BGP 255 0
221
NextHop Interface
127.0.0.1 InLoop0
30.1.1.2 Vlan12
30.1.1.1 Vlan12
127.0.0.1 InLoop0
30.1.1.2 Vlan12
127.0.0.1 InLoop0
127.0.0.1 InLoop0
NextHop Interface
11.1.1.1 Vlan11
11.1.1.1 Vlan11
4.4.4.9 NULL0