Bangladesh Network Operators Group, profile picture
Uploaded byBangladesh Network Operators Group
PDF, PPTX19,726 views

Introduction to Software Defined Networking (SDN)

Here are the key steps: 1. Kill any existing controllers running on the system 2. Clear out any existing Mininet topology using mn -c 3. Start the Ryu OpenFlow controller by running: ryu-manager --verbose ./simple_switch_13.py This starts the Ryu controller with the simple_switch_13.py application, which provides basic OpenFlow switch functionality. The --verbose flag prints debug information from the controller. We have now initialized the SDN environment with Ryu acting as the controller.

Embed presentation

Download as PDF, PPTX
Introduction to SDN Muhammahmad Moinur Rahman moin@1asia-ahl.com
History of Networking • Blackbox networking equipments • Big name companies building switching/routing devices • Includes Proprietary/OEM Silicon Chip • Wrapped up with a closed source Operating System (e.g. A desktop PC with MS Windows and MS Office)
Disadvantages of Current Scenario Technology was not designed keeping today in mind • Massive Scalability • Multi Tenant Networks • Virtualization • Cloud Computing • Mobility (Users/Devices/VM)
Disadvantages of Current Scenario(Contd) Protocols are Box Centric; Not Fabric Centric • Difficult to configure correctly(consistency) • Difficult to add new features(upgrades) • Difficult to debug(look at all devices)
Disadvantages of Current Scenario(Contd) Closed Systems (Vendor Hardware) • Stuck with given interfaces (CLI, SNMP, etc.) • Hard to meaningfully collaborate • Vendors hesitant to open up • No way to add new features by yourself ANSWER: Software Defined Networking
What is SDN? SDN is a framework to allow network administrators to automatically and dynamically manage and control a large number of network devices, services, topology, traffic paths, and packet handling (quality of service) policies using high-level languages and APIs. Management includes provisioning, operating, monitoring, optimizing, and managing FCAPS (fault, configuration, accounting, performance, and security) in a multi-tenant environment.
Networking Planes • Data Plane • Carries Network User Traffic • Control Panel • Carried Signalling Traffic • Management Panel • Carries Administrative Traffic
SDN Architecture
Need for SDN - Virtualization Use network resource • without worrying about where it is physically located • how much it is • how it is organized
Need for SDN - Orchestration Should be able to control and manage thousands of devices with one command
Need for SDN - Programmable Should be able to change behavior on the fly
Need for SDN - Dynamic Scaling Should be able to change size, quantity, capacity
Need for SDN - Automation • To lower OpEx • Minimize manual involvement • Troubleshooting • Reduce downtime • Policy enforcement • Provisioning/Re-provisioning/Segmentation of resources • Add new workloads, sites, devices, and resources
Need for SDN - Visibility Monitor resources, connectivity
Need for SDN - Performance Optimize network device utilization • Traffic engineering/Bandwidth management • Capacity optimization • Load balancing • High utilization • Fast failure handling
Need for SDN - Multi Tenancy Tenants need complete control over their • Addresses • Topology • Routing • Security
Need for SDN - Service Integration Provisioned on demand and placed appropriately on the traffic path • Load balancers • Firewalls • Intrusion Detection Systems (IDS)
Alternative APIs • Southbound APIs: XMPP (Juniper), OnePK (Cisco) • Northbound APIs: I2RS, I2AEX, ALTO • Overlay: VxLAN, TRILL, LISP, STT, NVO3, PWE3, L2VPN, L3VPN • Configuration API: NETCONF • Controller: PCE, ForCES
History Feb, 2011 - OpenFlow 1.1 Released Dec, 2011 - OpenFlow 1.2 Released Feb, 2012 - “Floodlight” Project Announced Apr, 2012 - Google announces at ONF Jul, 2012 - Vmware acquires Nicira Apr, 2013 - “OpenDaylight” Released
Hardware Internals • Logical View of a Switch • Physical Architecture of a Switch Switching Fabric Processor ASIC AISC data plane control plane Network O.S. ASIC ApplicationsApplications
Internals of SDN • Southbound API: decouples the switch hardware from control function – Data plane from control plane • Switch Operating System: exposes switch hardware primitives Network O.S. ApplicationsApplications Applications Southbound API SDN Switch Operating System Switch Hardware Network O.S. ASIC ApplicationsApplications Current Switch Vertical stack SDN Switch Decoupled stack
How SDN Works Controller (N. O.S.) ApplicationsApplicationsApplications Southbound API Switch H.W Switch O.S Switch H.W Switch O.S
Implications of SDN Controller (N. O.S.) ApplicationsApplicationsApplications Southbound API Switch O.S Switch HW Switch O.S Switch HW Switch O.S Switch HW Global View Programmatic Control Current Networking SDN Enabled Environment Network O.S. ASIC ApplicationsApplications Network O.S. ASIC ApplicationsApplications Network O.S. ASIC ApplicationsApplications
Implications of SDN(Cont) Current Networking SDN Enabled Environment Controller (N. O.S.) ApplicationsApplicationsApplications Southbound API Switch O.S Switch HW Switch O.S Switch HW Switch O.S Switch HW • Distributed protocols • Each switch has a brain • Hard to achieve optimal solution • Network configured indirectly • Configure protocols • Hope protocols converge • Global view of the network • Applications can achieve optimal • Southbound API gives fine grained control over switch • Network configured directly • Allows automation • Allows definition of new interfaces Network O.S. ASIC ApplicationsApplications Network O.S. ASIC ApplicationsApplications Network O.S. ASIC ApplicationsApplications
Dimensions of SDN Environments: Vendor Devices Vertical Stacks • Vendor bundles switch and switch OS • Restricted to vendor OS and vendor interface • Low operational overhead • One stop shop Whitebox Networking • Vendor provides hardware with no switch OS • Switch OS provided by third party • Flexibility in picking OS • High operational overhead • Must deal with multiple vendors
Dimensions of SDN Environments: Switch Hardware Virtual: Overlay • Pure software implementation • Assumes programmable virtual switches • Run in Hypervisor or in the OS • Larger Flow Table entries (more memory and CPU) • Backward compatible • Physical switches run traditional protocols • Traffic sent in tunnels • Lack of visibility into physical network Physical: Underlay • Fine grained control and visibility into network • Assumes specialized hardware • Limited Flow Table entries
Dimensions of SDN Environments: Southbound Interface OpenFlow • Flexible matching • L2, L3, VLAN, MPLS • Flexible actions • Encapsulation: IP-in-IP • Address rewriting: • IP address • Mac address BGP/XMPP/IS-IS/NetConf • Limited matching • IS-IS: L3 • BGP+MPLS: L3+MPLS • Limited actions • L3/l2 forwarding • Encapsulation
Dimensions of SDN Environments: Controller Types Modular Controllers • Application code manipulates forwarding rules • E.g. OpenDaylight, Floodlight • Written in imperative languages • Java, C++, Python • Dominant controller style High Level Controllers • Application code specifies declarative policies • E.g. Frenetic, McNettle • Application code is verifiable • Amendable to formal verification • Written in functional languages • Nettle, OCamal
• Controller Type • Modular: Floodlight • Southbound API: OpenFlow • OpenFlow 1.3 • SDN Device: Whitebox • (indigo) • SDN Flavor • Underlay+Overlay Ecosystem : BigSwitch
• Controller Type • Modular: OpenContrail • Southbound API: XMPP/NetConf • BGP+MPLS • SDN Device: Vertical Stack • Propriety Junos • SDN Flavor • Overlay Ecosystem : Juniper
SDN EcoSystem Arista OF + proprietary Underlay Vertical Stack Broadcom OF + proprietary Underlay Vertical Stack HP OF Underlay Vertical Stack Cisco OF + proprietary Underlay+Overlay Vertical Stack FloodLight OF Underlay+Overlay Whitebox Dell OF Underlay Vertical Stack HP OF Underlay Vertical Stack Alcatel BGP Overlay Vertical Stack Juniper BGP+NetConf Overlay Vertical Stack
OpenFlow • Developed in Stanford • Standardized by Open Networking Foundation (ONF) • Current Version 1.4 • Version implemented by switch vendors: 1.3 • Allows control of underlay + overlay • Overlay switches: OpenVSwitch/Indigo-light PC
SDN vs OpenFlow • Leading SDN protocol • Decouples control and data plane by giving a controller the ability to install flow rules on switches(Bare Metal) • Hardware or software switches can use OpenFlow • Spec driven by ONF
How SDN Works: OpenFlow Controller (N. O.S.) ApplicationsApplicationsApplications Southbound API Switch H.W Switch O.S Switch H.W Switch O.S OpenFlow OpenFlow
OpenFlow: Anatomy of a Flow Table Entry Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot L4 sport L4 dport Match Action Counter 1. Forward packet to zero or more ports 2. Encapsulate and forward to controller 3. Send to normal processing pipeline 4. Modify Fields When to delete the entry VLAN pcp IP ToS Priority Time-out What order to process the rule # of Packet/Bytes processed by the rule
Examples Switching * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * 00:1f:.. * * * * * * * port6 Flow Switching port3 Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action 00:20.. 00:1f.. 0800 vlan1 1.2.3.4 5.6.7.8 4 17264 80 port6 Firewall * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * * * * * * * 22 drop 37
Examples Routing * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * * * * 5.6.7.8 * * * port6 VLAN Switching * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * vlan1 * * * * * port6, port7, port9 00:1f.. 38
Data Path (Hardware) Control Path OpenFlow OpenFlow Controller OpenFlow Protocol (SSL/TCP) 39 OpenFlow: How it works
Controller PC Hardware Layer Software Layer Flow Table MAC src MAC dst IP Src IP Dst TCP sport TCP dport Action OpenFlow Client **5.6.7.8*** port 1 port 4port 3port 2port 1 1.2.3.45.6.7.8 40 OpenFlow: Anatomy of a Flow Table Entry
SDN Components : Hardwares OpenFlow Compliant (1.0-1.4) Switch • HP 8200 ZL, 6600, 6200ZL • Brocade 5400ZL, 3500 • IBM NetIron • Juniper OCX1100 • Baremetal Switch • OpenVSwitch
SDN Components : Controllers OpenFlow Compliant (1.0-1.4) Controller • POX: (Python) Pox as a general SDN controller that supports OpenFlow. It has a high-level SDN API including a queriable topology graph and support for virtualization. • IRIS: (Java) a Resursive SDN Openflow Controller created by IRIS Research Team of ETRI. • MUL: (C) MūL, is an openflow (SDN) controller. • NOX: (C++/Python) NOX was the first OpenFlow controller. • Jaxon: (Java) Jaxon is a NOX-dependent Java-based OpenFlow Controller. • Trema: (C/Ruby) Trema is a full-stack framework for developing OpenFlow controllers in Ruby and C. • Beacon: (Java) Beacon is a Java-based controller that supports both event-based and threaded operation. • Floodlight: (Java) The Floodlight controller is Java-based OpenFlow Controller. It was forked from the Beacon controller, originally developed by David Erickson at Stanford. • Maestro: (Java) Maestro is an OpenFlow "operating system" for orchestrating network control applications. • NDDI - OESS: OESS is an application to configure and control OpenFlow Enabled switches through a very simple and user friendly User Interface. • Ryu: (Python) Ryu is an open-sourced Network Operating System (NOS) that supports OpenFlow. • NodeFlow (JavaScript) NodeFlow is an OpenFlow controller written in pure JavaScript for Node.JS. • ovs-controller (C) Trivial reference controller packaged with Open vSwitch.
Demonstration Lab
Objectives • Basics of running Mininet in a virtual machine. • Mininet facilitates creating and manipulating Software Defined Networking components. • Explore OpenFlow, which is an open interface for controlling the network elements through their forwarding tables. A network element may be converted into a switch, router or even an access points via low-level primitives defined in OpenFlow. • Experience with the platforms and debugging tools most useful for developing network control applications on OpenFlow. • Run the Ryu controller with a sample application • Use various commands to gain experience with OpenFlow control of OpenvSwitch
Topology • Three hosts named h1, h2 and h3 respectively. Each host has an Ethernet interface called h1-eth0, h2-eth0 and h3-eth0 respectively. • Three hosts are connected through a switch names s1. The switch s1 has three ports named s1-eth1, s1-eth2 and s1-eth3. • The controller is connected on the loopback interface (in real life this may or may not be the case, it means the switch and controller are built in a single box). The controller is identified as c0 and connected through port 6633.
Topology Diagram C0 - Controller Switch H.W S1 Switch OpenFlow H1 – h1-eth0 H2 – h2-eth0 H3 – h3-eth0 S1-eth2 S1-eth1 S1-eth0
RYU Openflow controller Ensure that no other controller is present root@mininet-vm:~# killall controller controller: no process found root@mininet-vm:~# Note that 'controller' is a simple OpenFlow reference controller implementation in linux. We want to ensure that this is not running before we start our own controller.
RYU Openflow controller(Cont) Clear all mininet components root@mininet-vm:~# mn -c *** Removing excess controllers/ofprotocols/ofdatapaths/pings/noxes killall controller ofprotocol ofdatapath ping nox_core lt-nox_core ovs-openflowd ovs-controller udpbwtest mnexec ivs 2> /dev/null killall -9 controller ofprotocol ofdatapath ping nox_core lt-nox_core ovsopenflowd ovs-controller udpbwtest mnexec ivs 2> /dev/null pkill -9 -f "sudo mnexec" *** Removing junk from /tmp rm -f /tmp/vconn* /tmp/vlogs* /tmp/*.out /tmp/*.log *** Removing old X11 tunnels *** Removing excess kernel datapaths ps ax | egrep -o 'dp[0-9]+' | sed 's/dp/nl:/' *** Removing OVS datapathsovs-vsctl --timeout=1 list-br ovs-vsctl del-br s1 ovs-vsctl del-br s2 ovs-vsctl del-br s3 ovs-vsctl del-br s4 *** Removing all links of the pattern foo-ethX ip link show | egrep -o '(w+-ethw+)' *** Cleanup complete. root@mininet-vm:~#
RYU Openflow controller(Cont) Start the Ryu controller root@mininet-vm:~# ryu-manager --verbose ./simple_switch_13.py loading app ./simple_switch_13.py loading app ryu.controller.ofp_handler instantiating app ./simple_switch_13.py of SimpleSwitch13 instantiating app ryu.controller.ofp_handler of OFPHandler BRICK SimpleSwitch13 CONSUMES EventOFPSwitchFeatures CONSUMES EventOFPPacketIn BRICK ofp_event PROVIDES EventOFPSwitchFeatures TO {'SimpleSwitch13': set(['config'])} PROVIDES EventOFPPacketIn TO {'SimpleSwitch13': set(['main'])} CONSUMES EventOFPHello CONSUMES EventOFPErrorMsg CONSUMES EventOFPEchoRequest CONSUMES EventOFPPortDescStatsReply CONSUMES EventOFPSwitchFeatures Understanding simple_switch.py
MiniNet Environment root@mininet-vm:~# mn --topo=tree,1,3 --mac --controller=remote --switch ovsk,protocols=OpenFlow13 *** Creating network *** Adding controller *** Adding hosts: h1 h2 h3 *** Adding switches: s1 *** Adding links: (h1, s1) (h2, s1) (h3, s1) *** Configuring hosts h1 h2 h3 *** Starting controller *** Starting 1 switches s1 *** Starting CLI: mininet>
MiniNet Environment(Cont) Monitor controller to ensure that the switch connects connected socket:<eventlet.greenio.GreenSocket object at 0xa986c0c> address: ('127.0.0.1', 42733) connected socket:<eventlet.greenio.GreenSocket object at 0xa986cec> address: ('127.0.0.1', 42734) hello ev <ryu.controller.ofp_event.EventOFPHello object at 0xa9897ac> move onto config mode EVENT ofp_event->SimpleSwitch13 EventOFPSwitchFeatures switch features ev version: 0x4 msg_type 0x6 xid 0xb15cb575 OFPSwitchFeatures(auxiliary_id=0,capabilities=71,datapath_id= 1,n_buffers=256,n_tables=254) move onto main mode
MiniNet Environment(Cont) Dump flows on switch s1 mininet> dpctl dump-flows -O OpenFlow13 *** s1 ----------------------------------------- OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x0, duration=2.481s, table=0, n_packets=0, n_bytes=0, priority=0 actions=FLOOD,CONTROLLER:64 mininet>
MiniNet Environment(Cont) Passing Packets mininet> h1 ping h2 PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_req=1 ttl=64 time=5.10 ms 64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.238 ms 64 bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.052 ms 64 bytes from 10.0.0.2: icmp_req=4 ttl=64 time=0.051 ms ^C --- 10.0.0.2 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3001ms rtt min/avg/max/mdev = 0.051/1.360/5.100/2.160 ms mininet>
Controller Environment Monitor new messages in the controller window EVENT ofp_event->SimpleSwitch13 EventOFPPacketIn EVENT ofp_event->SimpleSwitch13 EventOFPPacketIn packet in from 00:00:00:00:00:01 port 1 to 00:00:00:00:00:02 on dpid 1 associate 00:00:00:00:00:01 with port 1 on dpid 1 packet in from 00:00:00:00:00:02 port 2 to 00:00:00:00:00:01 on dpid 1 associate 00:00:00:00:00:02 with port 2 on dpid 1 add unicast flow from 00:00:00:00:00:02 port 2 to 00:00:00:00:00:01 port 1 on dpid 1 EVENT ofp_event->SimpleSwitch13 EventOFPPacketIn packet in from 00:00:00:00:00:01 port 1 to 00:00:00:00:00:02 on dpid 1 add unicast flow from 00:00:00:00:00:01 port 1 to 00:00:00:00:00:02 port 2 on dpid 1
Mininet Environment Dump flows again to view differences mininet> dpctl dump-flows -O OpenFlow13 *** s1 ------------------------------------------------------------------------ OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x0, duration=38.044s, table=0, n_packets=0, n_bytes=0, priority=10,in_port=1,dl_src=00:00:00:00:00:01,dl_dst=ff:ff:ff:ff:ff:ff actions=ALL cookie=0x0, duration=37.044s, table=0, n_packets=3, n_bytes=238, priority=100,in_port=1,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:02 actions=output:2 cookie=0x0, duration=38.043s, table=0, n_packets=0, n_bytes=0, priority=10,in_port=2,dl_src=00:00:00:00:00:02,dl_dst=ff:ff:ff:ff:ff:ff actions=ALL cookie=0x0, duration=38.043s, table=0, n_packets=4, n_bytes=336, priority=100,in_port=2,dl_src=00:00:00:00:00:02,dl_dst=00:00:00:00:00:01 actions=output:1 cookie=0x0, duration=38.043s, table=0, n_packets=0, n_bytes=0, priority=5,in_port=2,dl_src=00:00:00:00:00:02,dl_type=0x88cc actions=drop cookie=0x0, duration=38.043s, table=0, n_packets=0, n_bytes=0, priority=5,in_port=1,dl_src=00:00:00:00:00:01,dl_type=0x88cc actions=drop cookie=0x0, duration=38.043s, table=0, n_packets=0, n_bytes=0, priority=10,in_port=2,dl_src=00:00:00:00:00:02,dl_dst=01:00:00:00:00:00/01:00:00 :00:00:00 actions=ALL cookie=0x0, duration=38.044s, table=0, n_packets=0, n_bytes=0, priority=10,in_port=1,dl_src=00:00:00:00:00:01,dl_dst=01:00:00:00:00:00/01:00:00 :00:00:00 actions=ALL cookie=0x0, duration=73.001s, table=0, n_packets=3, n_bytes=294, priority=0 actions=FLOOD,CONTROLLER:64
Mininet Environment Running a high bandwidth flow mininet> iperf *** Iperf: testing TCP bandwidth between h1 and h2 Waiting for iperf to start up...*** Results: ['5.52 Gbits/sec', '5.52 Gbits/sec'] mininet>
Mininet Environment Dump flows to see the flows which match mininet> dpctl dump-flows -O OpenFlow13 *** s1 ------------------------------------------------------------------------ OFPST_FLOW reply (OF1.3) (xid=0x2): ... ... cookie=0x0, duration=209.485s, table=0, n_packets=2384026, n_bytes=3609389036, priority=100,in_port=1,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:0a actions=output:10 ... ... cookie=0x0, duration=209.485s, table=0, n_packets=27163, n_bytes=1792770, priority=100,in_port=10,dl_src=00:00:00:00:00:0a,dl_dst=00:00:00:00:00:01 actions=output:1 ... ... cookie=0x0, duration=392.419s, table=0, n_packets=150, n_bytes=11868, priority=0 actions=FLOOD,CONTROLLER:6
Refereces 1. Mininet/Openflow Tutorials – Dean Pemberton 2. SDN – The Next Wave of Networking – Siva Valiappan
Questions

