The OpenFlow based Scale-Out Router

Document Version 1.0 2015-11-30





SDN made smarter



© 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control







The OpenFlow based Scale-Out Router Version 1.0 1 / 15



Legal Information

Copyright 2015 NoviFlow All Rights Reserved

Notice Information in this documentation is subject to change without notice. Unauthorized use, copying, or translation of this documentation can result in civil or criminal penalties. Any export of NoviFlow products is subject to the export controls of Canada and the other countries where NoviFlow has operations. No part of this documentation may be reproduced, translated, or transmitted in any form or by any means, electronic or mechanical, including photocopying or recording, for any purpose without the express written permission of an authorized representative of NoviFlow. Other product names used herein are for identification purposes only, and may be trademarks of their respective companies. Trademarks NoviFlow, NoviWare, NoviSwitch, NoviRouter, NoviConnect, NoviNID, NoviApps are trademarks of NoviFlow. All other trademarks are the property of their respective owners. Patents This product may be covered by one or more patents. NoviFlow Inc. 780 Brewster Ave., Suite 02--200 Montréal (QC) H4C 2K1 Tel: +1 (438) 807-4360 Fax: +1 (514) 221-3590 http://www.noviflow.com

© 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 2 / 15

Table of Contents Change History .............................................................................................................................................................................. 4 Abstract ........................................................................................................................................................................................... 4

1. An industry in transition ................................................................................................... 5 Today’s Network Management Challenges ........................................................................................................................ 5 The surge in traffic growth ....................................................................................................................................................... 5 SDN to the rescue… right? ........................................................................................................................................................ 7 A generation of uneven innovation ....................................................................................................................................... 8 2. The Scale-Out Router ....................................................................................................... 8 Components .................................................................................................................................................................................. 8 Advantages of the Scale-Out Router architecture: .......................................................................................................... 9 Advantages of the use of OpenFlow switches in the Scale-Out Router architecture: ...................................... 10 3. Requirements on OpenFlow Forwarding Plane ............................................................... 12 4. Use case: BGP Scale-Out Router ..................................................................................... 13 5. Summary ....................................................................................................................... 14

© 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 3 / 15

Change History

Date

Revision No.

Author

Revision Description

2015-11-30

1.0

Marc LeClerc

Initial version

Approved

Abstract This paper describes how Software Defined Networking (SDN), and specifically the OpenFlow protocol, can be used to build a new category of switches and routers that, whilst being fully functional and reliable, are centrally controlled via software, which make them much easier to scale and far more economical to operate than traditional “monolithic” routers. This “ScaleOut” approach to build networking equipment generates significant savings in both CAPEX and OPEX, as well as providing a more scalable, modular, flexible and programmable routing infrastructure far better equipped to deal with the challenges of exponentially growing numbers of connected devices, vastly changed usage patterns, and much better able to exploit new software based solutions for network optimization and virtualization. The intended audience for this white paper includes anyone who is currently spending a significant portion of their networking budgets on routing products, for example carriers, internet and cloud service providers, enterprise network staff, etc.



© 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 4 / 15

1. An industry in transition Today’s Network Management Challenges Recent years have seen both a tremendous increase in network traffic (+34% growth in total internet traffic in 2014, according to Cisco) and radical change in how electronic information is accessed, used and stored. The explosive growth in the use of online applications, virtualization and cloud services by an ever-expanding array of wired and mobile connected devices is overwhelming network engineers and forcing a complete re-think about standing assumptions and ideas of how networks should be built. The vast array of data formats, service types and online devices requires a far more dynamic and agile response than most network management tools were designed to handle, and they need to do so while ensuring availability, security, speed as well as the shortest time to market (TTM) for new services, Figure 1: Issues faced by Network Operators today all without increasing operating and equipment costs. The impending arrival of IoT (the Internet of Things) and the accelerating deployment of NFV (Network Functions Virtualization) only promise to amplify these challenges by requiring network infrastructure that can interact more meaningfully with the applications that use network resources. SDN provides powerful new approaches to solving these problems, however using these tools requires a major change in Data Centre and Network culture and an understanding of how this impacts the requirements, dimensioning and selection of network equipment. To make matters worse, using traditional switch and router metrics for the selection of SDN based solutions can lead to major roadblocks in their effective deployment.

