Network Engineer at a hospitality company with 10,001+ employees
Real User
Offers valuable unified fabric features and has good customer service
Pros and Cons
  • "The most valuable feature is the unified fabric."
  • "More how-to videos and instructional information is required."

What is our primary use case?

Our primary use case for the Cisco ACI solution is the data center.

How has it helped my organization?

This product has improved our organization through automation.

What is most valuable?

The most valuable feature is the unified fabric.

What needs improvement?

I recommend to customers that they meet a knowledgeable vendor to help them with it.

Buyer's Guide
Cisco ACI
April 2024
Learn what your peers think about Cisco ACI. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
768,924 professionals have used our research since 2012.

How are customer service and support?

Cisco ACI customer service is very good.

Which solution did I use previously and why did I switch?

Cisco ACI was sold to us. Everybody is using it now.

How was the initial setup?

With the initial setup of Cisco ACI, it is new, so you need to make sure issues pop up. You have to work through those issues. I would like to see included how-to videos.

What about the implementation team?

We went with a consultant, i.e. a third party vendor: HCL. They're very good.

Which other solutions did I evaluate?

Arista was one of the main alternatives that we evaluated.

What other advice do I have?

On a scale of one to 10, I would rate this product at an eight based on everybody else's experiences. It's pretty good. I don't have a full review.

More how-to videos and instructional information is required. We need to simplify it.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Network Engineer at CS Computer Systems
Real User
The simplicity of the deployment is one of its main benefits
Pros and Cons
  • "Now, our customers have tiers of management that have meetings with about the simplest tasks because it has to be approved from upper management and senior management and by the time it gets to the engineer that's going to deploy it, it takes way too long. With the solution, they can delegate a person who would be in charge of running the ACI as a whole, and it will be much faster because it doesn't have to go through the whole chain of command for the simple task of deploying one little machine on one port in the data center."
  • "I would like for there to be more information about it available. While using the ACI in the graphical interface, I would like if there was something that explained every step that you can click and it will tell you what you are doing in more detail."

What is our primary use case?

We're planning to use it as a product to sell to our customers. We are in the business of service integration. We offer solutions for our customers. We have specific customers who have a use for ACI because of the microsegmentation. They have five regional offices which all have five different people who are responsible for managing their site so we are trying to unite them and put everything under one roof and have a single place of control and visibility of the full network specifically for their data center.

How has it helped my organization?

Now, our customers have tiers of management that have meetings with about the simplest tasks because it has to be approved from upper management and senior management and by the time it gets to the engineer that's going to deploy it, it takes way too long. With the solution, they can delegate a person who would be in charge of running the ACI as a whole, and it will be much faster because it doesn't have to go through the whole chain of command for the simple task of deploying one little machine on one port in the data center.

What is most valuable?

It eases our deployment. Now, we use service requests when there's a project and we have to deploy it. So when the networking team gets a service request it'll be two clicks, anyone can do it. It will be less of a job, and it will be easier and faster. The main benefit is the simplicity of the deployment. On the flipside, it's also a drawback because if only one person does it and if he does something wrong, the whole system can stop working. If ten people are doing ten different things and one person messes up, it's only one error and it's easier to isolate the problem and fix it. A customer is going to deploy something on their own and more often than not, they don't have the knowledge and experience to understand what can go wrong, so they might accidentally clog the network.

What needs improvement?

If I was a customer who is using the ACI to run my network, I would like for there to be more information about it available. While using the ACI in the graphical interface, I would like if there was something that explained every step that you can click and it will tell you what you are doing in more detail. For me, I understand what's happening because I did a course, but the problem will be when our customers, who are not so versatile in this, start using it and won't know what's going on. If it works it's fine, but when they run into problems, then it's gonna be an issue. If everything works, it should be fine but if any issues come up, a lot of Cisco services will be needed.

What do I think about the scalability of the solution?

The scalability is impressive. I think the best thing about that is the vendor-agnostic part. In the lab, we did a VMware deployment from what I heard it doesn't matter how the VM is deployed, it can integrate with ACI and you can manage it from the Epic controller.

