SDN Controllers in the WAN Julian Lucek jlucekjuniper

  • Slides: 27
Download presentation
SDN Controllers in the WAN Julian Lucek jlucek@juniper. net @julianlucek © 2019 Juniper Networks

SDN Controllers in the WAN Julian Lucek jlucek@juniper. net @julianlucek © 2019 Juniper Networks

AGENDA Introduction to SDN Controller for WAN Towards Self-Driving with Closed Loop Automation Automated

AGENDA Introduction to SDN Controller for WAN Towards Self-Driving with Closed Loop Automation Automated Congestion Avoidance Dynamic Minimum Latency Path Self-Driving Egress Peering Engineering Automated Network Self-Healing P 2 MP Traffic Engineering © 2019 Juniper Networks 2

WAN CONTROLLER CONCEPT Requests via GUI Requests via Northbound REST API • Creation of

WAN CONTROLLER CONCEPT Requests via GUI Requests via Northbound REST API • Creation of LSPs according to service requirements. • Placement of LSP paths according to traffic demands. Controller Real-time topology (BGP-LS) Streaming Telemetry LSP status (PCEP) TE LSP creation/modification (PCEP, BGP SR-TE) MPLS Network © 2019 Juniper Networks • Automation of network operations.

TOPOLOGY DISCOVERY USING BGP-LS B F D BW=100 A H Adj-SID = 78 Admin-group:

TOPOLOGY DISCOVERY USING BGP-LS B F D BW=100 A H Adj-SID = 78 Admin-group: green K E SRLG 200 G C J Red-dashed zones denote IGP areas In practice, 2+ RR’s for resilience RR At least one BGP-LS session into each IGP area BGP-LS session Controller © 2019 Juniper Networks

PATH COMPUTATION ELEMENT PROTOCOL (PCEP) PCEP § PCE: Path Computation Element PCE Computes the

PATH COMPUTATION ELEMENT PROTOCOL (PCEP) PCEP § PCE: Path Computation Element PCE Computes the path PCEP PCC § PCC: Path Computation Client Receives the path. Sets up LSP using RSVP or Segment Routing. § PCEP: PCE Protocol (RFC 5440) PCC © 2019 Juniper Networks For PCE/PCC communication

CLOSED-LOOP AUTOMATION + User intent WAN Controller X Disturbances (Outages, Congestion etc) The Network

CLOSED-LOOP AUTOMATION + User intent WAN Controller X Disturbances (Outages, Congestion etc) The Network - Network state Measured output Streaming Telemetry Traffic on each link Traffic on each LSP Link latency data Packet loss stats Streaming Telemetry allows much more frequent updates than SNMP. Push paradigm, rather than request/response. Stats collected on linecard are sent directly from there without passing through control processor. © 2019 Juniper Networks

AUTOMATED ACTIONS, BASED ON LINK UTILISATION (1) Controller knows via Streaming Telemetry that red

AUTOMATED ACTIONS, BASED ON LINK UTILISATION (1) Controller knows via Streaming Telemetry that red link is currently experiencing high utilization © 2019 Juniper Networks

AUTOMATED ACTIONS, BASED ON LINK UTILISATION (2) Controller also knows via Streaming Telemetry how

AUTOMATED ACTIONS, BASED ON LINK UTILISATION (2) Controller also knows via Streaming Telemetry how much traffic is travelling on each LSP So it automatically moves away some LSPs from the congested link © 2019 Juniper Networks

PROGRAMMABLE COST FUNCTION Cost function = lowest IGP metric path that meets the required

PROGRAMMABLE COST FUNCTION Cost function = lowest IGP metric path that meets the required path constraints (BW etc) 15 15 10 X 10 10 Y Lowest IGP metric path Blue numbers show IGP metric © 2019 Juniper Networks

MINIMUM LATENCY PATH 10 10 11 X 11 10 Lowest latency path © 2019

MINIMUM LATENCY PATH 10 10 11 X 11 10 Lowest latency path © 2019 Juniper Networks Y Red numbers show latency of each link

MINIMUM LATENCY PATH Latency has increased Controller automatically moves minimum-latency LSP onto the lowest

MINIMUM LATENCY PATH Latency has increased Controller automatically moves minimum-latency LSP onto the lowest latency path 15 10 10 10 11 X 11 10 Lowest latency path © 2019 Juniper Networks Y Red numbers show latency of each link

AUTOMATED SELF-HEALING App. Formix 3. REST API call: North. Star WAN Maintenance Controller interval

AUTOMATED SELF-HEALING App. Formix 3. REST API call: North. Star WAN Maintenance Controller interval on Link L 1 4. WAN Controller recomputes paths of all TE LSPs that pass through Link L 1, and sends PCEP messages to corresponding ingress routers to change the paths accordingly 2. App. Formix determines that Link L 1 is unhealthy 1. Streaming Telemetry from all network nodes © 2019 Juniper Networks L 1

AUTOMATED SELF-HEALING App. Formix 3. REST API call: North. Star WAN Maintenance Controller interval

AUTOMATED SELF-HEALING App. Formix 3. REST API call: North. Star WAN Maintenance Controller interval on Link L 1 4. WAN Controller recomputes paths of all TE LSPs that pass through Link L 1, and sends PCEP messages to corresponding ingress routers to change the paths accordingly 2. App. Formix determines that Link L 1 is unhealthy 1. Streaming Telemetry from all network nodes © 2019 Juniper Networks L 1 https: //forums. juniper. net/t 5/Industry-Solutions-and-Trends/Enabling-rapid-remediation-in-the-Self -Driving-Network/ba-p/321375

SELF-DRIVING EGRESS PEERING ENGINEERING © 2019 Juniper Networks 14

SELF-DRIVING EGRESS PEERING ENGINEERING © 2019 Juniper Networks 14

