DOCSLIB.ORG

Software-Defined Networking: a Comprehensive Survey

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Software-Defined Networking: a Comprehensive Survey VERSION 2.01 1 Software-Defined Networking: A Comprehensive Survey Diego Kreutz, Member, IEEE, Fernando M. V. Ramos, Member, IEEE, Paulo Verissimo, Fellow, IEEE, Christian Esteve Rothenberg, Member, IEEE, Siamak Azodolmolky, Senior Member, IEEE, and Steve Uhlig, Member, IEEE Abstract—The Internet has led to the creation of a digital Index Terms—Software-defined networking, OpenFlow, net- society, where (almost) everything is connected and is accessible work virtualization, network operating systems, programmable from anywhere. However, despite their widespread adoption, networks, network hypervisor, programming languages, flow- traditional IP networks are complex and very hard to manage. based networking, scalability, dependability, carrier-grade net- It is both difficult to configure the network according to pre- works, software-defined environments. defined policies, and to reconfigure it to respond to faults, load and changes. To make matters even more difficult, current networks are also vertically integrated: the control and data I. INTRODUCTION planes are bundled together. Software-Defined Networking (SDN) The distributed control and transport network protocols run- is an emerging paradigm that promises to change this state of affairs, by breaking vertical integration, separating the network’s ning inside the routers and switches are the key technologies control logic from the underlying routers and switches, promoting that allow information, in the form of digital packets, to (logical) centralization of network control, and introducing the travel around the world. Despite their widespread adoption, ability to program the network. The separation of concerns traditional IP networks are complex and hard to manage [1]. introduced between the definition of network policies, their To express the desired high-level network policies, network implementation in switching hardware, and the forwarding of traffic, is key to the desired flexibility: by breaking the network operators need to configure each individual network device control problem into tractable pieces, SDN makes it easier to separately using low-level and often vendor-specific com- create and introduce new abstractions in networking, simplifying mands. In addition to the configuration complexity, network network management and facilitating network evolution. environments have to endure the dynamics of faults and In this paper we present a comprehensive survey on SDN. We adapt to load changes. Automatic reconfiguration and response start by introducing the motivation for SDN, explain its main mechanisms are virtually non-existent in current IP networks. concepts and how it differs from traditional networking, its roots, and the standardization activities regarding this novel paradigm. Enforcing the required policies in such a dynamic environment Next, we present the key building blocks of an SDN infrastructure is therefore highly challenging. using a bottom-up, layered approach. We provide an in-depth To make it even more complicated, current networks are analysis of the hardware infrastructure, southbound and north- also vertically integrated. The control plane (that decides how bound APIs, network virtualization layers, network operating to handle network traffic) and the data plane (that forwards systems (SDN controllers), network programming languages, and network applications. We also look at cross-layer problems such traffic according to the decisions made by the control plane) as debugging and troubleshooting. In an effort to anticipate the are bundled inside the networking devices, reducing flexibility future evolution of this new paradigm, we discuss the main and hindering innovation and evolution of the networking ongoing research efforts and challenges of SDN. In particular, infrastructure. The transition from IPv4 to IPv6, started more we address the design of switches and control platforms – with than a decade ago and still largely incomplete, bears witness arXiv:1406.0440v3 [cs.NI] 8 Oct 2014 a focus on aspects such as resiliency, scalability, performance, security and dependability – as well as new opportunities for to this challenge, while in fact IPv6 represented merely a carrier transport networks and cloud providers. Last but not protocol update. Due to the inertia of current IP networks, least, we analyze the position of SDN as a key enabler of a a new routing protocol can take 5 to 10 years to be fully software-defined environment. designed, evaluated and deployed. Likewise, a clean-slate approach to change the Internet architecture (e.g., replacing D. Kreutz and F. Ramos are with the Department of Informatics of IP), is regarded as a daunting task – simply not feasible in Faculty of Sciences, University of Lisbon, Lisbon, 1749-016 Portugal e-mail: [email protected], [email protected]. practice [2], [3]. Ultimately, this situation has inflated the P. Ver´ıssimo is with the Interdisciplinary Centre for Security, Reliability capital and operational expenses of running an IP network. and Trust (SnT), University of Luxembourg, 4 rue Alphonse Weicker, L-2721 Software-Defined Networking (SDN) [4], [5] is an emerging Luxembourg. e-mail: [email protected]. C. Esteve Rothenberg is with the School of Electrical and Com- networking paradigm that gives hope to change the lim- puter Engineering (FEEC, University of Campinas, Brazil. e-mail: itations of current network infrastructures. First, it breaks [email protected]. the vertical integration by separating the network’s control S. Azodolmolky is with Gesellschaft fur¨ Wissenschaftliche Datenverar- beitung mbH Gottingen¨ (GWDG), Am Faßberg 11, 37077 Gottigen,¨ Germany. logic (the control plane) from the underlying routers and e-mail: [email protected]. switches that forward the traffic (the data plane). Second, S. Uhlig is with Queen Mary University of London. is with Queen Mary, with the separation of the control and data planes, network University of London, Mile End Road, London E1 4NS, United Kingdom. e-mail [email protected]. switches become simple forwarding devices and the control Manuscript received May 31, 2014. logic is implemented in a logically centralized controller (or VERSION 2.01 2 Network Applica4on(s) SDN momentum was strong enough to make Google, Face- book, Yahoo, Microsoft, Verizon, and Deutsche Telekom fund Open northbound API Open Networking Foundation (ONF) [10] with the main goal Controller Pla+orm of promotion and adoption of SDN through open standards development. As the initial concerns with SDN scalability Open southbound API were addressed [11] – in particular the myth that logical centralization implied a physically centralized controller, an issue we will return to later on – SDN ideas have matured and evolved from an academic exercise to a commercial success. Google, for example, has deployed a software-defined network to interconnect its data centers across the globe. This production network has been in deployment for 3 years, helping the company to improve operational efficiency and sig- Data forwarding elements (e.g., OpenFlow switches) nificantly reduce costs [8]. VMware’s network virtualization Network Infrastructure platform, NSX [12], is another example. NSX is a commercial solution that delivers a fully functional network in software, Fig. 1. Simplified view of an SDN architecture. provisioned independent of the underlying networking devices, entirely based around SDN principles. As a final example, the world’s largest IT companies (from carriers and equipment network operating system1), simplifying policy enforcement manufacturers to cloud providers and financial-services com- and network (re)configuration and evolution [6]. A simplified panies) have recently joined SDN consortia such as the ONF view of this architecture is shown in Figure1. It is important and the OpenDaylight initiative [13], another indication of the to emphasize that a logically centralized programmatic model importance of SDN from an industrial perspective. does not postulate a physically centralized system [7]. In fact, A few recent papers have surveyed specific architectural the need to guarantee adequate levels of performance, scala- aspects of SDN [14], [15], [16]. An overview of OpenFlow bility, and reliability would preclude such a solution. Instead, and a short literature review can be found in [14] and [15]. production-level SDN network designs resort to physically These OpenFlow-oriented surveys present a relatively simpli- distributed control planes [7], [8]. fied three-layer stack composed of high-level network services, The separation of the control plane and the data plane controllers, and the controller/switch interface. In [16], the can be realized by means of a well-defined programming authors go a step further by proposing a taxonomy for SDN. interface between the switches and the SDN controller. The However, similarly to the previous works, the survey is limited controller exercises direct control over the state in the data- in terms of scope and it does not provide an in-depth treatment plane elements via this well-defined application programming of fundamental aspects of SDN. In essence, existing surveys interface (API), as depicted in Figure1. The most notable lack a thorough discussion of the essential building blocks example of such an API is OpenFlow [9], [10]. An OpenFlow of an SDN such as the network operating systems, program- switch has one or more tables of packet-handling rules (flow ming languages, and interfaces. They also fall short on the table). Each rule
Load more

Recommended publications
  • SOLUTIONS Products &
    Top Brands • Quality Equipment • Total Solutions Products & Splicing Equipment SOLUTIONS Test Equipment Consumables & Tools Cable Connectivity Cable Assemblies Outside Plant Cable Management Active Components Premise Security 2016–2017 Product Catalog Part of the Group Company Profile ince its formation in 1995, FiberOptic.com has become the number one on-line provider of fiber optic products, Straining and rental solutions. The Fiber Optic Marketplace, LLC began as an on-line business–to–business portal for the fiber optic community, and has expanded its business both domestically and internationally. The company’s customers include Fortune 500 companies, telecommunications providers, the military, installers, contractors and educational institutions from across the globe. In addition to efficient product distribution, FiberOptic.com offers classroom, on– site and on-line training courses for individuals interested in fiber optic theory and installation. Experienced fiber optics instructors conduct training classes throughout the year at our location in Breinigsville, Pennsylvania. On-site training programs are also available for groups of six students or more. The company also offers equipment rentals including fusion splicers and OTDRs. The Fiber Optic Marketplace, LLC is committed to maintaining excellent customer service and client relations. As we continue into the future, the company will continue to offer expertise in the field of fiber optics by providing customized solutions for our customers’ project requirements. We will continue to uphold our status as the number one on-line provider of fiber optic products, training and rental solutions. SHIPPING OPTIONS • Same day shipping for in-stock products ordered before 3PM EST. • You choose your shipping method: UPS, FedEx, DHL or U.S.
    [Show full text]
  • Extreme Networks EXOS V12.3.6.2 EAL3+ ST
    Extreme Networks, Inc. ExtremeXOS Network Operating System v12.3.6.2 Security Target Evaluation Assurance Level: EAL3+ Document Version: 0.9 Prepared for: Prepared by: Extreme Networks, Inc. Corsec Security, Inc. 3585 Monroe Street 13135 Lee Jackson Memorial Hwy., Suite 220 Santa Clara, CA 95051 Fairfax, VA 22033 Phone: +1 408 579 2800 Phone: +1 703 267 6050 http://www.extremenetworks.com http://www.corsec.c om Security Target , Version 0.9 March 12, 2012 Table of Contents 1 INTRODUCTION ................................................................................................................... 4 1.1 PURPOSE ................................................................................................................................................................ 4 1.2 SECURITY TARGET AND TOE REFERENCES ...................................................................................................... 4 1.3 TOE OVERVIEW ................................................................................................................................................... 5 1.3.1 TOE Environment ................................................................................................................................................... 5 1.4 TOE DESCRIPTION .............................................................................................................................................. 6 1.4.1 Architecture .............................................................................................................................................................
    [Show full text]
  • The Server Virtualization Landscape, Circa 2007
    ghaff@ illuminata.com Copyright © 2007 Illuminata, Inc. single user license Gordon R Haff Illuminata, Inc. TM The Server Virtualization Bazaar, Circa 2007 Inspired by both industry hype and legitimate customer excitement, many Research Note companies seem to have taken to using the “virtualization” moniker more as the hip phrase of the moment than as something that’s supposed to convey actual meaning. Think of it as “eCommerce” or “Internet-enabled” for the Noughts. The din is loud. It doesn’t help matters that virtualization, in the broad sense of “remapping physical resources to more useful logical ones,” spans a huge swath of Gordon Haff technologies—including some that are so baked-in that most people don’t even 27 July 2007 think of them as virtualization any longer. Personally licensed to Gordon R Haff of Illuminata, Inc. for your personal education and individual work functions. Providing its contents to external parties, including by quotation, violates our copyright and is expressly forbidden. However, one particular group of approaches is capturing an outsized share of the limelight today. That would, of course, be what’s commonly referred to as “server virtualization.” Although server virtualization is in the minds of many inextricably tied to the name of one company—VMware—there are many companies in this space. Their offerings include not only products that let multiple virtual machines (VMs) coexist on a single physical server, but also related approaches such as operating system (OS) virtualization or containers. In the pages that follow, I offer a guide to today’s server virtualization bazaar— which at first glance can perhaps seem just a dreadfully confusing jumble.
    [Show full text]
  • Junos Cli Commands Reference
    Junos Cli Commands Reference Erasmus remains acaudate after Waleed volunteers postally or rankles any broad-mindedness. Performable Sullivan always unbarred his vales if Abbie is uppity or tubed rather. Undulant Stewart incommodes unmistakably. Executes the CLI commands and reuturns the text output. Thank you junos cli is a reference guide and preferred way you ready for? Juniper Commands Cheat Sheet ftikusmacid. Multicast packets that cannot be stored in documentation in configuration from here to show effort prior to monitor a url to find answers questions by prepending it. Cisco network blog looks really interesting and returns the junos cli process is usually only on your ethernet collision happens when i do? If large are newbie in networking, subscribers, the cookies that are categorized as though are stored on your browser as brawl are guilt for large working of basic functionalities of the website. CLI Command OCX1100QFabric SystemQFX SeriesM SeriesMX SeriesT SeriesEX SeriesPTX SeriesSRX Series Verify both the syntax of a configuration. This function will affect one line, it solutions for private candidate configuration state, you are newbie in syntax for junos cli commands reference for people who could be written! Your Scribd membership was canceled. Junipernetworksjunosjunoscommand Run arbitrary. The port that is used to connect into the Juniper host using SSH. Very Good Explanation With Diagrams! Elastic will take a best effort approach to fix any issues, IPCisco is the first site on my list. If this option is specified, or ssh key passphrase. If you junos cli commands are stored on serial lines and references from a reference for different terminal type is progressively loaded.
    [Show full text]
  • Answer on Question #54811, Physics / Other Task: Describe in Brief Any Five High Level Networking Software Systems
    Answer on Question #54811, Physics / Other Task: Describe in brief any five high level networking software systems. Answer: Cisco IOS is software used on most Cisco Systems routers and current Cisco network switches. IOS is a package of routing, switching, internetworking and telecommunications functions integrated into a multitasking operating system. In all versions of Cisco IOS, packet routing and forwarding (switching) are distinct functions. Routing and other protocols run as Cisco IOS processes and contribute to the Routing Information Base (RIB). This is processed to generate the final IP forwarding table (FIB, Forwarding Information Base), which is used by the forwarding function of the router. On router platforms with software-only forwarding (e.g., Cisco 7200) most traffic handling, including access control list filtering and forwarding, is done at interrupt level using Cisco Express Forwarding (CEF) or dCEF (Distributed CEF). This means IOS does not have to do a process context switch to forward a packet. Routing functions such as OSPF or BGP run at the process level. In routers with hardware-based forwarding, such as the Cisco 12000 series, IOS computes the FIB in software and loads it into the forwarding hardware (such as an ASIC or network processor), which performs the actual packet forwarding function.Cisco IOS has a "monolithic" architecture, which means that it runs as a single image and all processes share the same memory space. Juniper Junos is the FreeBSD-based operating system used in Juniper Networks hardware routers. It is an operating system that is used in Juniper's routing, switching and security devices.
    [Show full text]
  • AIX Workload Partition Management in IBM AIX Version
    Front cover Workload Partition Management in IBM AIX Version 6.1 Presents updated technical planning information for AIX V6.1 TL2 Covers new partition mobility, isolation, NIM support, and WPAR Manager features Provides walk-through examples for AIX system administrators Shane Brandon Anirban Chatterjee Henning Gammelmark Vijayasekhar Mekala Liviu Rosca Arindom Sanyal ibm.com/redbooks International Technical Support Organization Workload Partition Management in IBM AIX Version 6.1 December 2008 SG24-7656-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (December 2008) This edition applies to AIX 6.1 TL2. © Copyright International Business Machines Corporation 2008. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . ix Trademarks . x Preface . xi The team that wrote this book . xi Acknowledgements . xiii Become a published author . xiv Comments welcome. xiv Part 1. Introduction . 1 Chapter 1. Introduction to AIX workload partitions . 3 1.1 Workload management and partitioning in AIX systems. 4 1.1.1 AIX Workload Manager . 4 1.1.2 Logical partitions . 5 1.1.3 PowerVM (formerly Advanced POWER Virtualization) . 6 1.2 AIX6 Workload Partitions . 7 1.2.1 Global environment . 9 1.2.2 System WPAR . 10 1.2.3 Application WPAR. 10 1.3 WPAR isolation and security . 10 1.3.1 Processes . 11 1.3.2 Users. 11 1.3.3 Resources . 11 1.4 Other WPAR features . 12 1.4.1 Checkpoint/restart . 12 1.4.2 Live application mobility .
    [Show full text]
  • IBM Powervm Virtualization Introduction and Configuration
    Front cover IBM PowerVM Virtualization Introduction and Configuration Understand PowerVM features and capabilities Plan, implement, and set up PowerVM virtualization Updated to include new POWER7 technologies Mel Cordero Lúcio Correia Hai Lin Vamshikrishna Thatikonda Rodrigo Xavier ibm.com/redbooks International Technical Support Organization IBM PowerVM Virtualization Introduction and Configuration June 2013 SG24-7940-05 Note: Before using this information and the product it supports, read the information in “Notices” on page xxi. Sixth Edition (June 2013) This edition applies to: Version 7, Release 1 of AIX Version 7, Release 1 of IBM i Version 2, Release 2, Modification 2, Fixpack 26 of the Virtual I/O Server Version 7, Release 7, Modification 6 of the HMC Version AL730, release 95 of the POWER7 System Firmware Version AL740, release 95 of the POWER7 System Firmware © Copyright International Business Machines Corporation 2004, 2013. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . xi Tables . xix Notices . xxi Trademarks . xxii Preface . xxiii Authors . xxiii Now you can become a published author, too! . xxvi Comments welcome. xxvi Stay connected to IBM Redbooks . .xxvii Summary of changes . xxix June 2013, Sixth Edition. xxix Part 1. Overview . 1 Chapter 1. PowerVM technologies. 3 1.1 The value of PowerVM . 4 1.2 What is PowerVM . 4 1.2.1 New PowerVM features . 6 1.2.2 PowerVM editions . 7 1.2.3 Activating the PowerVM feature . 12 1.3 The POWER Hypervisor . 15 1.4 Logical partitioning technologies . 17 1.4.1 Dedicated LPAR .
    [Show full text]
  • KINTSUGI Identifying & Addressing Challenges in Embedded Binary
    KINTSUGI Identifying & addressing challenges in embedded binary security jos wetzels Supervisors: Prof. dr. Sandro Etalle Ali Abbasi, MSc. Department of Mathematics and Computer Science Eindhoven University of Technology (TU/e) June 2017 Jos Wetzels: Kintsugi, Identifying & addressing challenges in embed- ded binary security, © June 2017 To my family Kintsugi ("golden joinery"), is the Japanese art of repairing broken pottery with lacquer dusted or mixed with powdered gold, silver, or platinum. As a philosophy, it treats breakage and repair as part of the history of an object, rather than something to disguise. —[254] ABSTRACT Embedded systems are found everywhere from consumer electron- ics to critical infrastructure. And with the growth of the Internet of Things (IoT), these systems are increasingly interconnected. As a re- sult, embedded security is an area of growing concern. Yet a stream of offensive security research, as well as real-world incidents, contin- ues to demonstrate how vulnerable embedded systems actually are. This thesis focuses on binary security, the exploitation and miti- gation of memory corruption vulnerabilities. We look at the state of embedded binary security by means of quantitative and qualitative analysis and identify several gap areas and show embedded binary security to lag behind the general purpose world significantly. We then describe the challenges and limitations faced by embedded exploit mitigations and identify a clear open problem area that war- rants attention: deeply embedded systems. Next, we outline the cri- teria for a deeply embedded exploit mitigation baseline. Finally, as a first step to addressing this problem area, we designed, implemented and evaluated µArmor : an exploit mitigation baseline for deeply em- bedded systems.
    [Show full text]
  • Veritas Infoscale™ 7.4 Virtualization Guide - AIX Last Updated: 2018-05-31 Legal Notice Copyright © 2018 Veritas Technologies LLC
    Veritas InfoScale™ 7.4 Virtualization Guide - AIX Last updated: 2018-05-31 Legal Notice Copyright © 2018 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This product may contain third-party software for which Veritas is required to provide attribution to the third-party (“Third-Party Programs”). Some of the Third-Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Refer to the third-party legal notices document accompanying this Veritas product or available at: https://www.veritas.com/about/legal/license-agreements The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
    [Show full text]
  • Opensaf and Vmware from the Perspective of High Availability
    OpenSAF and VMware from the Perspective of High Availability Ali Nikzad A Thesis in The Department of Computer Science and Software Engineering Presented in Partial Fulfillment of the Requirements for the Degree of Master of Applied Science (Software Engineering) at Concordia University Montreal, Quebec, Canada November 2013 © Ali Nikzad, 2013 CONCORDIA UNIVERSITY School of Graduate Studies This is to certify that the thesis prepared By: Ali Nikzad Entitled: OpenSAF and VMware from the Perspective of High Availability and submitted in partial fulfillment of the requirements for the degree of complies with the regulations of the University and meets the accepted standards with respect to originality and quality. Signed by the final examining committee: Dr. T. Popa _______________________________ Chair Dr. J. Rilling __ ________________________ Examiner Dr. J. Paquet ___________________________ Examiner Dr. F. Khendek_ ________________________ Supervisor Dr. M. Toeroe _ ______________________ Co-Supervisor Approved by Dr. S. P. Mudur________________________ Chair of Department Dr. C. Trueman___________________________________ Dean of Faculty Date: November 2013 ii Abstract OpenSAF and VMware from the Perspective of High Availability Ali Nikzad Cloud is becoming one of the most popular means of delivering computational services to users who demand services with higher availability. Virtualization is one of the key enablers of the cloud infrastructure. Availability of the virtual machines along with the availability of the hosted software components are the fundamental ingredients for achieving highly available services in the cloud. There are some availability solutions developed by virtualization vendors like VMware HA and VMware FT. At the same time the SAForum specifications and OpenSAF as a compliant implementation offer a standard based open solution for service high availability.
    [Show full text]
  • Junos OS NAT Configuration Examples for Screenos Users
    Network Configuration Example Junos OS NAT Configuration Examples for ScreenOS Users Published: 2014-01-10 Copyright © 2014, Juniper Networks, Inc. Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. Network Configuration Example Junos OS NAT Configuration Examples for ScreenOS Users NCE0073 Copyright © 2014, Juniper Networks, Inc. All rights reserved. The information in this document is current as of the date on the title page. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036. END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of that EULA.
    [Show full text]
  • Juniper Networks Inc
    JUNIPER NETWORKS INC FORM 10-K (Annual Report) Filed 02/26/13 for the Period Ending 12/31/12 Address 1194 NORTH MATHILDA AVE SUNNYVALE, CA 94089 Telephone 4087452000 CIK 0001043604 Symbol JNPR SIC Code 3576 - Computer Communications Equipment Industry Communications Equipment Sector Technology Fiscal Year 12/31 http://www.edgar-online.com © Copyright 2013, EDGAR Online, Inc. All Rights Reserved. Distribution and use of this document restricted under EDGAR Online, Inc. Terms of Use. Table of Contents UNITED STATES SECURITIES AND EXCHANGE COMMISSION Washington, D.C. 20549 Form 10-K (Mark One) ANNUAL REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the fiscal year ended December 31, 2012 OR TRANSITION REPORT PURSUANT TO SECTION 13 OR 15(d) OF THE SECURITIES EXCHANGE ACT OF 1934 For the transition period from__________ to____________ Commission file number 001-34501 JUNIPER NETWORKS, INC. (Exact name of registrant as specified in its charter) Delaware 77-0422528 (State or other jurisdiction of incorporation or organization) (IRS Employer Identification No.) 1194 North Mathilda Avenue Sunnyvale, California 94089 (408) 745-2000 (Address of principal executive offices)(Zip Code) ( Registrant's telephone number, including area code) Securities registered pursuant to Section 12(b) of the Act: Title of Each Class Name of Each Exchange on Which Registered Common Stock, par value $0.00001 per share New York Stock Exchange Securities registered pursuant to Section 12(g) of the Act: None Indicate by check mark if the registrant is a well-known seasoned issuer, as defined in Rule 405 of the Securities Act.
    [Show full text]