Improving Network Management with Software Defined Network Group 5 : z5001855 Xuling Wu z5026754 Haipeng Jiang z5031759 Sichen Wu z5044151 Aparna Sanil.

Slides:



Advertisements
Similar presentations
Resonance: Dynamic Access Control in Enterprise Networks Ankur Nayak, Alex Reimers, Nick Feamster, Russ Clark School of Computer Science Georgia Institute.
Advertisements

1 Resonance: Dynamic Access Control in Enterprise Networks Ankur Nayak, Alex Reimers, Nick Feamster, Russ Clark School of Computer Science Georgia Institute.
1 Resonance: Dynamic Access Control in Enterprise Networks Ankur Nayak, Alex Reimers, Nick Feamster, Russ Clark School of Computer Science Georgia Institute.
Towards Software Defined Cellular Networks
CloudWatcher: Network Security Monitoring Using OpenFlow in Dynamic Cloud Networks or: How to Provide Security Monitoring as a Service in Clouds? Seungwon.
NDN in Local Area Networks Junxiao Shi The University of Arizona
Software-Defined Networking, OpenFlow, and how SPARC applies it to the telecommunications domain Pontus Sköldström - Wolfgang John – Elisa Bellagamba November.
SDN and Openflow.
Network Innovation using OpenFlow: A Survey
Scalable Flow-Based Networking with DIFANE 1 Minlan Yu Princeton University Joint work with Mike Freedman, Jennifer Rexford and Jia Wang.
Building Your Own Firewall Chapter 10. Learning Objectives List and define the two categories of firewalls Explain why desktop firewalls are used Explain.
A Guide to major network components
Barracuda Networks Confidential1 Barracuda Backup Service Integrated Local & Offsite Data Backup.
Installing and Maintaining ISA Server. Planning an ISA Server Deployment Understand the current network infrastructure Review company security policies.
Scalable Server Load Balancing Inside Data Centers Dana Butnariu Princeton University Computer Science Department July – September 2010 Joint work with.
Hands-On Microsoft Windows Server 2008 Chapter 11 Server and Network Monitoring.
Networking Components Chad Benedict – LTEC
Windows Server 2008 Chapter 11 Last Update
Network Devices BY JACKSON HARDESTY. Hubs  Hubs are a now outdated way of sending signals at layer 2 compared to switches.  Hubs are used primarily.
Clinic Security and Policy Enforcement in Windows Server 2008.
Networking Components Christopher Biles LTEC Assignment 3.
Internet Service Provisioning Phase - I August 29, 2003 TSPT Web:
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Network Addressing Networking for Home and Small Businesses – Chapter 5.
Network Components: Assignment Three
Frenetic: A Programming Language for Software Defined Networks Jennifer Rexford Princeton University Joint work with Nate.
Software-Defined Networks Jennifer Rexford Princeton University.
Common Devices Used In Computer Networks
Version 4.0. Objectives Describe how networks impact our daily lives. Describe the role of data networking in the human network. Identify the key components.
OpenFlow: Enabling Innovation in Campus Networks
Objectives Configure routing in Windows Server 2008 Configure Routing and Remote Access Services in Windows Server 2008 Network Address Translation 1.
Professor OKAMURA Laboratory. Othman Othman M.M. 1.
Repeaters and Hubs Repeaters: simplest type of connectivity devices that regenerate a digital signal Operate in Physical layer Cannot improve or correct.
Othman Othman M.M., Koji Okamura Kyushu University 1.
© 2006 Cisco Systems, Inc. All rights reserved. Optimizing Converged Cisco Networks (ONT) Module 6: Implement Wireless Scalability.
NETWORK COMPONENTS Assignment #3. Hub A hub is used in a wired network to connect Ethernet cables from a number of devices together. The hub allows each.
IPower: An Energy Conservation System for Intelligent Buildings International Journal of Sensor Networks Yu-Chee Tseng, You-Chiun Wang, and Lun- Wu Yeh.
Othman Othman M.M., Koji Okamura Kyushu University 1.
Vic Liu Liang Xia Zu Qiang Speaker: Vic Liu China Mobile Network as a Service Architecture draft-liu-nvo3-naas-arch-01.
National Chi Nan University Automatic Event-Driven System for Network Management Author: Ya-Ling Wang, Arak Sae Yuan, Quincy Wu Date : 2/21/2012.
SDN AND OPENFLOW SPECIFICATION SPEAKER: HSUAN-LING WENG DATE: 2014/11/18.
Switch Features Most enterprise-capable switches have a number of features that make the switch attractive for large organizations. The following is a.
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.
1 OFF SYMB - 12/7/2015 Firewalls Basics. 2 OFF SYMB - 12/7/2015 Overview Why we have firewalls What a firewall does Why is the firewall configured the.
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.
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 4: Planning and Configuring Routing and Switching.
Network management Network management refers to the activities, methods, procedures, and tools that pertain to the operation, administration, maintenance,
Company LOGO Network Management Architecture By Dr. Shadi Masadeh 1.
1 Welcome to Designing a Microsoft Windows 2000 Network Infrastructure.
Header Space Analysis: Static Checking for Networks Broadband Network Technology Integrated M.S. and Ph.D. Eun-Do Kim Network Standards Research Section.
Fabric: A Retrospective on Evolving SDN Presented by: Tarek Elgamal.
0 Agile Controller Key Message KM 1: Service Experience-centered Network Redefinition KM 2: Network-wide United Security KM 3: Product Openness and Collaboration.
Software Defined Networking BY RAVI NAMBOORI. Overview  Origins of SDN.  What is SDN ?  Original Definition of SDN.  What = Why We need SDN ?  Conclusion.
SDN controllers App Network elements has two components: OpenFlow client, forwarding hardware with flow tables. The SDN controller must implement the network.
Programming SDN 1 Problems with programming with POX.
Instructor Materials Chapter 7: Network Evolution
Multi-layer software defined networking in GÉANT
University of Maryland College Park
CONNECTING TO THE INTERNET
Overview of SDN Controller Design
Software Defined Networking (SDN)
Software Defined Networking (SDN)
IS4680 Security Auditing for Compliance
70-293: MCSE Guide to Planning a Microsoft Windows Server 2003 Network, Enhanced Chapter 4: Planning and Configuring Routing and Switching.
Firewalls Jiang Long Spring 2002.
Cloud-Enabling Technology
OpenSec:Policy-Based Security Using Software-Defined Networking
Zhihui Sun , Fazhi Qi, Tao Cui
An Introduction to Software Defined Networking and OpenFlow
Presentation transcript:

