1 / 18

Software Defined-Networking

Software Defined-Networking. Network Policies. Access control: r eachability Alice can not send packets to Bob Application classification Place video traffic in the gold queue. Network Management: Past. Networking Yesterday. Data plane Determines how to forward a packet

pepper
Download Presentation

Software Defined-Networking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Defined-Networking

  2. Network Policies • Access control: reachability • Alice can not send packets to Bob • Application classification • Place video traffic in the gold queue

  3. Network Management: Past

  4. Networking Yesterday • Data plane • Determines how to forward a packet • Looks up the forwarding table to determine output port for a packet • Control plane • Determines how to populate the forwarding tables • Translate user commands into hardware • ACLs, MPLS • Runs a bunch of routing protocols • IGPs: OSPF, IS-IS, RIP, & EGPs: BGP Prefix MPLS Label Port Path 10.10.2.10 23 1 1 45 2.3.4.23 3 3 BGP OSPF VLAN IP MPLS

  5. Networking Yesterday • Control + Data-plane on each device • Network is a Distributed systems • Built to avoid failure (ArpaNet) • A network is supported by an infinite number of protocols • New protocols developed to support new functionality • Takes time to standardize and to change the hardware • Think: writing a distributed program in Perl • Error prone (Over 50% of errors caused by misconfig) • Time consuming • IT Operators are the most costly portion of IT • Takes up to 6 months for ISPs to roll out services for new costumers • Very difficult to add new functionality into the network

  6. Networking Evolution • SDN is nothing new • Circuit switching in Telephone networks • RCP – Centralize control plane • Configure protocols rather than control plane • 4D – clean-slate architecture • Ethane/Sane – Centralize control plane • Forces switches do encrypt/decrypt each packet • No standardized interface

  7. Requirements for SDN Network Operating System • Operate without Guarantees • Need abstraction for distributed state • Want to deal with information without worrying about the fact that the state is from a distribution • Logically Centralized • Compute configuration of each device • Need abstraction that simplifies configuration • Want to specify your intent  desired goal; the what • NOT: how to do it. • Operate within given network-level protocol • Need abstraction for forwarding model • Hide details about hardware specifics • No need to worry about he exact harware Network Operating System OpenFlow Protocol

  8. Enter Software Defined Networking:Separation of concerns • Network operator • Specify behavior on a model • Behavior == network policies • Network runtime • Provides abstract view of the network • Maps abstract view to global view • Function of the types of network policies to be supported • Network Operation System • Maps global view to physical view • Translate abstract commands to device configuration • Device interface: forwarding abstractions

  9. Thinks to think about • Distributed state abstraction • What is the right central view • Configuration abstraction • What should the interface to the Switch hardware look like • Forwarding abstraction • What to expose to the network operator

  10. SDN Network Network Controller Network Operation System

  11. OpenFlow Protocol • Message between controller and switches • Synchronous • Stats, Flow-mods • Asynchronous • Packet-in • Abstract hardware details • Allows direct control over forwarding table Match Action 10.2.3.4:10.2.3.3 Fwd Port 1 A2:e3:f1:ba:ea:23:* Drop

  12. The SDN Stack Controller Commercial Switches Software Ref. Switch NetFPGA Broadcom Ref. Switch HP, NEC, Pronto, Juniper.. and many more OpenFlow Switches Open vSwitch OpenWRT PCEngineWiFi AP 13

  13. The SDN Stack NOX Beacon … Trema Maestro Controller Commercial Switches Software Ref. Switch NetFPGA Broadcom Ref. Switch HP, NEC, Pronto, Juniper.. and many more OpenFlow Switches Open vSwitch OpenWRT PCEngineWiFi AP 14

  14. Controllers Too many to easily keep track of… http://yuba.stanford.edu/~casado/of-sw.html

  15. The SDN Stack NOX Beacon … Trema Maestro Controller Slicing Software FlowVisor Console FlowVisor Commercial Switches Software Ref. Switch NetFPGA Broadcom Ref. Switch HP, NEC, Pronto, Juniper.. and many more OpenFlow Switches Open vSwitch OpenWRT PCEngineWiFi AP 16

  16. FlowVisor Creates Virtual Networks FlowVisor CloudNaaS Stratos Simple switch Each application runs in an isolated slice of the network. OpenFlow Protocol OpenFlow Protocol OpenFlow Switch Reservations FlowVisor slices OpenFlow networks, creating multiple isolated and programmable logical networks on the same physical topology. OpenFlow Switch OpenFlow Switch

  17. The SDN Stack Simple Switch CloudNaaS … Applications Stratos NOX Beacon … Trema Maestro Controller Slicing Software FlowVisor Console FlowVisor Commercial Switches Software Ref. Switch NetFPGA Broadcom Ref. Switch HP, NEC, Pronto, Juniper.. and many more OpenFlow Switches Open vSwitch OpenWRT PCEngineWiFi AP 18

  18. The Dark Side of SDN • “Logically” centralized controller • Scalability • Fault tolerance • Flowtable entries • Limited number of TCAM entries • Can only support so many TCAM entries • SDN Abstractions • Currently one set of abstraction for all devices • Edge and Core fundamentally different • Switches Versus Middleboxes

More Related