Skip to main content

Advertisement

Springer Nature Link
Log in

Performance Analysis of SDN/OpenFlow Controllers: POX Versus Floodlight

  • Published:
Wireless Personal Communications Aims and scope Submit manuscript

Abstract

Software-Defined Networking (SDN) is an emerging network architecture that is adaptable, dynamic, cost-effective, and manageable. The SDN architecture is a form of network virtualization where the network controlling functions and forwarding functions are decoupled. A setup and configuration task of a control plane to work as an SDN controller is explained in this paper. This paper includes a brief survey of different SDN based OpenFlow-enabled controllers available in various programmable languages. This paper mainly focuses on two OpenFlow-enabled controllers, namely, POX—a Python-based controller and Floodlight—a Java-based controller. A performance comparison of both controllers is tested over different network topologies by analyzing network throughput and round-trip delay using an efficient network simulator called Mininet. A single, linear, tree and custom (user-defined) topologies are designed in Mininet by enabling external controllers. It is obtained that, a percentage improvement in round-trip time for Floodlight over POX is 11.5, 13.9, 19.6 and 14.4% for single, linear, tree and custom topology respectively. Similarly, a percentage improvement in throughput for Floodlight over POX is 5.4, 8.9, 3.8 and 4.9% for single, linear, tree and custom topology respectively.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Subscribe and save

Springer+ Basic
$34.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or eBook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1
Fig. 2
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9
Fig. 10
Fig. 11
Fig. 12
Fig. 13
Fig. 14
Fig. 15
Fig. 16
Fig. 17
Fig. 18
Fig. 19
Fig. 20
Fig. 21
Fig. 22
Fig. 23

Similar content being viewed by others

