Multiple controller management in software defined networking 2014 IEEE Symposium on Computer Applications and Communications (SCAC) Ying Li, Ligang Dong, Jianping Qu, Huafei Zhang School of Information & Electronic Engineering Zhejiang Gongshang University Hangzhou, China 1

Outline Introduction Proposed Scheme Mathematical Modeling Numerical Experiment Conclusion References 2

Introduction Controller dictates the overall network behavior Relying on a single controller for the entire network might not be feasible – large diameter – controller fails to work Contribution – multiple controllers manage the same network device 3

Proposed Scheme Architecture 4

Algorithm – Step1: The controller will choose network devices to deploy the virtual network – Step2: Network devices initiate connections to controller – Step3: The controller chooses to accept the connection initiated by network devices – Step4: Controller begin to get the network device’s information – Step5: If there are un-deployed virtual networks, then the controller will send deployment request messages to them. 5

– Step6: If the number of virtual networks that the network device doesn’t join in deploying is greater than a threshold, then the connection is tore down – Step7: When a connection is broken, the network device will re-initiate a connection to the controller. Then goto step3 Different controllers independently execute the above steps repeatedly If a network device often does not join in deploying of virtual networks – adaptive connection 6

Mathematical Modeling This model is constructed to disclose how to improve the performance of this scheme Has two parts: – Join ratio model – Connection ratio model 7

Join ratio model – Average number of virtual networks one network device joins: m – Total number of virtual networks deployed in the network managed by one controller: M – The join ratio of network device is: 8

Connection ratio model – Average number of network devices connected with one controller: n a – Total number of network devices managed by one controller: n – The connection ratio of network device is: 9

Numerical experiment Disclose the effects on the join ratio and the connection ratio of network device Threshold number of virtual networks that the network device doesn’t join before the connection is torn down: r Average time interval of two adjacent virtual networks being deployed: T Average time interval of an connection from teardown to re-setup: t 1 10

Let’s set r =10, T = 0.6s, t 1 = 6 11

Let’s set m=20, T=0.6s, t 1 =6s 12

Conclusion A larger threshold and smaller time interval can make the network devices used more effectively. It resolves the problem that different controllers belonging to different vendors cannot be managed centrally. 13

Reference A. Tootoonchian, and Y. Ganjali, Hyperflow: A Distributed Control Plane for OpenFlow, in: Proceedings of the 2010 INM conference, 2010, pp. 3–3. C. A. B. Macapuna, C. E. Rothenberg, and F. Magalh, In-Packet Bloom Filter Based Data Center Networking with Distributed OpenFlow Controllers, in: Proceedings of IEEE International Workshop on Management of Emerging Networks and Services, 2010, pp