Marketing Presentation Evolving the SP Network Infrastructure Speaker Name Dennis Cai Designation Speaker Name Distinguished Engineer, SP Infrastructure Team Designation Date: 00/00/0000 05/2015 Date: 00/00/0000

Agenda Evolving the SP Network Infrastructure The Technology Innovations Segment Routing x-EVPN The Architecture Evolution: ACE (Agile Carrier Ethernet)

Cisco Open Network Architecture Vision Applications / OSS/BSS Service Model Evolved Service Platform Device Model Evolved Programmable Network Network Storage Compute

Cisco’s Unified SDN Architecture for SP Network Infrastructure Cross Domain Orchestration (Tail-f NSO) Domain / functional APIs ESP Multi-layer WAN SDN (WAE, ODL) CPE Metro access Control (WAE, ODL) Data Center SDN (APIC, VTS) CPE Metro and Access WAN Data Centre EPN Transport Optical

Smooth Transition to the Future Network Infrastructure Service Agility: Fully Programmable Optimized and Application-aware Routing PnP of the BW capacity Network Infrastructure as Platform Future ? Operational Complexity Vendor Specific OS Integrated HW and SW Back-compatible Inter-operable Multi-services Service SLA Operation, Visibility Now Investment protection Device-Centric

Let’s start with SDN… driven by different business interest CP/DP separation white box NFV Openstack Programmable Controllers ODL … openflow

What Our Customers Care? Services, Application Service agility Business outcome … OPEN API Device-centric  Network as Platform Routers Switches R S Individual boxes, Cisco, Juniper, XR, XE, J, A, H … FB Controller Box is PnP, with limited local function Low OPEX and CAPEX

From Device Centric to Network-as-Platform Network-wide orchestration replaces the individual device config. This allows network wide service definition and deployment Orchestration The SDN controller behaves like a centralized control plane for network wide policy & control. Examples of network wide policies include application-aware routing, multi- layer traffic optimization, bandwidth calendaring & scheduling. SDN Controller Config Plane Control Plane Data Plane Device centric view What need on the device? Packet forwarding Efficient route distribution Rapid convergence with local failure detection and repair Local features: L1 features, OAM/PM, QoS, Timing, mcast replication … Network-wide view

It will be a long journey … Next Future Phase Now Orchestration SDN Controller Tail-f NSO Orchestration Tail-f NSO Orchestration SDN Controller Tail-f NSO WAE WAE XRv+ODL Reduced control plane on device Minimal control plane on device Full control plane on device Reduced Control Plane on Device AN: Autonomic Networking SR: Segment Routing X-EVPN Centralized service provisioning Work with existing network devices Network as Platform Fully programmable Device is PnP component With minimal local intelligence on device

Agenda Evolving the SP Network Infrastructure The Technology Innovations Segment Routing x-EVPN The Architecture Evolution: ACE (Agile Carrier Ethernet)

Introduce Segment Routing (1) Segment Routing is a Source Routing The source chooses a path and encodes it in the packet header as an ordered list of segments (Segment could be MPLS label or IPv6 address) The rest of the network executes the encoded instructions without any further per-flow state The intelligence is on the source router, while the rest of the routers can be kept very simple Source router intelligence is programmed by the external controller Application-engineered routing Seamless integration between network and controllers Simplify the MPLS and Routing

Introduce Segment Routing (2) Right Balance Distributed Is there middle ground? Centralized It’s right balance between distributed routing intelligence on the router and the centralized intelligence on the controller Router keep minimal local intelligence for features such as fast local re-route, shortest path forwarding within the local routing domain Complex inter-domain routing and application-aware routing are moved to controller to keep router as simple as possible

Introduce Segment Routing (3) Data Plane MPLS (segment ID = label) IPv6 (segment ID = V6 address) Data 7 46 4 Explicit loose path for low latency app Data 7 Dynamic path Control Plane Routing protocols with extensions (IS-IS,OSPF, BGP) SDN controller R1 SID: 1 R3 SID: 3 R5 SID: 5 No LDP, no RSVP-TE Explicit path R7 SID: 7 Paths options Dynamic (STP computation) Explicit (expressed in the packet) High cost Low latency Adj SID: 46 R2 SID: 2 R4 SID: 4 R6 SID: 6 Strict or loose path SID: Segment ID

Strong Operator Partnership and Demand Strong partnership with the Tier-1 SP and WEB customers: over 30 operators involved Real customer deployment across market segments in CY15 WEB Strong commitment for standardization and multi-vendor support SP Core/Edge SPRING Working-Group All key documents are WG-status Over 25 drafts maintained by SR team Over 50% are WG status Over 75% have a Cisco implementation Several interop reports are available SP Agg/Metro Large Enterprise

