Copyright © 2014 Juniper Networks, Inc. 1 JUNIPER CONFIDENTIAL
Juniper NorthStar ControllerColby Barth, DE, Juniper Networks JDI
February 2nd, 2015
Juniper Confidential
In collaboration with: Tony Le, Naresh Kumar, Sudhir Cheruathur, Ping Wang, Rendo Wibawa
Copyright © 2014 Juniper Networks, Inc. 2 JUNIPER CONFIDENTIAL Copyright © 2014 Juniper Networks, Inc. 2
AGENDA
11 INTRO. TO PCE ARCHITECTURE - STRATEGY
12 NORTHSTAR 1.0 COMPONENTS
13
14 NORTHSTAR 1.0 APPLICATIONS – FEATURES
15 NORTHSTAR 1.0 MISC. – WRAP-UP
JUNOS CLIENT – PCCD – BGP-LS
Copyright © 2014 Juniper Networks, Inc. 3 JUNIPER CONFIDENTIAL Copyright © 2014 Juniper Networks, Inc. 3
AGENDA
11 INTRO. TO PCE ARCHITECTURE - STRATEGY
12 NORTHSTAR 1.0 COMPONENTS
13
14 NORTHSTAR 1.0 APPLICATIONS – FEATURES
15 NORTHSTAR 1.0 MISC. – WRAP-UP
JUNOS CLIENT – PCCD – BGP-LS
Copyright © 2014 Juniper Networks, Inc. 4 JUNIPER CONFIDENTIAL
CHALLENGES WITH CURRENT NETWORKSHow to Make the Best Use of the Installed Infrastructure?
2
3
1? How do I use my network resources efficiently?
1? How can I make my network application aware?
1? How do I get complete & real-time visibility?
Copyright © 2014 Juniper Networks, Inc. 5 JUNIPER CONFIDENTIAL
NORTHSTAR: TRAFFIC ENGINEERING W/ A GLOBAL VIEW
Optimizations that require global orchestration Multi-layer (not just IP + Optical)
Reduce JUNOS complexity Large computations
An API for network
SOLVE HARD PROBLEMS
OFF-LOAD RTR CONTROL-PLANE
INTEGRATE WITH APPLICATIONS
Bin Packing or Network Defragmentation
Scheduling / Calendaring
Predictability
Adaptive TE Control Loops
Inter-domain Routing
Global Concurrent Optimization
Network Lifecycle Management
ADDRESS REAL NETWORKING PROBLEMS
Copyright © 2014 Juniper Networks, Inc. 6 JUNIPER CONFIDENTIAL
PCE: EVOLUTIONARY APPROACHActive Stateful PCE Extensions
REAL-TIME AWARENESS OF LSP & NETWORK STATE
PCE dynamically learns the network topology PCCs report the LSP state to the PCE
LSP ATTRIBUTE UPDATES Via the PCEP, the PCE can update LSP B/W & path attributes, if the LSP is *controlled*
CREATE & TEAR-DOWN LSPS The PCE can *create* LSPs on the PCC, ephemerally
HARDER PROBLEMS OFFLOADED FROMNETWORK ELEMENT
* No persistent configuration is present on the PCC
P2MP LSP path computation & P2MP tree diversity Disjoint SRC/DST LSP path diversity Multi-layer & multiple constraints
Copyright © 2014 Juniper Networks, Inc. 7 JUNIPER CONFIDENTIAL
PCE ARCHITECTUREA Standards-based Approach for Carrier SDN
Path Computation Element (PCE): Computes the path
Path computation Client (PCC): Receives the path and applies it in the network. Paths are still signaled with RSVP-TE.
PCE protocol (PCEP): Protocol for PCE/PCC communication
PCEP
PCC PCC
PCC
A path Computation Element (PCE) is a system component, application, or network node that is capable of determining and finding a suitable route for conveying data between a source and a destination
What are the components?What is it?
PCE
Copyright © 2014 Juniper Networks, Inc. 8 JUNIPER CONFIDENTIAL
ACTIVE STATEFUL PCEA centralized network controller
The original PCE drafts (of the mid-2000s) were mainly focused around passive stateless PCE architectures: More recently, there’s a need for a more ‘Active’ and ‘Stateful’ PCE NorthStar is an active stateful PCE This fits well to the SDN paradigm of a centralized network controller
What makes an active Stateful PCE different: The PCE is synchronized, in real-time, with the network via standard
networking protocols; IGP, PCEP The PCE has visibility into the network state; b/w availability, LSP attributes The PCE can take ‘control’ and create ‘state’ within the MPLS network The PCE dictates the order of operations network-wide .
Report LSP state Create LSP state
NorthStar
MPLS Network
Copyright © 2014 Juniper Networks, Inc. 9 JUNIPER CONFIDENTIAL Copyright © 2014 Juniper Networks, Inc. 9
AGENDA
11 INTRO. TO PCE ARCHITECTURE - STRATEGY
12 NORTHSTAR 1.0 COMPONENTS
13
14 NORTHSTAR 1.0 APPLICATIONS – FEATURES
15 NORTHSTAR 1.0 MISC. – WRAP-UP
JUNOS CLIENT – PCCD – BGP-LS
Copyright © 2014 Juniper Networks, Inc. 10 JUNIPER CONFIDENTIAL
SOFTWARE-DRIVEN POLICY
Topology Discovery Path Computation State Installation
NORTHSTAR COMPONENTS & WORKFLOW
PCEP TE LSP discoveryIGP-TE, BGP-LS TED discovery (BGP-LS, IGP) LSDB discovery (OSPF, ISIS)
PCEP Create/Modify TE LSP One session per LER(PCC)
ANALYZE OPTIMIZE VIRTUALIZE
Routing PCEPApplication Specific Alg’s
RSVP signaling
OPEN APIs
Copyright © 2014 Juniper Networks, Inc. 11 JUNIPER CONFIDENTIAL
PCE controlled LSPs A PCC may delegate control of an LSP
to the PCE Subsequent changes of an LSP’s
attributes MUST be made by the PCE
PCE provisioned LSPs PCE may create an LSP LSP state is referred to as ephemeral PCE provisioned LSPs are also PCE
controlled LSPs
Data-plane does not change
PCE CONTROL & EPHEMERAL STATELSP delegation, control, & creation
[edit protocols]pcep { pce NorthStar { lsp-provisioning; lsp-cleanup-timer <sec>;
[edit protocols]mpls { label-switched-path PCC1-to-PCC2 { lsp-external-controller NorthStar;
[edit protocols]pcep { pce NorthStar { delegation-cleanup-timeout <sec>;
Copyright © 2014 Juniper Networks, Inc. 12 JUNIPER CONFIDENTIAL
NORTHSTAR MAJOR COMPONENTS
NorthStar consists of several major components: JUNOS Virtual Machine(VM) Path Computation Server (PCS) Topology Server REST Server
Component functional responsibilities: The JUNOS VM, is used to collect the TE-database & LSDB
A new JUNOS daemon, NTAD, is used remote ‘flash’ the lsdist0 table to the PCS
The PCS has multiple functions: Peers with each PCC using PCEP for LSP state collection &
modification Runs application specific Algs for computing LSP paths
The REST server is the interface into the APIs
PCEJUNOS VM
NTAD
RPD
PCS
REST_Server
KVM Hypervisor
Centos 6.5
MPLS NetworkPCC
BGP-LS/IGP PCEP
Topo_Server
Copyright © 2014 Juniper Networks, Inc. 13 JUNIPER CONFIDENTIAL
The JunosVM is used to peer with the network for topology acquisition using:
BGP-LS Direct ISIS or OSPF adjacency ISIS or OSPF adjacency over a
GRE tunnelPCCs connect to the PCEServer via PCEP for LSP reportingPCEP sessions are established from each LSP head-end to the PCE Server
NORTHSTAR AS A BLACK-BOX
JUNOS VM
RPDPCE_Server
REST_ServerWeb Server
MPLS NetworkPCC
BGP-LS/IGP PCEP
Auth Module
PC Server
3rd Party ApplicationsUser Interface
PCS HTTPTCP
Copyright © 2014 Juniper Networks, Inc. 14 JUNIPER CONFIDENTIAL
Standard, custom, & 3rd party Applications
Topology Discovery Path Computation Path Installation
Topology API Path computation API Path provisioning API
PCEP PCEPApplication specific algorithmsIGP-TE / BGP-LS
REST REST REST
NorthStar pre-packaged applications Bandwidth Calendaring, Path Diversity, Premium
path, auto-bandwidth / TE++, etc…
NORTHSTAR NORTHBOUND APIIntegration with 3rd Party Tools and Custom Applications
Copyright © 2014 Juniper Networks, Inc. 15 JUNIPER CONFIDENTIAL
NORTHSTAR NORTHBOUND APIExample
REST = REpresentational State Transfer: REST is more a collection of principals rather than a set of
standards Uses standard HTTP / HTTPS – GET / POST /PUT / DELETE
operations One of the key concepts of REST is that of “statelessness”
– each request provides the full state information and the response provides the full response – no “state” information is maintained between requests
Create a resource for every service Identifies each resource using a URL
curl -X POST -H "Content-Type: application/json" -H "Cache-Control: no-cache" -d \ '{ "name" : ”LSP_0815", "from" : {"topoObjectType" :"ipv4","address": ”<Node_A_IP>"}, "to" : {"topoObjectType" :"ipv4","address": ”<Node_Z_IP>"}, "pathType" : "primary", "plannedProperties" : { "setupPriority" : 7, "holdingPriority" : 7, "bandwidth" : "100m" } }' \
http://<PCS_IP>:8091/NorthStar/API/v1/tenant/1/topology/1/te-lsps/
Create an LSP from node_A to node_Z
curl -X GET -H "Content-Type: application/json" -H "Cache-Control: no-cache”
http://<PCS_IP>:8091/NorthStar/API/v1/tenant/1/topology/1/te-lsps/LSP_0815
Retrieve LSP properties
Copyright © 2014 Juniper Networks, Inc. 16 JUNIPER CONFIDENTIAL
NORTHSTAR NORTHBOUND APISupported Functionality
Topology API Get a snapshot of the full topology Retrieve a node and its relationships like edges, LSPs, flows, etc… Retrieve a path and its properties
Path Provisioning API Provision a path with a given set of attributes Modify a path’s bandwidth or ERO
Path Computation API Compute the path between a set of endpoints, for a given set of constraints Compute two diverse paths for a given LSP Split a given LSP into multiple LSPs based on a given traffic event Re-optimize an LSP or all LSPs under different constraints Re-route around a node / link (e.g. for maintenance purposes)
NorthStar
PCC
Network management
REST APIs
PCEP BGP-LS
Copyright © 2014 Juniper Networks, Inc. 17 JUNIPER CONFIDENTIAL
NORTHSTAR 1.0 HIGH AVAILABILITY (HA)Active / Standby for delegated LSPs
NorthStar 1.0 supports a high availability model only for delegated LSPs: Controllers are not actively synced with each-other
Active / standby PCE model with up to 16 back-up controllers: PCE-group: All PCE belonging to the same group
LSPs are delegated to the primary PCE Primary PCE is the controller with the highest delegation priority Other controllers cannot make changes to the LSPs If a PCC looses connection with its primary PCE, it will immediately
use the PCE with next highest delegation priority as its new primary PCE
ALL PCCs MUST use the same primary PCE
[configuration protocols pcep]pce-group pce { pce-type active stateful; lsp-provisioning;
delegation-cleanup-timeout 600;}pce jnc1 {
pce-group pce; delegation-priority 100;}pce jnc2 {
pce-group pce; delegation-priority 50;
jnc1 jnc2
PCC
PCEPPCEP
Copyright © 2014 Juniper Networks, Inc. 18 JUNIPER CONFIDENTIAL
NORTHSTAR DEPLOYMENT
As previously mentioned, NorthStar consists of multiple ‘machines’: JUNOS Virtual Machine Path Computation Server (PCS) & REST ServerEach ‘machine’ requires reachability within the network JUNOS VM connects to the network via a hypervisor
vSwitch PCS connects to the network via the native Centos
interface Each require separate addressing Internally, the components are self addressed at system
startup
PCEJUNOS VM
NTAD
RPD
PCS
REST_Server
KVM Hypervisor
vSwitch
em0 em1
Centos 6.5
Copyright © 2014 Juniper Networks, Inc. 19 JUNIPER CONFIDENTIAL
NorthStar
BGP-LS speaker/Hierarchy
BGP-LS session(s)
TOPOLOGY ACQUISITION – BGP-LSVarious deployment options are supported
Using BGP-LS, allows an operator to ‘tap’ into all of BGP’s deployment & policy flexibility to support network architectures of all types: Supports various inter-area and Inter-domain deployment options Allows for fewer topology acquisition ‘sessions’ with NorthStar
NorthStar
ASBRs/ABRs
BGP-LS session(s)
Copyright © 2014 Juniper Networks, Inc. 20 JUNIPER CONFIDENTIAL
NorthStar
Redundant IGP Speakers
IGP Adj(s)
TOPOLOGY ACQUISITION – ISIS, OSPF & GRE TUNNELINGNative protocol topology acquisition
NorthStar can also be deployed where it peers with the network via its native IGP: ISIS and OSPFv2 are supported GRE tunneling is also supported to increase deployment flexibility Multi-area, multi-level & multi-domain networks MAY require many IGP adjacencies & GRE tunnels
NorthStar
ASBRs/ABRs
IGP Adj(s) over GRE tunnels
cbarth@vrr-84# show interfaces greunit 0 { tunnel { source 84.105.199.2; destination 84.0.0.101; } family inet { address 2.2.2.2/30; } family iso; family mpls;
cbarth@vrr-84# show protocols isisinterface gre.0 { point-to-point; level 2 metric 50000;}interface lo0.0;
Copyright © 2014 Juniper Networks, Inc. 21 JUNIPER CONFIDENTIAL
http://www.isocore.com/pdf/Fall 2014-Isocore - Final-Press Release.pdf
MULTI-VENDOR SUPPORT FOR BGP-LS / PCEPSuccessful Demonstration of WAN SDN Controller Interworking
Copyright © 2014 Juniper Networks, Inc. 22 JUNIPER CONFIDENTIAL Copyright © 2014 Juniper Networks, Inc. 22
AGENDA
11 INTRO. TO PCE ARCHITECTURE - STRATEGY
12 NORTHSTAR 1.0 COMPONENTS
13
14 NORTHSTAR 1.0 APPLICATIONS – FEATURES
15 NORTHSTAR 1.0 MISC. – WRAP-UP
JUNOS CLIENT – PCCD – BGP-LS
Copyright © 2014 Juniper Networks, Inc. 23 JUNIPER CONFIDENTIAL
JUNOS PCE CLIENT IMPLEMENTATION New JUNOS daemon, pccd
Enables a PCE application to set parameters for a traditionally configured TE LSPs and create ephemeral LSPs
PCCD is the relay/message translator between the PCE & RPD LSP parameters, such as the path & bandwidth, & LSP creation instructions are received from the
PCE are communicated to RPD via PCCD RPD then signals the LSP using RSVP-TE
PCEPCEP
PCCDPCEP RPD
MPLS Network
PCEP
JUNOS IPC
RSVP-TE
Copyright © 2014 Juniper Networks, Inc. 24 JUNIPER CONFIDENTIAL
Association of PCE provisioned LSPs with a template using a regex based name matchingAligned with how many customers use apply-groups in JUNOS today for applications like COS based forwarding
JUNOS MULTI-TEMPLATE SUPPORTprotocols { mpls { lsp-external-controller pccd { pce-controlled-lsp *-EF { label-switched-path-template ef-lsp; } pce-controlled-lsp *-AF { label-switched-path-template af-lsp; } pce-controlled-lsp *-BE { label-switched-path-template be-lsp; } } label-switched-path ef-lsp { link-protection; template; } label-switched-path af-lsp { ldp-tunneling; least-fill; link-protection; template; } label-switched-path be-lsp { ldp-tunneling; template;
protocols { mpls { lsp-external-controller pccd {+ pce-controlled-lsp <regex> {
Copyright © 2014 Juniper Networks, Inc. 25 JUNIPER CONFIDENTIAL
JUNOS MULTI-TEMPLATE SUPPORT (CONT.)
Once a PCE provisioned LSP is created and associated with a template it inherits the properties of the template If subsequent changes to the template are made, the existing provisioned LSP(s) will not inherit the
new changes Only new PCE provisioned LSPs will inherit the properties of the changed template
cbarth@vmx101-07> show path-computation-client lsp
Name Status PLSP-Id LSP-Type Controller Template LSP_to_vmx103 Primary(Act) 13 ext-provised jnc default_pvc To-vmx104-EF Primary(Act) 12 ext-provised jnc ef-lsp To-vmx104-BE Primary(Act) 11 ext-provised jnc be-lsp To-vmx104-AF Primary(Act) 10 ext-provised jnc af-lsp LSP_to_vmx102 Primary(Act) 9 ext-provised jnc default_pvc
Copyright © 2014 Juniper Networks, Inc. 26 JUNIPER CONFIDENTIAL
TOPOLOGY DISCOVERY WITH BGP-LS
Each link entry in the TED is “shadowed” as a prefix in the lsdist.0 RIB, such that it can be picked up by a BGP export policy
The shadowing process is explicitly enabled & only TED entries which conform to the specific policies will have RIB shadows
Policy control allows both creation/duplication & virtualization of the network topology
TED lsdist.0TED shadowing
policy BGP-LS Export policy
Topology Discovery
Topology API
Routing
NorthStarBGP-LS Session
Copyright © 2014 Juniper Networks, Inc. 27 JUNIPER CONFIDENTIAL
BGP-LS CONFIGURATIONEnabling of the traffic-engineering address family generates a MP AFI Capability code to be negotiated with peers
Each link entry in the TED gets “shadowed” as a prefix in the lsdist0 RIB, such that it can be picked up by a BGP export policy
protocols { bgp { family {+ traffic-engineering unicast;
protocols { mpls { traffic-engineering {+ database {+ import [policy1 policy2];
Copyright © 2014 Juniper Networks, Inc. 28 JUNIPER CONFIDENTIAL
CONFIGURATION (CONTINUED)The default policy of BGP is only to export routes, which are known via BGPIn order to advertise an entry leaked from TED, an export policy is required which matches against non-BGP routes in the lsdist0 RIB
policy-options { policy-statement isis-link-bgp { term 1 { from { protocol isis; source-address-filter 10.0.0.0/8 orlonger; } then accept;
Copyright © 2014 Juniper Networks, Inc. 29 JUNIPER CONFIDENTIAL Copyright © 2014 Juniper Networks, Inc. 29
AGENDA
11 INTRO. TO PCE ARCHITECTURE - STRATEGY
12 NORTHSTAR 1.0 COMPONENTS
13
14 NORTHSTAR 1.0 APPLICATIONS – FEATURES
15 NORTHSTAR 1.0 MISC. – WRAP-UP
JUNOS CLIENT – PCCD – BGP-LS
Copyright © 2014 Juniper Networks, Inc. 30 JUNIPER CONFIDENTIAL
NORTHSTAR CONSOLELaunch NorthStar-PCE or NorthStar-Simulation from a single interface
Copyright © 2014 Juniper Networks, Inc. 31 JUNIPER CONFIDENTIAL
Topology Discovery MPLS capacity planning ‘Full’ Offline Network Planning
NorthStar NorthStar Simulation IP/MPLSview
LSP Control/Modification FCAPs (PM, CM, FM)Exhaustive Failure Analysis
REAL-TIME NETWORK FUNCTIONS
Dynamic Topology updates via BGP-LS / IGP-TE
Dynamic LSP state updates via PCEP
Real-time modification of LSP attributes via PCEP (ERO, B/W, pre-emption, …)
MPLS LSP PLANNING & DESIGN
Topology acquisition via NorthStar REST API (snapshot)
LSP provisioning via REST API Exhaustive failure analysis &
capacity planning for MPLS LSPs MPLS LSP design (P2MP, FRR,
JUNOS config’let, …)
OFFLINE NETWORK PLANNING & MANAGEMENT
Topology acquisition & equipment discovery via CLI, SNMP, NorthStar REST API
Exhaustive failure analysis & capacity planning (IP & MPLS)
Inventory, provisioning, & performance management
NORTHSTAR SIMULATION MODENorthStar vs. IP/MPLSview
Copyright © 2014 Juniper Networks, Inc. 32 JUNIPER CONFIDENTIAL
BASIC TOPOLOGY & LSP VISUALIZATIONNodes/Links/LSP/SRLGs ‘tabs’ Rearrangeable fields Sorting/searching Table Export
LSP path details LSP type & attributes LSP path (reported RRO) Primary/secondary associations Diversity associations LSP logs
Copyright © 2014 Juniper Networks, Inc. 33 JUNIPER CONFIDENTIAL
BASIC TOPOLOGY & LSP VISUALIZATION (CONT.)
Nodes/Links/Tunnels/SRLGs ‘tabs’ Rearrangeable fields Sorting/searching Table Export
Tunnel path details LSP type & attributes LSP path (reported RRO) Primary/secondary associations Diversity associations LSP logs
Link details Reserved/Unreserved B/W (A->Z & Z->A) RSVP utilization IP addressing, metric, subscription B/W
Visual RRO display for selected LSP
Auto-b/w LSP
PCE initiated Primary/2ndary LSPs
PCE LSP Type
Copyright © 2014 Juniper Networks, Inc. 34 JUNIPER CONFIDENTIAL
BASIC TOPOLOGY & LSP VISUALIZATION(CONT.)SRLG details SRLG attributes learned from the IGP Links that comprise the SRLG
Node details PCEP enabled IP addressing, node ID, hostname, IGP
Network Summary Number of LSPs, …
NorthStar console Status of PCServer Activity logging
Copyright © 2014 Juniper Networks, Inc. 35 JUNIPER CONFIDENTIAL
DIVERSE PATH COMPUTATIONAutomated Computation of end-to-end diverse paths
Network-wide visibility allows NorthStar to support end-to-end LSP path diversity: Wholly disjoint path computations; Options for link, node and SRLG diversity
Pair of diverse LSPs with the same end-points or with different end-points
SRLG information learned from the IGP dynamically
Supported for PCE created LSPs(at time of provisioning) and delegated LSPs(though manual creation of diversity group)
Warning!Shared Risk Shared Risk
Eliminated
Primary LinkSecondary Link
CE
CE
CE
CE
NorthStar
Copyright © 2014 Juniper Networks, Inc. 36 JUNIPER CONFIDENTIAL
2 METHODS OF DIVERSITY ASSOCIATION
Creation of a Diversity GroupMaintaining diversity for delegated LSPs
Diversity at LSP CreationDiversity for PCE provisioned LSPs
The Delegated LSP must be already configured on the router and reported to NorthStar Select 2 or more delegated LSP from the
tunnel window Click "modify" button Click "type" button Go to "design" tab Choose the "diversity level" Enter a name for the "diversity group" Click "OK" Re-Provision those LSPs
NorthStar is being used to create diversely routed LSPs Click ”Add" button Select “Diverse Tunnel Pair …” Select PCC-A & PCC-Z pairs for each Tunnel Select Diversity “type“ Click “show path” Click "OK” Provision the LSPs
Copyright © 2014 Juniper Networks, Inc. 37 JUNIPER CONFIDENTIAL
SECONDARY / STANDBY LSP SUPPORTAutomated Computation of Secondary/Standby Paths
NorthStar supports secondary / standby LSP for PCE created and delegated LSPs:
draft-ananthakrishnan-pce-stateful-path-protection-00 draft-minei-pce-association-group-00 Client assigned group IDs, automatically allocated ID space Secondary /
Standby path
NorthStar
The operator can specify different attributes and / or constraints for the primary and secondary / standby paths: Delegated LSPs require no additional JUNOS configuration Multiple 2ndary LSPs, with various path constraints & attributes, may be created NorthStar ‘activates’ the 2ndary LSP in the case of inactive standby LSPs
Copyright © 2014 Juniper Networks, Inc. 38 JUNIPER CONFIDENTIAL
PCE CREATED SYMMETRIC LSPSLocal association of LSP symmetry constraint
Symmetric LSPs
NorthStar
NorthStar supports creating symmetric LSPs:
Does not leverage GMPLS extensions for co-routed or associated bi-directional LSPs Unidirectional LSPs (identical names) are created from nodeA to nodeZ & nodeZ to nodeA Symmetry constraint is maintained locally on NorthStar (attribute: pair =<value>)
Symmetric LSP creation
Copyright © 2014 Juniper Networks, Inc. 39 JUNIPER CONFIDENTIAL
MAINTENANCE-MODE RE-ROUTINGAutomated Path Re-computation, Re-signaling and Restoration
Automate re-routing of traffic before a scheduled maintenance window: Simplifies planning and preparation before and during a maintenance window Eliminate the risk that traffic is mistakenly affected when a node / link goes into maintenance mode Reduced need for spare capacity through the optimum use of resources available during the
maintenance window After the maintenance window finished paths are automatically restored to the (new) optimum path
1
Maintenance mode tagged: LSP paths are re-computed assuming
affected resources are not available
XX
X
2
In maintenance mode: LSP paths are automatically (make-
before-break)re-signaled
3
Maintenance mode removed: all LSP paths are re-stored to their
(new) optimal path
NorthStar
Copyright © 2014 Juniper Networks, Inc. 40 JUNIPER CONFIDENTIAL
Bandwidth calendaring allows network operators to schedule the creation/deletion/modification of an LSP: An LSP may be scheduled for creation or deletion at some point in the future An LSP may be scheduled for modification as some point in the future B/W calendaring is built into all the LSP add/modify UI ‘s
Example:1. Operator pre-provisions a calendar event, either through the calendaring
function native to NorthStar or through the path provisioning API2. NorthStar schedules the LSP provisioning event3. The LSP path is calculated at the scheduled point in time and the path is
provisioned in the network
Operator loads calendar event
NorthStar
LSP path provisioning at scheduled time
1
3
2
BANDWIDTH CALENDARINGTime-based LSP Provisioning
Copyright © 2014 Juniper Networks, Inc. 41 JUNIPER CONFIDENTIAL
GLOBAL CONCURRENT OPTIMIZATION Optimized LSP placement
NorthStar enhances traffic engineering through LSP placement based on a network wide visibility of the topology and LSP parameters: CSPF ordering can be user-defined, i.e. the operator can select which parameters such as LSP priority
and LSP bandwidth influence the order of placement Net Groom:
- Triggered on demand- User can choose LSPs to be optimized- LSP priority is not taken into account- No pre-emption
Path Optimization: - Triggered on demand or on scheduled
intervals (with optimization timer)- Global re-optimization toward all LSPs- LSP priority is taken into account - Preemption may happen
High priority LSPLow priority LSP
Global re-optimization
NorthStarBandwidth bottleneck!
CSPF failure
New Path request
Copyright © 2014 Juniper Networks, Inc. 42 JUNIPER CONFIDENTIAL
MPLS AUTO BANDWIDTHSmart LSPs with Auto-Bandwidth / TE++
Auto-b/w LSP creation with NorthStar 1.0: Dependent on JUNOS templates that define the auto-b/w policy PCC driven LSP B/W modification: auto-b/w policy & LSP statistics collection are
distributed PCE based path computation (ERO, bandwidth, etc…)
Auto-bandwidth and TE++ are vendor-specific implementations and will only work with a Juniper PCC: NorthStar discovers that a PCC is JUNOS and that a given LSP is an auto-b/w or TE++
sub-LSP via PCEP vendor-specific attributes NorthStar 1.0 only supports delegated TE++ LSPs, where sub-LSPs are associated
through a PCC generated association-group ID.
NorthStar
PCC
Path computation
Policy definitionStatistics collection
Copyright © 2014 Juniper Networks, Inc. 43 JUNIPER CONFIDENTIAL
MPLS AUTO-BANDWIDTHAuto-Bandwidth Example
1. JUNOS PCC will collect auto-bandwidth LSP statistics
2. Every adjustment interval the PCC will send a PcRpt message with a LSP bandwidth request
3. NorthStar will compute a new ERO for the requested B/W
4. NorthStar will send a PcUpdate message with the new ERO & bandwidth time
Adj_Interval B/W_Sample(s)
NorthStar
PcRpt Msg, b/w=14m
PcRpt Msg, b/w=12m
PcRpt Msg, b/w=15m
PcRpt Msg, b/w=16m
B/W
PcUpdate Message
1
4
3
2PCC
Copyright © 2014 Juniper Networks, Inc. 44 JUNIPER CONFIDENTIAL
NorthStar Auto-bandwidth (phase 1) Example – 5 minute adjust interval
-- schedule reroute for [email protected], Receive auto_bw requestprovision of tunnel 7.0.0.101:To-vmx104-auto-bw is scheduledprovisioning order placed at Mon Jan 5 16:58:37 2015
-- schedule reroute for [email protected], Receive auto_bw requestprovision of tunnel 7.0.0.101:To-vmx104-auto-bw is scheduledprovisioning order placed at Mon Jan 5 17:03:37 2015
cbarth@vmx101-07> show mpls lsp autobandwidth Lspname Last Requested Reserved Highwater AdjustTime LastAdjust BW BW BW mark Left (sec) To-vmx104-auto-bw 1.19323Mbps 3.78647Mbps 3.78647Mbps 3.78647Mbps 3 sec Mon Jan 5 13:58:36 2015
cbarth@vmx101-07> show mpls lsp autobandwidth Lspname Last Requested Reserved Highwater AdjustTime LastAdjust BW BW BW mark Left (sec) To-vmx104-auto-bw 3.78647Mbps 1.4055Mbps 1.4055Mbps 3.78647Mbps 175 sec Mon Jan 5 14:03:37 2015
NorthStar console
LSP Head-end
Copyright © 2014 Juniper Networks, Inc. 45 JUNIPER CONFIDENTIAL
INTER-DOMAIN TRAFFIC-ENGINEERINGOptimal Path Computation & LSP Placement
LSP [delegation, creation, optimization] of inter-domain LSPs Single active PCE across domains, BGP-LS for topology acquisition JUNOS Inter-AS requirements & constraints
http://www.juniper.net/techpubs/en_US/junos13.3/topics/usage-guidelines/mpls-enabling-inter-as-traffic-engineering-for-lsps.html
Inter-AS Traffic-Engineering
NorthStarNorthStar
Inter-Area Traffic-Engineering
AS 100
AS 200
Area 1
Area 2
Area 3Area 0
Copyright © 2014 Juniper Networks, Inc. 46 JUNIPER CONFIDENTIAL
PREMIUM PATH OPTIMIZATION Application-aware Path Computation
Optimum path is decided based on application specific requirements: Today only a single set of metrics are used for shortest path computation, often based on number of
hops (minimize port cost) and / or distance (minimize transport cost and latency) NorthStar can use additional ‘cost’ functions for path computation, stored in a separate topology file, to
decided the optimum path for each LSP The path computation API can use this capability to optimize path computation based on application
requirements, e.g. latency for voice and cost for web data
Lowest latency path (-) and back-up path
()
Lowest cost path (-) and back-up path ()
NorthStar
Copyright © 2014 Juniper Networks, Inc. 47 JUNIPER CONFIDENTIAL
LSP LOG HISTORY
A Per LSP log is maintained• Accessible by right clicking on an LSP & ‘show LSP events’• Select date range
Copyright © 2014 Juniper Networks, Inc. 48 JUNIPER CONFIDENTIAL
NORTHSTAR SIMULATION MODEOffline Network Planning & Modeling
NorthStar builds a near real-time network model for visualization and off-line planning through dynamic topology / LSP acquisition: Export of topology and LSP state to NorthStar simulation mode for ‘off-line’ MPLS network modeling Add/delete links/nodes/LSPs for future network planning Exhaustive failure analysis, P2MP LSP design/planning, LSP design/planning, FRR design/planning JUNOS LSP config’let generation
NorthStar-Simulation
Year 1
Year 3
Year 5
ExtensionYear 1
Copyright © 2014 Juniper Networks, Inc. 49 JUNIPER CONFIDENTIAL
MONITORING MODEVerify/Compare NorthStar computations, record and replay network events
Monitor mode archives the network / LSP state and allow play-back on a timeline: The operator can select time/date range to record No specific event monitoring (trap collection), but at regular time intervals Monitoring mode operates in passively, and does not imply that NorthStar has control of any LSPs in the
network A User can stop the reply, save a snapshot and then open the snapshot in NorthStar simulation to do tunnel
design and/or any failure simulation
X XX X
Copyright © 2014 Juniper Networks, Inc. 50 JUNIPER CONFIDENTIAL Copyright © 2014 Juniper Networks, Inc. 50
AGENDA
11 INTRO. TO PCE ARCHITECTURE - STRATEGY
12 NORTHSTAR 1.0 COMPONENTS
13
14 NORTHSTAR 1.0 APPLICATIONS – FEATURES
15 NORTHSTAR 1.0 MISC. – WRAP-UP
JUNOS CLIENT – PCCD – BGP-LS
Copyright © 2014 Juniper Networks, Inc. 51 JUNIPER CONFIDENTIAL
A REAL CUSTOMER EXAMPLE – PCE VALUECentralized vs. distributed path computation
51
Link
Util
izatio
n (%
)
1 4 7 10 13 16 19 22 25 28 31 34 37 40 43 46 49 52 55 58 61 64 67 70 73 76 79 82 85 88 91 94 97 100 103 106 109 112 115 118 121 124 127 130 133 136 139 142 145 148 151 154 157 160 1630.00%
20.00%
40.00%
60.00%
80.00%
100.00%
Distributed CSPF PCE centralized CSPF
TE-LSP operational routes are used for distributed CSPF
RSVP-TE Max Reservable BW set BW set to 92%
Modeling was performed with the exact operation LSP paths
Convert all TE-LSPS to EROs via PCE design action
Objective function is Min Max link utilizations
Only Primary EROS & Online Bypass LSPS Modeling was performed with 100% of
TE LSPS being computed by PCE
Up to 15% reduction in RSVP reserved B/W
Distributed CSPF Assumptions Centralized Path Calculation Assumptions
Copyright © 2014 Juniper Networks, Inc. 52 JUNIPER CONFIDENTIAL
NORTHSTAR 1.0 FRS delivery
NorthStar FRS is targeted for March-23rd:
(Beta) trials / evaluations already ongoing First customer wins in place
Target JUNOS releases: 14.2R3 Special * 14.2R4* / 15.1R1* / 15.2R1*
Supported platforms at FRS: PTX (3K, 5K), MX (80, 104, 240/480/960, 2010/2020, vMX) Additional platform support in NorthStar 2.0
* Pending TRD Process
NorthStar packaging & platform: Bare metal application only No VM support at FRS Runs on any x86 64bit machine that is supported
by Red Hat 6 or Centos 6 Single hybrid ISO for installation Based on Juniper SCL 6.5R3.0
Recommended minimum hardware requirements: 64-bit dual x86 processor or dual 1.8GHz Intel
Xeon E5 family equivalent 32 GB RAM 1TB storage 2 x 1G/10G network interface
Copyright © 2014 Juniper Networks, Inc. 53 JUNIPER CONFIDENTIAL
NORTHSTAR 1.0 H/W REQUIREMENTS Subscription based pricing for NorthStar There is no dependency on Motherboard, NIC cards etc as we support CentOS6.5 as
Host OS, verify it with CentOS6.5 supported hardware portal No preference on Vendor
Small ( 1-50 Nodes) Medium ( 50-250 Nodes) Large ( 250+ Nodes)
CPU: 64-bit dual 1.8GHz Intel® Xeon® E5 family equivalent
CPU: 64-bit Quad Intel® Xeon® Processor E5520 (2.26 GHz, 8MB L3 Cache) equivalent
CPU: 64 bit Quad core Intel® Xeon® Processor X5570 (2.93 GHz,8MB L3 Cache) equivalent
RAM: 16GBHard Drive: 250GBNetwork Port: 1/10GE( CSE2k matches this spec)
RAM: 64GBHard Drive: 500GBNetwork Port: 1/10GE
RAM: 128GBHard Drive: 1TBNetwork Port: 1/10GE
Copyright © 2014 Juniper Networks, Inc. 54 JUNIPER CONFIDENTIAL
NORTHSTAR DEMO OPTIONS
NorthStar Beta Version is installed and available for POC testing at: Sunnyvale POC Lab Herndon POC Lab Westford POC Lab Amsterdam POC Lab
SE’s can schedule a quick demo with Customers using: Juniper Cloud Labs ( JCL)
http://www.jcl.jnpr.net/ Contact: Nancy Cohen [email protected]
Open Labs, NJ http://www-int.juniper.net/sales/openlab/ [email protected]
Copyright © 2014 Juniper Networks, Inc. 55 JUNIPER CONFIDENTIAL
ADDITIONAL INFORMATION
Internal Resources: https://junipernetworks.sharepoint.com/teams/RBU/plm/core/NorthStar%
20and%20WANDL%20external%20website/SitePages/Home.aspx http://www.juniper.net/us/en/products-services/sdn/NorthStar-network-controller/
PCEP: http://tools.ietf.org/html/draft-ietf-pce-stateful-pce-07 https://tools.ietf.org/html/draft-crabbe-pce-pce-initiated-lsp-03 http://tools.ietf.org/html/draft-ananthakrishnan-pce-stateful-path-protection-00 http://tools.ietf.org/html/draft-minei-pce-association-group-00 RFC 5440: Path Computation Element (PCE) Communication Protocol (PCEP) RFC 7190: Conveying Vendor-Specific Constraints in the Path Computation Element Communication Protocol
BGP-LS: http://www.ietf.org/id/draft-ietf-idr-ls-distribution-05.txt
Copyright © 2014 Juniper Networks, Inc. 56 JUNIPER CONFIDENTIAL
SUPPORT CONTACTS
NorthStar PLMNaresh Kumar [email protected] Le [email protected] Barth [email protected]
E-mail lists to ask questions: [email protected]@[email protected]
High-IQ networking CoEDidier Bousser [email protected] Bowers [email protected] Lucek [email protected] van den Borne [email protected]
Marketing ContactDonyel Jones-Williams [email protected]
Copyright © 2014 Juniper Networks, Inc. 57 JUNIPER CONFIDENTIAL
THANK YOU
Top Related