How was the initial setup?

In the lab environment, we had a setup rebuilt, it was their virtual environment. It was a small deployment. Four switches in total, two leaf and two spine switches, and three controllers. From my past experiences with those types of deployments, the setup shouldn't be an issue. The natural connectivity between them and six switches should be easy. From the controller itself, the deployment of the overlay is pretty straightforward and simple.

What other advice do I have?

I would rate it an eight out of ten. 

I would advise a colleague to definitely try it. Mess around with it, test it as much as possible because it's a new solution. It's different from the traditional data center deployment so there's not a lot of internet posts about it in which you could go and Google and find out more information. The chances that someone has had your problem before and probably found a solution for it are slim so you might get stuck and you will have to go straight to Cisco.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
PeerSpot user
Buyer's Guide
Cisco ACI
April 2024
Learn what your peers think about Cisco ACI. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
768,924 professionals have used our research since 2012.
Network Architect at a computer software company with 10,001+ employees
Real User
Reliable, very scalable, and makes it easy to do global configurations
Pros and Cons
  • "It is very easy to do the configuration after you know how to work with the product. It is global, so you change one interface, and changes are reflected on every switch."
  • "Its graphical user interface (GUI) is not as user-friendly as it could be."

What is our primary use case?

This is software-defined networking. So, all the configuration done on a customer network is done with this application.

I am using the version before the latest version.

What is most valuable?

It is very easy to do the configuration after you know how to work with the product. It is global, so you change one interface, and changes are reflected on every switch.

What needs improvement?

Its graphical user interface (GUI) is not as user-friendly as it could be.

It is quite expensive.

For how long have I used the solution?

I have been using this solution for about a month.

What do I think about the stability of the solution?

It is stable and reliable.

What do I think about the scalability of the solution?

It is quite scalable. It is one of the most scalable products we have come across.

We have five people who are using it in our company in Portugal.

How are customer service and technical support?

We haven't had any need.

Which solution did I use previously and why did I switch?

We were using a different solution, but it was not for software-defined networking. It was for a different type of networking.

How was the initial setup?

It is very complex. All the configuration that needs to be done on the Cisco ACI is very complex. We have to create base policies for all the network devices and then implement it. Afterward, it is rather easy, but the implementation part is a long and complex process.

After it is deployed, it is rather easy because all the configuration is done automatically. You only need to do regular visits to see that it is working and do some regular tests. It is not that difficult.

What about the implementation team?

We took Cisco's help.

What's my experience with pricing, setup cost, and licensing?

It is quite expensive. It is not at all on the cheap or medium side.

What other advice do I have?

I am quite new to this product, and I am still learning it. My recommendation would depend upon the size of the organization. It is one of the flagship products of Cisco, but it is not a product that you can implement for any customer. It is more suitable for medium to large enterprises.

I would rate Cisco ACI an eight out of 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Assistant Director IT at a healthcare company with 10,001+ employees
Real User
Has the ability to do segmentation without running everything through a firewall but it is lacking integration with Tetration
Pros and Cons
  • "This product improved the way our company functions by enabling us to establish our goal of moving to a zero-trust model. That's how Cisco ACI helps us the most."
  • "It's a very complex system, as it should be. It's a new way of thinking about networking. Cisco ACI adds complexity. Cisco ACI is extremely complex. That's not necessarily a complaint, as much as it is a fact."

What is our primary use case?

The primary use case for ACI in our company is to do data center segmentation to move our network to a zero-trust model. 

How has it helped my organization?

This product improved the way our company functions by enabling us to establish our goal of moving to a zero-trust model. That's how Cisco ACI helps us the most.

What is most valuable?

The most valuable feature at this stage is that it can do segmentation without running everything through a firewall. You're able to do segmentation without having firewalls in the middle of all your connections. It is extendable to other data centers. You can extend your Layer 2 VLANs over Layer 3, using VXLAN.

What needs improvement?

I would like to see integration with Tetration. You should be able to use Tetration to manage your scripts and push into ACI without having to export, manually manipulate, script it, and then re-import back in ACI. It needs automation there.

