SlickFlow: Resilient source routing in Data Center Networks unlocked by OpenFlow

Ramos, Ramon Marques; Martinello, Magnos; Rothenberg, Christian Esteve

doi:10.1109/lcn.2013.6761297

Cited by 75 publications

(64 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Google B4 [8] may be one of the few examples that have proven that SDN can be resilient at scale. A number of related efforts [355], [476], [477], [261], [478], [479], [480], [481], [361] have started to tackle the concerns around control plane split architectures. The distributed controller architectures surveyed in Section IV-D are examples of approaches towards resilient SDN controller platforms with different tradeoffs in terms of consistency, durability and scalability.…”

Section: Resiliencementioning

confidence: 99%

“…On a related line of data plane resilience, SlickFlow [480] leverages the idea of using packet header space to carry alternative path information to implement resilient source routing in OpenFlow networks. Under the presence of failures along a primary path, packets can be rerouted to alternative paths by the switches themselves without involving the controller.…”

Section: Resiliencementioning

confidence: 99%

See 1 more Smart Citation

Software-Defined Networking: A Comprehensive Survey

et al. 2015

Self Cite

View full text Add to dashboard Cite

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

Section: Resiliencementioning

confidence: 99%

Section: Resiliencementioning

confidence: 99%

Software-Defined Networking: A Comprehensive Survey

et al. 2015

Self Cite

View full text Add to dashboard Cite

show abstract

“…RELATED WORK There have been many proposals in the literature to make forwarding decisions based on flat tags or labels including MPLS [19], VLANs [20] and SDN-based architectures [21], [22], [23]. MPLS [19] is a well-known source-routing protocol that forwards packets by writing and matching on labels attached to packets.…”

Section: Rdn Low Latency and Fast Failure Reactionmentioning

confidence: 99%

Programmable residues defined networks for edge data centres

Martinello

Liberato

Beldachi

et al. 2017

2017 13th International Conference on Network and Service Management (CNSM)

Self Cite

View full text Add to dashboard Cite

“…The SlickFlow approach [6] provides resilience in data center networks (DCN) using OpenFlow and is based on source routing. Primary and alternative backup paths are encoded in the packet header and OpenFlow primitives enable hardwarebased forwarding.…”

Section: Related Workmentioning

confidence: 99%

Loop-Free Alternates with Loop Detection for Fast Reroute in Software-Defined Carrier and Data Center Networks

Braun

Menth

2016

J Netw Syst Manage

View full text Add to dashboard Cite

Loop-Free Alternates (LFAs) are a local fast-reroute mechanism defined for IP networks. They are simple but suffer from two drawbacks. Firstly, some flows cannot be protected due to missing LFAs, i.e., this concept does not provide full protection coverage, which depends on network topology. Secondly, some LFAs cause loops in case of node or multiple failures. Avoiding those LFAs decreases the protection coverage even further. In this work, we propose to apply LFAs to OpenFlow-based networks. We suggest a method for loop detection so that loops can be avoided without decreasing protection coverage. We propose an implementation with OpenFlow that requires only a single additional flow rule per switch. We further investigate the percentage of flows that can be protected, not protected, or even create loops in different types of failure scenarios. We consider realistic ring and mesh networks as well as typical topologies for data center networks. None of them can be fully protected with LFAs. Therefore, we suggest an augmented fat-tree topology which allows LFAs to protect against all single link and node failures and against most double failures.

show abstract

SlickFlow: Resilient source routing in Data Center Networks unlocked by OpenFlow

Cited by 75 publications

References 3 publications

Software-Defined Networking: A Comprehensive Survey

Software-Defined Networking: A Comprehensive Survey

Programmable residues defined networks for edge data centres

Loop-Free Alternates with Loop Detection for Fast Reroute in Software-Defined Carrier and Data Center Networks

Contact Info

Product

Resources

About