Agenda

1. OpenflowY SDNFundamentos de Open Networking. Soluciones Open FlowMiguel Angel Rodríguez Fernándezmarodriguez@juniper.net

2. Agenda ARQUITECTURA SDN INTRODUCCION a Openflow CasosPrácticos

3. ARQUITECTURA SDN

4. En la actualidad:Cajascerradas y Protocolosdistribuidos Operating System App App App Specialized Packet Forwarding Hardware Operating System App App App Specialized Packet Forwarding Hardware Operating System Specialized Packet Forwarding Hardware Operating System App App App App App App Specialized Packet Forwarding Hardware Operating System Specialized Packet Forwarding Hardware 4 App App App

5. Un Acercamiento a “Software Defined Networking” App App App Network Operating System App App App App App App Operating System Specialized Packet Forwarding Hardware Operating System Specialized Packet Forwarding Hardware App App App App App App Operating System Specialized Packet Forwarding Hardware Operating System Specialized Packet Forwarding Hardware App App App Operating System Specialized Packet Forwarding Hardware 5

6. El Concepto“Software-defined Network” 3. Well-defined open API 2. At least one good operating system Extensible, possibly open-source App App App 1. Open interface to hardware Network Operating System Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware Simple Packet Forwarding Hardware 6

7. Software Defined Networking (SDN) • Los principalesobjetivos de SDN • Abstraer los elementos de la Red desde las Aplicaciones. • Control y Gestióncentralizadad de los dispositivos de red de diferentesfabricantes. • Teneruna Red abiertaquepermita ser programable y crearservicios de forma sencilla. • SDN esunaarquitecturaque divide el plano de conmutación y permiteque sea programable de una forma directa. LAS REDES ABIERTAS ADOPTARAN MAYORES INNOVACIONES.

8. Arquitectura SDN

9. Introducción aOpenflow

10. Plano de Control separado del plano de conmutación Plano de Control Centralizado. OpenFlowcontroller(La plataforma). Lógicamentecentralizada y fisicamentedistribuida. Plano de conmutación distribuido. OpenFlow switches (Pueden serrouters,firewalls). No esnecesariotenerprotocolos de routing . Software (kernel, hypervisor, userspace), Hardware (merchant silicon, ASICs, OpenFlow optimized ASICs) OpenFlowes el protocolo entre el plano de control y de conmutación. Aproximación a openflow

11. Plano de Control centralizado y conmutacióndistribuido. • OpenFlow controller • Plano de control centralizado • OpenFlow protocol • OpenFlow switch • Plano de conmutación

12. Arquitectura de un openflow controller Applications Replication Scheduler Data Center Multi Tenancy Load Balancer API (not standard) Basic Services Infrastructure Inventory Topology discovery Path computation Event dispatching GUI Protocol Engines CLI OpenFlow OF-Config FlowVisor (network partitioning)

13. EVOLUCION A OFN OpenFlow Controller Distributed control plane Control Process Secure Channel Simple Controller Forwarding Table Forwarding/Flow Dispatch Table Traditional Router/Switch OpenFlow Router/Switch

14. MAC src MAC dst IP Src IP Dst TCP sport TCP dport * * * 5.6.7.8 * * port 1 Action Ejemplo de OpenFlow Controller PC OpenFlow Client Software Layer Flow Table Hardware Layer port 2 port 1 port 3 port 4 5.6.7.8 1.2.3.4

15. Trestipos de mensajes y cadamensaje con múltiplessubtipos.:, controller-to-switch, asynchronousy symmetric. Controller-to-switch messages are initiated by the controller and used to directly manage or inspect the state of the switch. Features (query capabilities), modify-state(add/delete/modify flow/group entry), read-state, packet-out Asynchronous messages are initiated by the switch and used to update the controller of network events and changes to the switch state. Such as flow-removed, packet-in, port-status Symmetric messages are initiated by either the switch or the controller and sent without solicitation. hello, echo (request/reply), experimenter TIPOS DE MENSAJES

16. OpenFlow Basics Flow Table Entries (1.0) Rule Action Stats Packet + byte counters • Forward packet to zero or more ports • Encapsulate and forward to controller • Send to normal processing pipeline • Modify Fields • Any extensions you add! Switch Port VLAN ID VLAN pcp MAC src MAC dst Eth type IP Src IP Dst IP ToS IP Prot L4 sport L4 dport + mask what fields to match

