337
# Redistribute direct routes to the routing table of vpn1.
[PE2-bgp] ipv4-family vpn-instance vpn1
[PE2-bgp-vpn1] import-route direct
[PE2-bgp-vpn1] quit
[PE2-bgp] quit
5.
Verify the configuration:
After the configurations, PE 1 and PE 2 can ping each other:
[PE2] ping –vpn-instance vpn1 30.0.0.1
[PE1] ping –vpn-instance vpn1 20.0.0.1
Configuring carrier's carrier
Network requirements
Configure carrier's carrier for the scenario shown in
. In this scenario:
•
PE 1 and PE 2 are the provider carrier's PE routers. They provide VPN services for the
customer carrier.
•
CE 1 and CE 2 are the customer carrier's routers. They are connected to the provider carrier's
backbone as CE routers.
•
PE 3 and PE 4 are the customer carrier's PE routers. They provide MPLS L3VPN services for
the end customers.
•
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.
Figure 93 Network diagram
Device
Interface
IP address
Device
Interface
IP address
CE 3
GE2/1/1
100.1.1.1/24
CE 4
GE2/1/1
120.1.1.1/24
PE 3
Loop0
1.1.1.9/32
PE 4
Loop0
6.6.6.9/32
GE2/1/1
100.1.1.2/24
GE2/1/1
120.1.1.2/24