Recovery of software defined network from multiple failures: Openstate vs openflow
Software Defined Network (SDN) is an emerging network with clearer separation between control and data planes. Like non-SDN, SDN undergoes a recovery process upon occurrence of failures. The recovery process should take less than 50 msec to comply with service level agreement of Internet Service Pro...
Saved in:
Main Authors: | , , |
---|---|
Format: | Article |
Published: |
IEEE Computer Society
2018
|
Online Access: | https://www.scopus.com/inward/record.uri?eid=2-s2.0-85046082329&doi=10.1109%2fAICCSA.2017.32&partnerID=40&md5=fd81de8da2061aa0e484ac64ca8195d7 http://eprints.utp.edu.my/21714/ |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Institution: | Universiti Teknologi Petronas |
id |
my.utp.eprints.21714 |
---|---|
record_format |
eprints |
spelling |
my.utp.eprints.217142018-08-14T00:55:22Z Recovery of software defined network from multiple failures: Openstate vs openflow Zahid, M.S.M. Isyaku, B. Fadzil, F.A. Software Defined Network (SDN) is an emerging network with clearer separation between control and data planes. Like non-SDN, SDN undergoes a recovery process upon occurrence of failures. The recovery process should take less than 50 msec to comply with service level agreement of Internet Service Providers (ISPs). Currently, it is possible for SDN to meet the requirement with Openstate standard or protocol. However, the results were based on single failures only. Multiple failures may also occur and unavoidable. In this research, formulae to estimate recovery times of Openflow and Openstate are derived and proposed. It is obvious from the formulae that Openstate recovery time is better or equivalent to Openflow. Thus, we also conducted experiments to analyze the performance of Openstate with multiple failures using Mininet simulation software, in terms of three metrics: communication overhead, computation overhead of controller and packet loss. The performance of Openstate is compared to Openflow to observe how much the former is better than the later. From the simulation results, we conclude that Openstate has faster recovery time than Openflow. On the average, recovery time is 70 msec and 85 msec for Openstate and Openflow, respectively. This indicates that Openstate should be improved for faster recovery time. © 2017 IEEE. IEEE Computer Society 2018 Article PeerReviewed https://www.scopus.com/inward/record.uri?eid=2-s2.0-85046082329&doi=10.1109%2fAICCSA.2017.32&partnerID=40&md5=fd81de8da2061aa0e484ac64ca8195d7 Zahid, M.S.M. and Isyaku, B. and Fadzil, F.A. (2018) Recovery of software defined network from multiple failures: Openstate vs openflow. Proceedings of IEEE/ACS International Conference on Computer Systems and Applications, AICCSA, 2017-O . pp. 1178-1183. http://eprints.utp.edu.my/21714/ |
institution |
Universiti Teknologi Petronas |
building |
UTP Resource Centre |
collection |
Institutional Repository |
continent |
Asia |
country |
Malaysia |
content_provider |
Universiti Teknologi Petronas |
content_source |
UTP Institutional Repository |
url_provider |
http://eprints.utp.edu.my/ |
description |
Software Defined Network (SDN) is an emerging network with clearer separation between control and data planes. Like non-SDN, SDN undergoes a recovery process upon occurrence of failures. The recovery process should take less than 50 msec to comply with service level agreement of Internet Service Providers (ISPs). Currently, it is possible for SDN to meet the requirement with Openstate standard or protocol. However, the results were based on single failures only. Multiple failures may also occur and unavoidable. In this research, formulae to estimate recovery times of Openflow and Openstate are derived and proposed. It is obvious from the formulae that Openstate recovery time is better or equivalent to Openflow. Thus, we also conducted experiments to analyze the performance of Openstate with multiple failures using Mininet simulation software, in terms of three metrics: communication overhead, computation overhead of controller and packet loss. The performance of Openstate is compared to Openflow to observe how much the former is better than the later. From the simulation results, we conclude that Openstate has faster recovery time than Openflow. On the average, recovery time is 70 msec and 85 msec for Openstate and Openflow, respectively. This indicates that Openstate should be improved for faster recovery time. © 2017 IEEE. |
format |
Article |
author |
Zahid, M.S.M. Isyaku, B. Fadzil, F.A. |
spellingShingle |
Zahid, M.S.M. Isyaku, B. Fadzil, F.A. Recovery of software defined network from multiple failures: Openstate vs openflow |
author_facet |
Zahid, M.S.M. Isyaku, B. Fadzil, F.A. |
author_sort |
Zahid, M.S.M. |
title |
Recovery of software defined network from multiple failures: Openstate vs openflow |
title_short |
Recovery of software defined network from multiple failures: Openstate vs openflow |
title_full |
Recovery of software defined network from multiple failures: Openstate vs openflow |
title_fullStr |
Recovery of software defined network from multiple failures: Openstate vs openflow |
title_full_unstemmed |
Recovery of software defined network from multiple failures: Openstate vs openflow |
title_sort |
recovery of software defined network from multiple failures: openstate vs openflow |
publisher |
IEEE Computer Society |
publishDate |
2018 |
url |
https://www.scopus.com/inward/record.uri?eid=2-s2.0-85046082329&doi=10.1109%2fAICCSA.2017.32&partnerID=40&md5=fd81de8da2061aa0e484ac64ca8195d7 http://eprints.utp.edu.my/21714/ |
_version_ |
1738656327826145280 |