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).

SPRING: Introduction

Networking trends and requirements

SPRING: Market drivers

SPRING: Ecosystem

AGENDA

NETWORKING TRENDS

Traffic Growth Global Presence Cloud delivery

NETWORK REQUIREMENTS

Simple & Flexible

Resilient

Programmable

Extensible

Always available

SPRINGINTRODUCTION

INTRODUCTIONSource Packet Routing In NetworkinG (SPRING)

7

• Network => Collection of topological sub paths – called “Segments”• End-to-End path formed by stacking the segments• Segment represented as

• MPLS Labels• IPv6 address

R7 (egress)

R2 R3

R4R5

R1 (ingress)

LSP X

R6

KEY CONCEPTS

8

R2 R3

R4R5

R1 (Ingress)

R6R7 (Egress)

Node SID =

302

Adjacency SID

= 555

Adjacency SID

=718

Binding SID = 183

302183555718payload

EARLY ADOPTERS

SERVICE PROVIDERS

Shortest Path Routing

• No additional protocols

FRR (TI-LFA)

• 100% convergence

Traffic steering

• Light weight TE

Diverse Path

• No bandwidth reservations

Traffic Engineered

• With bandwidth reservation

CONTROLLER-BASED

PUBLIC CLOUD PROVIDERS

Public Cloud Data Center

DC-E

DC Fabric

Public Cloud Data Center

DC-E

DC Fabric

Public Cloud Data Center

DC-E

DC Fabric

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 ECOSYSTEMCONSIDERATIONS

PCEP

TE LSP discovery

IGP-TE, BGP-LS

TED discovery (BGP-LS, IGP)

LSDB discovery (OSPF, ISIS)

SOFTWARE-DRIVEN POLICY

ANALYZE OPTIMIZE AUTOMATE

RSVP signaling

PCEP/ Netconf/Yang / OpenConfig Create/Modify TE LSP

One session per LER(PCC)

SOFTWARE DRIVEN CONTROL

AGILITY

Agile service creation is foundation for new revenue generation

OPERATIONAL

SIMPLICITYReduce operational cost, maximize life of network

assets, rapid network tuning

FASTER TIME

TO REVENUEAbility to create faster

service deployment and better customer experience

NORTHSTARBETTER ECONOMICS, SIMPLIFIED OPERATION

R2R4R6R9payload

LABEL STACK DEPTH

16

R1

R2

R3

R4

R5

R6

R7

R9

R10

R11

R12

R13

R14

R15

R11R13R14R15payload

• Depth determined by TE requirements• Entropy requirements add to Label stack depth

LABEL STACK DEPTH

17

Juniper MX family Juniper PTX & QFX10K family

• Programmable ASIC• Flexible Label stack depth• Flexible Hash depth

• Fixed Pipeline• Label stack depth: 8• Label Hash: 8

REAL TIME TELEMETRY

Performance Monitoring, Accounting Enabling External Control

Number of ______ increases

Reporting granularity reduces or stays the same

Controller

State synchronization is required

Insert your metric here

Interfaces

Attachment Circuits

Protocol Sessions

Packet Forwarding Engines

Year

100s

1000s

FORWARDING

INTERFACE COUNTERS

FILTER / POLICER COUNTERS

INGRESS LSP STATISTICS

SID STATISTICS

ROUTING

BGP PEER INFORMATION

SPRING, RSVP PROTOCOL STATISTICS

ROUTING PROCESS MEMORY CONSUMPTION

2 Second Reporting

Granularity

Positive Performance

Impact

40 000 Metrics / Second

JUNOS STREAMING TELEMETRY SENSORS

OPTICAL POWER LEVELS

POWER CONSUMPTION

TEMPERATURE

NPU / LINE CARD CPU AND MEMORY

PLATFORM

JUNOS TELEMETRY INTEGRATION OPTIONS

Data Collection

Data Sources

Visualization / Analytics

OpenNTI

Potential integration

Customer

Application

Router

Other

Analytics

SPLUNK

Performance

Management

IBM Proviso

Infovista

CA

VistaInsight

PacketDesign

Monitoring

Cacti

MRTG

MX PTX

Northstar

Performance

Management

SevOne

QFX / EX

AppFormix

Juniper Applications

MIGRATIONINTRODUCING 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

Use Case:

• New domains being build with SPRING as transport

• Interworking of services with existing backbone

• Upgrading backbone to roll-out SPRING

PE

Existing LDP core

New SR core

SR upgraded region

PE

PE

LDP regionPEPE

Mapping Client Mapping Client/Server

LDP mapping client/server

SPRING & RSVP NETWORK

RSVP

SR

Northstar

RSVP subscription

adjust

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

Use-cases:

• SPRING in an existing RSVP network

• Traffic Mix – some traffic follows RSVP and some SPRING LSPs

SPRING simplifies network programmability

RECAP

Considerations when moving to SPRING based network

Juniper helps migrate to SPRING transport seamlessly