Scribd Logo
Upload

Welcome to Scribd!

  • 61 views

    Software Defined Networking Software Defined Networking: CS 4226: Internet Architecture

    Uploaded by

    jmariachi
    The document discusses software defined networking (SDN), a new approach to networking that separates the control plane from the data plane. This separation allows for centralized control and programmability of network behavior through open interfaces. SDN aims to make networks more flexible, easier to manage, and adaptable to innovation through principles of logical centralization, open standards, and virtualization of network functions.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Software Defined Networking Software Defined Networking: CS 4226: Internet Architecture

    Uploaded by

    jmariachi
    61 views41 pages
    The document discusses software defined networking (SDN), a new approach to networking that separates the control plane from the data plane. This separation allows for centralized control and programmability of network behavior through open interfaces. SDN aims to make networks more flexible, easier to manage, and adaptable to innovation through principles of logical centralization, open standards, and virtualization of network functions.

    Original Description:

    sdn

    Original Title

    05-SDN

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses software defined networking (SDN), a new approach to networking that separates the control plane from the data plane. This separation allows for centralized control and programmability of network behavior through open interfaces. SDN aims to make networks more flexible, easier to manage, and adaptable to innovation through principles of logical centralization, open standards, and virtualization of network functions.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    61 views41 pages

    Software Defined Networking Software Defined Networking: CS 4226: Internet Architecture

    Uploaded by

    jmariachi
    The document discusses software defined networking (SDN), a new approach to networking that separates the control plane from the data plane. This separation allows for centralized control and programmability of network behavior through open interfaces. SDN aims to make networks more flexible, easier to manage, and adaptable to innovation through principles of logical centralization, open standards, and virtualization of network functions.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 41

    Software Defined Networking

    Richard T. B. Ma
    School of Computing
    National University of Singapore

    Material from: Scott Shenker (UC Berkeley), Nick McKeown


    (Stanford), Jennifer Rexford (Princeton)

    CS 4226: Internet Architecture


    What is Software Defined Networking?

     A new approach to do networking


     new fundamental principles

     How does it contrast with traditional


    networking?

     Before knowing what it is, let us understand


    why we need it in the first place
     what is wrong with the current Internet?
    The Internet: A Remarkable Story

     Tremendous success
     from research experiment
    to global infrastructure

     Brilliance of under-specifying
     network: best-effort packet delivery
     hosts: arbitrary applications

     Enables innovation in applications


     web, P2P, VoIP, social networks, virtual worlds

     But, change is easy only at the edge… 


    Networks are Hard to Manage
     Operating a network is expensive
     more than half the cost of a network
     yet, operator error causes most outages

     Buggy software in the equipment


     routers with 20+ million lines of code
     cascading failures, vulnerabilities, etc.

     The network is “in the way”


     especially a problem in data centers
     … and home networks
    Networks Vs. Other Systems
     Networks are hard to manage
     computation and storage have been virtualized
    • creating more flexible and manageable infrastructure
     networks are still notoriously hard to manage
    • still heavily rely on network administrators
     Networks are hard to evolve
     ongoing innovation in systems software
    • new programming languages, operating systems, etc.
     networks are stuck in the past
    • routing algorithms change very slowly
    • network management extremely primitive
    Inside the Net: A Different Story

     Closed equipment
     software bundled with hardware
     vendor-specific interfaces

     Over specified
     slow protocol standardization

     Few people can innovate


     equipment vendors write the code
     long delays to introduce new features

    Impacts performance, security, reliability, cost…


    Networking as a Discipline
     Other fields in “systems”: OS, DB, DS, etc.
     Teach basic principles
     Are easily managed
     Continue to evolve

     Networking:
     Teach big bag of protocols
     Notoriously difficult to manage
     Evolves very slowly

    A failure from an academic point of view


    Why Does Networking Lag Behind?

     Networks used to be simple: Ethernet, IP, TCP….


     New control requirements led to great complexity
     isolation  VLANs, ACLs
     traffic engineering  MPLS
     packet processing  Firewalls, NATs
     payload analysis  Deep packet inspection
     Mechanisms designed and deployed independently
     complicated “control plane” design, primitive functionality
     stark contrast to the elegantly modular “data plane”

     Ability to master complexity  a curse


     extract simplicity is needed to build a discipline
    A Good Example: Programming
     Machine languages: no abstractions
     mastering complexity was crucial

     Higher-level languages: OS and other


    abstractions
     file system, virtual memory, abstract data
    types, ...

     Modern languages: even more abstractions


     object orientation, garbage collection,…

    Abstractions key to extracting simplicity


    Key to the Internet’s Success
     Hourglass IP model

     Layered service
    abstractions (why is
    this important?)
     decompose delivery into
    fundamental components
     independent, compatible
    innovation at each layer

     Only for network edges


    Complicated Router at the Core
    two key router functions:
     run routing algorithms/protocol (RIP, OSPF, BGP)
     forwarding datagrams from incoming to outgoing link
    routing Routing, management
    processor control plane
    (software)

    Forwarding
    line card line card data plane
    (hardware)
    switching
    input ports fabric output ports

    line card line card


    Two Key Definitions
     Data Plane: processing and delivery of packets
     based on state in routers and endpoints
     e.g., IP, TCP, Ethernet, etc.
     fast timescales (per-packet)

     Control Plane: establishing the state in routers


     determines how and where packets are
    forwarded
     routing, traffic engineering, firewall state, …
     slow time-scales (per control event)
    What have we learned so far?
     Layers are great abstractions
     layers only deal with the data plane
     no powerful control plane abstractions!

    “Modularity based on abstraction is the way


    things get done” – Barbara Liskov
    Abstractions  Interfaces  Modularity
     How do we find control plane abstractions?
     first define problem
     and then decompose it
    The network control problem
     Compute the configuration of each physical
    devices, e.g., forwarding tables

     Operate without communication guarantees

     Operate within given network-level


    protocol, e.g., RIP, OSPF.

    Only people who love complexity would


    find this a reasonable request!
    Separation of Control/Data Plane

    Control Plane

    Routing Data Plane Routing


    processor processor

    Switch Switch
    Switch Switch
    fabric Routing fabric
    processor

    Switch
    Switch
    fabric
    Benefits of Separation
     Independent evolution and development
     the software control of the network can evolve
    independently of the hardware.

     Control from high-level software program


     control behavior using higher-order programs
     debug/check behavior more easily
    Logically Centralized Control

    Routing Routing Routing


    Controller
    processor processor processor

    Control Plane

    Data Plane

    Switch Switch

    Switch
    Benefits of Centralization
     Centralized decisions are easier to make
     e.g., OSPF (RFC 2328) 244 pages
     distributed system part (builds consistent
    network 100 pages)
     routing algorithm (Dijkstra’s algorithm 4 pages)

     Logically vs. physically centralized


     issues with of a physically centralized
    controller?
     how to implement a logically centralized one?
    Open Interfaces

    Controller

    Southbound
    Southbound

    Control Plane
    Interface

    Interface
    Southbound
    Data Plane
    Interface

    Switch Switch

    Switch
    Programmability Application Control Plane

    Northbound
    Interface
    NetworkController
    Control Plane
    Southbound

    Southbound
    Control Plane
    Interface

    Interface
    Southbound
    Data Plane
    Interface

    Switch Switch

    Switch
    Benefits of Open Interfaces and
    Programmability
     Enable competitive technologies
     independent developments
     rapid innovation and fast evolution
     cheap and better networks

     Make network management much easier


     management goals are expressed as policies
     new control/services for network providers
     detailed configuration are done by controller
    A Quick Summary
     Principles of Software Defined Networking
     Separation of Control Plane and Data Plane
     Logically Centralized Control
     Open Interfaces
     Programmability

     All these principles use abstractions to


    modularize the network control problem.

     A nice analogy from Prof. Nick McKeown


    Mainframes
    AppAppAppAppAppAppAppAppAppAppApp

    Specialized
    Open Interface
    Applications
    Windows Mac
    Specialized or Linux or
    (OS) OS
    Operating
    System
    Open Interface
    Specialized
    Hardware Microprocessor

    Vertically integrated Horizontal


    Closed, proprietary Open interfaces
    Slow innovation Rapid innovation
    Small industry Huge industry
    Routers/Switches
    AppAppAppAppAppAppAppAppAppAppApp

    Specialized Open Interface


    Features
    Control Control Control
    Plane or Plane or Plane
    Specialized
    Control
    Plane Open Interface

    Specialized Merchant
    Hardware Switching Chips

    Vertically integrated Horizontal


    Closed, proprietary Open interfaces
    Slow innovation Rapid innovation
    Conventional Vs. SDN (Pros)

     Easy to
    program

     Consistent
    policies

     Better
    integration of
    programs

    D. Kreutz et al. “Software-Defined Networking: A Comprehensive Survey”,


    Proceedings of the IEEE, Vol. 103, No. 1, January 2015.
    Layers in a SDN

    D. Kreutz et al. “Software-Defined Networking: A Comprehensive Survey”,


    Proceedings of the IEEE, Vol. 103, No. 1, January 2015.
    Abstractions
     Specification

     Distribution

     Forwarding

    D. Kreutz et al. “Software-Defined Networking: A Comprehensive Survey”,


    Proceedings of the IEEE, Vol. 103, No. 1, January 2015.
    Three layers of abstractions
     Specification
     allow a application to express the desired
    network behavior without implementing it
     Distribution
     shield SDN apps from the distributed states,
    making distributed control logically centralized
     Forwarding
     allow any forwarding behavior desired by the
    network application (the control program) while
    hiding details of the underlying hardware
    OpenFlow Protocol and Switch

     OpenFlow protocol
     Open southbound API

     OpenFlow switch
     Forwarding abstraction
    Main components of an OpenFlow switch
    Packet flow through the processing pipeline
    OF terminology associated with packets
     For each packet from a packet flow
     Header and header field
     Pipeline fields
    • values attached to the packet during pipeline
    processing, e.g., ingress port and metadata
     Action: an operation that acts on a packet
    • e.g., drop, forward to a port, modify (decreasing TTL)
     Action set
    • accumulated while processed by flow tables
    • executed at then end of pipeline processing
    OpenFlow flow entry
     A flow entry in a flow table looks like

     Match field: packets are matched against


    • header fields and pipeline fields
    • may be wildcarded (any) or bitmasked (subset of bits)
     Priority: used to choose from multiple matches
     Instruction set
    • contains a list of actions to apply immediately
    • contains a set of actions to add to the action set
    • modify pipeline processing (go to another flow table)

     A “default” entry: table-miss flow entry


    Packet flow through an OF switch
    Matching and instruction execution

    Matching and Instruction execution in a flow table.


    Operation of SDN (controller-switch)

    S. Sezer et al. “Are we ready for SDN? Implementation Challenges for


    Software-Defined Networks”, IEEE Communications Magazine, July 2013.
    Interfaces of a SDN

    M. Jarschel et al. “Interfaces, attributes, and use cases: a compass for


    SDN”, IEEE Communications Magazine, June 2014.
    S. Sezer et al. “Are we ready for SDN? Implementation Challenges for
    Software-Defined Networks”, IEEE Communications Magazine, July 2013.
    Applications of SDN
     Killer application
     network virtualization

     Other applications
     datacenter and cloud computing
     wide-area networking (Google B4 WAN)
     software Internet exchange point (IXP)
     mobility and wireless
     security, measurement and monitoring
    References
     D. Kreutz et al. “Software-Defined
    Networking: A Comprehensive Survey”,
    Proceedings of the IEEE, Vol. 103, No. 1,
    January 2015.

     OpenFlow Switch Specification Ver. 1.5.1


    o https://www.opennetworking.org/images/stories/downloa
    ds/sdn-resources/onf-specifications/openflow/openflow-
    switch-v1.5.1.pdf

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy