1 | © 2015 Infinera Open SDN in Metro P-OTS Networks Sten Nordell CTO Metro Business Group

2 | © 2015 Infinera The New Network for a Software-driven World Old Model API – SDN Control New Simplified Model Services Network Functions Virtualized into Cloud Transport Functions Scale, Convergence, Software-Controlled Intelligent Transport Firewall SBC B-RAS MPLS PE L2/3 Packet Layer 1 OTN Layer 0 WDM Layered Network Dynamic Intelligent BW Network Efficiency Intelligent Automation App-Driven Performance

3 | © 2015 Infinera The evolution of Native Packet Optical in the Metro Native Packet Optical 1.0 Layer 1 Layer 2 Native Packet Optical 2.0 OTN Ethernet MPLS-TPCE2.0 Native Packet Optical 3.0

4 | © 2015 Infinera Metro P-OTS SDN 2.0 key characteristics  Open SDN architecture Open Source Software Open platform with added value Feature velocity driven OpenFlow based  Open APIs providing interoperability between transport layers  Built for Metro P-OTS networks Each switch instance controlled individually Node level for infrastructure  Scalable and distributed SDN controller architecture SDN

5 | © 2015 Infinera What applications are we focusing on?  Service oriented transport SDN apps Bandwidth On demand Flexible Calendaring Instant  Service chaining  Multi-layer coordination  L0 to L3 applications and services  Open APIs for network programmability

6 | © 2015 Infinera Metro P-OTS SDN 2.0 Overview OpenFlow 1.3 (+Extensions) REST APIs MEF Connectivity MEF Connectivity Host Discovery Simple DHCP Server Simple DHCP Server Policers vRouter Bandwidth Calendaring Bandwidth Calendaring Network Tap Network Tap Statistics Controller TNM SDN Web app Hardware Control Layer UI

7 | © 2015 Infinera Application examples

8 | © 2015 Infinera What:  Adjust services’ bandwidth levels freely and live Why:  Allows the operator to dynamically adjust bandwidth based on customers requests Flexible bandwidth E-LINE CE A CE B Video Source Video Source Video Display Video Display

9 | © 2015 Infinera What:  Define bandwidth limits based on date and time Why:  Define services providing more bandwidth when utilization is low (off-hours)  Define services only used at scheduled intervals Bandwidth Calendaring Network wide Utilization Time 00:0023:0012:0006:0018:00 0% 100% 50% Threshold Time 00:0023:0012:0006:0018:00 Bandwidth Calendar for Customer X 0% 100% 50% E-LINE CE A CE B

10 | © 2015 Infinera What:  Possibility to optimize the route of existing services Why:  Provides freed-up resources and improved services  Avoid sub-optimal routing as a result of changed network topology Optimize services CE Better path CE Existing path

11 | © 2015 Infinera What:  Operator provides a number of ports for connectivity between sites Why:  Customer can choose to connect or disconnect network ports  Customer get automated service realization by connecting end- point devices Instant services scenario E-LINE CE B CE A

12 | © 2015 Infinera What:  Enables services definitions to be bound up with a customer rather than to a physical network location Why:  Improving operational efficiency  Services follow the customer – e.g. when moving its offices  increases customer satisfaction EDU / Host mobility CE

13 | © 2015 Infinera What:  Basic level of protection provided without additional configuration of rings or linear protection Why:  Automated service restoration in case of faults/fiber break Automatic Restoration CE

14 | © 2015 Infinera What:  Tell network to re-route services away from a network element using a ”make-before-break” approach Why  Allows operator to remove traffic from a given element using a hitless approach Reduces network impact of a planned upgrade or replacement Redirect / Reroute services CE Alternative path CE Upgrade target

15 | © 2015 Infinera Virtualization SDN based vRouter in Metro P-OTS

16 | © 2015 Infinera Goal Physical topology Router topology vRouter IP Traffic

17 | © 2015 Infinera vRouter – How OSPF PDUs Routing Table Controller Forwarding Entries  Picks up control plane traffic: From each router neighbor For example OSPF packets  Passes the control packet to routing engine: And sends back packets to edges  Routing engine computes routing table Which is turned into forwarding rules vRouter OSPF ISIS Data flow

18 | © 2015 Infinera vRouter – Why – Mobile backhaul Link for protection  Without vRouter: All traffic goes to the core router Traffic between edge routers Even traffic that could go between ports in the switch  With vRouter: Enables effective routing between routers Traffic is no longer routed via core router Limited configuration needed for the vRouter. IS-IS would require no configuration Any change in router configuration reflected in vRouter

19 | © 2015 Infinera vRouter – Why – Smart aggregation  Without vRouter: Each client interface adds a port specific vlan Router has one vlan interface per client interface on port aggregation device All traffic goes to router Even traffic that could go between ports in switch Event traffic that could go between aggregation switches  With vRouter: One vRouter is created over the aggregation switches in the network All metro flows are handled efficiently Port to port flows Flows between aggregation switches Same operational model for vRouter as in routers L2 service can still be provided in parallel CE VLAN Flows CE

20 | © 2015 Infinera vRouter for Metro P-OTS SDN 2.0 on existing EMXPs Supported on existing EMXP family and PT-Fabric Core network agnostic Packet over OTU MPLS-TP over Ethernet Native Ethernet L3 Services  Internet  L3VPN  IPTV Mobile services  3G  LTE IP Router Mobile SGW OTN (switching grooming) MPLS (LSRs LERs) Ethernet (SVLAN, ERPS, …) WDM foundation - Flexible Optical Networks L2 services  E-Line  E-LAN  E-Tree  E-Access L3 services  VPN  Provider Edge  Service chaining

21 | © 2015 Infinera Summary Open SDN in Metro P-OTS Networks  Open SDN architecture OpenFlow based Native Packet Optical Open APIs for network programmability  Applications oriented for metro transport services Bandwidth on demand Service chaining Multi-layer coordination Supporting Layer 0 to Layer 3 services

22 | © 2015 Infinera Thank you