Software defined networking: Meeting carrier grade requirements

Abstract-The Internet has led to the creation of a digital society, where (almost) everything is connected and is accessible from anywhere. However, despite their widespread adoption, traditional IP networks are complex and very hard to manage. It is both difficult to configure the network according to predefined 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 planes are bundled together. Software-Defined Networking (SDN) is an emerging paradigm that promises to change this state of affairs, by breaking vertical integration, separating the network's control logic from the underlying routers and switches, promoting (logical) centralization of network control, and introducing the ability to program the network. The separation of concerns introduced between the definition of network policies, their implementation in switching hardware, and the forwarding of traffic, is key to the desired flexibility: by breaking the network control problem into tractable pieces, SDN makes it easier to create and introduce new abstractions in networking, simplifying network management and facilitating network evolution.In this paper we present a comprehensive survey on SDN. We start by introducing the motivation for SDN, explain its main concepts and how it differs from traditional networking, its roots, and the standardization activities regarding this novel paradigm. Next, we present the key building blocks of an SDN infrastructure using a bottom-up, layered approach. We provide an in-depth analysis of the hardware infrastructure, southbound and northbound APIs, network virtualization layers, network operating systems (SDN controllers), network programming languages, and network applications. We also look at cross-layer problems such as debugging and troubleshooting. In an effort to anticipate the future evolution of this new paradigm, we discuss the main ongoing research efforts and challenges of SDN. In particular, we address the design of switches and control platforms -with a focus on aspects such as resiliency, scalability, performance, security and dependability -as well as new opportunities for carrier transport networks and cloud providers. Last but not least, we analyze the position of SDN as a key enabler of a software-defined environment.

show abstract

“…Flexible and easy to deploy energy saving strategies. [565] Complex and static control and data plane restoration techniques.…”

Section: Deployment and Managementmentioning

confidence: 99%

Software-Defined Networking: A Comprehensive Survey

et al. 2015

View full text Add to dashboard Cite

show abstract

“…restoration and protection in OpenFlow networks. In the case of restoration, the alternative path is established by the controller when it receives the failure notification from the OpenFlow switches [4,5]. In the case of protection, two disjoint paths (working and protected) are established by the controller before the failure occurs in the network.…”

Section: Our Implemented Mechanisms and Experiments On High Speed Testbedmentioning

confidence: 99%

A Demonstration of Fast Failure Recovery in Software Defined Networking

Sharma

Staessens

Colle

et al. 2012

Lecture Notes of the Institute for Computer Sciences, Social Informatics and Telecommunications Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. Software defined networking (SDN) is a recent architectural framework for networking, which aims at decoupling the network control plane from the physical topology and at having the forwarding element controlled through a uniform vendoragnostic interface. A well-known implementation of SDN is OpenFlow. The core idea of OpenFlow is to provide direct programming of a router or switch to monitor and modify the way in which the individual packets are handled by the device. We describe our implemented fast failure recovery mechanisms (Restoration and Protection) in OpenFlow, capable of recovering from a link failure using an alternative path. In the demonstration, a video clip is streamed from a server to a remote client, which is connected by a network with an emulated German Backbone Network topology. We show switching of the video stream from the faulty path to the fault-free alternative path (restored or protected path) upon failure.

show abstract

“…Refs. [3,4] designed a passive failure recovery scheme for a SDN-based operator network. Each time a failure occurred, the switch notified the controller of the topology change, and then the controller completed the calculation of the failure recovery path and updates of relevant flow table.…”

Section: Introductionmentioning

confidence: 99%

Fast network restoration with equivalent cooperative routing

Dong

Huang

Sun

et al. 2017

J. Commun. Inf. Netw.

View full text Add to dashboard Cite

Aiming at the problem of failure recovery in current networks, a fast failure recovery method based on equivalent cooperative routing is proposed. Firstly, the transmission path between the source and destination nodes is divided into several non-overlapping path segments. Next, backup paths are deployed for each link in the path segment through segmented routing technology, which ensures fast routing recovery after failure. Additionally, in order to avoid damaging the QoS of the data stream through the failure recovery process, the transmission is guaranteed by the intersegment QoS complement. The experimental results show that the proposed method has a low failure recovery delay under a relatively small flow table cost.

show abstract

Software defined networking: Meeting carrier grade requirements

Cited by 103 publications

References 9 publications

Software-Defined Networking: A Comprehensive Survey

Software-Defined Networking: A Comprehensive Survey

A Demonstration of Fast Failure Recovery in Software Defined Networking

Fast network restoration with equivalent cooperative routing

Contact Info

Product

Resources

About