The surge in traffic growth According to Deutsche Bank, Amazon Web Services is forecast to book $16 billion in revenue by 2017 (source: Business Insider, Nov 3rd 2015). This is only one driver in the huge surge in traffic growth network managers are facing. Before the arrival of SDN, the solution to most networking problems was to “throw bandwidth” at them. This approach has led to extensive overprovisioning of networks, despite the fact that most network equipment is running at 10-15% utilization rates. Worse still, network devices © 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 5 / 15

running at 10-15% of capacity still consume 80% as much power (and air conditioning) as the same equipment at full utilization. In Data Centers located in densely populated metropolitan areas such as Manhattan, Electrical power consumption has become a bigger expense than rent! The situation at the network edge is exasperatingly worse. Consider that within data centers links and bandwidth are cheap. At the network edge, WAN links are much more expensive and throwing bandwidth at the problem is far less feasible because they take several weeks to several months to acquire. Routers often sit at the edge of the WAN and are the gatekeepers for traffic to get onto/off the WAN. Also, many of the typical nodes being deployed at the edge, such as load balancers, security appliances and edge routers, do not scale linearly as capacity increases, making upgrades complex and expensive. With the impending flattening of Moore’s law, it will be less and less possible to scale-up traditional architectures. Also, the increasing complexity of the software running in these monolithic routers (such as Provider Edge routers) amplifies the risks and costs of downtime, a major headache and threat to network managers’ job security! Just as the network nodes themselves don’t scale evenly across different network services, the nature of network traffic is changing radically: short vs. long packets, real-time vs. store-andforward, east-west vs. north-south, mobile vs. fixed, etc. This is altering the established ratios of the relative capacity requirements for data, control and application planes within each network service. For example, the advent of web-based video streaming services such as YouTube, Netflix, and the video linking capabilities offered by social media such as Facebook, has severely altered the ratio of control traffic to payload traffic. To cope, network managers are forced to further over-dimension these services, making traditional scale-up network appliances and allin-one boxes even more uneconomical. The increasing popularity of cloud-based solutions is also adversely impacting data networks. In addition to the issues presented above, public cloud resources are often being utilized in conjunction with private networks in hybrid cloud solutions (note: this has nothing to do with hybrid SDN switches) requiring network to deliver instant capacity when local demand suddenly grows beyond privately available capacity, a safety valve that allows private networks to be run at much higher utilization rates, reducing private network costs, and a disaster recovery network for business continuity in case of accidental or malicious interruption of private network services. For these types of services to be economically viable, it is necessary to quickly link and automatically reconfigure the network services between the private cloud and the public cloud. In the traditional network situation this process is excessively complex and slow, as at different stages in each of the examples above, the network links between private and public clouds have very different requirements for capacity, latency, address space, and so on. That complexity and sluggishness severely limits effective hybrid cloud deployments. Another complicating factor here is that there are at least two, and sometimes three or even four parties, involved in the network links between the private and public clouds. As a consequence, many such arrangements are overprovisioned, changes in network usage and availability are © 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 6 / 15

difficult or slow to detect, and the network cannot be reconfigured fast enough to deal with these changes anywhere near real-time. Network managers are often left “holding the bag” and being blamed for the inability for organizations to deploy improved business processes or deliver new services to customers.

SDN to the rescue… right? Many data center and network managers have turned to SDN to face these challenges. Indeed, SDN solutions provide both tools and strategies to overcome many of these issues, but to succeed these require first a clear understanding of the centralized flow management approach to solving network problems, and secondly deployment using forwarding planes that offer architectures and performance characteristics optimized to deliver it. This last is where many SDN projects run into trouble: they select SDN equipment based on evaluation criteria designed for the legacy networks. Network managers then discover the new equipment they just bought fall short in commercial deployment or are impossible to scale once usage increases. An essential SDN switch capability is to support large numbers of flows. However, many network managers never imagine that many SDN applications require not hundreds or thousands of flows, but rather hundreds of thousands, or even millions of flows. Let’s take as an example the use of SDN to implementation of network-wide Access Control Lists (ACL). Traditional switches were not designed with centralized logic in mind and only need to store information on a very limited portion of the network. Consequently they were designed without the flow table capacity needed to support applications that might address the entire network. Dozens of these switches are typically required to implement centralized ACLs, making the aggregate prices of these solutions economically and operationally (too much labor intensive management) unviable despite the relatively low per-box prices. Another key use of SDN today is to support deployment of Network Function Virtualization. Due to the limited number of flows supported in traditional switches, network virtualization has primarily been implemented in soft switches running on the servers themselves, requiring the dedication of one CPU core (at least) per server, and leading to reduction of 15 to 25% of the total revenue generating capacity of each server! This hidden cost of supporting NFV has been the nightmare of many network managers tasked with implementing NFV. Traditional ASIC based switches may be cheap and fast, but they can only support a small subset of OpenFlow specification, severely limiting the application of SDN solutions in networks. Hybrid switches try to compensate for this handicap by implementing a “fast path/slow path” architecture, where flows requiring more sophisticated SDN features are forwarded to the hybrid switch’s host processor running a virtual switch application (slow path) such as Open vSwitch, or OVS, usually at only about 5% the throughput of the ASIC part of the switch. This imbalance in capacity makes hybrid switch deployments very difficult to dimension, and even harder to scale effectively. In both cases network managers are left to explain which © 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 7 / 15