17. Switch Port Switch Port Switch Port MAC src MAC src MAC src MAC dst MAC dst MAC dst Eth type Eth type Eth type VLAN ID VLAN ID VLAN ID IP Src IP Src IP Src IP Dst IP Dst IP Dst IP Prot IP Prot IP Prot TCP sport TCP sport TCP sport TCP dport TCP dport TCP dport Action Action Action Examples (1/2) Switching 00:1f:.. * * * * * * * * * port6 Flow Switching port3 00:20.. 00:1f.. 0800 vlan1 1.2.3.4 5.6.7.8 4 17264 80 port6 Firewall * * * * * * * * * 22 drop

18. Switch Port Switch Port MAC src MAC src MAC dst MAC dst Eth type Eth type VLAN ID VLAN ID IP Src IP Src IP Dst IP Dst IP Prot IP Prot TCP sport TCP sport TCP dport TCP dport Action Action Examples (2/2) Routing * * * * * * 5.6.7.8 * * * port6 VLAN Switching port6, port7, port9 vlan1 00:1f.. * * * * * * * *

19. OpenFlow v1.0 Switch OpenFlow v1.0 Switch OpenFlow Controller Secure Channel OpenFlow Protocol sw SSL/TLS Flow Table hw

20. OpenFlow v1.1 Switch OpenFlow v1.1 Switch OpenFlow Protocol OpenFlow Controller Secure Channel SSL/TLS … Flow Table Flow Table Group Table Pipeline

21. OpenFlow v1.1 Switch OpenFlow v1.1 Switch OpenFlow Protocol OpenFlow Controller Secure Channel SSL/TLS … Flow Table Flow Table Group TableTable Pipeline

22. CASOS PRACTICOS

23. Keynote at Open Networking Symposium 2012 UrsHölzle, Senior Vice President Technical Infrastructure Google deployed OpenFlow in I-Scale network In production to connect all Google datacenters Replaced traditional routing protocols Google built OpenFlow switches themselves (but will buy if available) Cost savings (e.g. 100% link utilization, easier management) New opportunities http://www.youtube.com/watch?v=VLHJUfgxEO4 Google

24. Data center interconnect wanOpenflow instead of routing protocols • Logically centralized • OpenFlow controller • OpenFlow switch • no routing protocols

25. Data center con Arquitectura de SDN • Centralized • Orchestration • Virtualized • storage • Virtualized • services • Physical • IP Fabric • Virtualized • Network • Virtualized • Compute

26. Multi-tenancy using overlay networks • Virtual machine • Virtual switch • Hypervisor • Overlay tunnel

27. Virtualized services • Virtual firewall service

28. centralized orchestrationOF compute, storage, and network • Centralized • Orchestration Compute Storage Network • OpenFlow • The IP fabric • was not touched

29. Juniper is the recognizedleader of the network programmability movement, which is the conceptual foundation underlying the SDN approach. Long before the term “SDN” was coined, our disruptive network architectures were built on the premise of using innovativesoftware to give customers unprecedented levels of flexibility and control, with an end goal of transforming the economics and experience of networking. By simultaneously simplifying and opening up the network, Juniper pioneered the core capabilities and concepts behind SDNs. Posicionamiento de SDN

30. Open network Technologies FOR Innovation ... OSS/BSS Topology Client Path Client Juniper and Custom Space UIs / Workflows Network-aware Apps SNMP NETCONF SYSLOG HTTP RESTful Web Services ALTO server Any OF controller Juniper and Custom Application APIs Junos Space SDK Junos Space (Orchestration, Management, Monitoring Plane) OpenFlow BGP-TE ALTO PCP DMI Common Interfaces ALTO OpenFlow(extensible) PCE Custom Apps + APIs Custom Packet Processing Apps + APIs Custom Apps + APIson any OS Network Orchestration Junos SDK: Common APIs, RE APIs, Services APIs, Remote (VE) APIs Junos Control Plane(Routing Engine) Junos Service Plane (Service Engine) Junos Virtual Plane(Virtual Engine Environment) Automation Junos Data Plane (Packet Forwarding Engine) Network Devices Juniper Custom Silicon Juniper Platform Element Juniper Application Element

31. GRACIAS. PREGUNTAS 