More Related Content

PPTX
Software Defined Network - SDN
byVenkata Naga Ravi
 
PPTX
Sdn ppt
byPallavi Chhikara
 
PPTX
Introduction to SDN: Software Defined Networking
byAnkita Mahajan
 
PPTX
Software Defined Networks
byShreeya Shah
 
PPTX
Introduction to Software Defined Networking (SDN)
byBangladesh Network Operators Group
 
PDF
Introduction to OpenFlow
byJoel W. King
 
PPTX
Software Defined Network (SDN)
byAhmed Ayman
 
PPTX
SDN and NFV: Friends or Enemies
byJustyna Bak
 
Software Defined Network - SDN
byVenkata Naga Ravi
 
Sdn ppt
byPallavi Chhikara
 
Introduction to SDN: Software Defined Networking
byAnkita Mahajan
 
Software Defined Networks
byShreeya Shah
 
Introduction to Software Defined Networking (SDN)
byBangladesh Network Operators Group
 
Introduction to OpenFlow
byJoel W. King
 
Software Defined Network (SDN)
byAhmed Ayman
 
SDN and NFV: Friends or Enemies
byJustyna Bak
 

What's hot

PDF
SDN & NFV Introduction - Open Source Data Center Networking
byThomas Graf
 
PPTX
Software defined networking(sdn) vahid sadri
byVahid Sadri
 