the “new” SDN switches they just bought can’t run the intended SDN applications, or if they can, they only can do so at an unacceptably low throughput.

A generation of uneven innovation Despite the last twenty years’ breakthroughs in data center compute and storage, or even perhaps because of them, rising network costs remain an inescapable issue. Virtualization and the disaggregation of hardware and software have provided immense increases in compute and storage utilization and efficiency. Sadly, networking technology lags significantly in taking advantage of virtualization and disaggregation, resulting in rigid all-in-one designs, vendor lockin, multiplication of protocols, proprietary interfaces, non-deterministic network behavior, and a very limited ability to interact meaningfully with the applications and services that use network resources. Networks neither scale-up, nor scale-out as compute and storage now increasingly do. That inability in common networking architectures places hard limits on leveraging hyper-scale architectures, causing intractable problems for data center and network managers. Leaders such as Google and Facebook are using SDN and OpenFlow to implement innovative open networking hardware and software in their own networks to build hyper-scale network WAN solutions that are faster, more flexible and significantly more economical to scale than traditional box-based solutions. Can this same strategy be applied to routers in a broader industry context? Most network managers do not have the resources available to Google and Facebook, so how can they take advantage of the potential of SDN without falling into the cost/performance/capability traps described above? The rest of this paper will show how, with right selection of high-performance OpenFlow forwarding planes, SDN strategies indeed can be applied to build a genuine scale-out router solution that reduces routing CAPEX and OPEX, simplifies operations, increases agility and enables trouble-free scaling of applications from initial intro to massive deployments.

2. The Scale-Out Router Components The basic idea of the Scale-Out Router is to replace the monolithic scale-up router in a rack or chassis with a fully modular architecture based on commercial-of-the-shelf (COTS) servers, L2 switches and OpenFlow switches. In this architecture, the control plane portion of the router is transferred to virtual machines running on standard servers. This includes routing stacks and the logic to handle traditional router protocols such as BGP, IS-IS, LDP, etc… All the data-plane © 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 8 / 15

handling functions of the line cards are taken over by high-performance OpenFlow Switches. Finally, the chassis backplane is replaced by normal COTS layer 2 switches. They link all the other elements together in a fully scale-out architecture.



Figure 2: Elements of the Scale-Out Router





Advantages of the Scale-Out Router architecture: 1. Scalability: Seamlessly grow from very small configurations (a single OpenFlow switch) to the size of a data center by leveraging off-the-shelf Ethernet fabric as the “backplane” 2. Modularity: Mix and match any types and quantities of “line cards”, “service cards” and “backplane”, making it possible to scale each of these elements independently as usage patterns evolve and new applications/protocols are implemented 3. Flexibility: Additional use cases can leverage the Scale-Out Router, E.g., Service Chaining of VNFs for 4G/5G EPC, DPI, FW, LB, NATs, new functionality including Virtualized Network Functions (VNFs), Service Routers… 4. Agility: capability to reconfigure the network dynamically from the same basic components in real-time 5. Reduced CAPEX: A router is no longer a specialized appliance requiring users to pay a premium to get a simple compute blade or line card into a proprietary chassis a. Disaggregation drives costs down: Todays routers are vertically integrated solutions offered by a single vendor, an inefficient economic model that stifles competition. © 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 9 / 15

Disaggregation will drive costs out of routing solutions, just as it has done in the compute and storage worlds b. Equipment costs: No Vendor Lock-in! Open standards, COTS components and multiple vendors for each component provide for competition and drive down equipment prices c. Open source software components: Community based development of OpenFlow controllers and applications means lower costs for customers. 6. Reduced OPEX: a. Provisioning automation: Configuration management now under program control rather than CLI control b. Simplified operations: Capacity growth achieved not through endless fork lift upgrades but through simply adding servers (or VMs) and switches in a fully modular fashion, as was achieved with compute and storage disaggregation c. Reduced support costs: No vendor lock-in means reduced costs for hardware and software support.