What do I think about the stability of the solution?

It has been very stable. Upgrades have been very easy. We have no real complaints about the stability of the Cisco ACI platform.

What do I think about the scalability of the solution?

The scalability is great. You get more capacity. You can extend it to another data center remotely. 

How are customer service and technical support?

The technical support for this solution is great. We bought support and it's been going well. 

Which solution did I use previously and why did I switch?

We knew we needed to switch to another solution because of security concerns. We needed a zero-trust model. 

How was the initial setup?

For our migration approach, we did a very quick migration into it in a network-centric mode. We're starting to move into application-centered mode now. We're still in the migration period.

The initial setup was very complex. It's just a new technology platform. Nobody had training on it. Nobody knew what it was on my team. That makes it complex. 

It's a very complex system, as it should be. It's a new way of thinking about networking. Cisco ACI adds complexity. Cisco ACI is extremely complex. That's not necessarily a complaint, as much as it is a fact.

What about the implementation team?

To deploy Cisco ACI, we used Advanced Services. Our experience with them was fifty-fifty. It's still so new in Cisco that it was difficult for them. We deployed Tetration at the same time and there were a lot of issues there. The engineer they put on the project was great. 

What other advice do I have?

On a scale of one to ten, I would rate this product at a seven. It would be a lot higher, but it should have the ability to integrate with Tetration, as was marketed to us. It was a huge downfall for us when they decided not to do that right now. 

I advise anyone to get training before you implement Cisco ACI.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Director of Network and Security at a tech services company with 501-1,000 employees
Real User
Reduces complexity and the time required to grow or change our network infrastructure
Pros and Cons
  • "The most valuable feature is programmability, where we can manage a network via APIs and software, as opposed to having to manage complex hardware."
  • "I would like to see a lot more integrations with the rest of the Cisco portfolio."

What is our primary use case?

We use this solution to implement a network overlay. We have a software-defined network in our data center.

How has it helped my organization?

Prior to ACI, a network upgrade or network change would be much more complex than it is now. Reducing complexity means that it is faster to make changes.

What is most valuable?

The most valuable feature is programmability, where we can manage a network via APIs and software, as opposed to having to manage complex hardware.

What needs improvement?

I would like to see a lot more integrations with the rest of the Cisco portfolio. I would like to have ACI embedded into HyperFlex, as an example.

What do I think about the stability of the solution?

This solution is very stable now, although it has had hiccups, for sure.

Most of the early struggles with ACI were not that it would go down. Rather, it was more the stability of the management platform, which has improved a lot over time.

What do I think about the scalability of the solution?

This is a highly scalable solution, and we are running it in some really large environments. We have ACI installed in data centers that have more than one hundred leaps, which is thousands of servers.

How are customer service and technical support?

Technical support for this solution is pretty good.

We've had a few incidents with environment reliability, but getting to the right engineering teams hasn't been difficult.

Which solution did I use previously and why did I switch?

Our previous solution was legacy, three-tier networking. The market is changing, and software-defined networking is becoming the way to do business. Our network was the last piece to keep up, so it needed investment.

How was the initial setup?

The initial setup of this solution is pretty complex.

The complexity comes about when you migrate from legacy networks into an ACI network. It's a complex process and there aren't tools that make it easy. usually, you're going to build ACI almost band new. Managing it is not complex, but building it is.

What about the implementation team?

We handled the implementation in-house.

What was our ROI?

ROI would be hard to quantify, but it would come from a network with less downtime, less complexity in changes, and one that is easier to manage.

Which other solutions did I evaluate?

We evaluated solutions from Cisco, VMware, and HP. Cisco's solution, from a software perspective, may be slightly behind, but from a hardware perspective, it's the most scalable and best to support.

What other advice do I have?

My advice to anybody researching this solution is that you have to test it. You can't take the stats on paper. Rather, you have to actually do the R&D to see it in a real environment. I think a lot of people make the mistake of looking at the features on paper, without actually testing the full functionality.

This is a really strong product. It has been complex, but most of their recent advancements have been in simplification.

