Cisco acquisition of Cariden

Cisco acquisition of Cariden

Network Software

Cisco acquisition of Cariden

isco announced today the intended acquisition of Cariden, a network management software company. Cisco will purchase the self-funded Cariden for $141 million. This deal is on the heels of two other Cisco acquisitions. The purchase of the WiFi company Meraki for $1.2 billion and the cloud software company Cloupia for $125 million. Cariden has built it’s business from developing network management software targeting service providers. Cariden listed it’s business partners as Alcatel-Lucent, Big Switch Networks, Cisco and Juniper.

Cariden marketing focuses on capacity planning and business intelligence. The Cariden website claims to deliver the “global view” of networks. In August Cariden announced its blueprint for Software Defined Networking (SDN). It targeted the keywords for the service provider SDN market like, computational path elements (CPE), controller interfaces and big data components like predictive analytics.

The Cariden Take on SDN

“A full battery of Network Controllers including an OpenFlow controller interface.” – Cariden Introduces Blueprint for Infrastructure SDN

Reviewing the Cariden white paper “Infrastructure SDN with Cariden Technologies” reveals a company eager to enter into the new SDN ecosystem. They were featured in the BigSwitch press release as an analytics partner.  Big data analysis of networks is fairly handicapped in todays networks. The more the network operating system (NOS) are exposed by new primitives, the more available the extracted network data will be. Customers and vendors alike are seeing the promise of shifting away from only focusing on the ip prefix destinations and think along the lines of a more flexible flow based L2-L7 model to better integrate application awareness.

From the “Infrastructure SDN with Cariden Technologies White Paper”

Looking at SDN through the prism of value reveals three distinct areas of interest:

  1. Flow Services SDN that is closely tied to microflow visibility and programming made possible by OpenFlow
  2. Virtualization SDN that is closely tied to data centers and other multitenant compute-network environments
  3. Infrastructure SDN—Cariden’s focus—that is closely tied to providing visibility and control of network resources to software applications
Cariden Network Operating System

Depending on the value proposition, distinct classes of SDN have emerged, and it is useful to view their unique missions and note the services for which they typically show their benefits:

  • Flow Services SDN addresses the wealth of security and visibility applications that become possible with flow-level programmability
  • Virtualization SDN provides virtual network connectivity for efficiency and agility
  • Infrastructure SDN exposes network resources for continual optimization of resources and predictable handling of diverse traffic demands

Three key, sometimes overlooked, requirements for the NS-OS that it needs to provide are the following:

  • Centralized resource mediation such that there would be a single authoritative source for keeping track of resources and issuing them to various applications
  • Predictive analytics (anticipation of network behavior upon failure states or other “what if” scenarios) to enable applications to schedule resilient bandwidth resources into the future
  • Multivendor/layer interface that provides support for a wide range of infrastructure
Cariden Applications

Classifying SDN applications by the source of value they provide is useful in making sense of the many voices around SDN:

  • The first source of value is security and other services enabled by flow-level programmability; this is Flow Services SDN. 
  • The second source of value is virtualization, which can be termed Virtualization SDN. 
  • The third source of value is exposing programmability of network resources to software applications: Infrastructure SDN. 
Cariden Analytics

My Thoughts: The Cisco SDN Path Forward

If I had tried to get an explanation of SDN from the ONF, or an academic SDN purist, it would probably not deviate far from the the Cariden white paper. Cariden distinctly sees the value in a decoupled NOS from the underlying physical hardware. It saw itself as a intrinsic piece of the application ecosystem leveraging OpenFlow like primitives and controller APIs for path steering, instrumentation and application deliverables. I think their leadership and vision was on point and their selling price reflected that success.

Cisco has commited to the onePK roadmap both proprietary and open programmable APIs and some project both internal and external around SDN. This is business analytics and predictive analysis that should be able to reactively or proactively adjust topologies or do more traditional functions such as reporting functionality with a focus on capacity planning and the economics of growth.

This will clearly be integrated into the SDN onePK and eventual Insieme portfolio, the only question is will it be vertically or horizontally. Three scenarios for not just Cariden’s usage, but Cisco’s holistic SDN strategy could be:

  1. At the least, this will be a new network management play that has long since been missing from Cisco’s portfolio. Anyone in networking can tell CiscoWorks/NetRanger and every other vendors NMS horror stories. While the core focus is SP operators, according to the last graphic, Cariden was being positioned for the data center and enterprise space.
  2.  The UCS business model to networking. Cisco will incorporate this into its onePK open, yet proprietary version of SDN. Just as UCS is only compatable with Cisco x86 hardware, the same would hold true for its northbound applications such as this. To this day, a holistic view of data center analytics remains out of reach to mere mortals. Capturing resource consumption and usage to correlate storage, compute and networking in the data center is valuable to all sizes of customer base.
  3. Cisco embraces the open tent SDN strategy and re-positions itself from a custom hardware company to a software focused company in some product lines. This becomes a pluggable application into the larger SDN ecosystem agnostic to the underlying networking hardware.

The path is still fluid for everyone, including Cisco, but the fundamental goals should be getting sinking in. The vehicle we use to get there is much less important than arrival. Adding value in software to incentives hardware sales has been the path of x86 companies for the past decade. I feel abstractions and layering, will lead networks down a similar path at some point in time regardless of the vehicles; standards bodies or open source.

It is not a reflection on developers for the trail of useless network management products over the past decade. They have done as much as can be done with the archaic primitives in today’s monolithic devices. The industry is showing surprisingly quick progress as they wait on hardware that can begin delivering the products. Seeing networking vendors taking it as seriously as they are with R&D commitments and large acquisitions are quantifiable steps. More manageable and efficient networks to absorb the explosive growth mobility presents is critical in coming years. I would like to see Cisco focus more on the enterprise but they claim to see more demand currently from service providers and thus more focused on that revenue potential.

I like this acquisition, it is relevant to their core products even if the SDN evolutions is unceremoniously murdered. It is focused on adding value in software which has good margins and addressing customer pains in managing today’s scattered networks.

The Cariden white paper that the excerpts came from can be downloaded courtesy of our friends at

About the Author

Brent SalisburyI have over 15 years of experience wearing various hats from, network engineer, architect, devops and software engineer. I currently have the pleasure of working at the company that develops my favorite software I have ever used, Docker. My comments here are my personal thoughts and opinions. More at Brent's BioView all posts by Brent Salisbury →