Advantages of the use of OpenFlow switches in the Scale-Out Router architecture: Contrary to proprietary router solutions, the use of OpenFlow as the communication mechanism between the components of the disaggregated router (i.e. COTS OpenFlow switches, servers and L2 switches) enables carriers and data center operators to purchase individual components from different suppliers, hence preventing the typical vendor lock-in see today with traditional equipment. Furthermore, in the specific case of NoviFlow switches, all components of the disaggregated router using the NoviFlow switches are programmable, and hence new software features and bug corrections can be deployed in equipment already in production, bringing a radically different, dynamic approach to managing router capability and scalability.

© 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 10 / 15



Figure 3: A typical Scale-Out Router Configuration

This Scale-Out approach to create SDN based routers is the descendant of years of research and development of many Open Source SDN projects including RouteFlow, the Vandervecken project, and most recently the ONF’s (Open Networking Foundation) Atrium project, of which NoviFlow is contributing member. The cost savings in replacing traditional monolithic routers with SDN based routers in a Software Defined WAN deployment has been estimated by Gartner to be in the range of 65%. (See figure below.)

© 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 11 / 15

3. Requirements on OpenFlow Forwarding Plane Not all OpenFlow switches were created equal. In many cases they cannot be used with specific SDN applications because their internal packet processing pipelines do not support the needed OpenFlow functionalities (i.e. this is a major reason why some SDN deployments fail when moving from the lab into commercial deployment.) In some cases the application has the option of running with a vSwitch, but because of the limited forwarding capacity of vSwitches, these applications are for low bandwidths only (below 6-8 Gbps). In many case this is unacceptably low and will prevent commercial deployment, or make the service uneconomical or impractical to scale. As mentioned earlier, deploying OpenFlow at the intelligent edge may require millions of flows. However, legacy devices, and even most OpenFlow switches today, only support a few thousand flows at once, or if they do, they can only process a low number of flow modifications per second, rendering the switch unable to keep-up in more dynamic situations. Another key requirement is a fully programmable packet processing pipeline, as specified in the OpenFlow 1.3/1.4/1.5 standard. A highly programmable pipeline allows any combination of match fields, instructions and actions in any combination of one or multiple tables. ASICs typically have very limited and inflexible pipelines, and even some highly configurable pipelines are optimized for only one specific pipeline architecture at a time. Another key requirement is the ability to effectively manage scarce (expensive) WAN bandwidth resources. Different flows have different requirements on bandwidth and latency. For example, a temporary 300ms delay in delivering a packet for a user surfing the net will not be as damaging as a 300ms delay in packets for a VoIP call. Quality of Service (QoS) is a key concept and includes advance packet processing technologies such as classification, metering, marking, queuing, congestion avoidance, traffic shaping, scheduling prioritization for the purpose of providing different priority to different flows (applications, users, etc.) or to guarantee a certain level of performance to a flow. High-performance OpenFlow forwarding planes based on Network Processors (NPUs) have programmable pipelines, and so with appropriate software are capable of implementing all OpenFlow 1.3 and 1.4 match fields, actions and instructions. Consequently, NPU based OpenFlow switches, such as NoviFlow’s NoviSwitch products, can accommodate whatever OpenFlow features SDN applications need. Since NPUs are programmable, a further benefit of NPU base switches is that they are software upgradable. In the case of NoviSwitch products, NoviFlow offers Extended Software Support that includes major software revisions approximately every quarter, so that NoviSwitch users can keep up with new revisions of the OpenFlow specification as they are released.

© 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 12 / 15

With the appropriate TCAMs (Ternary Content-Addressable Memory) and DRAM (Dynamic Random Access Memory), NPUs based switches can also accommodate the huge flow tables needed for centralized SDN applications. NoviSwitch features flow table sizes of up to 1 million wildcard-match entries and 3 million exact-match flow entries, supporting up to 60 tables each. They are also equipped with advanced host processors to ensure flow-modification capacity required by these huge flow tables. By meeting these requirements, NPU based switches, such as NoviFlow’s NoviSwitches, can easily accommodate even the most demanding applications, and support multiple applications on the same switch. They offer the same level of programmability as soft-switches, but with the performance and throughput of hardware based switches, providing the full OpenFlow specification, scalability and software upgradability.

