That is a pretty broad question without context but here are some highlights off the top of my head:
ACI (which is basically VXLAN under the hood)
- Turnkey (VXLAN) fabric (simplified installation, turn up, and operations managed by the controllers) providing both the underlay and the overlay
- Centralized management - You manage all fabric configuration and policy from the APIC controllers
- Centralized visibility - The controller gives you a unified view of your entire fabric.
- Integrations with your virtualization solution (VMWARE etc.) to facilitate rapid provisioning and consistent policy
- Highly Scalable and supports Multi Site deployments
- Built for Automation
- Extensive cloud support
- Multi tenant and security policy "ready"
- Ties you to a specific Vendor (you can decide how important that is for you)
- There is a learning curve (but well worth it in my opinion)
- You can decouple your underlay from your overlay
- You can basically build this with any vendors hardware
- Lets you pick your underlay protocols
- Probably less of a learning curve and some "comfort" given that you are likely using the boxes you are used to today.
- You are back to box by box configuration unless you use something like DCNM (this capability is relatively new - Google "DCNM evpn fabric" to get a feel for that)
- You have to manage your underlay and your overlay
- You have to manage all other integrations
If you already have an overlay technology (say NSX) then a DCNM deployed/controlled fabric or a do-it-all-yourself fabric might edge out ACI if the ACI learning curve was a concern (either option has a learning curve typically). I've deployed NSX over ACI so it certainly works.
At this point its important to understand what you are trying to do (or what your customer is trying to do). Don't let them shy away from ACI because it seems difficult! It really is not. Understand their goals and requirements.
I wrapped up an ACI build early this year. Initially my customer was wary of ACI. When we wrapped up they told me that they were now in a position to really have a competitive advantage in their space.
HyperFlex HTML Plug-In Automated Installer
The HyperFlex HTML Plug-In Automated Installer automates installing the Cisco HyperFlex HTML Plug-In for VMware vCenter. It is available on the Cisco DevNet Code Exchange here or directly from GitHub at https://g...
Cisco® Nexus® Dashboard revolutionizes operations in today’s modern data-center environments. Join us to learn about the operational efficiencies realized from the seamless user experience of the dashboard and the powerful capabilities of Cisco Nexus Insi...
The HTML5 plug installation is successful. But I get the following error while I click on AVE. The other icons are showing up the results except AVE. Please let me know your SME thoughts on this error.
No VmmDomains Found