What is our primary use case?
We use this solution for everything layer 2 related to our infrastructure, from data centers to local networks. Our business is airports, so we utilize them throughout the entire airport infrastructure.
On a day-to-day basis, we use it for all switching layers, like access, core, or distribution. We also utilize 802.1X.
What is most valuable?
This solution has a pretty good rate of not causing unexpected behavior or failing. We're using maybe 900 switches right now. And, rarely, if ever, something fails, it's dependable.
What needs improvement?
First of all, there are some features that take a long time to get implemented, and other vendors have them for a long time before them. For example, it took a long time to have a way to commit change with the timer, so it gets undone if the user doesn't accept the change after it's done. Like, having to say the changes be done, and everything works fine. In the end, everything works fine, but it didn't exist. That's just an example of stuff that came late to Catalyst.
The CLI structure is mostly outdated sometimes. It doesn't really make sense how things connect to each other. It's not object-oriented, stuff like that.
Moreover, if you want to stack switches, you can't really do it except that you have stack modules, which I find is outdated. Like Juniper Switches, stacks, even switches that were on different locations over Layer 3, and stuff like that. I'd suggest stacking to take cues from other vendors.
For how long have I used the solution?
I have been using it for decades. Currently, I operate as the end user. In my previous role, I acted as an integrator, and we partnered with Cisco.
Buyer's Guide
Cisco Catalyst Switches
December 2024
Learn what your peers think about Cisco Catalyst Switches. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,053 professionals have used our research since 2012.
What do I think about the stability of the solution?
Sometimes, we have issues with stability. We even have some switches, like, that simply stopped working. Like, something went off, but it is not a usual occurrence. It's quite rare.
What do I think about the scalability of the solution?
The way we design things, we could scale them. We could scale, meaning that we could add more switches to our current design. But we're not at this point because there's no need yet. We pretty much thought about it right in the beginning.
We have about 750 users using this solution in my company.
How are customer service and support?
Sometimes, it's quick and helpful. Sometimes, we did have one case that took, like, months, and, eventually, things got solved after upgrading newer firmware that, by then, had been released. However, tech support did not solve the case.
Which solution did I use previously and why did I switch?
I have used HPE and Juniper in the past. I've also used Dell Power Connect and Luxul. First of all, they're on the more pricey end. They cost more than most. I'm not sure if that's true today, but when I still had to take into account money when it was my job to take into account money, they were on the pricing. So that's an accounting pro. HPE and Juniper, which were fine switches, both of them for, like, two-thirds of the price or something like that.
Stability, plus the fact that resources are very easily found. Moreover, everybody knows how to work with Cisco. Also, if anyone gets certified, we'll most probably start getting certified by Cisco because it's an industry-standard certification. So, people who work with Cisco are easier to find. And they pretty much work as advertised.
Cons: there are features that Cisco lacks interface-wise, like UI stuff that could be a lot better. For example, take a look at Juniper, and it's like night and day.
How was the initial setup?
We're currently transitioning to Catalyst 9200 series. We still have a lot of Catalyst 2960s in various locations, but they're being replaced with new ones.
We don't have any central management for the Switches. So it all gets done with copying, phasing, changing IPs, or whatever is relevant. So, the setup is not complicated as long as you know what you're doing. But that goes for everything, I guess. Like, if you already know how it works, then it's not complicated.
The setup is straightforward for me because I know what I'm doing. However, the CLI and the way iOS is structured could take a lot of improvement. There are some things in there. You have to know that they connect in a certain way, or else you won't ever find how it works. You need your Google open for a lot of stuff if you don't already know it.
What about the implementation team?
I was a part of the deployment team. We had already designed what needed to be deployed. We have multiple locations and multiple airports. Each airport was not in the same condition as the other ones.
For example, each airport had its own separate preexisting network. So, there were different strategies that we had to use in each airport to deploy the switches without disrupting the airport functions. It was not the same thing everywhere.
In general, we had a pretty simple design of what we needed, how many switches were sized, and what we expected in terms of customers. It was a pretty standard design to construct a backbone and distribution point within the airports. So, it was pretty much doing three or four templates. And just changing the variables on those templates. That was it.
We don't need a lot of resources or staff members for the deployment part because it depends on the size of the airport again. Like, if there were 300 devices to be deployed, we would need 15+ people. So, it depends on size.
Also, the time depends on the physical properties of the site that you are on. Where are the switches going to be installed? Where, in what condition is this place? Is it still under construction? Is it already constructed? Is it somewhere that's difficult to reach? All these are variables that should indicate how many people you need.
However, maintenance could be a bit more automated. Maybe if Cisco have a central management console or something, then it is more automated. The way we do it, we have to upgrade by ourselves. Like, it's stuck, or it's switched separately by hand. Using FTPs and FTPs and the old way of doing stuff. So, if there's a management, it's a central management tool. When we do maintenance, it's a hassle.
What other advice do I have?
I would recommend using the product. Overall, I would rate the solution an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.