Collect information from network Business Asks: Application-engineered Routing and Bandwidth Optimization Controller Program network Business Asks: Differentiate service for application needs Monetize the expensive peering links The Solution Application-engineered Routing How? controller intelligence + rapid network response in a simple and scalable way Collect information from network 12 8 90% usage 10 2 4 Low Lat, Low BW 50 Low latency Low bandwidth 1 40% 7 13 3 6 5 High latency High bandwidth 11 14 Default ISIS cost metric: 10 DC WAN PEER ISP Existing RSVP-TE traffic engineering is static, complex and not scale, which can’t meet the application-engineered requirement

Collect information from network The Solution: Segment Routing Application-engineered Routing and Bandwidth Optimization Controller Program network Controller learn the network topology and usage dynamically Controller calculate the optimized path for different applications: low latency, or high bandwidth Controller just program a list of the labels on the source routers. The rest of the network is not aware: no signaling, no state information  simple and Scalable {16001, 16002, 124, 147} Collect information from network Node SID: 16002 12 Adj SID: 124 8 90% usage 10 Node SID: 16001 2 4 Low Lat, Low BW 50 Low latency Low bandwidth 1 40% Peering SID: 147 7 13 {124, 147} {147} {16002, 124, 147} 3 6 5 High latency High bandwidth 11 14 Default ISIS cost metric: 10 DC WAN PEER

The Challenging of the existing L2VPN Service Network inefficiency Flood-and-learn, broadcast storm Active/Standby forwarding, can’t achieve per-flow load balancing like L3 service Signaling for pseudowire, not scalable Different operational models L3VPN and L2VPN works in different way Different type of the L2VPN: manual configuration, BGP auto-discovery, BGP signaling, LDP signaling, etc MPLS data plane vs. IP data plane Lack of programmability and policy control MAC learning happen at data plane Can’t have policy control per MAC address Difficult to be programmable First, let’s have a quick review of some of the challenging of the L2VPN service:

Why yet-another-VPN? Introducing MAC Routing: Ethernet VPN (EVPN) Control plane: BGP MAC Routing BGP advertise and learn the customer MAC address IP or MPLS PE1 CE1 PE2 PE3 CE3 PE4 Network Efficiency Single active multi-homing All active multi-homing Common L2/L3 VPN Operational Mode Flexible Policy Control C-MAC: M1 Consolidated VPN service with x-EVPN Data Plane: IP or MPLS, flexible

EVPN is next generation all-in-one VPN solution What is x-EVPN ? EVPN is next generation all-in-one VPN solution E-LAN (MP2MP L2VPN) E-LINE (P2P L2VPN) E-TREE (P2MP L2VPN) DC Fabric (IntraDC Overlay) IRB (L2/L3 Overlay) DCI (InterDC) IP-VPN (L3VPN) VPLS PW VPLS-ETREE VPLS,OTV 4364 EVPN (PBB-) EVPN EVPN VPWS EVPN ETREE EVPN- Overlay EVPN-IRB EVPN DCI EVPN-IRB

Converge the VPN Service to x-EVPN Common BGP Control Plane Evolution SP L2VPN & IP-VPN EVPN/EVPN-VPWS (MPLS, PBB, VXLAN) DCI EVPN/IP-VPN (VXLAN, MPLS) DC Fabric EVPN (VXLAN: L2 and L3) Smooth Migration Data Center 1 WAN/Core SP Acc/Agg Client SP DC bLeaf Leaf Spine Data Center 2 DC Gateway service SP Edge DCI Inter-operability SP L2VPN & IP-VPN EoMPLS, VPLS (T-LDP, BGP signaling, BGP AD) DCI VPLS, OTV IP-VPN DC Fabric Legacy VLAN, FP, Trill Existing

Agenda Evolving the SP Network Infrastructure The Technology Innovations Segment Routing x-EVPN The Architecture Evolution: ACE (Agile Carrier Ethernet)

Introduce the ACE (Agile Carrier Ethernet) Phase 1 Phase 2 Now Orchestration SDN Controller Tail-f NSO Orchestration Tail-f NSO Orchestration SDN Controller Tail-f NSO WAE WAE XRv+ODL On Device Minimal but sufficient AN: Autonomic Networking SR: Segment Routing VPN services (BGP/T-LDPor static) Centralized service provisioning Work with existing network devices Network as Platform Fully programmable Device is PnP component With minimal local intelligence

The Existing Solutions … MPLS-TP Unified MPLS Model L2 Bridging Model SDN SDN Controller SDN Model API Aggregation Control Plane and Data Plane Separation Access REP, G.8032, STP 802.1q/.1ad/.1ah Access Aggregation Access Aggregation Fully distributed IP/MPLS control plane Fully distributed Layer 2 control plane Complex Network Operation Simple ? Flexible and scalable Multi-Service Architecture Unified operation across domains Optimized forwarding Complex to operate and manage Simple, plug & play It only supports Ethernet services Not scalable No A/A load balancing BUM Complex across L2/L3 domains …

