Abstract

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.

Highlights

  • Software Defined Networking (SDN), which segregates the Control/Management Plane (C/M-Plane) from the forwarding or Data Plane (D-Plane) [1], has proven to be useful in creating innovative and flexible solutions for managing network resources

  • Soon after the release of OpenFlow (OF) [5], which was the enabler of SDN, the community started to raise their concerns about network failure recovery

  • Initial designs were implemented for single-link failures at the D-Plane; wherein once the connection between two network nodes is interrupted, the end-to-end path is recalculated so that the transmission can resume; this process is called fast restoration [6], which is the most straightforward mechanism to recover from a failure in SDN

Read more

Summary

Introduction

Software Defined Networking (SDN), which segregates the Control/Management Plane (C/M-Plane) from the forwarding or Data Plane (D-Plane) [1], has proven to be useful in creating innovative and flexible solutions for managing network resources. There are two major issues with SDN-based solutions, the first of which being scalability [2], and the second one being reliability of both the C/M- and D-Plane. In terms of reliability at the C/M-Plane, the SDN controller becomes a single-point-failure [3]. Initial designs were implemented for single-link failures at the D-Plane; wherein once the connection between two network nodes is interrupted, the end-to-end path is recalculated so that the transmission can resume; this process is called fast restoration [6], which is the most straightforward mechanism to recover from a failure in SDN. When the device is operational but not connected to the controller, the SDN-enabled network device, by default, does not have enough knowledge to recover from path failure. As a consequence, when the controller fails, the options are not as straightforward

Results
Discussion
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.