4. Use case: BGP Scale-Out Router

The diagram above presents the NoviFlow NoviRouter BGP Routing application deployed used the Scale-Out Router architecture. Major benefits of the NoviFlow Scale-Out BGP Router: • • •

Implements No forced hardware obsolescence (tech refresh) No vendor lock-in:

© 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 13 / 15

Open source control plane (ONOS/Quagga) Standards based components for both compute (COTS Servers), forwarding plane (COTS OpenFlow switches) and backplane (COTS L2 switches) • Breaks vendor lock-in and provides seamless growth from very small configurations (a single OpenFlow switch) to almost any size by leveraging off-the-shelf OpenFlow switches, Ethernet fabrics, and virtualized compute resources. • It provide a flexible and agile environment that can support multiple applications such as service chaining of VNFs for 4G/5G EPC, DPI, FW, LB, and NAT, and be expanded to support new protocols and functionalities as they become available • Utilizes carrier-grade NoviFlow NoviSwitch high performance NPU based switches, running the NoviWare OpenFlow forwarding plane software with the ability to process and execute flow logic based on packet headers AND contents Supports full OpenFlow 1.3 specification and most of OpenFlow 1.4, software upgradable as software updates supporting newer additions to OpenFlow specifications become available Ability to do some basic packet payload matching and handling via OpenFlow Experimenter feature Up to 1 million wildcard-match flow entries in TCAM, and 3 million exact-match flow entries in DRAM. Router based applications (such as BGP) often require handling very large tables (> 500,000 entries) • Wildcard matching for IP prefix based logic • Exact-match for address filtering (ACLs, blacklists, etc…) Ability to work with and enhance existing networks by supporting multiple tunneling protocols at both L2 and L3 BFD (Bidirectional Forwarding Detection) link monitoring to detect link failures and to reroute traffic without intervention from controllers/apps. • •

5. Summary Conventional solutions for network routing are not keeping up under the onslaught of exponentially rising traffic, radically evolving usage patterns and the need for more network agility and real-time response to changing conditions and application requirements. Traditional monolithic scale-up router architectures are too rigid to scale, too inflexible to repurpose and just plain too expensive to upgrade. SDN brings new network tools into play and enables new solution architectures to meet these challenges. The Scale-Out Router is a prime example of how SDN and OpenFlow change the equation by enabling the disaggregation of the monolithic router into its component elements (control plane, forwarding plane and backplane fabric): • Use most cost effective delivery platform for each element • Reduce costs by using COTS hardware • Each part can scale independently for maximum price/performance and flexibility to adapt to different use cases © 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 14 / 15

The Scale-out Router provides a scalable solution that can keep up with accelerating demand and meet changing network needs in real-time, while actually reducing both capital and operating costs. By using high-performance NoviFlow NoviSwitch products as part of the Scale-Out Router, network managers can ensure that the deployed solution runs on a mature, full-featured, carrier-grade OpenFlow forwarding plane that is proven in commercial deployments around the world, one that will gracefully scale as demand grows, and that can be easily upgraded as SDN, NFV, and OpenFlow specifications evolve. NoviFlow believes that the Scale-Out Router is only one of many new innovative ways to resolve network problems made possible by SDN. We are dedicated to providing SDN forwarding planes solutions and applications that truly deliver on the potential of genuine Software Defined Networking and OpenFlow. For more information please visit our website at: www.noviflow.com.

© 2015 NoviFlow, Inc. Confidential – DO NOT COPY – Hard copies of this document are for reference only The latest approved version is located under version control

The OpenFlow based Scale-Out Router Version 1.0 15 / 15

The OpenFlow based Scale-Out Router - NoviFlow

Nov 30, 2015 - Other product names used herein are for identification purposes only, and may be trademarks of their respective companies. .... Date. Revision No. Author. Revision Description. Approved ... The vast array of data formats,.

4MB Sizes 25 Downloads 214 Views

Recommend Documents

The OpenFlow based Scale-Out Router
Nov 30, 2015 - The latest approved version is located under version control. 3 / 15. Table of Contents. Change ... Today's Network Management Challenges .

Revisiting IP Routing Control Platforms with OpenFlow-based ...
view, we define an initial Routing-as-a-Service platform based on the RouteFlow ... In line with the design rationale and best practices of scale-out cloud ...

