Abstract
In distributed software-defined networking, switches can be assigned to a single master controller and one or more slave controllers, for resilience. However, only master controllers are allowed to install flow rules. Also, controllers install flow rules just at switches under their domain. This means that a particular flow may trigger the flow setup procedure multiple times, if the traversed switches are under different controller domains. This results into extra network load and instability. Here, in this article, the controller placement is planned having into account flow setup efficiency and possible future migrations from master to slave controllers. Results show that such flow setup and migration awareness results into long-term quality solutions for controller placement.
Sign-in/Register to access full text options 
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 callDisclaimer: 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.