PPTX
Introduction to SDN and NFV
byCoreStack
 
PDF
Introduction to Network Function Virtualization (NFV)
byrjain51
 
PDF
Software Defined Networking (SDN) Technology Brief
byZivaro Inc
 
PDF
SDN Fundamentals - short presentation
byAzhar Khuwaja
 
PPTX
VLAN
byVarsha Honde
 
PPTX
SDN Architecture & Ecosystem
byKingston Smiler
 
PDF
Network function virtualization
bySatish Chavan
 
PPTX
NFV +SDN (Network Function Virtualization)
byHamidreza Bolhasani
 
PDF
Introduction to Software Defined Networking (SDN)
byrjain51
 
PPTX
Software Defined networking (SDN)
byMilson Munakami
 
PDF
Beginners: Open RAN, White Box RAN & vRAN
by3G4G
 
PPTX
Network virtualization
byDamian Parniewicz
 
PDF
Introduction to OpenDaylight & Application Development
byMichelle Holley
 
PDF
5G Network Architecture and Design
by3G4G
 
PPTX
SD WAN
byBri Molina
 
PPTX
Network Virtualization
byKingston Smiler
 
PPTX
CCNA PPT
byAIRTEL
 
PDF
Cisco Live! :: Cisco ASR 9000 Architecture :: BRKARC-2003 | Las Vegas 2017
byBruno Teixeira
 
