Configuring Mpls L3Vpn Carrier's Carrier - HP 10500 Series Configuration Manual

[PE2] bgp 600
# Enable the capability to advertise labeled routes to IBGP peer 4.4.4.9 and to receive labeled
routes from the peer.
[PE2-bgp] peer 4.4.4.9 as-number 600
[PE2-bgp] peer 4.4.4.9 connect-interface loopback 0
[PE2-bgp] ipv4-family unicast
[PE2-bgp-ipv4] peer 4.4.4.9 enable
[PE2-bgp-ipv4] peer 4.4.4.9 label-route-capability
[PE2-bgp-ipv4] quit
# Configure the maximum hop count from PE 2 to EBGP peer 2.2.2.9 as 10.
[PE2-bgp] peer 2.2.2.9 as-number 100
[PE2-bgp] peer 2.2.2.9 connect-interface loopback 0
[PE2-bgp] peer 2.2.2.9 ebgp-max-hop 10
# Configure peer 2.2.2.9 as a VPNv4 peer.
[PE2-bgp] ipv4-family vpnv4
[PE2-bgp-vpnv4] peer 2.2.2.9 enable
[PE2-bgp-vpnv4] quit
# Redistribute direct routes to the routing table of vpn1.
[PE2-bgp] ip vpn-instance vpn1
[PE2-bgp-vpn1] ipv4-family unicast
[PE2-bgp-ipv4-vpn1] import-route direct
[PE2-bgp-ipv4-vpn1] quit
[PE2-bgp-vpn1] quit
[PE2-bgp] quit
Verify the configuration:
5.
# After the configurations, PE 1 and PE 2 can ping each other. Take PE 1 as an example:
[PE1] ping -a 30.0.0.1 -vpn-instance vpn1 20.0.0.1
PING 20.0.0.1 (20.0.0.1) from 30.0.0.1: 56 data bytes
56 bytes from 20.0.0.1: icmp_seq=0 ttl=255 time=0.000 ms
56 bytes from 20.0.0.1: icmp_seq=1 ttl=255 time=0.000 ms
56 bytes from 20.0.0.1: icmp_seq=2 ttl=255 time=0.000 ms
56 bytes from 20.0.0.1: icmp_seq=3 ttl=255 time=0.000 ms
56 bytes from 20.0.0.1: icmp_seq=4 ttl=255 time=0.000 ms
--- 20.0.0.1 ping statistics ---
5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.000/0.000/0.000/0.000 ms

Configuring MPLS L3VPN carrier's carrier

Network requirements
Configure carrier's carrier for the scenario shown in
PE 1 and PE 2 are the provider carrier's PE switches. They provide VPN services for the customer
•
carrier.
• CE 1 and CE 2 are the customer carrier's switches. They are connected to the provider carrier's
backbone as CE switches.
Figure 48. In this scenario:
149