Reactive Logic in Software-Defined Networking: Measuring Flow-Table Requirements Maurizio Dusi, Roberto Bifulco, Francesco Gringoli”, Fabian Schneider*

Slides:

Advertisements

Similar presentations

Routing Routing in an internetwork is the process of directing the transmission of data across two connected networks. Bridges seem to do this function.

Advertisements

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

Campus Testbed for Network Management and Operations Nick Feamster Georgia Tech Joint with Ankur Nayak, Russ Clark, Ron Hutchins, Campus OIT Also input.

Jennifer Rexford Princeton University MW 11:00am-12:20pm Logically-Centralized Control COS 597E: Software Defined Networking.

Logically Centralized Control Class 2. Types of Networks ISP Networks – Entity only owns the switches – Throughput: 100GB-10TB – Heterogeneous devices:

1 IP Forwarding Relates to Lab 3. Covers the principles of end-to-end datagram delivery in IP networks.

IP Forwarding Relates to Lab 3.

An Overview of Software-Defined Network Presenter: Xitao Wen.

ClosedFlow: OpenFlow-like Control over Proprietary Devices

Towards Virtual Routers as a Service 6th GI/ITG KuVS Workshop on “Future Internet” November 22, 2010 Hannover Zdravko Bozakov.

Scalable Network Virtualization in Software-Defined Networks

Traffic Management - OpenFlow Switch on the NetFPGA platform Chun-Jen Chung( ) SriramGopinath( )

1 Controlling High Bandwidth Aggregates in the Network.

Shadow Configurations: A Network Management Primitive Richard Alimi, Ye Wang, Y. Richard Yang Laboratory of Networked Systems Yale University.

An Overview of Software-Defined Network

FlowSense: Monitoring Network Utilization with Zero Measurement Cost Curtis Yu 1, Cristian Lumezanu 2, Yueping Zhang 2, Vishal Singh 2, Guofei Jiang 2,

1 IP Forwarding Relates to Lab 3. Covers the principles of end-to-end datagram delivery in IP networks.

OpenFlow Switch Limitations. Background: Current Applications Traffic Engineering application (performance) – Fine grained rules and short time scales.

An Overview of Software-Defined Network Presenter: Xitao Wen.

And how they are used. Hubs send data to all of the devices that are plugged into them. They have no ability to send packets to the correct ports. Cost~$35.

CRIO: Scaling IP Routing with the Core Router-Integrated Overlay Xinyang (Joy) Zhang Paul Francis Jia Wang Kaoru Yoshida.

1 IP Forwarding Relates to Lab 3. Covers the principles of end-to-end datagram delivery in IP networks.

Software Defined-Networking. Network Policies Access control: reachability – Alice can not send packets to Bob Application classification – Place video.

VeriFlow: Verifying Network-Wide Invariants in Real Time

Company LOGO Networking Components Hysen Tmava LTEC 4550.

Ch 1. Computer Networks and the Internet Myungchul Kim

PRESENTATION ON:- INTER NETWORK Guided by: Presented by:- Prof. Ekta Agrwal Dhananjay Mishra Prafull Jain Vinod Kumawat.

Cisco 3 - Switch Perrine. J Page 111/6/2015 Chapter 5 At which layer of the 3-layer design component would users with common interests be grouped? 1.Access.

Networking Components Michelle Vega Network System Administrations LTEC /026 Mr. West.

Jennifer Rexford Princeton University MW 11:00am-12:20pm Measurement COS 597E: Software Defined Networking.

SDN AND OPENFLOW SPECIFICATION SPEAKER: HSUAN-LING WENG DATE: 2014/11/18.

1 | © 2015 Infinera Open SDN in Metro P-OTS Networks Sten Nordell CTO Metro Business Group

1 He Says vs. She Says Model Validation and Calibration Kevin Chang HNTB Corporation

Introduction to Mininet, Open vSwitch, and POX

POSITION PAPER Reactive Logic in Software-Defined Networking: Accounting for the Limitations of the Switches Roberto Bifulco, Maurizio Dusi

1 Scalability of a Mobile Cloud Management System Roberto Bifulco* Marcus Brunner** Roberto Canonico* Peer Hasselmeyer** Faisal Mir** * Università di Napoli.

3.6 Software-Defined Networks and OpenFlow

Coping with Link Failures in Centralized Control Plane Architecture Maulik Desai, Thyagarajan Nandagopal.

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.

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.

SDN basics and OpenFlow. Review some related concepts SDN overview OpenFlow.

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

IEEE ICC ‘16 Dynamic M2M Device Attachment and Redirection in Virtual Home Gateway Environments Apostolos Papageorgiou, NEC Labs Europe Roberto Bifulco,

SDN challenges Deployment challenges

SDN Network Updates Minimum updates within a single switch

Software defined networking: Experimental research on QoS

HybNET: Network Manager for a Hybrid Network Infrastructure

