DOCSLIB.ORG

Taking Control of SDN-Based Cloud Systems Via the Data Plane

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Taking Control of SDN-Based Cloud Systems Via the Data Plane Taking Control of SDN-based Cloud Systems via the Data Plane Kashyap Thimmaraju Bhargava Shastry Tobias Fiebig Felicitas Hetzelt Security in Security in Faculty of Technology, Security in Telecommunications Telecommunications Policy and Management Telecommunications TU Berlin TU Berlin TU Delft TU Berlin Berlin, Germany Berlin, Germany Delft, Netherlands Berlin, Germany kash@sect:tu-berlin:de bshastry@sect:tu-berlin:de t:fiebig@tudelft:nl file@sect:tu-berlin:de Jean-Pierre Seifert Anja Feldmann Stefan Schmid∗† Security in Internet Network Faculty of Computer Telecommunications Architectures Science TU Berlin TU Berlin University of Vienna Berlin, Germany Berlin, Germany Vienna, Austria jpseifert@sect:tu-berlin:de anja@inet:tu-berlin:de schmiste@univie:ac:at ABSTRACT KEYWORDS Virtual switches are a crucial component of SDN-based cloud sys- Network Isolation; Network Virtualization; Data Plane Security; tems, enabling the interconnection of virtual machines in a flexible Packet Parsing; MPLS; Virtual Switches; Open vSwitch; Cloud Se- and “software-defined” manner. This paper raises the alarm onthe curity; OpenStack; Attacker Models; ROP; SDN; NFV security implications of virtual switches. In particular, we show that virtual switches not only increase the attack surface of the cloud, 1 INTRODUCTION but virtual switch vulnerabilities can also lead to attacks of much higher impact compared to traditional switches. Modern cloud systems such as OpenStack [1], Microsoft Azure [2] We present a systematic security analysis and identify four de- and Google Cloud Platform [3] are designed for programmabil- sign decisions which introduce vulnerabilities. Our findings moti- ity, (logically) centralized network control and global visibility. vate us to revisit existing threat models for SDN-based cloud setups, These tenets also lie at the heart of Software-defined Networking and introduce a new attacker model for SDN-based cloud systems (SDN) [4, 5] which enables cloud providers to efficiently utilize their using virtual switches. resources [6], manage their multi-tenant networks [7], and reason We demonstrate the practical relevance of our analysis using a about orchestration [8]. case study with Open vSwitch and OpenStack. Employing a fuzzing The data plane of Software-Defined Networks in the cloud are methodology, we find several exploitable vulnerabilities in Open highly virtualized [7]: Virtual switches (running on the servers) are vSwitch. Using just one vulnerability we were able to create a worm responsible for providing connectivity and isolation among virtual that can compromise hundreds of servers in a matter of minutes. machines [9]. Prominent virtual switches today are: Open vSwitch Our findings are applicable beyond virtual switches: NFV and (OvS) [10], Cisco Nexus 1000V [11], VMware vSwitch [12] and high-performance fast path implementations face similar issues. Microsoft VFP [2]. This paper also studies various mitigation techniques and discusses Virtual switches are typically not limited to provide traditional how to redesign virtual switches for their integration. switching but support an increasing number of network and middle- box functionality [2, 13], e.g., routing, firewalling, network address translation and load-balancing. Placing such functionality at the virtualized edge of the network (i.e., the servers) is attractive, as it ∗ Also with, Internet Network Architectures, TU Berlin. allows to keep the network fabric simple and as it supports scala- †Also with, Dept. of Computer Science, Aalborg University. bility [2, 9]. However, the trend to move functionality from the network fabric to the edge (virtual switch) also comes at the price of increased Permission to make digital or hard copies of all or part of this work for personal or complexity. For example, the number of protocols that need to be classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation parsed and supported by virtual switches (Open vSwitch and Cisco on the first page. Copyrights for components of this work owned by others than the Nexus 1000v) and OpenFlow [4] have been growing steadily over author(s) must be honored. Abstracting with credit is permitted. To copy otherwise, or the last years [14] (see Fig. 1). republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]. The trend towards more complex virtual switches is worrisome SOSR’18, March 28-29, 2018, Los Angeles, CA, USA as it may increase the attack surface of the virtual switch. For © 2018 Copyright held by the owner/author(s). Publication rights licensed to the example, implementing network protocol parsers in the virtual Association for Computing Machinery. ACM ISBN ......$15.00 switch is non-trivial and error-prone [15, 16]. These observations https://doi:org/::: lead us in this paper to conduct a security study of virtual switches. integrated the fixes. Ubuntu, Redhat, Debian, Suse, Mirantis, and OF 1.3 ovs-0.90.4OF 1.0ovs-1.0.0 OF 1.1 ovs-1.2.0OF 1.2 ovs-1.7.0 ovs-1.11.0 ovs-2.3.0 ovs-2.4.0 ovs-2.6.0ovs-2.7.0 other stakeholders have applied these fixes in their stable releases. 50 Furthermore, CVE-2016-2074 and CVE-2016-10377 were assigned 40 to the discovered vulnerabilities. 30 Structure: We provide necessary background information on SDN 20 in the cloud and virtual switches in Section 2. Section 3 introduces Parsed Protocols 10 and discusses our security analysis of virtual switches and existing 0 threat models. Based on this analysis we propose a new attacker Jul-2009 Jul-2010 Jul-2011 Jul-2012 Jul-2013 Jul-2014 Jul-2015 Jul-2016 Jul-2017 model. Section 4 presents a proof-of-concept case study attack on Jan-2009 Jan-2010 Jan-2011 Jan-2012 Jan-2013 Jan-2014 Jan-2015 Jan-2016 Jan-2017 Time OvS in OpenStack. We then investigate how our findings on OvS Open vSwitch OpenFlow vNexus relate to other virtual switches, high performance fast paths and SDN/NFV in Section 5. Subsequently, we discuss possible software Figure 1: The total number of parsed high-level protocols in mitigations and their performance impact in Section 6, and design two popular virtual switches and OpenFlow from 2009-2017. countermeasures in Section 7. After discussing related work in Section 8, we conclude in Section 9. Our contributions: 2 BACKGROUND • We present a systematic security analysis of virtual switches. This section reviews the background necessary to understand the We find that virtual switches not only increase the attack remainder of this paper. surface of an SDN-based cloud system (compared to their traditional counterparts), but can also have a much larger 2.1 SDN in the Cloud impact on cloud systems. Centralized network control and network-wide view are key design • Our analysis reveals four main factors that cause security goals for state-of-the-art cloud operating systems such as Open- issues: The co-location of virtual switches with the server’s Stack [1] and other commercial cloud providers, e.g., Google Cloud virtualization layer (in user- and kernel-space); centralized Platform [3]. Data plane isolation is typically ensured using separate control; complex packet parsing (and processing) of attacker physical/logical networks (guest, management and external) and controlled data. tunneling technologies [17] such as VLAN, GRE, VXLAN, MPLS, • Our findings motivate us to revisit current threat models. We etc. A cloud network generally comprises of a physical network observe that existing models do not encompass the security consisting of physical switches interconnecting virtualized servers issues identified in this paper leading us to introduce anew and an overlay (virtual) network interconnecting the VMs. The attacker model for the operation of virtualized data plane centralized control is attractive as it reduces the operational cost components in a Software-defined Network as well as in the and complexity of managing cloud networks [18]. It also provides context of Network Function Virtualization (NFV): A low- flexibility for managing and using cloud services, including VM budget attacker can cause significant harm on SDN-based migration. In addition, the servers in the cloud are connected to cloud systems. external networks (e.g., Internet) via a network node (router). In • We demonstrate the practical feasibility of our attacks on SDN, OpenFlow [4] is the de facto standard south bound protocol. OvS, a popular open-source virtual switch implementation Via the OpenFlow API, the controller can add, remove, update, and used in SDN-based cloud systems. This case study shows monitor flow tables and their flows. that commonly used virtual switch implementations are not resilient against our attacker model. Indeed, such an attacker 2.2 Virtual Switches can successfully exploit a whole SDN-based cloud setup The network’s data plane(s) can either be distributed across virtual- within minutes. ized servers or across physical (hardware) switches. OvS, VMware • We extend our study by surveying high performance fast vSwitch, and Cisco Nexus 1000V are examples of the former and paths, other virtual switch implementations, and related SDN are commonly referred to as virtual switches. Cisco VN-Link [19] and NFV technologies. We find that they are also susceptible and Virtual Ethernet Port Aggregator (VEPA) [20] are examples of to the same design issues. Furthermore, we find that soft- the latter. ware mitigations are commonly not considered during the Virtual switches have the advantage that inter-VM traffic, i.e., evaluation of new data plane components. traffic between VMs on the same server, does not leave that server. • We find that software mitigations for the vulnerabilities we The performance overhead of software-only switching (e.g., OvS) exploited could be adopted with a small performance penalty can be alleviated by hardware-offloading features: While tradition- for real-world traffic scenarios.
Load more

