• 06/02/2014
    8:00 AM
    Bob Laliberte
  • Bob Laliberte
  • Commentary
  • Connect Directly
  • Rating: 
    0 votes
    Vote up!
    Vote down!

Cisco ACI Making Progress

Since it launched last fall, Cisco's Application Centric Infrastructure has attracted a number of early adopters and a growing partner ecosystem, but Cisco still has a lot of work ahead to accelerate ACI adoption.

As Cisco continues its efforts to transform itself into the No. 1 IT company in the world, its Application Centric Infrastructure (ACI) initiative will be a critical step that many are closely following. Cisco has admitted it was late to the SDN game and it wasn’t until last fall that it fully launched ACI, which was based on technology from its Insieme spin-in, namely the Nexus 9000 and the Application Policy Infrastructure Controller (APIC).

When ACI was unveiled back in November, many had to hear the story a few times before fully understanding the approach. If I recall, it was the same for many when they first heard about UCS. ACI is a comprehensive approach that aligns with Cisco’s desire to provide a comprehensive IT platform to transform a customer’s computing environment, and it ensures the infrastructure is focused on the application.

Ultimately, ACI will tie together physical and virtual compute, network, and storage by leveraging centralized policies and orchestration.

Here is how ACI is shaping up:

  • The Nexus 9000 family has been available since December. The Cisco Application-centric Virtual Switch (AVS), which is an APIC-enabled Nexus 1000V virtual switch, also is available. Existing ASR 9000 and Nexus 7000 can be leveraged for datacenter interconnects in an ACI environment.
  • The APIC is going through beta testing and there is a simulator that can be deployed. APIC should be generally available this summer. Cisco is also releasing an APIC enterprise module this summer to tie application policy model into the access layer and WAN. This will enable APIC to leverage existing Cisco resources, and will be available for free to all SMARTnet customers.
  • It is widely understood that SDN will require an ecosystem of partners to deliver full functionality; Cisco’s ACI is no different. Currently, the Cisco ACI ecosystem includes A10 Networks, BMC, Canonical, Catbird, CA Technologies, CF Engine, Citrix, Cloudera, CloudStack, EMC, Embrane, Emulex, F5 Networks, IBM, MapR, Microsoft, NetApp, NetQoS, NetScout, Niksun, OpenStack, Opscode/Chef, Panduit, Python, Puppet Labs, Radware, Red Hat, SAP, Sourcefire (now owned by Cisco), Splunk, Symantec, VCE, and VMware.

According to Cisco, the ACI story is beginning to resonate: It already has 175 Nexus 9000 customers and more than 50 organizations testing APIC in one way or another. Note: APIC is not generally available yet; these are all beta or simulator customers. Both FlexPod and vBlock integrated compute platforms (ICPs) have committed to leveraging ACI as part of the platform. These initial numbers are impressive given the short time frame since launching, but given Cisco’s total installed market, it's barely scratching the surface.

What else does Cisco need to do to accelerate ACI adoption?

1. Validate the ACI technology and amplify the message. Tell the ACI story early and often. It will be imperative to elevate the ACI message and ensure organizations understand the comprehensive ACI story that covers physical and virtual and will encompass compute, network, and eventually storage.  

2. Work diligently with existing customers. Initial conversations indicated that existing customers with big investments in the prior Nexus family were not thrilled with the ACI approach. Cisco needs to show how they can protect their investments. You can bet competitors like Arista, Brocade, Dell, Extreme, HP, and Juniper all see this as an opportunity and are aggressively pursuing these customers.

3. Continue to expand and validate the ACI ecosystem. Cisco needs to continue to develop this ecosystem to provide as wide as possible choice of solutions. This is really about demonstrating to customers that Cisco is serious about delivering solutions to its customers and it’s not just a Barney-type ecosystem (Barney is the big purple dinosaur in the children's TV show that sings, “I love you, you love me”). The more Cisco can do to validate these multi-vendor solutions, the better.

4. Focus on security. Given the fact that Target just set the precedent that security is now a CEO problem and not just a CIO issue, you can expect there will be more attention paid to this area. By focusing on security with ACI, Cisco could accelerate adoption rates.


Surely, not yet another Press Release?
Although, even at this late stage I'd be willing to accept Cisco's internal use of ACI in production as valid progress, providing they could demonstrate it in something other than PowerPoint or on a Whiteboard.
More Security, please

The promise of all things SDN, given the current state of the world, should focus on security.The easiest way to get something to take off in the current enterprise climate is a promise of keeping a company (like Target) out of the news and off the Hill. Products and architectures like ACI should be able to have a compelling security story...lets have it!

Re: More Security, please

EricP, thanks for your thoughts! More and more I am hearing security cited as a major reason for SDN. VMware is certainly pushing the security message hard, but it seems very conceptual and a little hard to understand, IMHO. Would love to hear other views on that and what specific questions folks have.


Re: More Security, please

On the SDN and seurity front: We're actually going to have Chris Hoff here for a live radio interview on June 13 at 1:00 EDT to talk about the current state of network security and how SDN and automation factor in. Chris is currently the VP of planning and strategy at Juniper, but before that he worked at Cisco, and he is a highly respected security architect.

How about a hardware independent story for ACI

Bob - Nice article! I would think 'not requiring' the purchase of a Nexus 9000 is another way to improve the success of ACI.  It would make more sense if ACI worked with other non-Cisco hardware (as well) using standards-based southbound API (like OpenFlow) and at the same time provides more functionality with Cisco-specific hardware.

Re: How about a hardware independent story for ACI

The standard Cisco response appears to be you can run the Nexus 9000 in non-ACI mode (whatever that means), though however at the same time functionality is being extended to legacy Nexus gear, so perhaps you can get away with not having to buy the Nexus 9K gear, not sure if they've said that the APIC will support OpenFlow, but if it does theres the other bonus!

Just to add to the confusion, don't forget you've also got the Cisco ONE controller and the OpenDaylight-based XNC controller, virtual overlays are becoming more attractive by the day.

Are we moving past the era of tech giants?

As I read this article, the idea that Cisco is holding out hope to become the #1 tech giant stood out to me.  It probably would make the topic of an excellent debate.

I can't help but notice the painful decline that Microsoft has been going through as it tries to defend its empire on way too many fronts. It seems as though the new normal is the prevalance of disruptive technologies that constantly challenge the status quo.  

Re: Are we moving past the era of tech giants?

Abe, that's an interesting point. I'm not sure if we are moving beyond tech giants, or the nature of the companies is simply changing. Google, Amazon, and Facebook are geting awfully big.