SDN & NFV Introduction - Open Source Data Center Networking
byThomas Graf
 
Software defined networking(sdn) vahid sadri
byVahid Sadri
 
Introduction to SDN and NFV
byCoreStack
 
Introduction to Network Function Virtualization (NFV)
byrjain51
 
Software Defined Networking (SDN) Technology Brief
byZivaro Inc
 
SDN Fundamentals - short presentation
byAzhar Khuwaja
 
VLAN
byVarsha Honde
 
SDN Architecture & Ecosystem
byKingston Smiler
 
Network function virtualization
bySatish Chavan
 
NFV +SDN (Network Function Virtualization)
byHamidreza Bolhasani
 
Introduction to Software Defined Networking (SDN)
byrjain51
 
Software Defined networking (SDN)
byMilson Munakami
 
Beginners: Open RAN, White Box RAN & vRAN
by3G4G
 
Network virtualization
byDamian Parniewicz
 
Introduction to OpenDaylight & Application Development
byMichelle Holley
 
5G Network Architecture and Design
by3G4G
 
SD WAN
byBri Molina
 
Network Virtualization
byKingston Smiler
 
CCNA PPT
byAIRTEL
 
Cisco Live! :: Cisco ASR 9000 Architecture :: BRKARC-2003 | Las Vegas 2017
byBruno Teixeira
 

Viewers also liked

PPTX
Software-Defined Networking (SDN): Unleashing the Power of the Network
byRobert Keahey
 
PPTX
PAN Manager 7/8 ご説明
byShinjiNakai
 
PDF
SDN Adoption Challenges
byVimal Suba
 
PPTX
Software defined networks and openflow protocol
byMahesh Mohan
 
PDF
Cloud and Network Transformation using DevOps methodology : Cisco Live 2015
byVimal Suba
 
PPTX
Software-Defined Networking(SDN):A New Approach to Networking
byAnju Ann
 
PDF
The Challenges of SDN/OpenFlow in an Operational and Large-scale Network
byOpen Networking Summits
 
PDF
NFV for beginners
byDave Neary
 
PPTX
Software-Defined Networking SDN - A Brief Introduction
byJason TC HOU (侯宗成)
 
PDF
Software Defined Networks Explained
byCM Research
 
PPTX
SDN Basics – What You Need to Know about Software-Defined Networking
bySDxCentral
 
PPTX
Introduction to OpenFlow, SDN and NFV
byKingston Smiler
 
PPTX
10 facts about jobs in the future
byPew Research Center's Internet & American Life Project
 
Software-Defined Networking (SDN): Unleashing the Power of the Network
byRobert Keahey
 
PAN Manager 7/8 ご説明
byShinjiNakai
 
SDN Adoption Challenges
byVimal Suba
 
Software defined networks and openflow protocol
byMahesh Mohan
 
Cloud and Network Transformation using DevOps methodology : Cisco Live 2015
byVimal Suba
 
Software-Defined Networking(SDN):A New Approach to Networking
byAnju Ann
 
The Challenges of SDN/OpenFlow in an Operational and Large-scale Network
byOpen Networking Summits
 
NFV for beginners
byDave Neary
 
Software-Defined Networking SDN - A Brief Introduction
byJason TC HOU (侯宗成)
 
Software Defined Networks Explained
byCM Research
 
SDN Basics – What You Need to Know about Software-Defined Networking
bySDxCentral
 
Introduction to OpenFlow, SDN and NFV
byKingston Smiler
 
10 facts about jobs in the future
byPew Research Center's Internet & American Life Project
 

Similar to Introduction to Software Defined Networking (SDN)

PPTX
Software Defined Networking: Primer
byBangladesh Network Operators Group
 
PDF
Introduction to SDN
byMuhammad Moinur Rahman
 
PPTX
F14_Class1.pptx
bySameer Ali
 
PPTX
SDN - a new security paradigm?
bySophos Benelux
 
PPTX
Software Define Network, a new security paradigm ?
byJean-Marc ANDRE
 
PPTX
sdnppt-140325015756-phpapp01.pptx
byAamirMaqsood8
 
PPTX
Performance Evaluation for Software Defined Networking (SDN) Based on Adaptiv...
byUniversity of Technology - Iraq
 
PPTX
Software_Defined_Networking.pptx
byAsfawGedamu
 
PPTX
Software_Defined_Networking with authorization.pptx
byAhmedGouda93
 
PPTX
22IT508 - Full Stack Development with Node and React.pptx
byPandiya Rajan
 
PPTX
Software Defined Networking(SDN) and practical implementation_trupti
bytrups7778
 
PPT
Software defined networking
byGoogle
 
PPTX
Software Defined Networking (SDN)
byAalok Shah
 
PPTX
Sdn not just a buzzword
byJorge Bonilla
 
PDF
SDN Security Talk - (ISC)2_3
byWen-Pai Lu
 
PPTX
lect1_intro_SDN introductionpptnew1.pptx
byanchitaa1
 
PPTX
btNOG 9 presentation Introduction to Software Defined Networking
byAPNIC
 
PDF
Introduction to Software Defined Networking (SDN) presentation by Warren Finc...
byAPNIC
 
PDF
Software Define Networking (SDN)
byPradeep Kumar TS
 
PPTX
Cis sem sdn
byLino Quivén
 
Software Defined Networking: Primer
byBangladesh Network Operators Group
 
Introduction to SDN
byMuhammad Moinur Rahman
 
F14_Class1.pptx
bySameer Ali
 
SDN - a new security paradigm?
bySophos Benelux
 
Software Define Network, a new security paradigm ?
byJean-Marc ANDRE
 
sdnppt-140325015756-phpapp01.pptx
byAamirMaqsood8
 
Performance Evaluation for Software Defined Networking (SDN) Based on Adaptiv...
byUniversity of Technology - Iraq
 
Software_Defined_Networking.pptx
byAsfawGedamu
 
Software_Defined_Networking with authorization.pptx
byAhmedGouda93
 
22IT508 - Full Stack Development with Node and React.pptx
byPandiya Rajan
 
Software Defined Networking(SDN) and practical implementation_trupti
bytrups7778
 
Software defined networking
byGoogle
 
Software Defined Networking (SDN)
byAalok Shah
 
Sdn not just a buzzword
byJorge Bonilla
 
SDN Security Talk - (ISC)2_3
byWen-Pai Lu
 
lect1_intro_SDN introductionpptnew1.pptx
byanchitaa1
 
btNOG 9 presentation Introduction to Software Defined Networking
byAPNIC
 
Introduction to Software Defined Networking (SDN) presentation by Warren Finc...
byAPNIC
 
Software Define Networking (SDN)
byPradeep Kumar TS
 
Cis sem sdn
byLino Quivén
 