Improving Network Management with Software Defined Network Group 5 : z Xuling Wu z Haipeng Jiang z Sichen Wu z Aparna Sanil z Yun Feng z Kejiao Li z Dongquan Qi 1

Summary To operate, maintain and secure a communication was always a challenge. SDN separates the control plane and data plane and thereby breaks the rigid underlying infrastructure of network system. SDN introduces a centralized software program called controller for the operating the entire network. We also talk about prototype deployments in home and campus networks and how SDN improves the network management and performance. 2

Outline Introduction SDN Architecture Case study Conclusion 3

Introduction Why ? Difficulties to implement high-level policies on Low-level infrastructure. Various large numbers of routers, switches,etc. Closed equipment Software bundled with hardware Inflexibility Hard to introduce&deploy new protocol Complex environment (network states, events) Little mechanism to respond automatically manually adjust network configurations. 4 Router Management/ Policy plane Control plane Data plane

How? 5 SDN Concept: Separate Control plane and Data plane. Decision Maker (software) Packet forwarder( hardware)

Southbound interface OpenFlow Controller Northbound interface Procera 6 SDN Architecture

7

OpenFlow is a common southbound SDN interfaces. The Open Networking Foundation (ONF) is responsible for standardizing the OpenFlow protocol. There are a variety of OpenFlow controllers, e.g.: NOX C++ or Python to program Floodlight Java-based Maestro Multithreading 8 OpenFlow