I would rate this solution an eight out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner.
PeerSpot user
Systems Network Manager at a non-tech company with 1,001-5,000 employees
Real User
Easy to install and scale, but there is a steep learning curve attached
Pros and Cons
  • "It is a complete re-write of everything that you've ever thought of from a networking standpoint."
  • "It would be nice if I could specify network-centric in my design, and the system would organize and set itself up in that way."

What is our primary use case?

Our primary use for this solution is in our data center.

What is most valuable?

This is a modern, next-generation solution, and it is where the platform is going.

I have been told that this is an easy solution to configure, but we are just starting to deploy it, so that is to be determined.

What needs improvement?

ACI is not simple, by any stretch of the imagination.

We are not following the application-centric approach, but a network-centric approach instead. It would be nice if I could specify network-centric in my design, and the system would organize and set itself up in that way. Essentially, once you go into the GUI for the first time it would prompt you, and it would build out the infrastructure to accommodate your choice.

For how long have I used the solution?

Recently purchased.

What do I think about the stability of the solution?

We have been in a lot of sessions with them and have done a lot of work with it in the lab. We've seen it grow over time. The early versions of the code were buggy and flakey, but as they have gone through newer iterations, we've seen it get better. It is at the point now where were are comfortable with it going into a production data center.

What do I think about the scalability of the solution?

Scalability is definitely something that we're looking at, and it's one of the attractive features of ACI for us. It is easy to do.

The way ACI works is it is one configuration interface. If you want to add more then you just plug it in. I would not call it plug-and-play, but they've made it to the point where it is very close. 

This is important to us because we just don't know how our business is going to grow, and change, over time. It's a moving target for us. If we buy something today, and then there is a demand for more capacity in the data center, then we just have to buy more devices and plug them in. We don't have to do anything else. The infrastructure just becomes available for us to use. This differs considerably from the traditional Cisco, which involved a lot of command lines and configuration.

How are customer service and technical support?

We have not really dealt with technical support, yet. We are using the Cisco professional services to help us with the design and configuration.

Which solution did I use previously and why did I switch?

We were using the Cisco 9000 and we reached a point where investment was needed due to depreciation in our infrastructure. We needed to get rid of the old system, and then decide whether to stay with the Cisco 9000 or move to ACI. For us, we decided to employ a hybrid solution that uses both.

How was the initial setup?

The initial setup of this solution is pretty straightforward. It is a plug-and-play type of solution where you can just take it out of the box and connect the wires.

Once this system is in place then it becomes complicated. However, the initial go at it is pretty straightforward, which is nice.

What about the implementation team?

We are using Cisco professional services, as well as a VAR, to help us with the implementation. In order for us to go live, we have to make sure that our VAR is ready to support that.

What was our ROI?

It is too soon for us to realize ROI.

Which other solutions did I evaluate?

We're a Cisco shop, so we did not evaluate solutions from other vendors. We already have our partner for purchasing, and all of our relationships were already established. For us, it was simply a design decision between Cisco 9000 and ACI.

What other advice do I have?

We are currently testing this solution in a lab, preparing for our deployment into production.

We are not ready to approach this solution in an application-centric way. It's a great overall architecture, good scalability-wise, easy to configure, and a central configuration, but there are too many knobs to turn.

We were originally going to use ACI for everything. However, after we really started looking at the design and having conversations with our Cisco advanced services team, we saw that it made sense to use a hybrid solution.

My advice for anybody interested in implementing this solution is to have a good look at your data center, your architecture, and importantly your operational and support team. If you have people who are familiar with the traditional way of doing Cisco, and have never touched ACI before, then there is a steep learning curve ahead. The operational team will have to ramp up and be educated. That was definitely a factor for us.

We have a third party operational team, and we had to challenge them. We asked if it was something that they could do, and they needed to prove it to us, first. This was done before we even went into the solution. The number one thing is that you have to be able to support it. If you have only two people installing it, then you're not going to be able to run support 24/7 for when something breaks at three in the morning.

