During the 2016 MPLS WC conference in Paris, FR this past week we gave a demonstration of the Northstar TE ControllerTM learning, controlling and creating SPRING based Traffic Engineering LSPs across a Juniper Network. The Network consisted of seven Juniper vMX routers running ISIS and BGP.
The demonstration highlighted several pieces of technology and a number of Northstar’s existing applications such as:
Dynamic learning of SPRING Adjacency and Node SIDs via ISIS
Display of per Link Adjacency SIDs
Creation of SPRING TE LSPs via the Path Computation Protocol(PCEP)
Creation of diverse pairs of SPRING TE LSPs from different ingress routers using SRLG exclusion via the PCEP
It can be challenging to obtain optimal bin packing without significant network disruption and/or bandwidth over-booking when RSVP-TE LSPs are reserving bandwidth in a network in a PCE controlled network. A complex and involved process of make-before-break(MBB) LSP creation and LSP preemption is needed to optimize an existing network. Using Northstar's Zero-Bandwidth mode enables a PCE to route LSPs without considering the reservation style of the network or that a LSP set-up maybe rejected due to BW overbooking when a MBB operation is performed. This allows the PCE to optimize resource utilization more effectively and more aggressively thereby achieving greater network efficiency.
In a previous blog we were briefly introduced to a solution that enabled a packet-layer PCE to learn about the topology and link attributes of an under-lying transport layer network. This enables the packet-layer PCE to make more informed path computations by taking into account transport layer properties that would otherwise be hidden from the packet layer. In this blog, we will see the solution working, including several screen shots illustating the behavior, with a 3rd party transport system.
In Metro rings, typically most of the traffic goes from the nodes on the ring to a head end.
When the traffic on the ring is low (compared to the size of the links) it is obvious that the “most-efficient” solution is to build a ring of point-to-point connections between the nodes. When the traffic is high, it is equally obvious that the “most-efficient” solution is to connect every node directly to the head-end aggregation router(s) in a star or double-star "hub-and-spoke" formation.
Where it gets interesting is when you are some place in between and when there is at least some local traffic between the nodes on the ring, as well as the main traffic direct to the head-end(s). How do you mix point-to-point connections along the ring with direct connections to the head-end in the most efficient way?
These past few months have been an exciting start to our 2014 journey. As we approach the close of the first quarter and prepare to open the door to the second quarter filled with future opportunities, I’d like to reflect on the positive movement we have made so far. Juniper demonstrated leadership by unveiling innovative solutions, most notably Firefly Suite, Junos® Fusion, NorthStar Controller, and Juniper Argon Secure.