More from Bangladesh Network Operators Group

PDF
Taming the Tide: Autoscaling Kubernetes for Cost-Effective Load Balancing
byBangladesh Network Operators Group
 
PDF
Automating ISP Networks Using Ansible and IPAM as a Source of Truth [SoT]
byBangladesh Network Operators Group
 
PDF
OFFENSIVE OPERATIONS : THE ANATOMY OF A NETWORK TAKEOVER
byBangladesh Network Operators Group
 
PDF
A Day in the Life of IPv6 Scanning by Matsuzaki ʻmazʼ
byBangladesh Network Operators Group
 
PDF
DNSSEC Implementation Journey at Prime Bank’s Domain
byBangladesh Network Operators Group
 
PDF
DNSSEC Deployment for .BD SLDs by Abdul Awal
byBangladesh Network Operators Group
 
PDF
Optimizing DNS Performance in Kubernetes: Challenges and Best Practices
byBangladesh Network Operators Group
 
PPTX
Understanding Universal Acceptance (UA) and Technical Challenges
byBangladesh Network Operators Group
 
PDF
Hybrid Mesh Firewall: Network firewall revolution
byBangladesh Network Operators Group
 
PDF
DNS & DNSSEC operational best practices - Sleep better at night with KINDNS i...
byBangladesh Network Operators Group
 
PDF
IPv6 Mostly Experience at APRICOT by Yoshinobu Matsuzaki (IIJ)
byBangladesh Network Operators Group
 
PDF
Fast Reroute in SR-MPLS by Md Abdullah Al Naser
byBangladesh Network Operators Group
 
PDF
DDoS Mitigation Strategies by Md. Abdul Awal
byBangladesh Network Operators Group
 
PDF
DNS & DNSSEC operational best practices - Sleep better at night with KINDNS i...
byBangladesh Network Operators Group
 
PDF
Optics101 for non-Optical (IP) folks by Tashi Phuntsho
byBangladesh Network Operators Group
 
PPTX
The Internet Service Providers and Connectivity Providers of ICANN
byBangladesh Network Operators Group
 
PPTX
Integration of AI and GenAI in Education and beyond
byBangladesh Network Operators Group
 
PPTX
Strengthening Cyber Security with Tools and Human Expertise
byBangladesh Network Operators Group
 
PDF
Mental Health and Workplace Culture in Tech:A Personal Perspective
byBangladesh Network Operators Group
 
PDF
Network Efficiency:The LLM Advantage on network infrastructures
byBangladesh Network Operators Group
 
Taming the Tide: Autoscaling Kubernetes for Cost-Effective Load Balancing
byBangladesh Network Operators Group
 
Automating ISP Networks Using Ansible and IPAM as a Source of Truth [SoT]
byBangladesh Network Operators Group
 
OFFENSIVE OPERATIONS : THE ANATOMY OF A NETWORK TAKEOVER
byBangladesh Network Operators Group
 
A Day in the Life of IPv6 Scanning by Matsuzaki ʻmazʼ
byBangladesh Network Operators Group
 
DNSSEC Implementation Journey at Prime Bank’s Domain
byBangladesh Network Operators Group
 
DNSSEC Deployment for .BD SLDs by Abdul Awal
byBangladesh Network Operators Group
 
Optimizing DNS Performance in Kubernetes: Challenges and Best Practices
byBangladesh Network Operators Group
 
Understanding Universal Acceptance (UA) and Technical Challenges
byBangladesh Network Operators Group
 
Hybrid Mesh Firewall: Network firewall revolution
byBangladesh Network Operators Group
 
DNS & DNSSEC operational best practices - Sleep better at night with KINDNS i...
byBangladesh Network Operators Group
 
IPv6 Mostly Experience at APRICOT by Yoshinobu Matsuzaki (IIJ)
byBangladesh Network Operators Group
 
Fast Reroute in SR-MPLS by Md Abdullah Al Naser
byBangladesh Network Operators Group
 
DDoS Mitigation Strategies by Md. Abdul Awal
byBangladesh Network Operators Group
 
DNS & DNSSEC operational best practices - Sleep better at night with KINDNS i...
byBangladesh Network Operators Group
 
Optics101 for non-Optical (IP) folks by Tashi Phuntsho
byBangladesh Network Operators Group
 
The Internet Service Providers and Connectivity Providers of ICANN
byBangladesh Network Operators Group
 
Integration of AI and GenAI in Education and beyond
byBangladesh Network Operators Group
 
Strengthening Cyber Security with Tools and Human Expertise
byBangladesh Network Operators Group
 
Mental Health and Workplace Culture in Tech:A Personal Perspective
byBangladesh Network Operators Group
 
Network Efficiency:The LLM Advantage on network infrastructures
byBangladesh Network Operators Group
 

Recently uploaded

PPTX
Bibhav Singh.pptx it's very useful for us it's in very good and very nice
byabhishekjaiswal5th33
 
PDF
Micro project .pdf drone technology Report
byRenitaMamgain
 
PPTX
Role of VMware and Cloud Computing in CyberSecurity.pptx
byalehanoor1325
 
PDF
Xnspy vs FlexiSPY: 2025 Monitoring Comparison
byMichael Carter
 
PPT
Memory Organization In Assembly Language
byumairmuhammad0409
 
PDF
tokiohotellistening.pdf for tokiohotelfans
byrafaelgombos1234
 
PDF
WShell Gameplay and Games of Games of Games
byzramirezmtz9
 
PPTX
PRITHVI theater, A true artist. Newzfeaturez.pptx
bysc05digital
 
PPTX
Abhishek Jaiswal.ppt.pptx for you it is very useful for me and I am sharing w...
byabhishekjaiswal5th33
 
PDF
ARTIFICIAL INTELLIGENCE DEVELOPMENT SERVICE
bydavidjohansen1597
 
PPTX
COĞRAFYA ödevi 70 sayfa güzeldir hayırlı olsun
bydtilter
 
PDF
How Social Media Management Tools Work – Step-by-Step Guide
byTurrboo
 
PDF
Hire-NET-Developers. Dot Net Developers
byDigisoft Solution
 
PDF
ARTIFICIAL INTELLIGENCE DEVELOPMENT SERVICE
bydavidjohansen1597
 
PPTX
CaseStudy-CloudMigration -For USE CASE -Customer Success Info -6-Aug-25.pptx
bywinlentech
 
PPTX
Computer Science Degree for College .pptx
byHanenek1
 
PPTX
ChatGPT on education positively snd negatively
by88rtgpscxx
 
PPT
Lecture_3 Network Securityeyeyggegeg.ppt
bysawsan202
 
PPTX
Computer Networks 01[1 using all terms].pptx
bywaqasahmedbhatti633
 
PPTX
SriLank SLT LTE Network Sharing V2.pptx
bynthuang
 
Bibhav Singh.pptx it's very useful for us it's in very good and very nice
byabhishekjaiswal5th33
 
Micro project .pdf drone technology Report
byRenitaMamgain
 
Role of VMware and Cloud Computing in CyberSecurity.pptx
byalehanoor1325
 
Xnspy vs FlexiSPY: 2025 Monitoring Comparison
byMichael Carter
 
Memory Organization In Assembly Language
byumairmuhammad0409
 
tokiohotellistening.pdf for tokiohotelfans
byrafaelgombos1234
 
WShell Gameplay and Games of Games of Games
byzramirezmtz9
 
PRITHVI theater, A true artist. Newzfeaturez.pptx
bysc05digital
 
Abhishek Jaiswal.ppt.pptx for you it is very useful for me and I am sharing w...
byabhishekjaiswal5th33
 
