The other week I attended the “Software Defined Networking 2013” conference in London. This is a UK-based event for the discussion of SDN, OpenFlow and Network Virtualisation Solutions from a strategic perspective. There were quite a few interesting perspective s I picked up at this conference. In particular, the conference for me reinforced the potential of SDN – but if you apply it to the wrong problem, you may not get the return you hope for!
Top of mind for me, then, coming out of this conference was a demo of “What SDN Can Do For You” from one of our competitors. At best, the phrase “using a sledge hammer to crack a nut” comes to mind.
The demo came from our friends in Palo Alto, who once (boldly but incorrectly!) predicted that “Cisco UCS would be dead a year after launch”. They gave a SDN-focused demo that, when I “peeled back the onion”, didn’t demonstrate a compelling SDN use case. Rather, it convinced me that if you have this particular problem as illustrated in their demo, you don’t need SDN: you need a new vendor!
Tags: ACI, application centric infrastructure, architectural approach, Cisco collaboration, Cisco Services, Cisco WebEx, jabber, Jabber Video, network virtualization, onePK, SDN, software defined network
Last week I was in London for the Gartner Data Center Conference. As always there was a wide range of interesting topics being discussed, all very useful. Working in Cisco Data Center Services, I am interested in many data center topics, however this year I was interested to hear perspectives on SDN, how the market is evolving, and how the attendees -- including many senior IT practitioners -- are considering SDN adoption.
London’s Big Ben at Night
From a Cisco perspective, we were showcasing the recently launched Application Centric Infrastructure (ACI), which generated a lot of interest. There is growing awareness among our customers that ACI could do for networks and applications what the Cisco UCS has done for the server market (with UCS server profiles in the latter proving a good analogy to help customers understand the potential of ACI).
So what were some of my key takeaways from the SDN discussion I heard here? And what were the questions that in my view are still not being discussed sufficiently across the industry?
Read More »
Tags: ACI, application centric infrastructure, Cisco Data Center, Cisco SDN Controller, Cisco Services, SDN, software defined networking
To read the first part of the Network Matters blog series that discusses how an architectural approach to mobility is essential for the Future of Mobility, click here. To read the second part of the series that focuses on how IT leaders can rely on a network to simplify the process of onboarding new mobile technology, click here. For the third part of this series that discusses how Service Providers can deepen their enterprise customer relationships by addressing pain points and meeting new enterprise mobility challenges, click here.
In the new mobile and cloud era, applications are evolving and changing the role of networking at a rapid pace.
In this final blog post of the Network Matters series, I’ll discuss how mobility is driving an application economy that is enabled by intelligent networks.
Read More »
Tags: application centric infrastructure, Cisco, cloud, future of mobility, mobility, unified communications, wireless
By now, given all the launch and blogging activity activity over the past week or so, I am sure your understanding of and interest in Application Centric Infrastructure (ACI) will have grown. Many of you will be asking “how do I get started as quickly as possible?”, and “how can I free up some time and resources to investigate?” You understand the “what” - now, as I blogged recently on SDN, it’s time to understand more about the “why” and take action on the “how”. How then do you get off that start line as quickly as possible?
Get Set To Go With ACI
As with many things in life, it helps if you get help from someone who has “been there” and “done that”. And that’s where Cisco Services comes in, as Scott Clark, the VP for our Data Center Services team, introduced last week. So let’s talk about why Cisco Services should be your partner in this application centric world, and what services can help you.
Read More »
Tags: ACI, application centric infrastructure, Application Economy, Cisco, Cisco Domain Ten, Cisco Nexus 9000, Cisco Services, data center, Insieme, SDN
We’ve been getting a lot of great questions about ACI since our launch as people try and better understand the value of an application-oriented approach. I got the following questions on my blog post about the Application Virtual Switch that probed on some of the thinking behind an application-aware architecture, and why now was the right time to release it (after all, John Chambers called it the most disruptive Cisco innovation in a decade!). Anyway, on to the Q&A:
I’d like to know more about the path that Cisco pursued to evolve towards an “application aware” architecture. This back-story (how Cisco arrived at this juncture) would be very helpful to industry analysts, customers and institutional investors. Here’s some of the key questions on my mind.
- What were the primary roadblocks that inhibited the adoption of this innovative approach in the past?
I would say that the Application Centric Infrastructure (ACI) was a combination of a Eureka! moment, that people just never thought of it before, and that it was also an insightful evolution from early SDN technology. So, it might be fair to say that SDN had to come along, and then we realized, here might be a better way to program the network (with an application-oriented model, rather than a network-centric model).
That might be another way of saying that the lack of SDN as a precursor to ACI was a roadblock. But I think of it as networks were just built on hardware that were optimized to pass packets and other very specific tasks. And the limitations of historical networking protocols and traditional network designs, coupled with very limited ways in which you could manage a network and tell it what to do, all served as roadblocks to implementing anything like ACI. So the roadblocks that had to be cleared included the ability to program switches through software interfaces, and to centrally manage the software applications or controllers to orchestrate the broader network, not an individual device. Those are some of the things SDN brought along.
Read More »
Tags: ACI, APIC, application centric infrastructure, Cisco ONE, nexus, onePK, OpenFlow, SDN, XNC Controller