MPLS Device Roles in a Core Network
MPLS (Multiprotocol Label Switching) efficiently directs data between nodes, especially within ISP core networks or large geographically dispersed networks. The architecture relies on three distinct router roles:
Customer Edge (CE) Routers
- Located at the edge of the customer network, typically provided by the customer.
- Completely unaware of MPLS, only use traditional IP routing.
- Connect to Provider Edge routers, often via dynamic routing protocols like OSPF, EIGRP, BGP, or even static routing.
Provider Edge (PE) Routers (Official Name: Label Edge Router / LER)
- Sit at the edge of the MPLS infrastructure, connecting to one or more CE routers.
- Responsible for:
- Ingress: Receiving packets from CE and assigning an MPLS label.
- Egress: Removing the MPLS label and forwarding the plain IP packet to the correct customer.
- Only PE and P routers have MPLS configuration knowledge.
Provider (P) Routers (Official Name: Label Switch Router / LSR)
- Core network devices interconnecting PE routers and other P routers.
- Switch packets based solely on MPLS labels within the core, without inspecting IP headers.
MPLS Encapsulation & Label Switching Process
MPLS inserts a 4-byte header between the Layer 2 frame header and the Layer 3 IP header, making it a Layer 2.5 protocol. The header includes a 20-bit label value used for packet forwarding.
Step-by-step flow:
- CE → PE: CE sends an unlabeled IP packet. PE assigns label (e.g., label 27) and forwards it.
- PE → P Router: PE looks up its MPLS forwarding table for the destination, finds the outgoing label (e.g., 27), exit interface, and next hop IP.
- P Router → Next P Router: P router swaps the label (e.g., 27 → 28) and forwards based on the new label and next hop.
- Last P Router: Action is
Pop Label, removes the MPLS label entirely before sending to the destination PE. - PE → CE: PE receives a plain IP packet and uses standard IP routing to deliver it to the CE router.
Key Advantage: MPLS forwarding tables are smaller and more efficient to search than hundreds or thousands of IP routing table entries. For a broader explanation of how this differs from standard IP routing fundamentals, see the connected and local routes guide.
Label Distribution Protocol (LDP)
LDP is the protocol that automatically populates MPLS forwarding tables:
- Creates LDP neighbor adjacencies between all MPLS-enabled interfaces on PE and P routers.
- Each router locally generates labels for its own prefixes.
- Advertises these labels to all LDP neighbors.
- Ensures every MPLS router knows which label to use for which destination and which label to swap or pop next.
No need to manually configure label mappings, LDP handles it dynamically. For a high-level overview of how MPLS compares to other networking concepts, check out this simple guide on what MPLS is. Additionally, to understand the device roles in context with other networking hardware, see the breakdown on routers, switches, and firewalls.
Hello! This is Lazarus at telecom.Tech, where telecom and networking technologies... are simply explained! Today, we'll be simply explaining MPLS labels, MPLS device roles, and the Label Distribution Protocol. Now whether you're new to MPLS or you just want to brush up on
your understanding of the technology, this video series is just for you! You can be notified of new content within this MPLS video series by simply subscribing and enabling notifications. If you do so, you're all set, and if you find this video useful, please do click that thumbs-up button.
Now in the last video, we introduced MPLS as a technology that is used to efficiently direct data between nodes, and it's a technology that you'll most often find within the core network of an ISP, or other large geographically dispersed networks. Now this here is an example of an MPLS core
network connected to several customer sites. Now the first thing we'll look at is what we call the Customer Edge router or the CE router. These here are all CE routers. These are the routers at the edge of the customer network. They are equipment provided typically by the customer at their own
sites, and they connect to the MPLS network. Now behind each CE router, we have the rest of the customer network at that particular site. Now these routers are completely oblivious to any MPLS configuration. They don't know anything about MPLS, but they, in turn, are connected
to what we often call Provider Edge routers, or PE routers. Now Provider Edge routers are those routers that exist on the edge of the MPLS infrastructure. These are the devices that connect to the customer premises equipment which are the CE routers. So by definition, PE routers connect
to one or more CE routers. Now the term "Provider Edge" or PE is somewhat of an unofficial name, but it is used very often. The official name of these routers within the framework of MPLS is Label Edge Router or LER. Now these PEs or LERs have MPLS configuration on them. Upon ingress of a packet
into the MPLS infrastructure, they are the ones that receive the packets from the CE and assign a label to them based on the configuration that has been applied for that particular customer. Similarly upon egress of the packet from the MPLS network, the PEs are the devices that forward
a packet to the correct customer after having removed the MPLS label. Now the PE and CE devices will typically be configured as routing peers using some dynamic routing protocol. The CE router will inform the PE router of all of its own routes within the customer network using either EIGRP or
OSPF or BGP or even static routing, although that's not typically recommended, but it can be done. And finally we have what are often called the P routers, or the Provider routers. These here are the P routers within the MPLS topology. These are essentially the devices that are not on the
edge of the MPLS infrastructure, but they're part of the core network interconnecting PE devices and other P routers as well. Now like the PE device, the P designation is also somewhat unofficial, but you will see it written in this way in many MPLS diagrams and documentation. The official
name of this device in the MPLS framework is Label Switch Router or LSR. So the P routers or the LSRs are there to switch packets based on their labels within the MPLS core. Now here's an overall view with all of the routers labeled in the role that they play within MPLS.
Remember, CE routers are oblivious to MPLS configurations and the CE and PE routers simply have a regular routing protocol peering between them, while PE and P routers are the only ones that have any knowledge of MPLS infrastructure and configurations. Now let's take a look at MPLS
encapsulation in a little more detail. Here we see the data going from the CE device to the PE device where a label is added. This label is added in the MPLS header which is inserted between the Layer 2 frame header and the Layer 3 IP header. Remember MPLS is often called a Layer 2.5 protocol for
this reason, because it fits in between these two headers. Within the MPLS header, we see various fields. For now we'll focus on the label value which is a 20-bit numerical value that's assigned to the particular packet. This label is what is used throughout MPLS to direct the packet
to its appropriate destination. Now if we look at the MPLS forwarding table within the PE router, we see something like this. This is the command we would use in a Cisco IOS router to see this table. Now don't worry about the details of this output for now, just focus on this first entry here. In
order to get to this destination, we are using a label of 27 and we have our destination address here. The exit interface and the next hop IP that correspond with this particular label are found here. So we know that this is the next hop we need to send our packet to. Next when it
arrives on the P router, we see this entry here. You can see that the label is being switched to label 28. The appropriate exit interface and next hop IP are also indicated here, so that packet can be forwarded appropriately on the next P router. We see the process continues from node
to node until it gets to the final PE router that connects to the remote customer site. Now when the P router receives something that is tagged with label 28 with a destination of 4.4.4.4, it's outgoing label says "Pop Label" which means remove the label. The label is actually removed
by the last P router in the path to our intended destination. Now once this packet reaches the PE router here, it no longer has an MPLS label, and it's just normal routing that takes place. Remember PE and CE routers have a regular IP routing peering so it is only IP routing that's
used to get that data to its intended destination over that last link. So that's a brief, somewhat simplistic overview of this whole process of MPLS label switching, and the roles that the CE, PE and P routers play in the process. Now these MPLS forwarding tables are entities that are much more
efficient to be searched in order to determine in the next hop rather than searching through hundreds or thousands of entries within a routing table. Now one last question that may come to mind is this how are these labels determined and how is the MPLS forwarding table populated? That's
done using the Label Distribution Protocol or LDP. Now LDP is a protocol that automatically creates LDP neighbor adjacencies between all MPLS-enabled interfaces on PE and P routers. Adjacencies are created and then neighbors can begin to exchange information about labels. Each router locally
generates labels for its prefixes and then it'll advertises those labels to its LDP neighbors. Now that's how each MPLS router populates its MPLS forwarding table. Now the details of this actual operation of LDP with the various control plane and forwarding plane entities that are
used in this process, we'll leave for another video, but for now suffice it to say that LDP is responsible for ensuring that those forwarding tables are populated with the appropriate labels. So that's the gist of MPLS labels, device roles, and a brief introduction to the LDP protocol. So
far so good I hope! For now, I hope you found this video useful, and if you have, please click that thumbs-up button! 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!
The three main roles are Customer Edge (CE) routers, Provider Edge (PE) routers (also called Label Edge Routers/LERs), and Provider (P) routers (also called Label Switch Routers/LSRs). CE routers are customer-owned and unaware of MPLS, using only traditional IP routing. PE routers sit at the edge of the MPLS network, adding or removing labels, while P routers switch packets based solely on MPLS labels within the core.
First, the CE router sends an unlabeled IP packet to the ingress PE, which assigns an MPLS label (e.g., label 27). The PE forwards the labeled packet to a P router, which swaps the label (e.g., 27 to 28) and forwards it further. The last P router pops the label to send a plain IP packet to the egress PE, which then delivers it to the destination CE using standard IP routing.
The MPLS header is a 4-byte (32-bit) field inserted between the Layer 2 frame header and the Layer 3 IP packet header, making MPLS a Layer 2.5 protocol. It contains a 20-bit label value used by routers to forward packets without inspecting the IP header, enabling faster and more efficient switching.
LDP (Label Distribution Protocol) automatically populates MPLS forwarding tables by establishing neighbor adjacencies on all MPLS-enabled interfaces. Each router locally generates labels for its own prefixes and advertises them to all LDP neighbors, so every router knows which label to use for each destination and how to swap or pop labels accordingly. This eliminates the need for manual label configuration.
CE routers are designed to operate at the customer edge and typically run only standard IP routing protocols (OSPF, BGP, etc.). They do not participate in MPLS because their sole job is to send unlabeled IP packets to the PE. In contrast, PE and P routers are part of the MPLS infrastructure and are configured with MPLS forwarding tables and protocols like LDP.
MPLS forwarding tables are significantly smaller and more efficient to search than traditional IP routing tables, which may contain hundreds or thousands of entries. By switching packets based on a short label rather than a long IP prefix lookup, MPLS reduces processing overhead and improves packet forwarding speed, especially in large ISP core networks.
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
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.
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.
MPLS Label Operations: Pushing, Swapping, and Popping Explained
Learn the fundamentals of MPLS label operations including pushing, swapping, and popping. This video breaks down how LDP labels are added, switched, and removed as packets traverse an MPLS network, with a practical topology example showing label stack management for Layer 3 VPNs.
How BGP Is Used in the MPLS Core: Edge Routing Explained
Learn how BGP operates only on the perimeter of an MPLS network, enabling PE routers to share customer routes while core P routers stay label-switching only. This video breaks down the CE/PE/P router roles, IBGP full-mesh on edges, and why MPLS beats IP routing for scalability.
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.
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