This is a good solution, but I would really like to see the network-centric philosophy of configuration to be a little bit easier. The learning curve is steep. But, being somebody who has been traditional Cisco, iOS, and command line, I can say that this is completely different. It is a complete re-write of everything that you've ever thought of from a networking standpoint. It can simplify your life if you do it right.

I would rate this solution a seven out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user234747 - PeerSpot reviewer
Practice Manager - Cloud, Automation & DevOps at a tech services company with 501-1,000 employees
Real User
It offers third party integration via OpFlex however, you can only use the Nexus 9000 series hardware for the ACI fabric.

Originally posted at vcdx133.com.

I recently completed the Cisco ACI Field Engineering course. This post describes the major building blocks of the Cisco Application Centric Infrastructure (ACI) and how it all fits together.

Cisco ACI is the next generation of Data Center flexible network fabrics, it replaces what you currently have with Nexus 2K, 5K and 7K (traditional Core, Distribution, Access or FabricPath architecture). Cisco’s previous TRILL-based leaf and spine technology is FabricPath, which has nothing to do with ACI (based upon VXLAN). The two are not compatible and unrelated, aside from supporting the Clos-type architecture.

Cisco ACI is designed to provide a unified fabric for physical and virtual networking, moving away from the management of individual physical switches. If you are used to the policy construction of the Cisco UCS, then you will easily understand Cisco ACI.

The Cisco Application Centric Infrastructure (ACI) has the following major components:

  • Clos-type Leaf and Spine architecture with VXLAN ECMP
  • Application Policy Infrastructure Controller (APIC) – minimum of three per fabric. The APIC has a UI but is really designed for northbound REST API integration with a Cloud Management Platform that will push policy into the ACI fabric.
  • 3rd party integration via OpFlex (open policy protocol supporting XML and JSON)
  • Nexus 9000 Product Family – 9500 series & 9300 series
  • Spine Switches – Nexus 9336 fixed chassis (“baby spine”) or 9736 line card with the 95xx chassis
  • Application Virtual Switch (AVS) – replaces the Nexus 1000V and allows APIC policy to be pushed to the vSwitch

The diagram below illustrates the Cisco ACI Leaf and Spine architecture, complete with APIC management nodes.

Cisco ACI is driven via policy and the main policy groups are:

  • APIC Controllers
  • Fabric, Access & Inventory
  • Tenants
  • VM Domains
  • Layer 4 to Layer 7 Services
  • AAA & Security


Weaknesses (Cisco APIC version 1.0)

  • Can only use the Nexus 9000 series hardware for the ACI fabric. There is talk of other Nexus models and other vendors being supported in the future.
  • Only a small number of vendors support OpFlex at this point in time (eg. F5, Citrix).
  • Cisco ACI was released in 2014, it will take some time for it to gain maturity.
  • Currently does not have the concept of Micro-segmentation as a service of the hypervisor (like VMware NSX-v does).
  • ACI Fabric “Federation” (unifying multiple ACI fabrics into one) is not currently supported.
  • Single vCenter to multiple ACI fabrics is currently not supported (technically possible, but is an unsupported configuration).
  • Operationally complex without a Cloud Management Platform to push policy, which is true for any network virtualisation solution.
  • Current supported CMPs are OpenStack and Cisco UCS Director.
  • QoS enforcement within the ACI fabric is currently not supported.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Sr. Voice Engineer at SGWS
Real User
A time-saver that allows us to work more efficiently
Pros and Cons
  • "This solution allows you to do everything quicker and more efficiently."
  • "The CLI needs to be improved."

What is our primary use case?

Our primary use for this solution is centralization.

How has it helped my organization?

This solution has improved the way we operate because it is a time-saver.

What is most valuable?

This solution allows you to do everything quicker and more efficiently.

What needs improvement?

The CLI needs to be improved.

What do I think about the stability of the solution?

This product is pretty stable. 

What do I think about the scalability of the solution?

The scalability is really good.

Which solution did I use previously and why did I switch?

We did not use another solution prior to this one.

How was the initial setup?

Our setup is still in progress.

What about the implementation team?

We used an integrator to assist us.

What other advice do I have?

This is a solution that I would recommend.

I would rate this solution a ten out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user