H3C Technologies H3C S12500-X Series Switches - Manual (Page 179)

168
<CE2> system-view
[CE2] interface vlan-interface 12
[CE2-Vlan-interface12] ip address 20.0.0.2 24
[CE2-Vlan-interface12] quit
# Configure 20.0.0.1 as an EBGP peer, and redistribute direct routes.
[CE2] bgp 65002
[CE2-bgp] peer 20.0.0.1 as-number 600
[CE2-bgp] address-family ipv4 unicast
[CE2-bgp-ipv4] peer 20.0.0.1 enable
[CE2-bgp-ipv4] import-route direct
[CE2-bgp-ipv4] quit
[CE2-bgp] quit
Verifying the configuration
# After the configurations, execute the display ip routing-table command on CE 1 and CE 2 to display
routes to each other. CE 1 and CE 2 can ping each other.
Configuring MPLS L3VPN carrier's carrier
Network requirements
Configure carrier's carrier for the scenario shown in Figure 52 . In this scenario:
• 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.
• PE 3 and PE 4 are the customer carrier's PE switches. 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.