Network Management is dull. No excuses. Monitoring and interacting with the devices that move data from one location to another is a thankless undertaking that most of us building networks leave to an afterthought. Part of that is the complexity associated with managing networks. There are at least a dozen common methods for interacting with devices in the network including SNMP, CLI, AAA, Syslog, Netflow, and fancy XML/HTTP interfaces. So much variety breeds complexity so we tend to set our goals pretty low for interactivity with the network.
What if we had one common mechanism for interacting with the network? Different devices running different software would all speak a common language to the applications managing and monitoring them. Now what if that language was something the programmers writing those applications understood implicitly like an API library they could compile directly into their program? That would make interacting with the network as simple as making a procedure call within the application. That’s exactly what onePK – or the “one Platform Kit” – accomplishes.
Read More »
Tags: APIs, APM, application management, Application Performance Management, Application Visibility and Control, applications, AVC, Cisco APIs, deep packet inspection, Dynamic QoS, One Platform Kit, onePK, QoS, router, SDN, secret packets, software defined networking, video quality
By Uwe Lambrette, Director, Cisco Internet Business Solutions Group
Amsterdam may be the one place on earth where it rains more than it does in London. So, it was no surprise that I encountered stormy weather on my flight to Broadband World Forum (BBWF) 2012. As things turned out, the conference theme and the weather were clearly aligned, since the BBWF is fiercely embracing evolution to cloud. Here are some core themes that emerged as I shared some of Cisco IBSG’s findings at the conference:
Cloud 2.0: Most service providers (SPs) have already launched an initial cloud offering and are now beginning to measure scaling and growth. The initial offering is often a stand-alone cloud solution, typically focused on infrastructure as a service (IaaS). Once their original implementation goes live, SPs often need to focus on the following improvements: Read More »
Tags: BBWF, broadband, Broadband World Forum, Cisco, cloud, cloud 2.0, cloud economics, cloud go-to-market strategy, cloud service brokers, Hybrid Cloud, IaaS, IBSG, infrastructure as a service, network and cloud integration, SaaS, SDN, SDNs, Service Provider, software as a service, software defined networking
For those of you wondering about the impact to Cisco of Software Defined Networking and the combined SDN strategy of VMware and Nicira, I point you to a very rational and well-articulated article by Mike Fratto of Network Computing, that basically says Cisco doesn’t have much to worry about. (Enterprise Strategy Group had already said something similar, by the way).
Specifically, Fratto says:
The lack of programmability in existing networking hardware is certainly a problem, but VMware’s acquisition of Nicira does not mean that Cisco and its ilk will be marginalized… It does mean the role and management of the physical network is changing, and I think Cisco is further ahead than most of its competitors in creating a vision for the next phase of networking.
I couldn’t agree more. Since Cisco live! when we announced our Cisco ONE strategy for network programmability as well as the advances in our Nexus 1000V portfolio for virtual network overlays, I have been posting on many of the same points.
My take here was that the VMware-Nicira acquisition did not portend a strategic break with Cisco, and while there are some obvious overlaps in our product lines, there are still a number of areas of collaboration, cooperation and interoperability. The virtual network infrastructure is just one piece of a larger software stack and the differentiation will likely be decided in the orchestration, management and applications built on top of the newly programmable infrastructures sometime down the road. Read More »
Tags: Cisco ONE, Cisco Open Network Environment, FabricPath, LISP, Nexus 1000v, Nexus 5000, Nexus 7000, Nicira, OpenStack, OTV, SDN, software defined networking, virtual network overlays, VMware, vPath, VXLAN
So, some closing thoughts on ONS. I know its a bit late, but hey, when you’re out of the office for a few days, things pile up a bit–overall, I think the ONF folks did a fine job with the event.
As I look back at ONS, I am reminded of one of my favorite IT quotes, courtesy of Bill Gates:
We always overestimate the change that will occur in the next two years and underestimate the change that will occur in the next ten
Long-term, I think SDN or the concepts it represents will certainly have a hand in shaping how we do networking a decade for now–how we get there and what that destination really looks like is a bit less certain.
First, I think we are early enough in the game that the technology is far from unsettled:
- Most folks are shipping 1.0 code, either literally or figuratively, and I am betting there are unseen technologies in the wings that will help shape things and I am sure folks will find interesting ways to also repurpose existing technology
- We can pretty much expect some wave of M&A to help shape the vendor and technology landscape
- As I have noted before, there is a lot of dogma about what SDN is right now that is not helpful, but I also believe it will eventually fall by the wayside
Eventually the market will sort this stuff out, and a handful of organizations are in a position to drive their own solutions, but for regular folks, I think there is enough near-term uncertainty here that it will give people pause–both in terms of customer adoption as well as ecosystem investment.
Read More »
Tags: Open Networking Summit, OpenFlow, SDN, software defined networking
So, the theme for the day was “Less Unicorns, More Ponies”
I have to admit, I could not attend some of the afternoon sessions–there is a define downside to going to a conference with your boss.
Anyway, we heard from a number of folks (a lot of SPs and academics) that are doing the hard work of trying to do useful real-world things with OpenFlow and SDN. There were a fair number of successes but also a good number of struggles. Kudos to the ONS folks for trying to present a balanced view as opposed to hosting a two-day OpenFlow pep rally. So, sadly, the shine is starting to come off the SDN unicorn, but in the long run, this what needs to happen for the long term health of SDN.
Hands down, my favorite session was Igor Gashinsky from Yahoo! for a number of reasons: 1) it was darn entertaining, 2) I think hyperscale data centers present some the most interesting and demanding environments right now, 3) the use case was interesting, and 4) frankly, it allows me to make a point.
It seems that much of the conversation around SDN centers on the southbound conversation–the ability to program the hardware. While that is certainly useful and interesting, at least as interesting and important is the northbound conversation–the ability to extract interesting information from the infrastructure and make it available to the controllers, applications, tools, etc. In Igor’s case, he talked about being able to extract info directly out of the switching hardware to facilitate troubleshooting–not an inconsequential task when you have 20K servers and 400K VMs. Its a good use case but I also think its just scratching at the surface.
I believe its an interesting topic and one of the things that David Ward will dig into a bit further during his session this afternoon.
Tags: hyperscale, OpenFlow, SDN, software defined networking