H3C Technologies H3C S7500E Series Switches - Manual (Page 299)

6-74
[PE2-bgp-af-vpnv4] peer 2.2.2.9 enable
[PE2-bgp-af-vpnv4] quit
# Specify to inject 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
After you complete the above configurations, PE 1 and PE 2 should be able to ping each other:
[PE2] ping –vpn-instance vpn1 30.0.0.1
[PE1] ping –vpn-instance vpn1 20.0.0.1
Example for Configuring Carrier’s Carrier
Network requirements
The Level 2 carrier provides MPLS L3VPN services to customers.
As shown in Figure 6-23 ,
z
PE 1 and PE 2 are PEs of the Level 1 carrier backbone.
z
CE 1 and CE 2 are devices of the Level 2 carrier and work as CE to access the Level 1 carrier
backbone.
z
PE 3 and PE 4 are devices of the Level 2 carrier and work as PE to provide access service for the
customers of the Level 2 carrier.
z
CE 3 and CE 4 are customers of the Level 2 carrier.
The key of the carrier’s carrier configuration lies in the exchange process of two kinds of routes:
z
The exchange of the internal Level 2 carrier VPN routes on the Level 1 carrier backbone. In this
process, the Level 2 carrier accesses the Level 1 carrier backbone as CE.
z
The exchange of customer VPN routes of the Level 2 carrier between PEs of the Level 2 carrier.
In this process, MP-IBGP peer relationship must be established between the PEs of the Level 2
carrier (that is, between PE 3 and PE 4).