Introduction In the last few posts we have created a primary and secondary label switched path (LSP) through our Multiprotocol Label Switching (MPLS) core with traffic switching over to the secondary in the event of a primary failure.  However, this takes time and this will not work for traffic that is considered critical and if…

Introduction In the last post (Juniper Static Label Switched Paths (Part 1)), we took our MPLS core from the posts Simple Juniper MPLS Core w/ L3VPN (Part 1) and Simple Juniper MPLS Core w/ L3VPN (Part 2) and expanded it to add Label Switched Paths in the MPLS core to perform deterministic pathing for our…

Introduction Label Switched Paths (LSP) are signaled paths in MPLS that allow you designate criteria of how a traffic from one provider edge router traverses the MPLS core to another provider edge router.  These criteria could be something as simple as explicit hops that must be taken or it can be based off of more…

Introduction If you haven’t already, please go to the first post Simple Juniper MPLS Core w/ L3VPN (Part 1) as that sets up the topology, routing, and label distribution that we need to continue setting up our customer edge devices.  For this post, we need to do a few things to successfully route traffic from…

Introduction Setting up a simple MPLS core using virtual SRX’s is simple and only limited by the hardware which you run the virtual machines (other limitations exist for MPLS using vSRX’s including not being able to run Layer 2 services such as VPLS and L2circuts).  Using these virtual machines, we can create a complete MPLS…