A few days ago I had the privilege of being part of an VXLAN-related tweetfest with @bradhedlund, @scott_lowe, @cloudtoad, @JuanLage, @trumanboyes (and probably a few others) and decided to write a blog post explaining the problems VXLAN faces due to lack of control plane, how it uses IP multicast to solve that shortcoming, and how OpenFlow could be used in an alternate architecture to solve those same problems.
Read more ...Thanks for reading my news about VXLAN, IP multicast, OpenFlow and control planes at my blog Bros Droid if you want too share this article, please put the resource, and if you think this article is very usefully dont forget to bookmark this site with CTRL + D on your keyboard to web browser.
More Articles :
OpenFlow and Ipsilon: Nothing New Under the Sun- IRS – just what the SDN Goldilocks is looking for?
- Why is OpenFlow focused on L2-4?
- SDN Controller northbound API is the crucial missing piece
- OpenFlow/SDN: Hype, Useful Tool or Panacea?
- OpenStack/Quantum SDN-based virtual networks with Floodlight
- VMware buys Nicira: a Hypervisor Vendor Woke Up
- Midokura’s MidoNet: a Layer 2-4 virtual network solution
- SDN, Career Choices and Magic Graphs
- Why is RESTful API better than SNMP?