Omar Sultan writes on the Cisco Data & Cloud blog ….. We continue to strongly support ONF and its efforts related to SDN and our support has and will continue to been demonstrated in tangible ways. One of the elements of the Cisco ONE announcement is onePK, which is an enabling technology and one of the [...]
In this blog post, Dan Hershey (from Big Switch) gets some toys from the lab and shows how to build an SDN Controller application that uses OpenFlow. This application uses a Pronto switch as an “active patch panel” to connect two Cisco switches together. Things to think about: You can use OpenFlow to do things that [...]
There is an old saying “A man with his eyes fixed on Heaven doesn’t see where he is going”. It’s an almost perfect description of how the major vendors are bringing Software Defined Networking to the market.
The consistent message from all the vendors and especially the Cisco, Juniper and Brocade is that there are “no use cases for SDN”. In the last three months, this has been a constantly repeated statement both publicly and privately. This beggars belief that vendors can’t see immediate needs that deliver long term gains.
I suspect that the root of this problem is the big companies want to solve big problems. And by solving big problems they figure that they can make big revenue. Alright, I get that. It’s understandable that large organisations need a constant revenue stream to feed the insatiable maws of their shareholders. However, the vendors re also missing the most real and immediate problem of networking today. Simply, Networking is too hard.
Vendors haven’t developed tools that keep the complexity of networking under control. Complexity can be reduced to this: “I don’t have big problems, I have lots of small problems.” You can have debates about addressing complexity and how to attack it, but it nearly always boils down to this: start small.
Omar Baldonado talks about the value of openness for SDN & OpenFlow My takeaway from that panel and the other speakers is that we’ve arrived here at this point in the industry because of the openness of software-defined networking. Many of the components of SDN already existed as the audience pointed out, but it is [...]
SDN/OpenFlow is about Network Management, at least, in part. But the rich tools for software control dont’ exist. I also think don’t think that todays management _platforms_ (such as Tivoli, OpenView and BMC) are suitable for network orchestration in the future.
Intel talks about the their Fulcrum silicon (FM6000) fully supporting OpenFlow. If one of the bigger merchant silicon vendors is shipping OpenFlow ready silicon, then I would expect new products to arrive in the next few months. I believe Intel is demoing this at Interop. We’ve also contributed our Barcelona 10GbE TOR switch reference platform [...]
Brad Casemore makes that case that HP is not telling us enough about it’s OpenFlow technology. HP has been a major contributor to several initiatives, including QoS code for OpenFlow v1.1 and the first vendor to offer OpenFlow support on it’s network switches. Yet, HP is not necessarily getting the recognition it deserves for these [...]
Responding to Omar’s wrap on the ONS
In this blog post, Calle Moberg (from Tail-F Systems who makes NETCONF software) highlights that the ONF has embraced NETCONF as mandatory for configuration of OpenFlow enabled devices. I didn’t know this was coming: [...] OF-CONFIG1.0 requires that devices supporting OF-CONFIG 1.0 MUST implement NETCONF protocol as the transport. This in turn implies as specified [...]
Internets of Interest is a conceit of mine where I collect useful, relevant or just fun places on the Internet and a bit commentary about what I’ve found interesting about them. With the Open Network Summit 2012 happening last week, there was an avalanche of hype from the mainstream press. I’ve attempted to pick something off [...]