References

  1. Hakiri, A., Gokhale, A., Berthou, P., & Gayraud, T. (2014). Software-defined networking: Challenges and research opportunities for future internet. Computer Networks, 75(A), 453–471. doi:10.1016/j.comnet.2014.10.015.

    Article  Google Scholar 

  2. Turner, J., & McKeown, N. (2007). Can Overlay hosting services make IP ossification irrelevant? In Proceedings PRESTO: Workshop on programmable routers for the extensible service of tomorrow, Princeton, NJ.

  3. Astuto, B. N., Mendonca, M., Nguyen, X. N., Obraczka, K., & Turletti, T. (2014). A survey of software-defined networking: Past, present, and future of programmable networks. IEEE Communications Surveys and Tutorials, 16(3), 1617–1634.

    Article  Google Scholar 

  4. Software-Defined Networking (SDN) Definition—Open networking foundation, open networking foundation (online). https://www.opennetworking.org/sdn-resources/sdndefinition.

  5. Kreutz, D., Ramos, F. M. V., Verissimo, P., Rothenberg, C. E., Azodolmolky, S., & Uhlig, S. (2015). Software-defined networking: A comprehensive survey. Proceedings of the IEEE, 103(1), 14–76.

    Article  Google Scholar 

  6. SDN Resources, SDxCentral, (2015). (online) https://www.sdxcentral.com/resources/sdn/.

  7. Lara, A., Kolasani, A., & Ramamurthy, B. (2014). Network innovation using openflow: A survey. IEEE Communication Surveys and Tutorials, 16(1), 493–512.

    Article  Google Scholar 

  8. McKeown, N., Anderson, T., Balakrishnan, H., Parulkar, G., Peterson, L., Rexford, J., et al. (2008). OpenFlow: Enabling innovation in campus networks. ACM SIGCOMM Computer Communication Review, 38(2), 69–74.

    Article  Google Scholar 

  9. Doria, A., Salim, J. H., Haas, R., Khosravi, H., Wang, W., Dong, L., Gopal, R., & Halpern, J. (2010). Forwarding and control element separation (ForCES) protocol specification. Internet Engineering Task Force (online). Available: http://www.ietf.org/rfc/rfc5810.txt.

  10. Pfaff, B., & Davie, B. (2013). The Open vSwitch database management protocol, RFC 7047 (Informational), internet engineering task force (online). Available: http://www.ietf.org/rfc/rfc7047.txt.

  11. Song, H. (2013). Protocol-oblivious forwarding: Unleash the power of SDN through a future-proof forwarding plane. In Proceedings of the second ACM SIGCOMM workshop on hot topics in software defined networking. New York, NY, USA: ACM, pp. 127–132.

  12. Smith, M., Dvorkin, M., Laribi, Y., Pandey, V., Garg, P., & Weidenbacher, N. (2014). OpFlex control protocol, internet draft, internet engineering task force (online). http://tools.ietf.org/html/draft-smith-opflex-00.

  13. Bianchi, G., Bonola, M., Capone, A., & Cascone, C. (2014). OpenState: Programming platform-independent stateful OpenFlow applications inside the switch. SIGCOMM Computer Communication Review, 44(2), 44–51.

    Article  Google Scholar 

  14. OpenFlow Current Deployment, OpenFlow. (2011). (online). http://archive.openflow.org/wp/current-deployments/.

  15. Richardson, L., & Ruby, S. (2008). RESTful web services. Sebastopol: O’Reilly Media, Inc.

    Google Scholar 

  16. Foster, N., Harrison, R., Freedman, M. J., Monsanto, C., Rexford, J., Story, A., & Walker, D. (2011). Frenetic: A network programming language. SIGPLAN Notices, 46(9), 279–291.

    Article  MATH  Google Scholar 

  17. Voellmy, A., & Hudak, P. (2011). Nettle: Taking the sting out of programming network routers. In Proceedings of the 13th international conference on practical aspects of declarative languages, ser. PADL’11. Berlin, Heidelberg: Springer, pp. 235–249.

  18. Monsanto, C., Foster, N., Harrison, R., & Walker, D. (2012). A compiler and run-time system for network programming languages. SIGPLAN Notices, 47(1), 217–230.

    Article  Google Scholar 

  19. Voellmy, A., Kim, H., & Feamster, N. (2012). Procera: A language for highlevel reactive network control. In Proceedings of the first workshop on hot topics in software defined networks, ser. HotSDN’12. New York, NY, USA: ACM, pp. 43–48.

  20. Monsanto, C., Reich, J., Foster, N., Rexford, J., & Walker, D. (2013). Composing software-defined networks. In Proceedings of the 10th USENIX conference on Networked Systems Design and Implementation, ser. nsdi’13. Berkeley, CA, USA: USENIX Association, pp. 1–14.

  21. Anderson, C. J., Foster, N., Guha, A., Jeannin, J.-B., Kozen, D., Schlesinger, C., et al. (2014). NetKAT: Semantic foundations for networks. SIGPLAN Notices, 49(1), 113–126.

    MATH  Google Scholar 

  22. OpenFlow Switch Specification, Version 1.0.0 (Wire Protocol 0x01), December 2009 (online). http://www.openflow.org/documents/openflow-spec-v1.0.0.pdf.

  23. OpenFlow Switch Specification, Version 1.4.0 (Wire Protocol 0x05), October 2013 (online). https://www.opennetworking.org/images/stories/downloads/sdn-resources/onf-specifications/openflow/openflow-spec-v1.4.0.pdf.

  24. Home—Open Networking Foundation, 2013 (online). https://www.opennetworking.org/index.php?lang=en.

  25. Bholebawa, I. Z., Jha, R. K., & Dalal, U. D. (2016). Performance analysis of proposed openflow-based network architecture using mininet. Wireless Personal Communication, 86(2), 943–958. doi:10.1007/s11277-015-2963-4.

    Article  Google Scholar 

  26. Liu, Y., Li, Y., Wang, Y., & Yuan, J. (2015). Optimal scheduling for multi-flow update in software-defined networks. Journal of Network and Computer Applications, 54(C), 11–19.

    Article  Google Scholar 

  27. Metter, C., Seufert, M., Wamser, F., Zinner T., & Tran-Gia, P. (2017). Analytic model for SDN controller traffic and switch table occupancy. In IEEE 12th international conference on network and service management (CNSM), pp. 109–117. doi: 10.1109/CNSM.2016.7818406.

  28. Gude, N., Koponen, T., Pettit, J., Pfaff, B., Casado, M., McKeown, N., & Shenker, S. (2008). NOX: Towards an operating system for networks. ACM SIGCOMM Computer Communication Review, 38(3), 105–110.

    Article  Google Scholar 

  29. McCauley, M. (2009). POX (online). http://www.noxrepo.org/.

  30. Floodlight is a Java-based OpenFlow controller. (2012). (online). http://floodlight.openflowhub.org/.

  31. Saikia, D. (2013). MuL OpenFlow controller (online). http://sourceforge.net/projects/mul/.

  32. Takamiya, Y., & Karanatsios, N. (2012). Trema OpenFlow controller framework (online). https://github.com/trema/trema.

  33. Erickson, D. (2013). The Beacon OpenFlow controller. In Proceedings of the second ACM SIGCOMM workshop on Hot topics in software defined networking, ser. HotSDN’13. New York, NY, USA: ACM, pp. 13–18.

  34. Cai, Z., Cox, A. L. & Ng, T. S. E. (2011). Maestro: A system for scalable openflow control, Rice University, Tech. Rep.

  35. Nippon Telegraph and Telephone Corporation. (2012). Ryu network operating system (online). http://osrg.github.com/ryu/.

  36. Naning, H. S., Munadi R., & Effendy, M. Z. (2017). SDN controller placement design: For large scale production network. In IEEE Asia Pacific conference on wireless and mobile (APWiMob), pp. 74–79. doi:10.1109/APWiMob.2016.7811452.

  37. Lantz, B., Heller B., & McKeown, N. (2010). A network in a laptop: Rapid prototyping for software-defined networks. In Hotnets-IX proceedings of the 9th ACM SIGCOMM workshop on hot topics in networks, New York, NY, USA.

  38. Team, T. M. (2012). Mininet: An instant virtual network on your laptop (or Other PC) (online). http://www.mininet.org.

  39. McCauley, M. (2009). About POX | NOXRepo (online). http://www.noxrepo.org/pox/about-pox/.

  40. McCauley, M. (2013). Noxrepo/pox. Github (online). https://github.com/noxrepo/pox.

  41. McCauley, M. (2014). POX Wiki—Open Netwroking Lab—confluence (online). https://openflow.stanford.edu/display/ONL/POX+Wiki.

  42. Big Switch Networks, Inc. | The Leader in Open Software Defined Networking. (2015). Big switch networks (online). http://www.bigswitch.com/.

  43. Floodlight OpenFlow Controller—Project Floodlight. (2015). Big switch network (online). http://www.projectfloodlight.org/floodlight/.

  44. Architecture—Floodlight Controller—Project Floodlight. (2012). Big Switch Network (online). https://floodlight.atlassian.net/wiki/display/floodlightcontroller/Architecture.

  45. Jha, R. K., Kharga, P., Bholebawa, I. Z., Satyarthi, S., Gupta, A., & Kumari, S. (2014). OpenFlow technology: A journey of simulation tools. International Journal of Computer Network and Information Security (IJCNIS), 6(11), 49–55.

    Article  Google Scholar 

  46. Blial, O., Mamoun, M. B., & Benaini, R. (2016). An overview on SDN architectures with multiple controllers. Journal of Computer Networks and Communications. doi:10.1155/2016/9396525.

    Google Scholar 

  47. Ma, Y. W., Chen, J. L., Tsai, Y. H., Cheng, K. H., & Hung, W. C. (2016). Load-balancing multiple controllers mechanism for software-defined networking. Wireless Personal Communications. doi:10.1007/s11277-016-3790-y.

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Department of Electronics and Communication Engineering, S. V. National Institute of Technology, Surat, Gujarat, 395007, India

    Idris Z. Bholebawa & Upena D. Dalal

Authors
  1. Idris Z. Bholebawa
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Upena D. Dalal
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Idris Z. Bholebawa.

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Bholebawa, I.Z., Dalal, U.D. Performance Analysis of SDN/OpenFlow Controllers: POX Versus Floodlight. Wireless Pers Commun 98, 1679–1699 (2018). https://doi.org/10.1007/s11277-017-4939-z

Download citation

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s11277-017-4939-z

Keywords

Search

Navigation

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy