# Configure the capability to advertise labeled routes to IBGP peer 18.104.22.168 and to receive labeled
routes from the peer.
[PE2-bgp] peer 22.214.171.124 as-number 600
[PE2-bgp] peer 126.96.36.199 connect-interface loopback 0
[PE2-bgp] peer 188.8.131.52 label-route-capability
# Configure the maximum hop count from PE 2 to EBGP peer 184.108.40.206 as 10.
[PE2-bgp] peer 220.127.116.11 as-number 100
[PE2-bgp] peer 18.104.22.168 connect-interface loopback 0
[PE2-bgp] peer 22.214.171.124 ebgp-max-hop 10
# Configure peer 126.96.36.199 as a VPNv4 peer.
[PE2-bgp] ipv4-family vpnv4
[PE2-bgp-af-vpnv4] peer 188.8.131.52 enable
# Redistribute direct routes to the routing table of vpn1.
[PE2-bgp] ipv4-family vpn-instance vpn1
[PE2-bgp-vpn1] import-route direct
Verify the configuration:
PE 1 and PE 2 can ping each other:
[PE2] ping –vpn-instance vpn1 184.108.40.206
[PE1] ping –vpn-instance vpn1 220.127.116.11
Configuring carrier's carrier
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
CE 1 and CE 2 are the customer carrier's switches. They are connected to the provider carrier's
backbone as CE switches.
PE 3 and PE 4 are the customer carrier's PE switches. They provide MPLS L3VPN services for the end
CE 3 and CE 4 are customers of the customer carrier.
The key to carrier's carrier deployment is to configure exchange of two kinds of routes:
Exchange of the customer carrier's internal routes on the provider carrier's backbone.
Exchange of the end customers' VPN routes between PE 3 and PE 4, the PEs of the customer carrier.
In this process, an MP-IBGP peer relationship must be established between PE 3 and PE 4.
37. In this scenario: