Episode 29 – MPLS Part 2 – VPNs

In a continuation of our MPLS deep-dive series, Nick Russo, Russ White, Jordan Martin, and Eyvonne Sharp return to discuss some of the operational considerations when using MPLS VPNs.

We would like to thank Core BTS for sponsoring this episode of Network Collective. Core BTS focuses on partnering with your company to deliver technical solutions that enhance and drive your business. If you’re looking for a partner to help your technology teams take the next step, you can reach out to Core BTS by emailing them here.

We also would also like to thank Cumulus Networks for sponsoring this episode of Network Collective. Cumulus is bringing S.O.U.L. back to the network. Simple. Open. Untethered. Linux. For more information about how you can bring S.O.U.L. to your network, head on over to https://cumulusnetworks.com/networkcollectivehassoul. There you can find out how Cumulus Networks can help you build a datacenter as efficient and as flexible as the worlds largest data centers and try Cumulus technology absolutely free.

Show Notes:

1. When enterprise use the term “MPLS”, SP provided VPNS is often what they mean
2. Generally means a private WAN service, L2 or L3VPN
3. Quick packet walk (L3VPN only)
   1. CE sends IP packet to ingress PE
   2. Ingress PE performs lookup in FIB
   3. Ingress PE pushes labels in the order in which route recursion occurs
   4. Ingress PE sends to core
   5. Core routers lookup in LFIB for label swaps
   6. Egress PE receives from core
   7. Assuming PHP, egress PE consults LFIB
   8. Action is to remove all labels and send to CE
4. Overl