NOX: Towards an Operating System for Networks

IP Forwarding Covers the principles of end-to-end datagram delivery in IP networks.

IP Forwarding Relates to Lab 3.

Chapter 5 Network Layer: The Control Plane

CS 31006: Computer Networks – The Routers

IP Forwarding Relates to Lab 3.

Software Defined Networking

Network Core and QoS.

Data Plane Jennifer Rexford Fall 2018 (TTh 1:30-2:50 in Friend 006)

IP Forwarding Relates to Lab 3.

Networking and Network Protocols (Part2)

IP Forwarding Relates to Lab 3.

Chapter 5 Network Layer: The Control Plane

Chapter 5 Data Link Layer – Hub, Switch

Network Core and QoS.

Presentation transcript:

Reactive Logic in Software-Defined Networking: Measuring Flow-Table Requirements Maurizio Dusi*, Roberto Bifulco*, Francesco Gringoli”, Fabian Schneider* * NEC Laboratories Europe “ Università degli studi di Brescia

Page 2 © NEC Corporation 2014 Background: SDN and OpenFlow ▌SDN: the network control plane is separated from the network data plane Forwarding Element Controller Forwarding Element Forwarding Element Control Plane Data Plane Routing Table Forwarding Table

Page 3 © NEC Corporation 2014 …L3_SRCL3_DSTL4_SRCL4_DST…Action OpenFlow: proactive approach Forwarding Element …L3_SRCL3_DSTL4_SRCL4_DST…Action Any112/8Any Fwd-to: 2 L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80 L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80 Controller flow_mod

Page 4 © NEC Corporation 2014 …L3_SRCL3_DSTL4_SRCL4_DST…Action OpenFlow: reactive approach Forwarding Element …L3_SRCL3_DSTL4_SRCL4_DST…Action Any112/8Any Fwd-to: 2 L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80 L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80 Controller flow_mod packet_in

Page 5 © NEC Corporation 2014 …L3_SRCL3_DSTL4_SRCL4_DST…Action OpenFlow: flow entries definition Forwarding Element …L3_SRCL3_DSTL4_SRCL4_DST…Action Any112.45/16Any Fwd-to: 2 L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80 L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80 Controller flow_mod packet_in L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80 packet_in flow_mod …L3_SRCL3_DSTL4_SRCL4_DST…Action Any112.45/16Any Fwd-to: 2 Ant112.46/16Any Fwd-to: 1 L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80

Page 6 © NEC Corporation 2014 …L3_SRCL3_DSTL4_SRCL4_DST…Action OpenFlow: flow entry’s idle timeout Forwarding Element …L3_SRCL3_DSTL4_SRCL4_DST…Action Any112/8Any Fwd-to: 2 L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80 L3_SCR: L3_DST: L4_SRC: 5433 L4_DST: 80 Controller flow_mod packet_in 1 2 3

Page 7 © NEC Corporation 2014 Understanding control/data plane interactions ▌Switch simulator Based on the reactive OpenFlow model Flow entry definition is configurable (also the idle timeout) Input: traffic trace Output: number of packet_in, flow_mod per second number of flow entries in the flow table per second ▌Simplified controller model: Only packet_in and flow_mod interactions The same flow entry definition is applied for all the incoming flows E.g., flow entry is defined by the destination IP address/32 and idle timeout is 10 seconds.

Page 8 © NEC Corporation 2014 Datasets ▌Access network DSLAM of an European ISP, 2007 (protected by NDA  ) University of Brescia campus network’s edge router, 2009 (publicly available) ▌Core network PAIX, Tier1 backbone link, 2005 (publicly available) CAIDA, Tier1 backbone link, 2013 (publicly available)

Page 9 © NEC Corporation 2014 What if? Proactive approach ▌Number of flow table entries in the switch flow table ACL Routing/Policy-based routing ▌How this numbers compare to actual switches’ flow tables? Hardware OpenFlow switches can host a few 1000s entries.

Page 10 © NEC Corporation 2014 Playing with the idle timeout (DSLAM trace) ▌Flows are not always active! Increase

Page 11 © NEC Corporation 2014 Impact of flow entry definition ▌Timeout fixed at 10s (common value in many OpenFlow Controllers)

Page 12 © NEC Corporation 2014 Impact of flow entry definition ▌Timeout fixed at 10s (common value in many OpenFlow Controllers) 60k 4k

Page 13 © NEC Corporation 2014 Conclusion ▌Reactive, or partially-reactive control plane enables advanced SDN use cases; ▌Using reactive entries installation can reduce the flow table size by orders of magnitude Requires the switch to handle more frequent flow table updates; ▌In access networks current OpenFlow switches can cope the flow table requirements, also with fine granular flow definition; ▌In core networks current OpenFlow switches can only be used with coarse grained flows; ▌Understanding the effects of a reactive control plane on the flows delay is a required next step.