Thank you for joining us today! The presentation will begin shortly. Thank you for your patience.

DemoFriday Logistics Enable pop-ups within your browser. Turn on your system s sound to hear the streaming presentation. Questions? Submit them to the Host at anytime in the chat box. Technical problems? Click Help or submit a question for assistance. Copyright 2012-201. SDNCentral LLC. All Rights Reserved October 30, 201

Jose L iste Derek Tay Scott Raynovich Technical Marketing Engineer Technical Marketing Engineer VP of Content & Research Cisco Cisco SDxCentral Copyright 2012-201. SDNCentral LLC. All Rights Reserved October 30, 201

Welcome to SDxCentral DemoFriday Realizing your WAN / MAN Orchestration dreams using SDN with Segment Routing Relevant Industries Who Should Attend? Key Takeaways Service Provider Enterprise Financial WEB / Over-The-Top (OTT) Network Engineer Network Operator Network Manger/Director/VP Product Manager Planning Team System Engineer Consulting System Engineer Software Engineer/Manager SDN WAN/MAN Orchestration is deployable and now Segment Routing provides simplicity and scalability by expressing explicit path in the packet Fully automated 0ms protection by is enabled by default Provide first strong step to the Unified Forwarding Plane and to Application Engineered Routing Copyright 2012-201. SDNCentral LLC. All Rights Reserved October 30, 201

Welcome to SDxCentral DemoFriday Realizing your WAN / MAN Orchestration dreams using SDN with Segment Routing Today s Demo: WAN optimization use case using SDN / Segment Routing Cisco s WAN Automation Engine (WAE) acting as a controller of an MPLS Segment Routing network Programmatic access to controller requesting instantiation forwarding policies using PCE-initiated Segment Routing Traffic Engineering (SR-TE) Scenarios with automatic re-optimization of existing paths triggered by network topology changes Copyright 2012-201. SDNCentral LLC. All Rights Reserved October 30, 201

WAN / MAN Orchestration using SDN Segment Routing Derek Tay, Jose Liste October 201

What is Segment Routing? Source Routing The source chooses a path and encodes it in the packet header as an ordered list of segments The rest of the network executes the encoded instructions without any further per-flow state Segment: an identifier for any type of instruction Forwarding or service Traffic Engineering with Segment Routing Distributed computation or Centralized No extra protocol (e.g. RSVP-TE) No midpoint state

Application Engineered Routing - with Segment Routing Provide automated 0ms protection in case of failure 4 Cloud controller Application controller WAN controller Provide automated 0ms protection in case of failure 4 End-end cross domain solution App DC WAN BR Focus on main value: The application VTF OVS ToR Spine Leaf DCI LSR BR App 1 Classify Application flow and push SR segment list 2 Top segment provides ECMPpath to selected DCI 3 Next segments implement WAN Policy: Capacity Latency Avoidance Disjointness BR Last segment selects egress peer Lower OPEX One system, Simple, Scalable Step by Step deployment And select Egress BR s

Demonstration Objectives In this demonstration you will experience the following: Cisco WAN Automation Engine (WAE) acting as Controller of an MPLS Segment Routing network built with ASR 9000 and XRv devices Programmatic access to Cisco WAE requesting instantiation of traffic engineering policies in the network Path Computation Element (PCE)-initiated Segment Routing Traffic Engineering (SR-TE) policies Automatic re-optimization of existing paths triggered by network topology changes (Link Failures and Link Performance Degradation)

Demo Components REST APIs APP WAE WAN Controller PCEP BGP-LS P1 CE1 PE1 PE2 CE2 IS-IS Segment Routing / MPLS network P2 BGP-LS = BGP Link State PCEP = Path Computation Element Protocol

Initial State 0 Using MPLS labels propagated via SR ISIS extensions, traffic CE1-CE2 travels over LSP following IGP best path Lo0 SID 16141 POP (PHP) 16042 0 30 P1 20 CE1 PE1 Lo0 SID 16041 0 PE2 Lo0 SID 16042 CE2 P2 Lo0 SID 16142 IGP metric = RED TE metric = BLUE

Application Request 1 APP 4 WAE 2 WAE computes path meeting constraints Path found!!! In-contract == cumulative TE metric = 20 1 4 REST API APP requests PATH PE1-PE2 with latency < 4 msec;; or otherwise lowest possible when out-of-contract WAE replies to APP Path found in-contract 16142 16042 3 WAE deploys path onto the network using PCEP Forwarding instructions in SR ERO: Follow IGP path to P2 then follow IGP path to PE2 P1 0 30 20 CE1 16142 PE1 POP (PHP) 0 PE2 Lo0 SID 16042 CE2 16042 P2 Lo0 SID 16142 POP (PHP) IGP metric = RED TE metric = BLUE

6 Link Failure 9 CE1 APP WAE deploys new path onto the network Forwarding instructions in SR ERO: Follow IGP path to P2 then follow low TE metric link P2-P1 then follow IGP path to PE2 Network self-heals in less than 0-msec Fast Reroute (TI-LFA) Optimal backup path No controller involvement!!! 16142 24000 16042 PE1 POP (PHP) 16142 24000 16042 0 30 P1 0 P2 WAE Lo0 SID 16142 7 20 Adj SID 24000 8 WAE reacts to topology changes Re-optimizes path in the network Path found!!! In-contract == cumulative TE metric = 40 No need to communicate to APP!!! BGP-LS update sent to WAE PE2 Lo0 SID 16042 Link Fails CE2 IGP metric = RED TE metric = BLUE Adj SID = Adjacency SID TI-LFA = Topology Independent Loop Free Alternate

Link Performance Degradation APP 1 WAE 13 WAE reacts to topology changes Re-optimizes path in the network Path found!!! Out-of-contract == cumulative TE metric = 0 1 14 WAE replies to APP Path found out-off-contract WAE deploys new path onto the network Forwarding instructions in SR-ERO: Follow low TE metric link PE1-P1 then follow IGP path to PE2 CE1 POP (PHP) 24003 16042 PE1 0 30 24003 16042 P1 0 12 20 TE DB update is propagated via BGP-LS to WAE PE2 CE2 Adj SID 24003 Excessive Link Delay e.g. 60 msec 11 Router adjusts TE metric P2 Lo0 SID 16142 IGP metric = RED TE metric = BLUE TI-LFA = Topology Independent Loop Free Alternate

Summary In this demonstration you experienced the following: Application programming the Segment Routing network to deliver traffic through WAN Cisco WAN Automation Engine (WAE) acting as a WAN Controller Path Computation Element used to instantiate SR-TE policies Automatic 0ms protection in case of failures Automatic re-optimization of existing paths triggered by network topology changes

Thank you.