Transforming Evolved Programmable Networks CKN: New Capabilities in the Evolved Programmable Network (EPN) Greg Nehib, Senior Marketing Manager, Cisco Systems Bertrand Duvivier, Principal Engineer, Cisco Systems May 5, 2015
Existing Infrastructure Model Won t Scale to Address Network & Data Center Growth Programmable Physical Complex Static Silos Hardware Virtual Manual Processes Evolved Programmable Network Transforming to bond the Network, Data Center, & Applications 2
Entering a New Era in the SP Network Evolution Frame Relay DS0, DS1, DS3 Muxs PSTN ISDN ATM QAM IP Core $1,400,000,000,000 Service Provider Opportunity SMDS Edge X.25 in the Internet of Everything APPLICATIONS EVOLVED SERVICES PLATFORM Access / Agg IPv6 EVOLVED PROGRAMMABLE NETWORK TDM Era IP NGN Era 3
Cisco Service Provider Strategy An Open Network Architecture for Transforming Business through Innovation Cisco Services SMART SERVICE CAPABILITIES Applications Evolved Services Platform Business Services Service Profile Mobility Video Consumer Service Broker Orchestration Engine Catalog of Virtual Functions OPEN APIs OPEN APIs OPEN APIs OPEN APIs Evolved Programmable Network VNF Compute Storage VNF Network 4
Three New Capabilities for the EPN Transformation Tools Deploying Programmable Solutions - Application Engineered Routing Leveraging Physical Infrastructure - CPAK Line cards for the ASR 9000 Use of Virtualization - Virtual Routers with IOS-XRv IPv6 EVOLVED PROGRAMMABLE NETWORK 5
What makes Application Engineered Routing Unique? Tied to the Industry Leading Physical Routers ASR & NCS Families Highly Scalable, Mature Platforms, Proven Investment Protection Widespread Adoption across All Segments, High Quality Solutions Built-in Programmability NETCONF/YANG Support Orchestration via NSO (TailF) Network Simplification 100 to 1,000 times reduction in the number of TE Tunnels required in an MPLS network Built-in protection mechanisms What does it mean? Lowered CAPEX & OPEX with more features & deployment options 6
Application Engineered Routing
Networks need to be rethought Applications and Network interaction is key IP Core APPLICATIONS Edge EVOLVED SERVICES PLATFORM Acce ss/ Agg IPv6 EVOLVED PROGRAMMABLE NETWORK IP NGN Era Designed to support a set of services Designed to support any kind of services Static traffic patterns Dynamic traffic patterns Manual configuration (CLI) Automation (APIs, Controllers, ) Apps Independent of Network App & Network Interaction 8
Application Engineered Routing Definition Applications express requirements bandwidth, latency, SLAs 1 Application s Applications are mapped to a path defined by a list of segments 3 SDN Controller SDN controllers are capable of collecting data from the network topology, link states, link utilization, 2 Segment Routing (SW upgrade) The network only maintains segments No application state 9
Segment Routing
Velocity SR concept was proposed to operators in November 2012 Only two years have elapsed since the first public SR presentation and demo MPLS SDN world congress, March 2013 A lot happened, let s see! 11
IETF Segment Routing: a Cisco innovation with wide industry support www.segment-routing.net tools.ietf.org/wg/spring/ Strong partnership with lead operator group Strong commitment for standardization and multi-vendor support SPRING Working-Group Over 25 drafts maintained by SR team Over 50% are WG status Over 75% have a Cisco implementation Several interoperability reports are 12
Deployment In CY2015, SR will be deployed in all of these markets WEB SP Core/Edge SP Agg/Metro Large Enterprise 13
Key Concepts
Segment Routing Segment Routing Technical view Data Plane Path expressed in the packet Data Dynamic path MPLS (segment labels) IPv6 (+ SR extension header) Control Plane Routing protocols with extensions (IS-IS,OSPF, BGP) SDN controller ( BGP, PCEP, NETCONF/ YANG) Explicit path Paths options Dynamic (STP computation) Explicit (expressed in the packet) 15
IGP Prefix Segment Signaled by ISIS/ OSPF Shortest-path to the IGP prefix 12 10 2 4 Global SRGB + Index => 16000+5 = 16005 13 1 3 16005 6 5 7 SRGB: Segment Routing Global Block default 16000 14 11 DC (BGP-SR) WAN (IGP-SR) PEER 16
IGP Adjacency Segment Signaled by ISIS/ OSPF Forward on the IGP adjacency Local 12 13 10 1 124 2 4 7 1XY X is the from Y is the to 14 11 3 6 5 DC (BGP-SR) WAN (IGP-SR) PEER 17
Anycast Prefix Segment Same prefix advertised by multiple nodes Traffic is forwarded to one of the Anycast prefix-sids based on best IGP path If primary node fails, traffic is auto re-routed to the other node 12 10 13 11 14 DC (BGP-SR) 1 3 100 2 4 16100 6 5 100 WAN (IGP-SR) 7 PEER 18
BGP Prefix Segment Shortest-path to the BGP prefix Global Signaled by BGP 12 16001 10 2 4 Used in Large Scale Data Center where there is no IGP 13 1 3 6 5 7 14 11 DC (BGP-SR) WAN (IGP-SR) PEER 19
BGP Peering Segment Forward to the BGP peer Local 1XY 12 10 2 4 147 Low Lat, Low BW X is the from Y is the to Signaled to the controller by BGP- LS (topology information) 13 14 11 1 3 6 5 High Lat, High BW 7 DC (BGP-SR) WAN (IGP-SR) PEER 20
SDN Controller SDN controller collects via BGP-LS IGP segments BGP segments Topology 12 10 SDN Controller BGP-LS BGP-LS 2 4 Low Lat, Low BW 13 1 7 3 6 5 14 11 DC (BGP-SR) WAN (IGP-SR) PEER 21
An end-to-end path as a list of segments SDN controller computes that the green path can be encoded as 16002: IGP prefix SID 124: IGP Adj SID 147: BGP peering SID SDN controller programs a single per-flow state to create an applicationengineered end-toend policy 12 13 14 PCEP SR, Netconf SR, BGP SR-TE 10 11 DC (BGP-SR) {16002 124, 147} SDN Controller 1 3 2 4 50 6 5 Default ISIS cost metric: 10 WAN (IGP-SR) Low Lat, Low BW 7 PEER 22
Binding Segment SDN controller instructs edge to install an SRTE policy For this traffic, push this list of segments SDN controller defines the SRTE policy Explicit: it provides an explicit list of segments Dynamic: it provides optimization objective and constraints to the edge router. The edge router computes the list of segments to match these objectives. PCEP-request (SR Policy, low-latency, to 4) 200: pop and push {16002, 124} 1 PCEP-reply (OK, BSID: 200) 2 4 50 SDN Controller The edge router assigns a binding segment to the SRTE policy and installs it in dataplane Pop and Push the related list of segments Binding segment is local Controller collects binding segments and characteristics of the SRTE policies (e.g. PCEP) 3 6 5 Default ISIS cost metric: 10 Default Latency metric: 10 WAN 23
Application Engineered Routing Low-Latency to 7 for application A12 SDN Controller PeerSID: 147, Low Lat, Low BW Per-application flow engineering End-to-End DC, WAN, AGG, PEER Millions of flows No signaling No midpoint state No reclassification at boundaries The network scaling and simplicity is preserved 12 Push {16001, 200, 147} 13 14 10 11 DC (or AGG) Low-Lat to 4 1 3 200: pop and push {16002, 16004} BSID: 200 ISIS: 35 2 4 6 5 Default ISIS cost metric: 10 Default Latency metric: 10 WAN Low Lat, Low BW PeerSID: 147, High Lat, High BW 7 PEER 24
Incremental Deployment Use-Cases
IPv4/v6 VPN/Service transport IGP only No LDP, no RSVP-TE 16007 vpn ECMP pkt pkt Site1 1 2 3 vpn pkt 4 7 pkt 6 5 16007 Site2 vpn pkt 26
Seamless interworking with LDP Seamless deployment 16007 vpn pkt 2 3 LDP(7) vpn pkt vpn pkt pkt Site1 1 4 7 pkt 6 5 Site2 16007 vpn pkt 27
TILFA FRR 7 50msec FRR in any topology 16007 2 3 IGP Automated No LDP, no RSVP-TE pkt 1 4 Optimum Post-convergence path No midpoint backup state Detailed operator report S. Litkowski, B. Decraene, Orange Mate Design 16005 16007 pkt 6 5 16007 pkt How many backup segments Capacity analysis 28
Application Engineered Routing Cloud controller VTC Application controller WAN controller Provide automated 50ms protection in case of failure 4 End-end cross domain solution App DC WAN BR VTF ToR Leaf Spine DCI LSR BR Focus on main value: The application App 1 Classify Application flow and push SR segment list 2 Top segment provides ECMPpath to selected DCI Next segments implement WAN Policy: Capacity Latency Avoidance Disjointness 3 BR 5 Last segment selects egress peer Lower OPEX One system, Simple, Scalable Step by Step deployment And select Egress BR s 29
Application Engineered Routing Journey Adding value at your own pace Enable Segment Routing on the network (Software only) Insert Orchestration, SDN controller Benefits Network Simplification Connect with Cisco s and third party VNFs Network Resiliency End-User Experience Network Optimization Service Velocity E2E Application Control 30
Summary
Comcast s Converged Network is the strategic platform for delivering our Internet, Video, Voice, and Business products. As new advanced services are developed leveraging technologies like; Cloud and NFV, our network needs to simplify, scale and become extensible. We see IPv6 and Segment Routing as major elements in the evolution of the network. The ability of the network to support, not impede the innovation occurring in software and services, will be a major step forward. John Leddy, VP of Network Strategy, Comcast 32
Summary The EPN Transition Enabling Operators to Transform Their Business New EPN Solutions Programmability Application Engineered Routing Physical Scale ASR 9000 Virtual Scale IOS-XRv New Innovations Business Outcomes Availability Application Engineered Routing Today s Topic High Availability Virtualization with IOS-XRv 9000 Physical Scale with ASR 9000 HD Application Engineered Routing delivers: Network Simplification Network Programmability Shipping today: Application Engineered Routing Phase 1 (Segment Routing) 33
Stay Informed http://www.segment-routing.net/ ask-segment-routing@cisco.com www.linkedin.com segment routing group 34