Recommended publications
  • Examining Factors of the NFV-I Impacting Performance and Portability
    WHITE PAPER Examining Factors of the NFV-I Impacting Performance and Portability www.ixiacom.com 915-0953-01 Rev. A, May 2015 2 Table of Contents Introduction ................................................................................................. 4 Compute Platform ........................................................................................ 7 CPU/Motherboard and Storage .............................................................. 8 CPU Pinning ........................................................................................... 9 Logical Processor Support ................................................................... 11 QuickPath Interconnect (QPI) ...............................................................12 Packet Processing Enhancements and Acceleration ............................13 Storage .................................................................................................16 Network Interface Cards (NICs) .................................................................17 PCI Passthrough ...................................................................................18 Single Root I/O Virtualization (SR-IOV) ...............................................18 Host OS and Hypervisor ............................................................................21 Open Source NFV-I Platforms ............................................................. 23 Know the Performance Curve ............................................................. 24 Virtual Networking ...................................................................................
    [Show full text]
  • Hypervisor Based Password Security
    HyperPass: Hypervisor Based Password Security James "Murphy" McCauley, Radhika Mittal Abstract Phishing attacks: It has been shown that it is quite Passwords are the linchpin in the security of an increasing possible to fool users into divulging passwords and other number of online services – services that range from private data [11]. While some are quick to dismiss such social networking to business communication to banking. attacks as “user error”, phishing can be coupled with Given their importance, it is unfortunate that passwords network-based attacks or can incorporate techniques such are relatively easily stolen using a number of different as homograph domain names to create user experiences types of attack. We introduce HyperPass: an approach that are very difficult to differentiate from legitimate ones. and proof-of-concept system that aims to prevent some of Attacking hosts: By compromising a user’s machine, these attacks by moving passwords from a user’s normal passwords can be stolen directly in any of several operating environment into a secure hypervisor. Notably, ways, e.g., by examining HTTP post data, reading them this is done while maintaining compatibility with existing from browser password managers, or logging keystrokes. online services, applications, and operating systems. These techniques have been used by botnets (the Torpig botnet alone steals a password every second [30]) as well 1 Introduction as by off-the-shelf “spyware” which has even been pre- installed on rental computers [24]. While preventing Passwords are the linchpin of online security. Certainly, this sort of host compromise is an ongoing effort by both there are other major technologies involved in cyberse- industry and academia, it continues to be an elusive goal.
    [Show full text]
  • Oracle® Linux Virtualization Manager Getting Started Guide
    Oracle® Linux Virtualization Manager Getting Started Guide F25124-11 September 2021 Oracle Legal Notices Copyright © 2019, 2021 Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Circuit‐Based Logical Layer 2 Bridging in Software‐Defined Data Center Networking
    Received: 2 November 2018 Revised: 3 May 2019 Accepted: 13 July 2019 DOI: 10.1002/dac.4128 RESEARCH ARTICLE Circuit‐based logical layer 2 bridging in software‐defined data center networking Yao‐Chun Wang | Ying‐Dar Lin Computer Science, National Chiao Tung Summary University, Hsinchu, Taiwan With the expansion of the size of data centers, software‐defined networking Correspondence (SDN) is becoming a trend for simplifying the data center network manage- Yao‐Chun Wang, Computer Science, National Chiao Tung University, Hsinchu, ment with central and flexible flow control. To achieve L2 abstractions in a Taiwan. multitenant cloud, Open vSwitch (OVS) is commonly used to build overlay Email: [email protected] tunnels (eg, Virtual eXtensible Local Area Network [VXLAN]) on top of existing underlying networks. However, the poor VXLAN performance of OVS is of huge concern. Instead of solving the performance issues of OVS, in this paper, we proposed a circuit‐based logical layer 2 bridging mechanism (CBL2), which builds label‐switched circuits and performs data‐plane multicasting in a software‐defined leaf‐spine fabric to achieve scalable L2 without overlay tunneling. Our evaluations indicate that direct transmission in OVS improves throughput performance by 58% compared with VXLAN tunneling, and data‐ plane multicasting for ARP reduces address resolution latency from 149 to 0.5 ms, compared with control‐plane broadcast forwarding. The evaluation results also show that CBL2 provides 0.6, 0.4, and 11‐ms protection switching time, respectively, in the presence of switch failure, link failure, and port shutdown in practical deployment. KEYWORDS cloud, datacenter, layer 2, multitenancy, network virtualization, OpenFlow, SDN 1 | INTRODUCTION Infrastructure‐as‐a‐Service (IaaS)1 providers enable enterprise customers (who are also called tenants) to obtain flex- ible and on‐demand virtualized infrastructures, by using virtualization technologies that share the computing resources (eg, servers, storages, and networks) in a data center.
    [Show full text]
  • Neutron Integration
    oVirt – Neutron Integration July 2013 Mike Kolesnik 1/49 Agenda oVirt network configuration Neutron overview Integration benefits External providers Neutron as an external provider Under the hook Future work 2/49 oVirt Network Configuration 3/49 Network View Network - a logical entity that represents a layer 2 broadcast domain Defined within the scope of a data center 4/49 Adding a New Network Give it a name Define the network properties (VLAN, MTU, VM/Non-VM) 5/49 Adding a New Network Make the network available in the selected clusters. 6/49 Host Level Configuration Optional vs. required networks Host level configuration: 7/49 Adding Network to a vNIC 8/49 Supported Configuration - Linux Bridge 1 .. N 1 .. N VM VM VM VM SW Bridge SW Bridge SW Bridge VLAN VLAN VLAN bond NIC NIC 9/49 Neutron Overview 10/49 OpenStack Networking - Neutron Neutron provides network connectivity-as-a- service It offers a plug-in architecture designed to support various network technologies through vendor specific plug-ins and API extensions Exposes REST API for accessing the service Available plugins: Linux Bridge, OVS, Cisco Nexus, NVP, Ryu, NEC, etc... 11/49 Neutron high level architecture Neutron API Neutron Plugin - Create network - Create network . Compute nodes API clients . configured according to - Create Port - Create Port selected plugin, by either: * Agent at each node * External network controller (e.g. UCSM) API extensions DB API + plugin = Neutron service Compute nodes 12/49 Integration Benefits Add support in oVirt for the various network technologies provided via Neutron plugins Leverage L3 services modeled in Neutron Enjoy both worlds: Neutron for managing VM networks oVirt for managing infrastructure networks (Migration network, storage network etc.) Neutron networks are exposed side by side with oVirt networks which allows the user to use oVirt mature implementation for network configuration 13/49 Integration bits 14/49 External Providers An external product that can be used to provide resources for oVirt Resources that can be provided: hosts, networks, etc.
    [Show full text]
  • Flexible, Software-Defined Networking Infrastructure
    Flexible, software-defined networking infrastructure Red Hat Enterprise Linux enabling the clouds Clouds Need Red Hat Enterprise Linux Rashid Khan Russell Bryant Networking Services Office of Technology Wednesday, May 03, 2017 #redhat #rhsummit OS Matters Red Hat Enterprise Linux Enables, Empowers, Excels, Enterprise Cloud Red Hat Enterprise Linux (RHEL) #redhat #rhsummit OS Matters ! Core operating system needs support ● Evaluation of patches regarding stability and ● Dedicated to RHEL impact (Hardening) ○ ~700 Developers ● Single point of support (no tennis match of bugs) ○ ~ 400 QA ● Minimizes downtime with balance of stability and security (CVE) ● In addition ○ Layered products Guarantee of API and ABI ■ Developers ● Applications will work after minor upgrades ■ QA ● 3rd party kernel modules under kabi program will ○ Support Services continue work ○ ~14,000 people ready to ● Synchronization of user space with kernel ensure your success features ○ ● Somethings like HW Integration with layered products, and Ansible, and a acceleration cannot be done whole portfolio of products without the OS! #redhat #rhsummit Network Security, Isolation, Tunnels Security and Isolation For Multi-tenancy, Fairness, Enterprise readiness ● Robust Firewalling ○ Connection Tracking with NAT in OVS ○ NetFilter ● Network Namespaces ● L2 Security via MACsec ● L3 Security via IPsec #redhat #rhsummit Tunnels and Isolation ● VLANs (limited identifiers) ● VXLAN with HW offload with IPv6 also ● Geneve (more flexible) ● QinQ 802.1ad (great results) C C C C C V C
    [Show full text]
  • Learn About VXLAN in Virtualized Data Center Networks
    Learn About VXLAN in Virtualized Data Center Networks Data centers have rapidly increased their server virtualization over the past decade, resulting in dramatic increases in agility. This, in turn, has created a demand for data center networks that are equally flexible and agile. Virtualization of the network is the next obvious step – decoupling the virtual network from the physical network makes it easier to manage, automate, and orchestrate. One common method being used today to virtualize data center networks is the use of overlay networks. An overlay network sits on top of the physical network, enabling Network overlays are the use of a virtual network of switches, routers, firewalls, load balancers, and so on. created by encapsulating This decoupling of the virtual from the physical enables fast programmatic provision- traffic and tunneling it ing of the network for any application. You no longer have to orchestrate changes over the physical network. Although relatively new to across a set of physical devices. data center networks, Creating a virtual overlay network also benefits the physical, or underlay, network, overlay networks have been used in campus which can now be a simple IP network that is concerned solely with delivering packets networks for years to carry to destinations. An overlay network adds simplicity, resiliency, and scale to the wireless LAN traffic over physical network, another reason overlay networks are gaining popularity. the wired network. Figure 1 illustrates an overlay network. From the perspectives of virtual machine 1 and virtual machine 2 (VM1 and VM2), traffic between them is taking the route shown by the dotted line, going through traditional networking devices such as switches, routers, and firewalls, which are instantiated in the hosts.
    [Show full text]
  • The Design and Implementation of Open Vswitch
    The Design and Implementation of Open vSwitch Ben Pfaff∗ Justin Pettit∗ Teemu Koponen∗ Ethan J. Jackson∗ Andy Zhou∗ Jarno Rajahalme∗ Jesse Gross∗ Alex Wang∗ Jonathan Stringer∗ Pravin Shelar∗ Keith Amidon† Martin Casado∗ ∗VMware †Awake Networks What is Open vSwitch? From openvswitch.org: “Open vSwitch is a production quality, multilayer virtual switch licensed under the open source Apache 2.0 license. It is designed to enable massive network automation through programmatic extension, while still supporting standard management interfaces and protocols (e.g. NetFlow, sFlow, SPAN, RSPAN, CLI, LACP, 802.1ag).” Where is Open vSwitch Used? ● Broad support: – Linux, FreeBSD, NetBSD, Windows, ESX – KVM, Xen, Docker, VirtualBox, Hyper-V, … – OpenStack, CloudStack, OpenNebula, … ● Widely used: – Most popular OpenStack networking backend – Default network stack in XenServer – 1,440 hits in Google Scholar – Thousands of subscribers to OVS mailing lists Open vSwitch Architecture VMs VM 1 VM 2 ... VM n Netlink Hypervisor ovsdb-server OVSDB ovs-vswitchd kernel module l O r e w e V o S l n D F s n r B e u p e O k NICs Controller Use Case: Network Virtualization OpenFlow tables Table 0 Table 1 Table 24 packet packet Flow 1 Flow 1 Flow 1 ingress ... egress Flow 2 Flow 2 Flow 2 ... ... ... Physical L2 ... Logical to to Logical Lookup Physical OpenFlow Pipeline Implications for Forwarding Performance OpenFlow tables Table 0 Table 1 Table 24 packet packet Flow 1 Flow 1 Flow 1 ingress ... egress Flow 2 Flow 2 Flow 2 ... ... ... Physical to L2 ... Logical to Logical Lookup Physical k hash k0 hash k1 hash ... 24 lookups lookups lookups 100+ hash lookups per packet for tuple space search? Non-solutions ● All of these helped: – Multithreading – Userspace RCU – Batching packet processing – Classifier optimizations – Microoptimizations ● None of it helped enough: % versus x.
    [Show full text]
  • Virtual Switching Plays an Important Role in the Data Center, So I'm Going to Give a Brief Overview of the Different Products
    Virtual switching plays an important role in the data center, so I’m going to give a brief overview of the different products. What is virtual switching? Well, a physical server these days usually has a hypervisor as operating system, which has only one function: virtualizing other operating systems to virtual machines that are running on top of the hypervisor. These virtual machines can be Windows, Linux, Solaris, or even other operating systems. These virtual machines need network connectivity. For that, they share one or more physical network interface cards on the server, commonly called a pNIC. To regulate this network traffic, a virtual switch, called a vSwitch, runs in software on the hypervisor and connects these pNICs with the virtual network interface cards of the virtual machines, called vNICs. So it looks like this: The blue parts are done in software, only the last part, the pNIC, is physical. There are three big players in the hypervisor market: Citrix with XenServer, Microsoft with Hyper-V and VMware with ESXi or vSphere. Each has their own implementation of a virtual switch. Apart from that, Cisco has a Nexus 1000 virtual switch. Citrix Xenserver I have no experience with XenServer and so far I’ve found litte information on it. A virtual switch that can be used is Open vSwitch, an open source product which runs on Xen and Virtualbox. I’m not sure if this is the only virtual switch that XenServer supports. Open vSwitch supports a variety of features you would expect from a switch: trunking, 802.1q VLAN tags, link aggregation (LACP), tunneling protocols, SwitchPort ANalyser (SPAN), IPv6, basic QoS.
    [Show full text]
  • Deploy the Extrahop Discover Appliance on a Linux KVM Published: 2020-02-23
    Deploy the ExtraHop Discover Appliance on a Linux KVM Published: 2020-02-23 The following procedure guides you through the deployment process of the ExtraHop Discover EDA 1000v or EDA 2000v virtual appliance on a Linux kernel-based virtual machine (KVM). You should be familiar with basic KVM administration before proceeding. If you have not already done so, download the ExtraHop Discover virtual appliance file for KVM from the ExtraHop Customer Portal . Important: If you want to deploy more than one ExtraHop virtual appliance, create the new instance with the original deployment package or clone an existing instance that has never been started. System requirements Your environment must meet the following requirements to deploy a Discover appliance: EDA 1000v EDA 2000v A KVM hypervisor environment capable of hosting a A KVM hypervisor environment capable of hosting a VM that includes: VM that includes: • 4 GB RAM • 6 GB RAM • Two vCPUs • Six vCPUs • 4 GB boot disk (virtio-scsi interface • 4 GB boot disk (virtio-scsi interface recommended recommended • 40 GB datastore disk • 250 GB datastore disk (Optional) Open vSwitch virtual switch software (Optional) Open vSwitch virtual switch software An ExtraHop virtual appliance license key An ExtraHop virtual appliance license key Package contents The installation package for KVM systems is a tar.gz file that contains the following items: Description EDA 1000v file name EDA 2000v file name Domain XML configuration file eda-1000v.xml eda-2000v.xml Boot disk extrahop-boot.qcow2 extrahop-boot.qcow2 Datastore disk extrahop-data.qcow2 extrahop-data.qcow2 Deploy the Discover virtual appliance To deploy the Discover virtual appliance, complete the following procedures: • Determine the best virtual bridge configuration for your network • Create a virtual capture bridge that contains the traffic you want to monitor • Edit the domain XML configuration file • Configure a mirror session on the virtual bridge © 2020 ExtraHop Networks, Inc.
    [Show full text]
  • Throughput and Latency of Virtual Switching with Open Vswitch: a Quantitative Analysis
    Throughput and Latency of Virtual Switching with Open vSwitch: A Quantitative Analysis Paul Emmerich · Daniel Raumer · Sebastian Gallenm¨uller · Florian Wohlfart · Georg Carle Abstract Virtual switches, like Open vSwitch, have the traditional benefits of software switches: high flex- emerged as an important part of today's data centers. ibility, vendor independence, low costs, and conceptual They connect interfaces of virtual machines and pro- benefits for switching without Ethernet bandwidth lim- vide an uplink to the physical network via network itations. The most popular virtual switch implementa- interface cards. We discuss usage scenarios for virtual tion { Open vSwitch (OvS [43]) { is heavily used in switches involving physical and virtual network inter- cloud computing frameworks like OpenStack [7] and faces. We present extensive black-box tests to quantify OpenNebula [6]. OvS is an open source project that is the throughput and latency of software switches with backed by an active community, and supports common emphasis on the market leader, Open vSwitch. Finally, standards such as OpenFlow, SNMP, and IPFIX. we explain the observed effects using white-box mea- The performance of packet processing in software surements. depends on multiple factors including the underlying hardware and its configuration, the network stack of Keywords Network measurement Cloud Perfor- · · the operating system, the virtualization hypervisor, and mance evaluation Performance characterization · · traffic characteristics (e.g., packet size, number of flows). MoonGen Each factor can significantly hurt the performance, which gives the motivation to perform systematic experiments to study the performance of virtual switching. We carry 1 Introduction out experiments to quantify performance influencing factors and describe the overhead that is introduced Software switches form an integral part of any virtu- by the network stack of virtual machines, using Open alized computing setup.
    [Show full text]
  • 2016 Mega NFV Report Pt. 1: MANO and NFVI
    Market Report 2016 Mega NFV Report Pt. 1: MANO and NFVI The Trusted News and Resource Site for SDx, SDN, NFV, Cloud and Virtualization Infrastructure Market Report | 2016 Mega NFV Report Pt. 1: MANO and NFVI contents Table of Contents Introduction – NFV Platforms Grow Up . 1 Investment Benefits of NFV in NFVI and MANO . 3 NFV Architecture . 5 NFV Market Landscape . 11 NFV MANO Products. 16 NFVI Products . 16 NFV Monitoring and Testing Products . 17 Vendor Profiles . 18 MANO and NFVI Products [Featured] Brocade: Brocade SDN Controller . 21 Brocade: Brocade Vyatta Network OS . 22 Cisco Systems, Inc.: Cisco NFV Infrastructure . 23 Cisco Systems, Inc.: Cisco Network Services Orchestrator (NSO) enabled by Tail-f . 23 Cisco Systems, Inc.: Cisco Virtual Topology System (VTS) . 23 Cisco Systems, Inc.: Cisco Elastic Services Controller (ESC) . 23 Juniper Networks, Inc.: Juniper Networks Contrail . 24 Wind River: Titanium Server . .26 MANO ADVA Optical Networking: Ensemble Orchestrator . 27 Affirmed Networks: Affirmed Mobile Content Cloud . 27 Amartus: Chameleon SDS . .27 Anuta Networks, Inc.: Anuta Network NCX . .28 ATTO Research: Athena . 28 Avaya Inc.: Avaya SDN Fx Architecture . 28 Brocade: Brocade VNF Manager . .29 Canonical: Ubuntu OpenStack . 29 CA Technologies: CA Virtual Network Assurance . 29 CENX, Inc: Exanova Service Intelligence . 30 Ciena: Ciena Blue Planet . .30 Ericsson Network Manager & Ericsson Cloud Manager . 30 Fujitsu: Network Virtuora OM and Virtuora RV . 31 Huawei: Huawei FusionSphere . 31 MRV Communications: MRV Pro-Vision . 31 Nakina Systems: NI-CONTROLLER . 32 Nakina Systems: NI-FRAMEWORK . .32 NEC/Netcracker: NEC/Netcracker Orchestration . 32 Nokia: CloudBand . 33 © 2016 SDNCentral LLC. All Rights Reserved. Page ii Market Report | 2016 Mega NFV Report Pt.
    [Show full text]