What is our primary use case?
My main use case for Cisco ACI involves working with various customers, some of whom utilize Cisco ACI as a traditional network after migrating their existing setup, while others have complex networks that segment traffic and employ PBR and other advanced features that Cisco ACI offers.
Day-to-day, I work on project-based tasks where customers approach me with specific needs, such as installing new pairs of firewalls. I analyze their current networks and assist them in achieving their migration goals, such as in a significant ongoing project where I built a multi-pod Cisco ACI fabric and oversee the documentation and operations during weekly migration phases for different networks or VLANs.
When assisting with migrations, I encounter various challenges, and preparation is crucial, as numerous things can go wrong. The biggest challenge I see is moving from a traditional data center to Cisco ACI, which requires a significant change in mindset since engineers accustomed to configuring VLANs, interfaces, and routing protocols individually must adopt thinking in terms of policies, endpoint groups, and application connectivity.
Therefore, the key is to shift the mindset as it differs greatly from traditional networking, emphasizing the need for a solid preparation and execution plan to ensure successful migration without downtime.
Every migration is distinct, and there is no one-size-fits-all approach. In my experience, the pivotal factors for successful migration include proper planning, understanding the customer's existing infrastructure, and ensuring that everyone involved comprehends the migration process alongside Cisco ACI's logic, which contrasts with traditional networks. Effective communication is crucial, as is the technology aspect; ensuring mutual understanding of Cisco ACI's functionality and having a proper execution plan is vital.
How has it helped my organization?
Cisco ACI has a tremendously positive impact on my organization and is one of the favorite products in the data center space. I receive excellent feedback from approximately 99% of customers, who find Cisco ACI reliable with minimal issues or bugs encountered.
While upgrading annually is necessary to stay current, overall stability is a hallmark of Cisco ACI. The initial learning curve can be steep due to its unique behavior compared to traditional networking, but the long-term benefits manifest as time savings through policy reusability and simplified configurations.
I find it challenging to provide specific time metrics for common tasks since it often depends on the task at hand. After Cisco ACI fabric is built, creating policies initially takes time, but once established, they can be easily reused across access ports, allowing for efficient configuration without repetitive setups. The time savings vary with the specifics of each task.
What is most valuable?
In my opinion, one of the standout features of Cisco ACI is definitely the Service Graph with PBR, which I highlight to my customers. In traditional networks, you need specific configurations to insert service devices between different VLANs, but with Cisco ACI, the process is streamlined.
Using Service Graph with PBR allows for effective traffic redirection based on policy tags without requiring default gateways or complex setups. You can establish contracts between different segments, making it easier to filter and process traffic, which is a feature my customers frequently appreciate and utilize.
The impact of Service Graph PBR on troubleshooting and flexibility for my customers is significant. While it might be complex at first if someone is new to Cisco ACI, once they understand how it operates, it adds immense operational flexibility. Instead of creating numerous objects for traffic redirection, Service Graph with PBR allows for easy attachment to a contract, and with a good understanding of its functionality, troubleshooting becomes manageable.
This flexibility empowers customers to route traffic seamlessly, enhancing their overall network management experience.
There are many valuable and unique features in Cisco ACI that my customers often mention. One highlight is the fault detection capabilities; when an issue arises, customers can quickly access the APIC GUI, review faults, and pinpoint issues based on timestamps. Additionally, the ability to track events, audits, and the health scores of EPGs significantly enhances troubleshooting efficiency.
Cisco ACI's design inherently favors automation, being built with REST API calls, which facilitates integration with various automation tools including Ansible or Terraform.
I appreciate that everything done in Cisco ACI relates to API calls from the APIC, emphasizing its automation-focused design. The extensive documentation available for the API enables users to leverage diverse automation methods such as Ansible, Terraform, or custom Python scripts, making it essential for those who want maximum efficiency from Cisco ACI.
What needs improvement?
I do not have pain points or areas for improvement in Cisco ACI that I can pinpoint. Most complaints from customers arise due to insufficient knowledge of their networks or Cisco ACI itself. To maximize Cisco ACI's potential, comprehensive understanding of both Cisco ACI and how applications communicate is essential.
Frequently, customers become discouraged after transitioning from traditional networking due to its complexity, and they struggle with the steep learning curve necessary to appreciate Cisco ACI's capabilities fully.
The documentation for Cisco ACI is extensive and excellent, with numerous white papers and courses available. I believe there is little to enhance, as the existing resources effectively support users in understanding Cisco ACI.
For how long have I used the solution?
I have been working with Cisco ACI for four and a half years, and with Cisco networking, I have approximately seven years of experience in total. In my current company, I have been for ten months, but even in a previous job, I was working with the same technologies in a very similar position. Thus, I have used VXLAN, BGP, and EVPN for over four and a half years.
I started my journey as an operations professional responsible for monitoring Cisco ACI fabrics and handling small troubleshooting tickets related to connectivity issues. Slowly, I transitioned into project work and design aspects, where I handled the implementation of changes like adding a new firewall or service graph PBR.
I developed a method of procedure document outlining the analysis and implementation process for changes, and now I function primarily in an architect role, managing the entire life cycle of networking within Cisco ACI.
What do I think about the scalability of the solution?
Cisco ACI's scalability is one of its most significant benefits, easily allowing organizations to grow without the limitations of a traditional three-tier architecture. When more access ports are needed, simply adding a leaf and connecting it to the existing spines facilitates expansion.
How are customer service and support?
My experience with Cisco ACI's customer support is generally positive, though I perceive recent declines compared to previous service levels. Nevertheless, I find the support to be adequate and my interactions satisfactory.
Which solution did I use previously and why did I switch?
Before Cisco ACI, I did not work with any alternative data center networking solutions, as my experience has predominantly been with Cisco. The primary change involved transitioning from classic NX-OS networks and three-tier architecture to working with Cisco ACI as my first software-defined networking solution.
What was our ROI?
I cannot provide specific metrics regarding return on investment, but one clear takeaway is that customers running Cisco ACI since 2016 continue utilizing the same hardware without significant issues, indicating solid investment value and longevity.
What's my experience with pricing, setup cost, and licensing?
Regarding pricing, setup costs, and licensing for Cisco ACI, I observe that it is on the more expensive side, although discounts sometimes make it more affordable. Overall, it is recognized as a premium solution.
Which other solutions did I evaluate?
Customers often evaluate options including Huawei and Extreme Fabric, but Cisco ACI consistently wins the bidding due to its superior offerings.
What other advice do I have?
I rate Cisco ACI a solid ten out of ten. I chose this rating because of my overall experience, the extensive capabilities it offers, including automation and monitoring, and the strong recommendation I would give to customers who genuinely need it.
In my organization, Cisco ACI is deployed entirely on-premises. While I leverage virtual APICs on ESXi, all deployments remain within my premises, with no current hybrid or public cloud deployments.
I do not notice a strong trend among my customers toward moving Cisco ACI to the cloud; their preference leans heavily toward on-premises solutions. There has been speculation about a Cisco ACI cloud offering, but it appears to be losing traction, and I have yet to encounter customers expressing interest in cloud deployments for Cisco ACI.
I advise others considering Cisco ACI to invest time in understanding it fully. The learning curve may be steep initially, but subsequent familiarity makes managing Cisco ACI much simpler and rewarding.
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. Cisco Distributor, Partner