2016 IEEE International Conference on Communications (ICC) 2016
DOI: 10.1109/icc.2016.7510886
|View full text |Cite
|
Sign up to set email alerts
|

Fast failover and switchover for link failures and congestion in software defined networks

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
37
0
5

Year Published

2017
2017
2024
2024

Publication Types

Select...
5
3

Relationship

0
8

Authors

Journals

citations
Cited by 63 publications
(43 citation statements)
references
References 13 publications
1
37
0
5
Order By: Relevance
“…This process was done exclusively in the data plane (OpenFlow switches) and took less than ten milliseconds, which is an acceptable value for disruption in an inter-domain environment (less than 50 ms [34]). The measured millisecond interval was coherent with the FF mechanism recovery times found in the literature [35,36].…”
Section: Scenario Ii-external Link Failuresupporting
confidence: 89%
See 1 more Smart Citation
“…This process was done exclusively in the data plane (OpenFlow switches) and took less than ten milliseconds, which is an acceptable value for disruption in an inter-domain environment (less than 50 ms [34]). The measured millisecond interval was coherent with the FF mechanism recovery times found in the literature [35,36].…”
Section: Scenario Ii-external Link Failuresupporting
confidence: 89%
“…Hence, for future works, it is interesting to investigate the different approaches for the manipulation of flows in an OpenFlow network, for example, proactive and active strategies [29]. Another idea in this line of thought is to manage and apply a more aware congestion control for the flows, e.g., a switchover mechanism [36] that changes congested flows to different paths during the lifetime of the flows.…”
Section: Future Work and Limitationsmentioning
confidence: 99%
“…We have implemented the simulation environment using Mininet 2.2.1 installed on a patched Linux Kernel (4.11.0-rc8+) that supports CAN-Utils Package namespaces [14]. Additionally, we have built the protocol adapters based on TCP/IP Sockets (that ensure retransmission in the case of a packet loss) and CAN-Sockets [23].…”
Section: Sdivnmentioning
confidence: 99%
“…Several attempts have been made to achieve faster recovery using the FF group to eliminate the involvement of controller for detouring [8,10,11]. Sharma et al and Katz and Ward [8,24] used Bidirectional Forwarding Detection (BFD) protocol to detect path failure and reroute the flows on the preconfigured alternate path in around 42-48 ms.…”
Section: Related Workmentioning
confidence: 99%
“…Pre-provisioned recovery schemes, based on end-to-end path protection strategies for handling network failures, are well known and deployed in production networks for faster recovery. Several authors have proposed the SDN-based recovery schemes for single-link failure-handling and showed improved results regarding reduced recovery time [8][9][10][11][12][13]. However, it requires additional signalling mechanism by the failure-affected switches to notify the failure event to the source switch of the primary path, which could cause additional recovery delay.…”
Section: Introductionmentioning
confidence: 99%