TY - JOUR
T1 - On Designing a Resilient SDN C/M-Plane for Multi-Controller Failure in Disaster Situations
AU - Guillen, Luis
AU - Takahira, Hiroyuki
AU - Izumi, Satoru
AU - Abe, Toru
AU - Suganuma, Takuo
N1 - Publisher Copyright:
© 2013 IEEE.
PY - 2020
Y1 - 2020
N2 - Network survivability is the ability to maintain service continuity in the presence of failures. This ability might be critical in times where large-scale failures occur, as in the case of disasters. In the past years, Software Defined Networking (SDN) has shown a great potential to allow network programmability by segregating the Control/Management Plane (C/M-Plane) from the forwarding or Data Plane (D-Plane). The controller, a centralized entity, has an overview of the entire network under its domain, which allows it to make informed routing decisions. However, the controller becomes a single-point-of-failure as network devices will have limited knowledge if not connected to a controller. Moreover, in disaster situations, if the affected area is considerably large, there is a high probability that more than a single controller will fail in a short period. Various studies, either following a protection or restoration techniques, have been proposed to address resiliency on SDN, but most of them only consider link or device failure; however, the failure of various controllers due to a large-scale disaster is less explored. In this paper, we consider multi-controller failure and propose a mechanism to reduce the non-operational network devices in disaster situations. Preliminary results show that, by applying the proposed approach, it is possible to achieve substantial improvements in network survivability, with considerably less cost of implementation than existing methods. In particular, using simulation, we achieved a 20% decrease of non-operational devices at the C/M-Plane; and an increase of 30% of success rate at the D-Plane, even if half of the controllers in the topology failed.
AB - Network survivability is the ability to maintain service continuity in the presence of failures. This ability might be critical in times where large-scale failures occur, as in the case of disasters. In the past years, Software Defined Networking (SDN) has shown a great potential to allow network programmability by segregating the Control/Management Plane (C/M-Plane) from the forwarding or Data Plane (D-Plane). The controller, a centralized entity, has an overview of the entire network under its domain, which allows it to make informed routing decisions. However, the controller becomes a single-point-of-failure as network devices will have limited knowledge if not connected to a controller. Moreover, in disaster situations, if the affected area is considerably large, there is a high probability that more than a single controller will fail in a short period. Various studies, either following a protection or restoration techniques, have been proposed to address resiliency on SDN, but most of them only consider link or device failure; however, the failure of various controllers due to a large-scale disaster is less explored. In this paper, we consider multi-controller failure and propose a mechanism to reduce the non-operational network devices in disaster situations. Preliminary results show that, by applying the proposed approach, it is possible to achieve substantial improvements in network survivability, with considerably less cost of implementation than existing methods. In particular, using simulation, we achieved a 20% decrease of non-operational devices at the C/M-Plane; and an increase of 30% of success rate at the D-Plane, even if half of the controllers in the topology failed.
KW - Disaster resilient networks
KW - SDN
KW - multi-controller failure
KW - network management
UR - http://www.scopus.com/inward/record.url?scp=85090036399&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=85090036399&partnerID=8YFLogxK
U2 - 10.1109/ACCESS.2020.3013323
DO - 10.1109/ACCESS.2020.3013323
M3 - Article
AN - SCOPUS:85090036399
SN - 2169-3536
VL - 8
SP - 141719
EP - 141732
JO - IEEE Access
JF - IEEE Access
M1 - 9154756
ER -