Software–Defined Networking Meron Aymiro. What is Software-Defined Networking?  Software-Defined Networking (SDN) has the potential of to transcend the.

Slides:



Advertisements
Similar presentations
OpenFlow and Software Defined Networks. Outline o The history of OpenFlow o What is OpenFlow? o Slicing OpenFlow networks o Software Defined Networks.
Advertisements

Layer 3 Switching. Routers vs Layer 3 Switches Both forward on the basis of IP addresses But Layer 3 switches are faster and cheaper However, Layer 3.
OpenFlow Costin Raiciu Using slides from Brandon Heller and Nick McKeown.
Author : Martín Casado, Teemu Koponen, Scott Shenker, Amin Tootoonchian Publisher : Presenter : Pei-Hua Huang Date : 2013/10/02 Fabric: A Retrospective.
© Copyright 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Software Defined Networking.
SDN and Openflow.
Network Innovation using OpenFlow: A Survey
1© Copyright 2015 EMC Corporation. All rights reserved. SDN INTELLIGENT NETWORKING IMPLICATIONS FOR END-TO-END INTERNETWORKING Simone Mangiante Senior.
Jaehoon (Paul) Jeong, Hyoungshick Kim, and Jung-Soo Park
Class 3: SDN Stack Theophilus Benson. Outline Background – Routing in ISP – Cloud Computing SDN application stack revisited Evolution of SDN – The end.
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. New Virtual Application.
Software-defined Networks October 2009 With Martin Casado and Scott Shenker And contributions from many others.
Enabling Innovation Inside the Network Jennifer Rexford Princeton University
Nick McKeown, Tom Anderson, Hari Balakrishnan, Guru Parulkar, Larry Peterson, Jennifer Rexford, Scott Shenker, Jonathan Turner, SIGCOM CCR, 2008 Presented.
Software-Defined Networks Jennifer Rexford Princeton University.
Software Defined Networks and OpenFlow SDN CIO Summit 2010 Nick McKeown & Guru Parulkar Stanford University In collaboration with Martin Casado and Scott.
Software-Defined Networking - Attributes, candidate approaches, and use cases - MK. Shin, ETRI M. Hoffmann, NSN.
Open networking w/ Marist College Software Defined Networks.
FUTURE OF NETWORKING SAJAN PAUL JUNIPER NETWORKS.
SDN AND OPENFLOW SPECIFICATION SPEAKER: HSUAN-LING WENG DATE: 2014/11/18.
Module 1: Configuring Routing by Using Routing and Remote Access.
A survey of SDN: Past, Present and Future of Programmable Networks Speaker :Yu-Fu Huang Advisor :Dr. Kai-Wei Ke Date:2014/Sep./30 1.
Aaron Gember, Theophilus Benson, Aditya Akella University of Wisconsin-Madison.
SDN and Openflow. Motivation Since the invention of the Internet, we find many innovative ways to use the Internet – Google, Facebook, Cloud computing,
SDN Management Layer DESIGN REQUIREMENTS AND FUTURE DIRECTION NO OF SLIDES : 26 1.
1 | © 2015 Infinera Open SDN in Metro P-OTS Networks Sten Nordell CTO Metro Business Group
SOFTWARE DEFINED NETWORKING/OPENFLOW: A PATH TO PROGRAMMABLE NETWORKS April 23, 2012 © Brocade Communications Systems, Inc.
Network Virtualization Sandip Chakraborty. In routing table we keep both the next hop IP (gateway) as well as the default interface. Why do we require.
Introduction to Avaya’s SDN Architecture February 2015.
OpenFlow: Enabling Innovation in Campus Networks Yongli Chen.
© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Embrace the Future of.
Fabric: A Retrospective on Evolving SDN Presented by: Tarek Elgamal.
Software Defined Networking and OpenFlow Geddings Barrineau Ryan Izard.
Programming Assignment 2 Zilong Ye. Traditional router Control plane and data plane embed in a blackbox designed by the vendor high-seed switching fabric.
Atrium Router Project Proposal Subhas Mondal, Manoj Nair, Subhash Singh.
Preliminaries: EE807 Software-defined Networked Computing KyoungSoo Park Department of Electrical Engineering KAIST.
Communication Needs in Agile Computing Environments Michael Ernst, BNL ATLAS Distributed Computing Technical Interchange Meeting University of Tokyo May.
Software Defined Networking BY RAVI NAMBOORI. Overview  Origins of SDN.  What is SDN ?  Original Definition of SDN.  What = Why We need SDN ?  Conclusion.
SDN & NFV Driving Additional Value into Managed Services.
Developing an Implementation Framework for the Future Internet using the Y-Comm Architecture, SDN and NFV Glenford Mapp Associate Professor Middlesex University,
Instructor Materials Chapter 7: Network Evolution
SDN challenges Deployment challenges
Multi-layer software defined networking in GÉANT
Distributed Mobility Management for Future 5G Networks : Overview and Analysis of Existing Approaches IEEE Wireless Communications January 2015 F. Giust,
Author: Ragalatha P, Manoj Challa, Sundeep Kumar. K
Presenter: Ciaran Roche
Week 6 Software Defined Networking (SDN): Concepts
Introduction to Networks
Software Defined Networking (SDN)
Stanford University Software Defined Networks and OpenFlow SDN CIO Summit 2010 Nick McKeown & Guru Parulkar In collaboration with Martin Casado and Scott.
A Novel Framework for Software Defined Wireless Body Area Network
Chapter 2: Static Routing
Implement Inter-VLAN Routing
Indigo Doyoung Lee Dept. of CSE, POSTECH
The Stanford Clean Slate Program
Cloud Computing and Cloud Networking
CS 31006: Computer Networks – The Routers
Software Defined Networking (SDN)
2 - IP Routing.
Software Defined Networking
Enabling Innovation Inside the Network
Firewalls Routers, Switches, Hubs VPNs
Implement Inter-VLAN Routing
Virtual LAN VLAN Trunking Protocol and Inter-VLAN Routing
Implement Inter-VLAN Routing
Software Defined Networking
Chapter-6 Access Network Design.
Implement Inter-VLAN Routing
Multicasting Unicast.
An Introduction to Software Defined Networking and OpenFlow
Presentation transcript:

