Cisco Application Centric Infrastructure (ACI) is network virtualization technology.
N/A
Cisco Meraki MX
Score 9.1 out of 10
N/A
Cisco Meraki MX Firewalls is a combined UTM and Software-Defined WAN solution. Meraki is managed via the cloud, and provides core firewall services, including site-to-site VPN, plus network monitoring.
LAN, Storage network and compute were already Cisco so we moved from Nexus to Cisco Application Centric Infrastructure as natural alignment and simplified the dc operations.
The enormous difference between Catalyst and Meraki products is the granular and simple deployment. The Cisco security appliance firewall gives one and you more granular activity whereas the Cisco Meraki MX is focused on plug and play and it gets one and you going. I like …
I feel that Cisco ACI is quite good at different architecture designs. You can have it as just a straight layer two network. You can have it like we have with a vast layer three network and I think just for the layer three network it has easen up the use. I think the use cases for layer three networking is better for ACI. If you just want to do the layer two, you can still use Cisco Nexus and so on and that should be almost simpler in some way.
It's very well suited for retail locations where you have a small footprint and it's a collapsed core design and it's connecting to a larger hub. We don't necessarily use them in our data centers just because they don't have the full capability we have. We use FTDs in our data centers, so we use a different Cisco product for that. So I would say they're really good at setting up sites quickly, getting them connected, protecting the traffic, and then they're a little weak in a data center right now.
Cisco ACI, The object model is very complicated. It's something difficult to understand and also because there is a user interface, there's a web user interface, but it's not optimal to use it because if you want to deploy a large amount of VLAN or a large amount of tenants, it's quite difficult to do it or it's quite challenging. Maybe if you want to configure a large amount of ports using the web interface, it's not appropriate because it takes a lot of time. It also provides APIs to do that, but as I say, the object model is very difficult to understand and there is very little documentation about automation of the ACI and maybe there is but it's not so easy to find.
The Cisco Meraki MX series is phenomenal at allowing us to remotely manage networks. So the devices usually act as the brain behind our client's networks, which makes it really, really easy for our team to take a look at what's going on in those client network environments, resolve any issues, and make sure that our client's networks are staying secure.
I think something I've just went to a session with hyper fabric and the ideas that hyper fabric has. Keep it really simple because Cisco ACI is a complex system and adopt some of the ideas behind hyper fabric, bring it to ACI that will be really beneficial. So as I said, automation is a great thing, but it's still, you need to have the background and the really complex stuff that happens behind the scenes to leverage the value of that solution. And by adding more simplicity to it, I think that will be a great thing. And also integrating with other applications in terms of the automation.
Provided with the intensive fault isolation for the CISCO ACI, we are glad that we have this Data Center Solution in place and we will continue to renew as long as the future needed requirements are meet and more helpful features will be enabled in the future with the integration of security
The simplicity and ease of use for the Meraki Dashboard make it an easy choice for our organization to renew our Meraki Enterprise Agreement. We will likely continue using the Meraki MC67-C, MX450, and other MX models in their catalog until we shift away from Meraki completely
You'll need a lot of training and hands on experience to get the most out of the product. There are a lot of very useful features in the ACI product. Often times there are a lot of ways to get to a solution for chalanges in the field. The solutions might be different eacht time. Knowing which one to implement is somtimes a challenge.
Some features simply aren't there, but the ones that are there are pretty easy to use. Sometimes it is easy to get lost when trying to find the specific device you want to work on, but that's mostly due to how rarely we have to go into the interface.
It allways works. If there are problems with links going down by accident (say someone accidentally unpatches something they shouldn't have), we rarely miss more then one packet over the link. Also, using VPCs we are able to upgrade the software on the switches without the attached EPs ever noticing.
Meraki MX devices support high availability (HA) configurations, which ensures minimal downtime if one device goes offline. This feature has helped us maintain a stable and reliable network, even in cases of hardware failures. ince Meraki is cloud-managed, we've noticed that the cloud infrastructure is generally highly reliable, with minimal service interruptions or downtime. This makes it easier to manage the network remotely without significant availability concerns. Meraki automatically pushes firmware updates and patches, which helps maintain system stability without requiring manual intervention. These updates are rolled out in a manner that ensures minimal disruption to service.
Day to day operations on Cisco ACI do not require much human intervention, the platform ticks over without any major faults. Being able to rapidly replicate the communication between two groups of machines across multiple sub networks speeds up new application delivery, and the integration into vmWare allows multiple teams within IT to work together to problem solve rapidly.
The interface is pretty responsive. The lower end devices are easy to overwhelm if you have a lot of throughput. Be sure the model you get is rated for the amount of traffic you will have. Overbuild if possible, otherwise you won't be fully leveraging the connection from your ISP.
Cisco provides users and partners with a multitude of data for you to consume. I think that the stuff in the public domain goes a long way to assisting you find any answers you may need, plus insights and information from areas such as DevNet provide you with access to more than just the traditional release notes and the like
I haven't ever had a bad experience with Meraki support. On the few occasions where I wasn't understanding the UI or needed some clarification about what a setting actually would do, I contacted them and they were very quickly able to provide help. Returns are simple and fast, too. We had to return a defective device one time and they shipped the replacement before we had even un-racked the one that was faulty. Unlike many other vendors, they didn't ask use to a do long list of scripted diagnostics, they just took my word for it that the device was broken and sent out a replacement immediately
The Cisco ACI training provided by Cisco was in depth, covered all of our requirements, and allowed us to implement and maintain the platform without issues.
great when they offered it, really tested your knowledge with hands on and see what your peers from other orgs know. glad to see that we were ahead of the curve of what our peers knew
Being involved in the implmentation gives you more overview on how things are supposed to be working and communicating, you can easily performce troubleshooting and understanding the troubleshooting scenario
Implementing Meraki MX devices in phases—starting with a pilot group or select branch offices—was invaluable. This allowed us to identify potential configuration issues, troubleshoot problems, and refine our setup before rolling it out company-wide. It also helped to get feedback from early users and adjust the deployment strategy accordingly. The SD-WAN capabilities in Meraki MX were essential for optimizing our WAN traffic and ensuring better application performance across various locations.
Actually we start our learning in networking career with Cisco. So it is very useful or easier to learn this product. And honestly speaking, I didn't work in any other data center solution other than Cisco. So I cannot compare what it gives us more than other popular stuff. But this is very nice product like from Cisco.
The Meraki Dashboard has been a lot more intuitive than CradlePoint NetCloud. We switched from CradlePoint to Cisco Meraki MX because we were already familiar with the interface which allowed us to be familiar with a single dashboard.
Cisco ACI scales well and is suited in scenarios such as multi-cloud or large data centre implementations. It is not suited to smaller deployments as the efficiencies that it provides are not fully realised. It is well suited in large environments that contain both virtual and bare-metal machines allowing a great deal of flexibility. It is also perfect to support multi-tenancy platforms.
When I first started with my company we had various infrastructure and a mix of tech. Since going to Cisco Meraki MX we have noticed better network performance and our new sites are much easier to bring online. Users have noticed an improvement in VPN connection and getting into all our systems.
We've definitely spent quite a bit of time relearning how to do things in ACI, but I think the investment has been well worth while considering that we can now deploy tenants and leaves from the ground up in a matter of seconds.
We can if we choose to upgrade an entire datacenters worth of switches in a single night. (We've chosen to break it up for availability requirements, but if you didn't require 99.999% uptime like us you may be able to do it)
From a positive impact? Basically it allows us to set up shop very quickly. It allowed us to add sites to our network very quickly. From a negative perspective, I think the only thing is that I can see from a negative perspective is I have a preference to working with ACLI in terms of how I engage with the youth tool At the moment, the only way to actually engage with a tool is on a gui and sometimes what I'd actually like is more detailed information in terms of actual configuration that you'll actually get out of ACLI.