A network control framework. Purpose: helps operators express event-driven network policies using a high-level functional programming language. Serves as a glue between high-level event-driven network policies and low-level network configuration. Use control domains to express event-driven network policies. 9 Procera

10 Procera Control domain

11 Procera Architecture

Event source: network components or middle boxes that can send dynamic events to the procera controller. e.g.: IDS, Authentication systems, SNMP Policy engine: parsing the network policy expressed with a policy language, also processing various events that come from event sources Language: allows operators to specify complex network policies in a simple language based on functional reactive programming (FRP) 12

Establish a connection to each OpenFlow-capable switch through the OpenFlow protocol. Insert, delete, or modify packet forwarding rules in switches through this connection. Also react to packet-in events and switch-join events that come from switches. – For packet-in events, install relevant forwarding rules in switch – For switch-join events, establish a new connection with that specific switch 13 Controller

Case study CAMPUS NETWORK HOME NETWORK 1.POLICY 2.DEPLOYMENT STATUS 1.IMPROVEMENT 2.POLICY 3.DEPLOYMENT STATUS 14

Campus Network-Policy Require unregistered end-host device to undergo an authentication process via an authentication web portal. After successful authentication, the device is scanned for possible vulnerabilities. If none are found, the device is finally granted access to the internal network and the Internet. Other events: 5 hours’ inactivity & infection. 15

Transitions and events in campus network 16

Implementing such complex policy relies on many technologies. eg. VLAN, firewall rules, etc. Requires network operators to independently configure multiple different components, including middle boxes, management servers, and numerous ad hoc scripts. Procera can automatically finish these configuration work, which significantly simplifies the expression of these types of policies. 17

Campus network deployment status 18

Home Network-Improvement Limited Visibility into broadband performance and overall status. Inflexible closed software installed in common home gateways  hard to introduce new functions for home network. ISPs start to enforce monthly bandwidth caps to limit data usage.  users need a new system to monitor and manage devices data usage. Issues 19

Improving Visibility: BISMARK BISmark is a collection of home gateways installed in households, a centralized management and data collection server, and multiple measurement servers deployed around the world. Improve visibility into home broadband performance and its overall status. Provide continuously monitoring of the status of home networks, and ensure that customers receive their promised service. Improving Control: SDN SDN makes it much easier to introduce new functions. It is possible to combine BISmark’s measurement data and procera to build a management system that reacts to various conditions of the home. network. Example: Traffic shapping, proactively prefetching and caching. SDN paradigm enable a central controller to make various kinds of traffic engineering decisions and pushing rules to home gateways to enforce such policy greatly increases the flexibility of home network management. 20

Uncapped device can access the Internet normally. When the device’s data usage exceeds the monthly cap value set by the home user, it is blocked-Capped. The reverse transition is triggered when the cap value is increased or data usage of devices are reset due to the end of a billing cycle. Procera automatically detects caped or uncapped devices every 5sec. 21

Home Network- Deployment Status NetGear WNDR 3700v2 and 3800 wireless routers are used as OpenFlow-capable forwarding devices. Home users use the router as a wireless access point and observe no particular difference from any normal wireless access point. The wireless router runs a customized firmware based on OpenWrt that implements OpenFlow protocol version

Conclusion Network configuration is becoming complex due to Continually changing network state & Low-level per-device network configuration. SDN basic idea: separating control plane from switches, managing the whole network, rather than individual network component. The practice of Procera based on SDN structure in these two examples demonstrate OpenFlow-CAPABLE switches give possibilities for expressing complex network policies while reducing management in settings. 23

QUESTIONS? 24

Thank you 25