Software–Defined Networking Meron Aymiro

What is Software-Defined Networking?  Software-Defined Networking (SDN) has the potential of to transcend the limitations of the current networking infrastructures.  “The basic premise behind SDN is that by separating control of network functions from hardware devices, administrators acquire more power to route and direct traffic in response to changing requirements.” 1  Control Plane  Data plane

Issues with Traditional IP Networking They are complex and hard to manage.  The control plane and the data plane are joined together in a network device.  During configuration - Each individual network device must be configured separately using Vendor-specific commands  Network environments have to endure the dynamics of faults and adapt to load changes  Slow progressions of improvement.

Why use SDN? The separation of the control plane from data plane will give ways  Directly programmable  Simplification of network devices  Inexpensive  Flexibility  Scalability  Optimization of resources

OpenFlow  OpenFlow is the first standard communications interface defined between the control and forwarding layers of an SDN architecture  This communication protocol that gives access to the forwarding plane of a network switch or router over the network.  OpenFlow enabled network controllers to determine the path of network packets across a network of switches.  Currently most vendor of commercial switches now include support of the OpenFlow application programming interface (API) 

Layers of SDN

SDN is the future of networking.  SDN was projected to grow into a $3.7 billion industry in 2016  SDN is already servicing big companies like Google, Facebook, Yahoo, Verizon  Since vedor- locking will not be an issue with SDN, it will invite more research and innovation

References arXiv: arXiv: [cs.NI]

Thank You.

Questions?