Time-based Updates in OpenFlow: A Proposed ... - Semantic Scholar
Jul 7, 2013 - same scheduled execution time. A controller can also invoke a time-based sequence. ∗The Israel Pollak academic chair at Technion; this work ...

All-Optical Packet Router Based on Multi- Wavelength ...
2.1 All-optical Core Network and 1×M PPM-HP-based WDM Router. An all-optical core network with up to 16 edge nodes and a number of core routers (core nodes) K is shown in Fig. 1(a), with each edge node having a unique known decimal address from 0 to

NoviSwitch™ 2128 High Performance OpenFlow Switch
NoviFlow Inc.™ aims to change the traditional approach to networking by making switching smarter. ... Up to 1 Million wildcard match flow entries in TCAM,.

openflow tutorial pdf
Loading… Page 1. Whoops! There was a problem loading more pages. openflow tutorial pdf. openflow tutorial pdf. Open. Extract. Open with. Sign In. Main menu.

RouterBOARD in OpenFlow -
Nov 19, 2013 - OpenFlow support is available as standalone openflow package. ... PC-B. ARP Request. Packet-in. Packet-out. ARP Reply. ICMP_Echo ...

RouterBOARD in OpenFlow -
Nov 19, 2013 - hardware acceleration are to be added. Current ... and bug reports. OpenFlow support is available as standalone openflow package. OpenFlow ...

Router Simulator.pdf
Sign in. Loading… Whoops! There was a problem loading more pages. Whoops! There was a problem previewing this document. Retrying... Download. Connect ...

NoviSwitch™ 2128 High Performance OpenFlow Switch
Today's major network operators demand flexible, scalable switching solutions that ... Software Defined Networking to improve the cost/performance, security, ...

router performance pdf
Retrying... Download. Connect more apps... Try one of the apps below to open or edit this item. router performance pdf. router performance pdf. Open. Extract.

cisco router command pdf
Sign in. Loading… Whoops! There was a problem loading more pages. Whoops! There was a problem previewing this document. Retrying... Download. Connect ...

Common Mistakes on Router Evaluation
Analyzing RFP responses. ‣ 1st Selection based on RFP responses ... One version of software for the whole test. • You can't swap the code in production when ...

woodworking with the router bill hylton pdf
There was a problem previewing this document. Retrying... Download. Connect more apps... Try one of the apps below to open or edit this item. woodworking ...

man-69\wireless-router-reviews.pdf
PDF Ebook : Cisco Wireless Router E4200 Reviews. 30. PDF Ebook : Cisco E3200 Wireless Router Reviews. Page 3 of 5. man-69\wireless-router-reviews.pdf.

C6 El router 201617.pdf
Page 2 of 60. *. © 2007 Cisco Systems, Inc. Todos los. derechos reservados. Cisco Public. OBJETIVOS. ○ Describir los cuatro procesos básicos de la capa de ...

konfigurasi-router-mikrotik-lengkap.pdf
Interface: WIFI >> Address: 192.168.20.254/24. Page 3 of 23. konfigurasi-router-mikrotik-lengkap.pdf. konfigurasi-router-mikrotik-lengkap.pdf. Open. Extract.

Cisco Plug-in for OpenFlow Configuration Guide 1.3
Feb 4, 2014 - Upgrading an Application in a Virtual Services Container 39. Collecting ... documentation as an RSS feed and delivers content directly to your desktop using a reader application. The ...... VS: Flow created: Rule: ip,dl_vlan=3 Actions:

Mininet: Squeezing a 1000 node OpenFlow Network onto a Laptop
Laptop. Bob Lantz, [email protected]. November 19, 2009 ... Solution: virtual network on laptop. - my bias: large scale behavioral simulation ... Page 9 ...

WWMM router bit storage box.pdf
WWMM Router bit storage box. WoodworkingForMereMortals.com. Outer frame and lid frame details. Page 3 of 10. WWMM router bit storage box.pdf. WWMM ...

NetPiler: Detection of Ineffective Router Configurations - CiteSeerX
A simple example configuration of inter-domain routing. A line between two .... its settlement-free peers, one can apply a route filter on BGP sessions with each of ...

Router Security Configuration Guide Supplement ...
A supplement to the NSA Router Security Configuration Guide offering security ...... protocols (e.g. VoIP, chat, video) or essential control protocols (e.g. BGP).

man-164\sagemcom-router-setup.pdf
Download. Connect more apps... Try one of the apps below to open or edit this item. man-164\sagemcom-router-setup.pdf. man-164\sagemcom-router-setup.pdf.