The CTO of a company requires the support of a network consultant to deliver an MPLS solution without resigning to a certain degree of redundancy and scalability. Which solution effectively scales to hundreds or thousands of sites?

A hierarchical L3VPN topology using Network-facing Provider Edge (N-PE) routers and User-facing Provider Edge (U-PE) routers is a design pattern specifically created for massive scalability. This model, also known as Hierarchical VPNs (HVPN) or Carrier's Carrier, avoids the quadratic scaling problem of a full-mesh design where every PE must peer with every other PE. Instead, U-PEs connect to regional N-PEs, which form a scalable core. This hierarchy drastically reduces the number of BGP sessions and Label Switched Paths (LSPs) that any single router must maintain, allowing the network to efficiently support hundreds or thousands of sites while preserving redundancy.

A. L2VPNs face significant scalability challenges with a large number of sites due to MAC address table sizes and the overhead of replicating broadcast, unknown unicast, and multicast (BUM) traffic.
B. A full mesh of direct LSPs and BGP sessions between all PEs is fundamentally unscalable. The number of sessions grows quadratically (O(n²)), overwhelming router resources in large networks.
C. Frame format encapsulation and interworking are L2VPN features for protocol interoperability. They do not address the core control plane and data plane scalability issues inherent in large L2VPNs.

1. Cisco Official Documentation: MPLS Configuration Guide, Cisco IOS XE Release 17.x, "MPLS VPN—Carrier-Supporting-Carrier for IPv4" section. This document states, "The MPLS VPN carrier-supporting-carrier feature allows an MPLS VPN service provider to scale its services by using its backbone to provide VPN services to its customers." It details the N-PE and U-PE architecture.

2. Cisco Press Publication: De Ghein, L. (2006). MPLS Fundamentals. Cisco Press. In Chapter 10, "Advanced MPLS VPN Topics," the "Carrier's Carrier VPNs" section explains that this hierarchical model is a solution to the scalability problem where a backbone carrier provides VPN services to a customer carrier, effectively creating the N-PE/U-PE structure.

3. IETF Standard: Rosen, E., & Rekhter, Y. (February 2006). BGP/MPLS IP Virtual Private Networks (VPNs). RFC 4364. Section 10, "Multi-AS Backbones," describes the architectural options (A, B, and C) for interconnecting autonomous systems, which form the basis for hierarchical VPN models like Carrier's Carrier to achieve large-scale deployments.