Abstract:
To achieve high availability, fault tolerance is desirable for most networks, including Software Defined Networks (SDNs). Link and switch failures are commonly observed i...Show MoreMetadata
Abstract:
To achieve high availability, fault tolerance is desirable for most networks, including Software Defined Networks (SDNs). Link and switch failures are commonly observed in SDN, severely affecting the network performance and even making the whole system break down. In this paper, we propose a protection-based recovering method for link failures using vlan-tag, which is fast with low memory consumption. Inheriting from protection mechanism, our method is able to react and recover quickly without the participation of controller(s) by immediately switching to the backup path(s) precomputed when failure occurs. More importantly, it is memory efficient as it calculates the backup based on each link (instead of each flow), and simply assigns a vlan-id for each link, avoiding the high memory (TCAM used for flow table storage is costly) requirements of conventional protection methods. The simulation results expose that our method can recover from link failures within 20 ms (on the average) like other protection approaches, while the restoration needs 50 ms (on the average). Moreover, in experimental environment our method requires 100 times less flow table entries' amount than the protection method based on each flow to store backup paths.
Published in: 2016 IEEE 35th International Performance Computing and Communications Conference (IPCCC)
Date of Conference: 09-11 December 2016
Date Added to IEEE Xplore: 19 January 2017
ISBN Information:
Electronic ISSN: 2374-9628
References is not available for this document.
Contents Select All
1.
Nick Mckeown, Scott Shenker, Tom Anderson, Larry Peterson, Jonathan Turner, Hari Balakrishnan, et al., "Openflow: Enabling innovation in campus networks", ACM Computer Communication Review, April 2008.
2.
D. Kreutz, F.M.V. Ramos, P. EstevesVerissimo, C. EsteveRothenberg, S. Azodolmolky and S. Uhlig, "Software-defined networking: A comprehensive survey", Proceedings of the IEEE, vol. 103, no. 1, pp. 14-76, January 2015.
3.
Sushant Jain, Alok Kumar, Subhasree Mandal, Joon Ong, Leon Poutievs-ki, Arjun Singh, et al., "B4: Experience with a globally-deployed software defined wan", Special Interest Group on Data Communication (SIGCOMM) 2013 ACM International Conference on, pp. 3-14, August 2013.
4.
Jean-Philippe Vasseur, Mario Pickavet and Piet Demeester, Network Recovery: Protection and Restoration of Optical SONET-SDH IP and MPLS., Morgan Kaufmann, August 2004.
5.
Malcolm Betts, Nurit Sprecher, Satoshi Ueno, Ben Niven-Jenkins and Deborah Brungard, "Requirements of an mpls transport profile", RFC 5654, September 2009.
6.
Sachin Sharma, Dimitri Staessens, Didier Colle, Mario Pickavet and Piet Demeester, "Openflow: Meeting carrier-grade recovery requirements", Computer Communications, vol. 36, no. 6, pp. 656-665, March 2013.
7.
Andrew R. Curtis, Jeffrey C. Mogul, Jean Tourrilhes, Praveen Yala-gandula, Puneet Sharma and Sujata Banerjee, "Devoflow: Scaling flow management for high-performance networks", Proceedings of the ACM SIGCOMM 2011 Conference SIGCOMM ‘11, pp. 254-265, 2011.
8.
Sekar Vyas, Ratnasamy Sylvia, Michael K. Reiter, Norbert Egi and Guangyu Shi, "The middlebox manifesto: enabling innovation in mid-dlebox deployment", ACM Workshop on Hot Topics in Networks, pp. 1-6, 2011.
9.
H. Huang, S. Guo, P. Li, W. Liang and A. Y. Zomaya, "Cost minimization for rule caching in software defined networking", IEEE Transactions on Parallel and Distributed Systems, vol. 27, no. 4, pp. 1007-1016, April 2016.
10.
Openflow switch specification: Version 1.0.0, December 2009.
11.
Openflow switch specification: Version 1.1.0, Feburuary 2011.
12.
Jue Chen, Jinbang Chen, Fei Xu, Min Yin and Wei Zhang, "When software defined networks meet fault tolerance: A survey", Algorithms and Architectures for Parallel Processing (ICA3PP) 2015 International Conference on, pp. 351-368, November 2015.
13.
Hyojoon Kim, M. Schlansker, J. R. Santos, J. Tourrilhes, Y. Turner and N. Feamster, "Coronet: Fault tolerance for software defined networks", 2012 20th IEEE International Conference on Network Protocols (ICNP), pp. 1-2, Oct 2012.
14.
Mark Reitblatt, Marco Canini, Arjun Guha and Nate Foster, "Fattire: Declarative fault tolerance for software-defined networks", Hot Topics in Software Defined Networking (HotSDN) 2013 Proceedings of 2nd Workshop on, pp. 109-114, August 2013.
15.
M. Desai and T. Nandagopal, "Coping with link failures in centralized control plane architectures", 2010 Second International Conference on COMmunication Systems and NETworks (COMSNETS 2010), pp. 1-10, Jan 2010.
16.
F. Botelho, A. Bessani, F. M. V. Ramos and P. Ferreira, "On the design of practical fault-tolerant sdn controllers", 2014 Third European Workshop on Software Defined Networks, pp. 73-78, Sept 2014.
17.
F. A. Botelho, F. M. V. Ramos, D. Kreutz and A. N. Bessani, "On the feasibility of a consistent and fault-tolerant data store for sdns", 2013 Second European Workshop on Software Defined Networks, pp. 38-43, Oct 2013.
18.
N. Katta, H. Zhang, M. Freedman and J. Rexford, "Ravana: controller fault-tolerance in software-defined networking", 2015 1st ACM SIG-COMM Symposium on Software Defined Networking Research, pp. 1-4, June 2015.
19.
Peter Peresini, Nedeljko Vasic, Marco Canini and Dejan Kostic, "Automatic failure recovery for software-defined networks", Hot Topics in Software Defined Networking (HotSDN) 2013 Proceedings of 2nd Workshop on, pp. 1-6, August 2013.
20.
Andrea Sgambelluri, Alessio Giorgetti, Filippo Cugini, Francesco Paolucci and Piero Castoldi, "Openflow-based segment protection in ethernet networks. Optical Communications and Networking", IEEE/OSA Journal of, vol. 5, no. 9, pp. 1066-1075, September 2013.
21.
Ramon Marques Ramos and Christian Esteve Rothenberg, "Slickfiow: Resilient source routing in data center networks unlocked by openfiow", Local Computer Networks (LCN) 2013 IEEE 38th Conference on, pp. 606-613, October 2013.
22.
Mininet..
23.
Openvswitch.
