MPLS Network Roles: CE, PE, and P Routers
- CE (Customer Edge): Located at each customer site, these routers connect to the provider network.
- PE (Provider Edge): Found at the perimeter of the MPLS network; they participate in BGP and exchange customer routes.
- P (Provider): Form the MPLS core; they perform label switching but do not run BGP or know customer IP prefixes.
Three Essential Protocols for MPLS
1. Routing Between CE and PE
Any IGP (OSPF, EIGRP) or BGP can be used so the CE advertises its internal networks to the PE.
2. Underlay IGP for ISP Infrastructure
OSPF or IS-IS runs among all PE and P routers so they can find each other. This underlay does not carry customer routes.
3. BGP Between PE Routers Only
- BGP is deployed only on the edge (PE routers), not in the core (P routers).
- Since the ISP is a single AS (e.g., AS 100), full-mesh IBGP peerings must exist among all PEs.
- P routers simply relay BGP messages via the underlay IGP but never process BGP themselves.
Why MPLS Is More Efficient Than IP Routing
Without MPLS, every router (including core P routers) would need to know all customer routes, potentially hundreds of thousands of prefixes.
With MPLS:
- Only PE routers maintain customer routes in BGP.
- Core P routers use labels to forward packets, ignoring source/destination IPs.
- This offloads the routing table burden from the core, enabling massive scalability.
How BGP Enables Advanced MPLS Features
Beyond simple route exchange, BGP is essential for Layer 3 VPNs (L3VPNs) in MPLS networks. These VPNs isolate customer traffic from one another while still using the shared MPLS infrastructure, a critical requirement for production deployments. This topic is covered in a follow-up video.
Key Takeaway
In an MPLS core, BGP runs strictly at the edge (PE routers) to exchange customer prefixes via IBGP. Core P routers remain label-switching engines, oblivious to customer IP networks. This design is what gives MPLS its performance and scalability advantages over pure IP routing.
Additional Resources
To deepen your understanding of how MPLS works at the packet level, check out MPLS Label Operations: Pushing, Swapping, and Popping Explained and learn how the Label Distribution Protocol (LDP) automates label assignment across the core.
hello this is Lazarus at Telecom Tech where Telecom and networking Technologies are simply explained today
we'll be simply explaining how bgp is typically employed in the MLS core now don't forget to subscribe to enable
notifications and to like this video If you like this video and if you have questions or feedback please feel free
to write them in the comments below I'm always happy to read them and to respond now in a typical MLS ology like this one
we have the CE rter the PE rter and the pters CE stands for customer Edge and these routers are located at the edge of
each customer Network the C routers connect to the provider Edge routers or the PE rter and those rter are found all
along the perimeter or the edge of the MLS Network finally we have the provider routers or the P rooters which
constitute the very core of the MLS Network now to make all of this work in the way that we
demonstrated in previous videos we need to deploy various Technologies first we need a rooting
protocol between the CE and the PE this way the CE can advertise the networks found on the customer Network to the PE
router here we can use any rooting protocol we choose including ospf eigrp or even
bgp secondly we need to establish an underlay rooting protocol within the ISP infrastructure this is so that all of
the p and PE routers can find each other and communicate with each other remember this rooting protocol is not here to
advertise customer networks it's there to establish the control plane on the ISP infrastructure on top of which MLS
will be able to function typically for large scale ISP networks it's either ospf or Isis that are used
for this underlay rooting protocol third we need to deploy some protocol that will allow the PE routs to
share their customer networks with each other so that they know what labels to push onto the packets as they send them
through the MLS core and this is where bgp comes in now for our purposes we're going to
assume that the whole of the ISP network is contained within a single bgp autonomous system or as we'll use as
number 100 to Define it this as contains all of the PE and pters that belong to this MLS
topology now remember we already have an igp running which allows all of the PE and pters to reach each other since
we're configuring bgp within a single as we're going to be creating ibgp peerings now where are we going to configure ibgp
specifically we'll need to create a set of full mesh ibgp peerings between all of the PE roters however the pters will
not be participating in bgp at all now I know what some of you are thinking isn't it a prerequisite to have a full mesh
ibgp peering within an AS how can we leave the pters out of it well yes but that prerequisite is applied only to bgp
routers the pters are not bgp routers you're allowed to have a router within your topology that's not running bgp and
that is not participating in any bgp peerings it may even be relaying bgp messages between ibgp peers because of
the underlying igp but it still won't be violating the ibgp full mesh peering rule so only the PE rter participate in
bgp by becoming ibgp peers with all other PE routers in other words only the outer edge of the MLS Network
participates in ibgp not the inner core of pters now the reason for this is that
bgp in such a scenario is used to allow PE roters to share the customer networks with each other
so pe1 here will advertise to all other PE rter the IP addresses behind the C1 router here so pe2 here populates its
bgp table with this network but remember PE roters are also running ldp and are becoming ldp neighbors with pters so
this PE rter learns which label it should push on a packet to get those packets to the proper destination
now the realization that bgp runs on the perimeter of the MLS network will help us to further understand why MLS and
label switching is more efficient than IP rooting if we didn't use MLS all of these routs in the ISP infrastructure
must learn about all of the roots that exist in all of the customer networks that means that this pter here must have
a rooting table that includes all of the networks of all of these potential hundreds of customer routers but with
our MLS setup using bgp the pters are completely oblivious to all customer networks isn't that a huge load off so
when ce1 forwards a packet to pe1 that is destined for this customer Network here how does it get to pe2 and then to
C2 well from pe1 all through the MLS core only label switching takes place remember label switching that efficient
method of directing traffic the pters only use labels and nothing else they don't care about the source and
destination IPS in the packet they simply use the labels that the PE routers push onto the packets as they're
sent through the topology now in this video we just talked about bgp and its ability to
exchange the IP prefixes of the customer networks between the PE router however bgp is able to provide much more for MLS
in particular it's ideal to allow the use of what are known as layer 3 vpns within an MLs topology until now we've
been allowing customers to communicate with each other over the MLS infrastructure but we haven't isolated
those customers from each other and as you can understand that is definitely a prerequisite in order to put this into
any production Network layer 3 vpns in MLS allow this separation of customer networks on the MLS topology and it's
bgp that makes that possible we'll talk about that in a future video now i' would like to mention that the title of
this video is using bgp in the MLS core but strictly speaking there is no bgp in the core pters it's only running along
the perimeter between the PE routers but it was difficult for me to find a title that was concise and descriptive enough
enough to convey that meaning so I just thought I'd stick with that title in any case that covers the use of bgp on the
edge of the MLS core Network I hope you found this video useful and if you have please click that Thumbs Up Button if
you have any questions feel free to leave a comment below and please subscribe to get updates to newly
published videos I'm Lazarus at Telecom Tech I hope this has been helpful for you and I'd like to thank you for
watching
Three protocols are needed: 1) A routing protocol (IGP or BGP) between CE and PE routers for customers to advertise their networks, 2) An IGP (like OSPF or IS-IS) as an underlay among all PE and P routers for internal communication, and 3) BGP (specifically iBGP) exclusively between PE routers to exchange customer routes across the network.
CE (Customer Edge) routers sit at each customer site and connect to the provider network. PE (Provider Edge) routers are at the perimeter of the MPLS network; they run BGP and exchange customer routes. P (Provider) routers form the core of the MPLS network and perform label switching, but they do not run BGP or know about customer IP prefixes.
BGP is only run on PE routers to maintain the scalability and performance of the MPLS core. P routers simply relay BGP messages via the underlay IGP but never process the BGP protocol itself. This design ensures that core routers only handle label-based forwarding, avoiding the need to manage potentially hundreds of thousands of customer IP routes.
MPLS offloads the routing table burden from core routers. In traditional IP routing, every router would need to know all customer routes. With MPLS, only PE routers maintain customer routes via BGP, while core P routers use labels to forward packets without examining source or destination IP addresses. This design allows the MPLS core to scale efficiently without being overloaded with routing information.
BGP is crucial for enabling Layer 3 VPNs (L3VPNs) in MPLS networks. These VPNs allow different customers to share the same MPLS infrastructure while keeping their traffic isolated from one another. This capability is a core requirement for production deployments where service providers must offer secure, scalable, and separated connectivity to multiple clients.
Core P routers relay BGP messages between PE routers using the underlay IGP (such as OSPF or IS-IS). They forward these packets based on label-switching or IP routing in the underlay, but they never inspect the BGP payload or maintain BGP state. This allows BGP communication to traverse the core without adding processing overhead to P routers.
Keep this summary
Save it to LunaNotes and it becomes a real note in your library — editable, searchable, and ready to turn into flashcards or a diagram. Free to start.
Save to LunaNotesOr summarise for another video.
32K+ people have turned 65K+ videos into notes
“Very useful tool. I'm using it for the last couple weeks and I'm loving it so far. Makes learning on YouTube a great experience.”
This summary and transcript were automatically generated using AI with the Free YouTube transcript summary tool by LunaNotes.
Related summaries
Basic MPLS Configuration on Cisco IOS: Step-by-Step Guide
Learn how to configure MPLS on Cisco IOS routers in a typical ISP network. This video walks through the full process: eBGP peerings with customers, OSPF underlay, iBGP full mesh among PEs, and finally enabling MPLS with LDP, followed by verification using LFIB and PHP.
MPLS Labels, Device Roles & LDP Protocol Explained Simply
This video from telecom.Tech breaks down MPLS labels, the roles of CE, PE, and P routers, and how the Label Distribution Protocol (LDP) auto-populates forwarding tables. A clear, beginner-friendly overview of MPLS core network operations and packet switching mechanics.
MPLS VPNs: RD, RT & VPNv4 Routes Explained Simply
This video explains how MPLS VPNs use Route Distinguishers (RDs) and Route Targets (RTs) to differentiate customer networks with overlapping IP addresses. It covers VPNv4 route advertisement, MP-BGP updates, and VPN labels for Layer 3 VPN isolation.
MPLS Explained: What Is Multi-Protocol Label Switching? (Simple Guide)
MPLS is a high-performance network protocol used in ISP core networks to efficiently direct data between nodes using labels instead of IP lookups. It sits between Layer 2 and Layer 3, encapsulates multiple protocols, and is ideal for interconnecting customer sites securely. This video provides a simple introduction to MPLS, comparing it to traditional IP routing and explaining its key benefits.
LDP in MPLS: Label Distribution Protocol Simply Explained
Learn how Label Distribution Protocol (LDP) works in MPLS networks. This comprehensive guide explains label exchange, LIB and LFIB constructs, and penultimate label popping from first principles.
Most viewed summaries
A Comprehensive Guide to Using Stable Diffusion Forge UI
Explore the Stable Diffusion Forge UI, customizable settings, models, and more to enhance your image generation experience.
Kolonyalismo at Imperyalismo: Ang Kasaysayan ng Pagsakop sa Pilipinas
Tuklasin ang kasaysayan ng kolonyalismo at imperyalismo sa Pilipinas sa pamamagitan ni Ferdinand Magellan.
Mastering Inpainting with Stable Diffusion: Fix Mistakes and Enhance Your Images
Learn to fix mistakes and enhance images with Stable Diffusion's inpainting features effectively.
Pamamaraan at Patakarang Kolonyal ng mga Espanyol sa Pilipinas
Tuklasin ang mga pamamaraan at patakaran ng mga Espanyol sa Pilipinas, at ang epekto nito sa mga Pilipino.
How to Install and Configure Forge: A New Stable Diffusion Web UI
Learn to install and configure the new Forge web UI for Stable Diffusion, with tips on models and settings.
Found this summary useful?
Take it with you. One click puts it in your own LunaNotes library.
Save to LunaNotes