The true OpenFlow zealots would love you to believe that you can drop whatever you’ve been doing before and replace it with a clean-slate solution using dumbest (and cheapest) possible switches and OpenFlow controllers.
In real world, your shiny new network has to communicate with the outside world … or you could take the approach most controller vendors did, decide to pretend STP is irrelevant, and ask people to configure static LAGs because you’re also not supporting LACP.
Read more ...Thanks for reading my news about Implementing Control-Plane Protocols with OpenFlow 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?
- VMware buys Nicira: a Hypervisor Vendor Woke Up
- The future of SDN
- Does CPU-based forwarding performance matter for SDN?
- Legacy Protocols in OpenFlow-Based Networks
- NETCONF = Expect on steroids
- Why is RESTful API better than SNMP?
- OpenStack/Quantum SDN-based virtual networks with Floodlight
- We need both OpenFlow and NETCONF