SELF-DRIVING EGRESS PEERING ENGINEERING (EPE) prefix X Each PE sends flow stats to Controller

SELF-DRIVING EGRESS PEERING ENGINEERING (EPE) prefix X Each PE sends flow stats to Controller - how much traffic the PE is sending to each destination prefix. ASBR G ASBR E ASBR 1 ASBR F Controller decides which {egress link, egress ASBR} each PE should use to send traffic to prefix X. ASBR 2 PE 1 PE 4 PE 2 © 2019 Juniper Networks Cost function based on: • cost to reach ASBR • cost of using each peering link • current utilisation of each peering link • user-defined preferences PE 3 15

SELF-DRIVING EGRESS PEERING ENGINEERING (EPE) prefix X Peering link on ASBR 1 is approaching

SELF-DRIVING EGRESS PEERING ENGINEERING (EPE) prefix X Peering link on ASBR 1 is approaching congestion outbound. ASBR G ASBR E ASBR 1 ASBR F Controller moves traffic from PE 2 to prefix X onto one of the peering links on ASBR 2 PE 1 PE 4 PE 2 © 2019 Juniper Networks PE 3 16

EPE INGREDIENTS: PEER-SID • ID ASBR B S de IP 200 • o r.

EPE INGREDIENTS: PEER-SID • ID ASBR B S de IP 200 • o r. N e Pe 100 = • IP Peer. Node SID = 200 ASBR A ASBR C • ID ID j. S r. Ad Pee 0 0 =4 j. S r. Ad Pee 0 0 =3 SID values manually configured on ASBR A Advertised via BGP-LS to North. Star SID label steers packet towards desired peering link ASBR A pops label, so plain IP packet is sent on the peering link ASBR D © 2019 Juniper Networks 17

SELF-DRIVING EGRESS PEERING ENGINEERING (EPE) prefix X ASBR G Traffic to Prefix X from

SELF-DRIVING EGRESS PEERING ENGINEERING (EPE) prefix X ASBR G Traffic to Prefix X from PE 2 uses the SR-TE tunnel shown in red, which has been computed and instantiated by the Controller. ASBR F ASBR E 30 0 ASBR 1 ASBR 2 26 This tunnel steers the traffic across the core to ASBR 2, and then onto the peering link to ASBR F 17 58 PE 1 PE 4 PE 2 PE 3 SR-TE tunnel: Push 300, Push 26, Push 58, Push 17 (top), NH=ASBR 2 © 2019 Juniper Networks 18

P 2 MP LSPS WITH WAN CONTROLLER © 2019 Juniper Networks 19

P 2 MP LSPS WITH WAN CONTROLLER © 2019 Juniper Networks 19

P 2 MP LSP PATH DIVERSITY Multicast Source • Diversely routed P 2 MP

P 2 MP LSP PATH DIVERSITY Multicast Source • Diversely routed P 2 MP LSPs Receiver at Site A © 2019 Juniper Networks Controller performs diverse path computation and then instantiates the P 2 MP LSPs using PCEP Applications: • • • Receiver at Site B Broadcast TV Financial Market Data Air Traffic Radar

P 2 MP LSP: PHYSICAL LAYOUT © 2019 Juniper Networks 21

P 2 MP LSP: PHYSICAL LAYOUT © 2019 Juniper Networks 21

P 2 MP LSP: LOGICAL LAYOUT © 2019 Juniper Networks 22

P 2 MP LSP: LOGICAL LAYOUT © 2019 Juniper Networks 22

North. Star P 2 MP LSP deployment in SKY Source: IBC 2019 Showcase Theatre,

North. Star P 2 MP LSP deployment in SKY Source: IBC 2019 Showcase Theatre, http: //vsf. tv/events_archive/2019 -09_IBC 2019/Tuesday/Massimo%20 Magnani%20 -%20 IBC%202019%2 -%20 JNPR%20 SKYTV%20 NS%20 Controller%20 in%20 M&B%20 Networks%20 IBC 2019%20 v 9. pdf 23

North. Star P 2 MP LSP deployment in SKY Source: IBC 2019 Showcase Theatre,

North. Star P 2 MP LSP deployment in SKY Source: IBC 2019 Showcase Theatre, http: //vsf. tv/events_archive/2019 -09_IBC 2019/Tuesday/Massimo%20 Magnani%20 -%20 IBC%202019%20%20 JNPR%20 SKYTV%20 NS%20 Controller%20 in%20 M&B%20 Networks%20 IBC 2019%20 v 9. pdf 24

North. Star P 2 MP LSP deployment in SKY Source: IBC 2019 Showcase Theatre,

North. Star P 2 MP LSP deployment in SKY Source: IBC 2019 Showcase Theatre, http: //vsf. tv/events_archive/2019 -09_IBC 2019/Tuesday/Massimo%20 Magnani%20 -%20 IBC%202019%20%20 JNPR%20 SKYTV%20 NS%20 Controller%20 in%20 M&B%20 Networks%20 IBC 2019%20 v 9. pdf 25

USEFUL REFERENCES • North. Star Controller documentation • https: //www. juniper. net/documentation/product/en_US/northstar-controller • Blogs

USEFUL REFERENCES • North. Star Controller documentation • https: //www. juniper. net/documentation/product/en_US/northstar-controller • Blogs at https: //forums. juniper. net/t 5/user/viewprofilepage/user-id/24095 • Nanog presentation • https: //www. youtube. com/watch? v=vz. F 6 T 5 Jl 3 Qg • PCEP and BGP-LS deep-dive webinar • https: //www. ipspace. net/PCEP_and_BGP-LS_Deep_Dive © 2019 Juniper Networks

THANK YOU! © 2019 Juniper Networks

THANK YOU! © 2019 Juniper Networks