ARTIFICIAL INTELLIGENCE DEVELOPMENT SERVICE
bydavidjohansen1597
 
COĞRAFYA ödevi 70 sayfa güzeldir hayırlı olsun
bydtilter
 
How Social Media Management Tools Work – Step-by-Step Guide
byTurrboo
 
Hire-NET-Developers. Dot Net Developers
byDigisoft Solution
 
ARTIFICIAL INTELLIGENCE DEVELOPMENT SERVICE
bydavidjohansen1597
 
CaseStudy-CloudMigration -For USE CASE -Customer Success Info -6-Aug-25.pptx
bywinlentech
 
Computer Science Degree for College .pptx
byHanenek1
 
ChatGPT on education positively snd negatively
by88rtgpscxx
 
Lecture_3 Network Securityeyeyggegeg.ppt
bysawsan202
 
Computer Networks 01[1 using all terms].pptx
bywaqasahmedbhatti633
 
SriLank SLT LTE Network Sharing V2.pptx
bynthuang
 

Introduction to Software Defined Networking (SDN)

  • 1.
    Introduction to SDN MuhammahmadMoinur Rahman moin@1asia-ahl.com
  • 2.
    History of Networking •Blackbox networking equipments • Big name companies building switching/routing devices • Includes Proprietary/OEM Silicon Chip • Wrapped up with a closed source Operating System (e.g. A desktop PC with MS Windows and MS Office)
  • 3.
    Disadvantages of CurrentScenario Technology was not designed keeping today in mind • Massive Scalability • Multi Tenant Networks • Virtualization • Cloud Computing • Mobility (Users/Devices/VM)
  • 4.
    Disadvantages of CurrentScenario(Contd) Protocols are Box Centric; Not Fabric Centric • Difficult to configure correctly(consistency) • Difficult to add new features(upgrades) • Difficult to debug(look at all devices)
  • 5.
    Disadvantages of CurrentScenario(Contd) Closed Systems (Vendor Hardware) • Stuck with given interfaces (CLI, SNMP, etc.) • Hard to meaningfully collaborate • Vendors hesitant to open up • No way to add new features by yourself ANSWER: Software Defined Networking
  • 6.
    What is SDN? SDNis a framework to allow network administrators to automatically and dynamically manage and control a large number of network devices, services, topology, traffic paths, and packet handling (quality of service) policies using high-level languages and APIs. Management includes provisioning, operating, monitoring, optimizing, and managing FCAPS (fault, configuration, accounting, performance, and security) in a multi-tenant environment.
  • 7.
    Networking Planes • DataPlane • Carries Network User Traffic • Control Panel • Carried Signalling Traffic • Management Panel • Carries Administrative Traffic
  • 8.
  • 9.
    Need for SDN- Virtualization Use network resource • without worrying about where it is physically located • how much it is • how it is organized
  • 10.
    Need for SDN- Orchestration Should be able to control and manage thousands of devices with one command
  • 11.
    Need for SDN- Programmable Should be able to change behavior on the fly
  • 12.
    Need for SDN- Dynamic Scaling Should be able to change size, quantity, capacity
  • 13.
    Need for SDN- Automation • To lower OpEx • Minimize manual involvement • Troubleshooting • Reduce downtime • Policy enforcement • Provisioning/Re-provisioning/Segmentation of resources • Add new workloads, sites, devices, and resources
  • 14.
    Need for SDN- Visibility Monitor resources, connectivity
  • 15.
    Need for SDN- Performance Optimize network device utilization • Traffic engineering/Bandwidth management • Capacity optimization • Load balancing • High utilization • Fast failure handling
  • 16.
    Need for SDN- Multi Tenancy Tenants need complete control over their • Addresses • Topology • Routing • Security
  • 17.
    Need for SDN- Service Integration Provisioned on demand and placed appropriately on the traffic path • Load balancers • Firewalls • Intrusion Detection Systems (IDS)
  • 18.
    Alternative APIs • SouthboundAPIs: XMPP (Juniper), OnePK (Cisco) • Northbound APIs: I2RS, I2AEX, ALTO • Overlay: VxLAN, TRILL, LISP, STT, NVO3, PWE3, L2VPN, L3VPN • Configuration API: NETCONF • Controller: PCE, ForCES
  • 19.
    History Feb, 2011 -OpenFlow 1.1 Released Dec, 2011 - OpenFlow 1.2 Released Feb, 2012 - “Floodlight” Project Announced Apr, 2012 - Google announces at ONF Jul, 2012 - Vmware acquires Nicira Apr, 2013 - “OpenDaylight” Released
  • 20.
    Hardware Internals • LogicalView of a Switch • Physical Architecture of a Switch Switching Fabric Processor ASIC AISC data plane control plane Network O.S. ASIC ApplicationsApplications
  • 21.
    Internals of SDN •Southbound API: decouples the switch hardware from control function – Data plane from control plane • Switch Operating System: exposes switch hardware primitives Network O.S. ApplicationsApplications Applications Southbound API SDN Switch Operating System Switch Hardware Network O.S. ASIC ApplicationsApplications Current Switch Vertical stack SDN Switch Decoupled stack
  • 22.
    How SDN Works Controller(N. O.S.) ApplicationsApplicationsApplications Southbound API Switch H.W Switch O.S Switch H.W Switch O.S
  • 23.
    Implications of SDN Controller(N. O.S.) ApplicationsApplicationsApplications Southbound API Switch O.S Switch HW Switch O.S Switch HW Switch O.S Switch HW Global View Programmatic Control Current Networking SDN Enabled Environment Network O.S. ASIC ApplicationsApplications Network O.S. ASIC ApplicationsApplications Network O.S. ASIC ApplicationsApplications
  • 24.
    Implications of SDN(Cont) CurrentNetworking SDN Enabled Environment Controller (N. O.S.) ApplicationsApplicationsApplications Southbound API Switch O.S Switch HW Switch O.S Switch HW Switch O.S Switch HW • Distributed protocols • Each switch has a brain • Hard to achieve optimal solution • Network configured indirectly • Configure protocols • Hope protocols converge • Global view of the network • Applications can achieve optimal • Southbound API gives fine grained control over switch • Network configured directly • Allows automation • Allows definition of new interfaces Network O.S. ASIC ApplicationsApplications Network O.S. ASIC ApplicationsApplications Network O.S. ASIC ApplicationsApplications
  • 25.
    Dimensions of SDNEnvironments: Vendor Devices Vertical Stacks • Vendor bundles switch and switch OS • Restricted to vendor OS and vendor interface • Low operational overhead • One stop shop Whitebox Networking • Vendor provides hardware with no switch OS • Switch OS provided by third party • Flexibility in picking OS • High operational overhead • Must deal with multiple vendors
  • 26.
    Dimensions of SDNEnvironments: Switch Hardware Virtual: Overlay • Pure software implementation • Assumes programmable virtual switches • Run in Hypervisor or in the OS • Larger Flow Table entries (more memory and CPU) • Backward compatible • Physical switches run traditional protocols • Traffic sent in tunnels • Lack of visibility into physical network Physical: Underlay • Fine grained control and visibility into network • Assumes specialized hardware • Limited Flow Table entries
  • 27.
    Dimensions of SDNEnvironments: Southbound Interface OpenFlow • Flexible matching • L2, L3, VLAN, MPLS • Flexible actions • Encapsulation: IP-in-IP • Address rewriting: • IP address • Mac address BGP/XMPP/IS-IS/NetConf • Limited matching • IS-IS: L3 • BGP+MPLS: L3+MPLS • Limited actions • L3/l2 forwarding • Encapsulation
  • 28.
    Dimensions of SDNEnvironments: Controller Types Modular Controllers • Application code manipulates forwarding rules • E.g. OpenDaylight, Floodlight • Written in imperative languages • Java, C++, Python • Dominant controller style High Level Controllers • Application code specifies declarative policies • E.g. Frenetic, McNettle • Application code is verifiable • Amendable to formal verification • Written in functional languages • Nettle, OCamal
  • 29.
    • Controller Type •Modular: Floodlight • Southbound API: OpenFlow • OpenFlow 1.3 • SDN Device: Whitebox • (indigo) • SDN Flavor • Underlay+Overlay Ecosystem : BigSwitch
  • 30.
    • Controller Type •Modular: OpenContrail • Southbound API: XMPP/NetConf • BGP+MPLS • SDN Device: Vertical Stack • Propriety Junos • SDN Flavor • Overlay Ecosystem : Juniper
  • 31.
    SDN EcoSystem Arista OF +proprietary Underlay Vertical Stack Broadcom OF + proprietary Underlay Vertical Stack HP OF Underlay Vertical Stack Cisco OF + proprietary Underlay+Overlay Vertical Stack FloodLight OF Underlay+Overlay Whitebox Dell OF Underlay Vertical Stack HP OF Underlay Vertical Stack Alcatel BGP Overlay Vertical Stack Juniper BGP+NetConf Overlay Vertical Stack
  • 32.
    OpenFlow • Developed inStanford • Standardized by Open Networking Foundation (ONF) • Current Version 1.4 • Version implemented by switch vendors: 1.3 • Allows control of underlay + overlay • Overlay switches: OpenVSwitch/Indigo-light PC
  • 33.
    SDN vs OpenFlow •Leading SDN protocol • Decouples control and data plane by giving a controller the ability to install flow rules on switches(Bare Metal) • Hardware or software switches can use OpenFlow • Spec driven by ONF
  • 34.
    How SDN Works:OpenFlow Controller (N. O.S.) ApplicationsApplicationsApplications Southbound API Switch H.W Switch O.S Switch H.W Switch O.S OpenFlow OpenFlow
  • 35.
    OpenFlow: Anatomy ofa Flow Table Entry Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot L4 sport L4 dport Match Action Counter 1. Forward packet to zero or more ports 2. Encapsulate and forward to controller 3. Send to normal processing pipeline 4. Modify Fields When to delete the entry VLAN pcp IP ToS Priority Time-out What order to process the rule # of Packet/Bytes processed by the rule
  • 36.
    Examples Switching * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * 00:1f:.. ** * * * * * port6 Flow Switching port3 Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action 00:20.. 00:1f.. 0800 vlan1 1.2.3.4 5.6.7.8 4 17264 80 port6 Firewall * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * * * * * * * 22 drop 37
  • 37.
    Examples Routing * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * ** * 5.6.7.8 * * * port6 VLAN Switching * Switch Port MAC src MAC dst Eth type VLAN ID IP Src IP Dst IP Prot TCP sport TCP dport Action * * vlan1 * * * * * port6, port7, port9 00:1f.. 38
  • 38.
    Data Path (Hardware) ControlPath OpenFlow OpenFlow Controller OpenFlow Protocol (SSL/TCP) 39 OpenFlow: How it works
  • 39.
    Controller PC Hardware Layer Software Layer Flow Table MAC src MAC dst IP Src IP Dst TCP sport TCP dport Action OpenFlowClient **5.6.7.8*** port 1 port 4port 3port 2port 1 1.2.3.45.6.7.8 40 OpenFlow: Anatomy of a Flow Table Entry
  • 40.
    SDN Components :Hardwares OpenFlow Compliant (1.0-1.4) Switch • HP 8200 ZL, 6600, 6200ZL • Brocade 5400ZL, 3500 • IBM NetIron • Juniper OCX1100 • Baremetal Switch • OpenVSwitch
  • 41.
    SDN Components :Controllers OpenFlow Compliant (1.0-1.4) Controller • POX: (Python) Pox as a general SDN controller that supports OpenFlow. It has a high-level SDN API including a queriable topology graph and support for virtualization. • IRIS: (Java) a Resursive SDN Openflow Controller created by IRIS Research Team of ETRI. • MUL: (C) MūL, is an openflow (SDN) controller. • NOX: (C++/Python) NOX was the first OpenFlow controller. • Jaxon: (Java) Jaxon is a NOX-dependent Java-based OpenFlow Controller. • Trema: (C/Ruby) Trema is a full-stack framework for developing OpenFlow controllers in Ruby and C. • Beacon: (Java) Beacon is a Java-based controller that supports both event-based and threaded operation. • Floodlight: (Java) The Floodlight controller is Java-based OpenFlow Controller. It was forked from the Beacon controller, originally developed by David Erickson at Stanford. • Maestro: (Java) Maestro is an OpenFlow "operating system" for orchestrating network control applications. • NDDI - OESS: OESS is an application to configure and control OpenFlow Enabled switches through a very simple and user friendly User Interface. • Ryu: (Python) Ryu is an open-sourced Network Operating System (NOS) that supports OpenFlow. • NodeFlow (JavaScript) NodeFlow is an OpenFlow controller written in pure JavaScript for Node.JS. • ovs-controller (C) Trivial reference controller packaged with Open vSwitch.
  • 42.
  • 43.
    Objectives • Basics ofrunning Mininet in a virtual machine. • Mininet facilitates creating and manipulating Software Defined Networking components. • Explore OpenFlow, which is an open interface for controlling the network elements through their forwarding tables. A network element may be converted into a switch, router or even an access points via low-level primitives defined in OpenFlow. • Experience with the platforms and debugging tools most useful for developing network control applications on OpenFlow. • Run the Ryu controller with a sample application • Use various commands to gain experience with OpenFlow control of OpenvSwitch
  • 44.
    Topology • Three hostsnamed h1, h2 and h3 respectively. Each host has an Ethernet interface called h1-eth0, h2-eth0 and h3-eth0 respectively. • Three hosts are connected through a switch names s1. The switch s1 has three ports named s1-eth1, s1-eth2 and s1-eth3. • The controller is connected on the loopback interface (in real life this may or may not be the case, it means the switch and controller are built in a single box). The controller is identified as c0 and connected through port 6633.
  • 45.
    Topology Diagram C0 -Controller Switch H.W S1 Switch OpenFlow H1 – h1-eth0 H2 – h2-eth0 H3 – h3-eth0 S1-eth2 S1-eth1 S1-eth0
  • 46.
    RYU Openflow controller Ensurethat no other controller is present root@mininet-vm:~# killall controller controller: no process found root@mininet-vm:~# Note that 'controller' is a simple OpenFlow reference controller implementation in linux. We want to ensure that this is not running before we start our own controller.
  • 47.
    RYU Openflow controller(Cont) Clearall mininet components root@mininet-vm:~# mn -c *** Removing excess controllers/ofprotocols/ofdatapaths/pings/noxes killall controller ofprotocol ofdatapath ping nox_core lt-nox_core ovs-openflowd ovs-controller udpbwtest mnexec ivs 2> /dev/null killall -9 controller ofprotocol ofdatapath ping nox_core lt-nox_core ovsopenflowd ovs-controller udpbwtest mnexec ivs 2> /dev/null pkill -9 -f "sudo mnexec" *** Removing junk from /tmp rm -f /tmp/vconn* /tmp/vlogs* /tmp/*.out /tmp/*.log *** Removing old X11 tunnels *** Removing excess kernel datapaths ps ax | egrep -o 'dp[0-9]+' | sed 's/dp/nl:/' *** Removing OVS datapathsovs-vsctl --timeout=1 list-br ovs-vsctl del-br s1 ovs-vsctl del-br s2 ovs-vsctl del-br s3 ovs-vsctl del-br s4 *** Removing all links of the pattern foo-ethX ip link show | egrep -o '(w+-ethw+)' *** Cleanup complete. root@mininet-vm:~#
  • 48.
    RYU Openflow controller(Cont) Startthe Ryu controller root@mininet-vm:~# ryu-manager --verbose ./simple_switch_13.py loading app ./simple_switch_13.py loading app ryu.controller.ofp_handler instantiating app ./simple_switch_13.py of SimpleSwitch13 instantiating app ryu.controller.ofp_handler of OFPHandler BRICK SimpleSwitch13 CONSUMES EventOFPSwitchFeatures CONSUMES EventOFPPacketIn BRICK ofp_event PROVIDES EventOFPSwitchFeatures TO {'SimpleSwitch13': set(['config'])} PROVIDES EventOFPPacketIn TO {'SimpleSwitch13': set(['main'])} CONSUMES EventOFPHello CONSUMES EventOFPErrorMsg CONSUMES EventOFPEchoRequest CONSUMES EventOFPPortDescStatsReply CONSUMES EventOFPSwitchFeatures Understanding simple_switch.py
  • 49.
    MiniNet Environment root@mininet-vm:~# mn--topo=tree,1,3 --mac --controller=remote --switch ovsk,protocols=OpenFlow13 *** Creating network *** Adding controller *** Adding hosts: h1 h2 h3 *** Adding switches: s1 *** Adding links: (h1, s1) (h2, s1) (h3, s1) *** Configuring hosts h1 h2 h3 *** Starting controller *** Starting 1 switches s1 *** Starting CLI: mininet>
  • 50.
    MiniNet Environment(Cont) Monitor controllerto ensure that the switch connects connected socket:<eventlet.greenio.GreenSocket object at 0xa986c0c> address: ('127.0.0.1', 42733) connected socket:<eventlet.greenio.GreenSocket object at 0xa986cec> address: ('127.0.0.1', 42734) hello ev <ryu.controller.ofp_event.EventOFPHello object at 0xa9897ac> move onto config mode EVENT ofp_event->SimpleSwitch13 EventOFPSwitchFeatures switch features ev version: 0x4 msg_type 0x6 xid 0xb15cb575 OFPSwitchFeatures(auxiliary_id=0,capabilities=71,datapath_id= 1,n_buffers=256,n_tables=254) move onto main mode
  • 51.
    MiniNet Environment(Cont) Dump flowson switch s1 mininet> dpctl dump-flows -O OpenFlow13 *** s1 ----------------------------------------- OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x0, duration=2.481s, table=0, n_packets=0, n_bytes=0, priority=0 actions=FLOOD,CONTROLLER:64 mininet>
  • 52.
    MiniNet Environment(Cont) Passing Packets mininet>h1 ping h2 PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. 64 bytes from 10.0.0.2: icmp_req=1 ttl=64 time=5.10 ms 64 bytes from 10.0.0.2: icmp_req=2 ttl=64 time=0.238 ms 64 bytes from 10.0.0.2: icmp_req=3 ttl=64 time=0.052 ms 64 bytes from 10.0.0.2: icmp_req=4 ttl=64 time=0.051 ms ^C --- 10.0.0.2 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3001ms rtt min/avg/max/mdev = 0.051/1.360/5.100/2.160 ms mininet>
  • 53.
    Controller Environment Monitor newmessages in the controller window EVENT ofp_event->SimpleSwitch13 EventOFPPacketIn EVENT ofp_event->SimpleSwitch13 EventOFPPacketIn packet in from 00:00:00:00:00:01 port 1 to 00:00:00:00:00:02 on dpid 1 associate 00:00:00:00:00:01 with port 1 on dpid 1 packet in from 00:00:00:00:00:02 port 2 to 00:00:00:00:00:01 on dpid 1 associate 00:00:00:00:00:02 with port 2 on dpid 1 add unicast flow from 00:00:00:00:00:02 port 2 to 00:00:00:00:00:01 port 1 on dpid 1 EVENT ofp_event->SimpleSwitch13 EventOFPPacketIn packet in from 00:00:00:00:00:01 port 1 to 00:00:00:00:00:02 on dpid 1 add unicast flow from 00:00:00:00:00:01 port 1 to 00:00:00:00:00:02 port 2 on dpid 1
  • 54.
    Mininet Environment Dump flowsagain to view differences mininet> dpctl dump-flows -O OpenFlow13 *** s1 ------------------------------------------------------------------------ OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x0, duration=38.044s, table=0, n_packets=0, n_bytes=0, priority=10,in_port=1,dl_src=00:00:00:00:00:01,dl_dst=ff:ff:ff:ff:ff:ff actions=ALL cookie=0x0, duration=37.044s, table=0, n_packets=3, n_bytes=238, priority=100,in_port=1,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:02 actions=output:2 cookie=0x0, duration=38.043s, table=0, n_packets=0, n_bytes=0, priority=10,in_port=2,dl_src=00:00:00:00:00:02,dl_dst=ff:ff:ff:ff:ff:ff actions=ALL cookie=0x0, duration=38.043s, table=0, n_packets=4, n_bytes=336, priority=100,in_port=2,dl_src=00:00:00:00:00:02,dl_dst=00:00:00:00:00:01 actions=output:1 cookie=0x0, duration=38.043s, table=0, n_packets=0, n_bytes=0, priority=5,in_port=2,dl_src=00:00:00:00:00:02,dl_type=0x88cc actions=drop cookie=0x0, duration=38.043s, table=0, n_packets=0, n_bytes=0, priority=5,in_port=1,dl_src=00:00:00:00:00:01,dl_type=0x88cc actions=drop cookie=0x0, duration=38.043s, table=0, n_packets=0, n_bytes=0, priority=10,in_port=2,dl_src=00:00:00:00:00:02,dl_dst=01:00:00:00:00:00/01:00:00 :00:00:00 actions=ALL cookie=0x0, duration=38.044s, table=0, n_packets=0, n_bytes=0, priority=10,in_port=1,dl_src=00:00:00:00:00:01,dl_dst=01:00:00:00:00:00/01:00:00 :00:00:00 actions=ALL cookie=0x0, duration=73.001s, table=0, n_packets=3, n_bytes=294, priority=0 actions=FLOOD,CONTROLLER:64
  • 55.
    Mininet Environment Running ahigh bandwidth flow mininet> iperf *** Iperf: testing TCP bandwidth between h1 and h2 Waiting for iperf to start up...*** Results: ['5.52 Gbits/sec', '5.52 Gbits/sec'] mininet>
  • 56.
    Mininet Environment Dump flowsto see the flows which match mininet> dpctl dump-flows -O OpenFlow13 *** s1 ------------------------------------------------------------------------ OFPST_FLOW reply (OF1.3) (xid=0x2): ... ... cookie=0x0, duration=209.485s, table=0, n_packets=2384026, n_bytes=3609389036, priority=100,in_port=1,dl_src=00:00:00:00:00:01,dl_dst=00:00:00:00:00:0a actions=output:10 ... ... cookie=0x0, duration=209.485s, table=0, n_packets=27163, n_bytes=1792770, priority=100,in_port=10,dl_src=00:00:00:00:00:0a,dl_dst=00:00:00:00:00:01 actions=output:1 ... ... cookie=0x0, duration=392.419s, table=0, n_packets=150, n_bytes=11868, priority=0 actions=FLOOD,CONTROLLER:6
  • 57.
    Refereces 1. Mininet/Openflow Tutorials– Dean Pemberton 2. SDN – The Next Wave of Networking – Siva Valiappan
  • 58.