Our Vision: the Agile Carrier Ethernet ? ? Balance Distributed Is there middle ground? Centralized Service: Controller Controller Transport: Segment Routing Open API Auto-discovery Autonomic Network Infrastructure Minimal but “Sufficient” distributed control plane on network nodes w Centralized intelligence on the SDN service controller

Autonomic Networking: Secure, Plug-n-Play Plug-n-Play: New node use v6 link local address to build adjacency with existing nodes, no initial configuration is required Secure: New node is authenticated using its SUID, and then build encrypted tunnel with its adjacent nodes Always-on VOOB: Consistent reachability between Controller and network devices over Virtual Out-of- band management VRF. Even with user mis-configuration, the VOOB will still remain up AAA Misconfig / Routing Misconfig Registrar Dark Layer 2 Cloud ` Michael Steve

ACE Transport: Unified MPLS with Segment Routing Unified MPLS with SR Isolated network domains BUT with common IP/MPLS technology using segment routing SDN controlled inter-domain for end-to-end routing Common operational model and common policy control No network boundary due to different technologies, simple solution for network high availability Back compatible with existing network: LDP/RSVP-TE, RFC 3107 Tail-f, WAE Tail-f, WAE Core island B  A [GW2, GW1, A] AB: [GW1, GW2, B] Access GW1 GW2 Access A Aggregation Core Aggregation B GW1 GW2 Metro island DC Metro island DC island

ACE Service: Unified VPN Service Model Unified VPN simple service model P2P L2VPN: provisioned by controller MP L2VPN: x-EVPN technology L3VPN: centralized on the GW node using PWHE virtual interface PW P2P L2VPN PW x-VPN PW MP L2VPN PW IP-VPN PW L3VPN PWHE PWHE Tail-f VPN service provisioning Access GW1 GW2 Access A Aggregation Core Aggregation B GW1 GW2

ACE Phase 2: Centralized Control Plane w Controller Controller run centralized service control plane (BGP, T-LDP) on-behalf-of network nodes Controller program the RIB/FIB to the network node for the optimized forwarding Tail-f NSO controller for end-to-end service provisioning Tail-f VPN service provisioning x-VPN, IP-VPN Controller Controller Access GW1 GW2 Access A Aggregation Core Aggregation B GW1 GW2 One Single XR Virtual Router One Single XR Virtual Router

Is Openflow the answer? The classic SDN story: Full control plane and data plane separation Network box has no intelligence Network is simplified dramatically SDN Controller OpenFlow Flow Tables Commoditized forwarding box But wait, how about service and service SLA? Does it support all the services ? Does it support high availability? How scalable it’s? how fast to program in a large network How does it inter-operate with my existing network? …

Our Vision (5 years ago): nV Satellite One virtual Router nV Satellite: Full control plane and data plane separation Centralized control plane on Host Satellite box has no/little intelligence Satellite Protocol Satellite Host AND, full service and service SLA support All existing service by IOS-XR asr9k Network fast reroute Regular router function, inter-operate with existing network Similar operation mode Simple port extender (OF switch) Centralized control plane (Controller) But …

The Market Adoption of the nV Satellite Solution One of the most successful innovation from Cisco Extremely Fast Ramp: 300+ customers worldwide in 2+ years Major Tier-1 SP across markets: Cable/MSO, Telco, Mobile, Carrier Ethernet, Enterprise

nV Satellite Evolution High Dense 10G Satellite Topology expansion Feature offload

The Evolution of the nV Satellite Architecture Existing nV Satellite Controller based nV System Centralized forwarding on Host No local forwarding Local FIB download Optimized forwarding Proprietary SACP, MACinMAC fabric Limited topologies support Standard based fabric Any network topology Feature offload Fully coupled with Host function Big engineering effort Light feature offload Provisioning with Netconf/yang Centralized control plane on Host Control plane scale limited by Physical chassis Centralized service control plane on XRv XRv scale out Cisco proprietary solution Big effort to support new HW as satellite Open, Standard solution 3rd party device, minimal effort as satellite

CAPEX Saving with limited features and low scale on the FB Callisto: Controller-based nV System Concept Single interface to provision Controller XR Control Plane Controller Add new BW capacity Simple operation: PnP ODL Provisioning RIB distribution Telemetry Fabric manager CAPEX Saving with limited features and low scale on the FB Standard APIs Feature provisioning FIB/RIB programming Forwarding Boxes FB FB FB FB FB FB One Single XR Virtual Router

Evolving to the Future Network Infrastructure Tail-f NSO WAE Tail-f NSO XRv+ODL Future WAE ODL+App Network Infrastructure as Platform Centralized Provisioning Controller Intelligence Centralized Provisioning Protocol Evolution Segment Routing, x-EVPN, Autonomic Networking Tail-f NSO Now

Q&A