H3C Technologies H3C S10500 Series Switches - Manual (Page 244)

233
of the Level 2 carrier. Routes of the customer networks connected to a Level 2 carrier are exchanged
through the BGP session established between the routers of the Level 2 carrier. This can greatly reduce
the number of routes maintained by the Level 1 carrier network.
Implementation of carrier’s carrier
Compared with the common MPLS L3VPN, the carrier’s carrier is different because of the way in which
a CE of a Level 1 carrier, that is, a Level 2 carrier, accesses a PE of the Level 1 carrier:
• If the PE and the CE are in a same AS, you must configure IGP and LDP between them.
• If the PE and the CE are not in the same AS, you must configure MP-eBGP to label the routes
exchanged between them.
In either case, you must enable MPLS on the CE of the Level 1 carrier. Moreover, the CE holds the VPN
routes of the Level 2 carrier, but it does not advertise the routes to the PE of the Level 1 carrier; it only
exchanges the routes with other PEs of the Level 2 carrier.
A Level 2 carrier can be an ordinary ISP or an MPLS L3VPN service provider.
When the Level 2 carrier is an ordinary ISP, its PEs run IGP to communicate with the CEs, rather than
MPLS. As shown in Figure 63 , PE 3 and PE 4 exchange VPN routes of the Level 2 carrier through iBGP
sessions.
Figure 63 Scenario where the Level 2 carrier is an ISP
When the Level 2 carrier is an MPLS L3VPN service provider, its PEs must run IGP and LDP to
communicate with CEs. As shown in Figure 64 , PE 3 and PE 4 exchange VPN routes of the Level 2 carrier
through MP-iBGP sessions.