NETWORK DEPLOYMENT WITH SEGMENT ROUTING (SPRING) Aman Kapoor Director, Product Management
This statement of direction sets forth Juniper Networks current intention and is subject to change at any time without notice. No purchases are contingent upon Juniper Networks delivering any feature or functionality depicted in this presentation. This presentation contains proprietary roadmap information and should not be discussed or shared without a signed non-disclosure agreement (NDA).
AGENDA Networking trends and requirements SPRING: Introduction SPRING: Market drivers SPRING: Ecosystem
NETWORKING TRENDS Traffic Growth Global Presence Cloud delivery
NETWORK REQUIREMENTS Simple & Flexible Resilient Always available Programmable Extensible
SPRING INTRODUCTION
INTRODUCTION Source Packet Routing In NetworkinG (SPRING) R1 (ingress) R2 LSP X R3 R6 R7 (egress) R4 R5 Network => Collection of topological sub paths called Segments End-to-End path formed by stacking the segments Segment represented as MPLS Labels IPv6 address 7
KEY CONCEPTS Node SID = 302 Binding SID = 183 302 183 555 718 pay load R1 (Ingress) R2 R3 R6 Adjacency SID =718 R7 (Egress) R4 R5 Adjacency SID = 555 8
EARLY ADOPTERS
SERVICE PROVIDERS CONTROLLER-BASED Shortest Path Routing FRR (TI-LFA) 100% convergence Traffic steering Light weight TE Diverse Path No bandwidth reservations Traffic Engineered With bandwidth reservation No additional protocols
PUBLIC CLOUD PROVIDERS DC-E DC-E DC Fabric DC Fabric Public Cloud Data Center DC-E Public Cloud Data Center DC Fabric Public Cloud Data Center
SERVICE PROVIDERS - TELCO CLOUD S S S S L L L L L L L L L L L L L L L L Storage Access VNFs Backbone
SPRING ECOSYSTEM CONSIDERATIONS
SOFTWARE DRIVEN CONTROL SOFTWARE-DRIVEN POLICY ANALYZE OPTIMIZE AUTOMATE PCEP TE LSP discovery IGP-TE, BGP-LS TED discovery (BGP-LS, IGP) LSDB discovery (OSPF, ISIS) RSVP signaling PCEP/ Netconf/Yang / OpenConfig Create/Modify TE LSP One session per LER(PCC)
NORTHSTAR BETTER ECONOMICS, SIMPLIFIED OPERATION FASTER TIME TO REVENUE Ability to create faster service deployment and better customer experience OPERATIONAL SIMPLICITY Reduce operational cost, maximize life of network assets, rapid network tuning AGILITY Agile service creation is foundation for new revenue generation
LABEL STACK DEPTH R6 R9 R11 R2 R4 R6 R9 R11 pay load R13 R14 R15 pay load R1 R2 R3 R4 R5 R7 R10 R12 R13 R14 R15 Depth determined by TE requirements Entropy requirements add to Label stack depth 16
LABEL STACK DEPTH Juniper MX family Programmable ASIC Flexible Label stack depth Flexible Hash depth Juniper PTX & QFX10K family Fixed Pipeline Label stack depth: 8 Label Hash: 8 17
REAL TIME TELEMETRY Performance Monitoring, Accounting Enabling External Control Interfaces Attachment Circuits Protocol Sessions Packet Forwarding Engines 1000s 100s Insert your metric here Number of increases Reporting granularity reduces or stays the same Year Controller State synchronization is required
JUNOS STREAMING TELEMETRY SENSORS FORWARDING INTERFACE COUNTERS FILTER / POLICER COUNTERS INGRESS LSP STATISTICS SID STATISTICS PLATFORM OPTICAL POWER LEVELS POWER CONSUMPTION TEMPERATURE NPU / LINE CARD CPU AND MEMORY 2 Second Reporting Granularity ROUTING BGP PEER INFORMATION SPRING, RSVP PROTOCOL STATISTICS ROUTING PROCESS MEMORY CONSUMPTION 40 000 Metrics / Second Positive Performance Impact
JUNOS TELEMETRY INTEGRATION OPTIONS Visualization / Analytics Customer Application Northstar AppFormix Juniper Applications Performance Management SevOne Monitoring Cacti MRTG Analytics SPLUNK Performance Management IBM Proviso Infovista CA VistaInsight PacketDesign Other Data Collection OpenNTI Potential integration Data Sources Router MX PTX QFX / EX
MIGRATION INTRODUCING SPRING IN BROWN FIELD NETWORK
SPRING & LDP NETWORK Concept: Mapping Server creates FEC mappings and distributes in the SPRING network Mapping client stitches traffic between the domains PE Existing LDP core PE Use Case: Mapping Client Mapping Client/Server New SR core PE New domains being build with SPRING as transport Interworking of services with existing backbone PE LDP region SR upgraded region PE Upgrading backbone to roll-out SPRING LDP mapping client/server
SPRING & RSVP NETWORK Concept: SPRING traffic governs RSVP bandwidth allocations Each router measures SPRING traffic Backpressure RSVP based on configured thresholds Seamless: No modification to existing RSVP behavior Northstar Use-cases: SPRING in an existing RSVP network Traffic Mix some traffic follows RSVP and some SPRING LSPs RSVP subscription adjust RSVP SR
RECAP SPRING simplifies network programmability Considerations when moving to SPRING based network Juniper helps migrate to SPRING transport seamlessly