Application-centric networking? More like Cisco-centric networking

Cisco's software-defined networking solution seems to answer one question: How to sell more Cisco products to enterprises

Call it the un-SDN, if you will. Cisco's new Application-Centric Infrastructure (ACI) initiative promises to tackle networking problems only partially addressed by current software-defined networking.

Cisco does have a good sense of the problem at hand. Networks still have lousy notions of which applications run across them and can't really tell what those apps need. Inspecting packets is slow and error-prone. There has to be a better way -- ergo, says Cisco, ACI.

But is it the only better way?

The idea behind ACI is twofold. First, you have a piece of hardware (in this case, the newly introduced Nexus 9000 switch) that can run either with Cisco-native silicon or third-party chips that supply any number of standard SDN APIs. (Yes, OpenFlow is a third-party option.) Second, you have a software policy controller to define service levels and access privileges for applications using the network hardware. This approach spans both the physical and virtual domains, touted by Cisco as a big advantage.

Cisco claims the SDN problem can't be solved by simply abstracting everything away from the hardware since that's where the actual problems lie. But not everyone agrees with ACI as an answer, and not simply because it consists largely of (what else?) more Cisco hardware.

Cisco's hardware vs. competitors' SDN software

That hardware -- mainly, the Nexus 9000 data center switch -- comes from Cisco's $800 million-plus spin-in purchase of Insieme Networks. It's a startup Cisco funded for the sake of creating market-specific network products that flank rather than eclipse Cisco's existing line and are solidly welded to Cisco's bigger business plans.

That's why it's crucial to look at this in the light of Cisco's competition -- mainly VMware, HP, and the rest of the folks who've sunk heavily into OpenFlow as the pill for all SDN ills. Cisco doesn't want to lose out to folks that can market generic switches with software overlays or ODM switches running Linux, nor does it want to be beaten to markets it's yet to penetrate (such as storage and Layer 4-7 hardware) or areas where it's feeling pressure from upstarts like Arista (high-speed low-latency switching).

But ignore the fact that Cisco is pushing more of its hardware as the solution to this problem. What's still hazy about ACI, and one of its biggest possible drawbacks, is how it's meant to be implemented with the very applications it's supposed to help. Only a few details have emerged so far. As Jim Duffy reported in Network World, there's a RESTful API, which implies that the applications themselves have to advertise intent to the controller.

1 2 Page
From CIO: 8 Free Online Courses to Grow Your Tech Skills
Join the discussion
Be the first to comment on this article. Our Commenting Policies