What is our primary use case?
I use Cisco Catalyst Switches mostly in apartment complexes. They are apartment buildings, where one apartment has three or four bathroom/bedroom combinations and each resident who lives in those has their own connection to the switch. Additionally, the common areas of the building have a connection to the switch.
I've used Cisco Catalyst Switches in that environment, providing internet to a complex, both fiber and copper. We have taken and put cable TV, converted the satellite signals off of DIRECT TV satellites, and broadcasted all their channels, including local channels in the complex. There are approximately 250 channels through the same switches by converting the output to a network environment by turning them around and sending it back out on the other end for coaxial cable distribution. I've been working a lot in the MDFs and the IDFs of the individual complexes.
What is most valuable?
We use the VLANs to separate library, office, and individual apartments. With some of the reporting that receive, we're able to take and track down where people like to put in their own wireless routers. Sometimes they will take a DSL modem from AT&T that they brought from home, hook it in backward, and it will give rogue addresses causing issues.
It's been pretty easy for us to track down where those rogue addresses are coming from and shut the port down until we can have a technician go out and fix it properly.
There are a lot of features that Cisco Catalyst Switches have. However, they're not always needed.
The security of Cisco Catalyst Switches seems to be sound. It's very good with security. I've had no issues, security-wise. The important this is to know what to do to fix problems if you have a security issue, and it seems to work, whether you're using Cisco Catalyst Switches, Opensense, pfSense firewalls, or any normal firewall issues. Cisco Catalyst Switches are able to communicate to all the other hardware very well.
What needs improvement?
I use the Cisco Catalyst Switches command-line interface(CLI) a lot out in the field, but there are some web interfaces features that are available that I haven't used very much. I'm more comfortable with the CLI, but the web interfaces are very lacking.
The application controls that you have when you go through the Cisco Catalyst Switches for configuration and to see your whole network could improve. If the interface could display and recognize devices other than the Catalyst that you might have in the network to allow you to build your network. It does not necessarily need to control them, but to see they're there and how they're hooked up would make a big difference when it comes to trying to map and monitor the network activity in the system.
Those are two areas I find in the Cisco Catalyst Switches that are not as robust as some of the newer solutions, such as Aruba. You could see everything's controlled by the web interfaces, but not as much by the CLI. I don't like that Arubas CLIs, but I do like the web interface where you can see everything and control everything without having to load a special application on a computer and/or use the CLI. You can visually see all the information, and I find that's an easier learning curve for people monitoring. I haven't used it very much with the Cisco Meraki's, but a lot of the places we have worked have been with governments, and they use a lot of the Cisco Catalyst line of solutions.
If someone was trying to manage their own office, I would rate the usability of Cisco Catalyst Switches a five out of ten. Unless you know the CLI well then you will use the interface that is a little bit tricky to work with.
For how long have I used the solution?
I have been using Cisco Catalyst Switches for approximately 10 years.
Buyer's Guide
Cisco Catalyst Switches
May 2025
Learn what your peers think about Cisco Catalyst Switches. Get advice and tips from experienced pros sharing their opinions. Updated: May 2025.
851,604 professionals have used our research since 2012.
What do I think about the stability of the solution?
Most of the stability issues I have found have been hardware-related and not software. I have found that sometimes a port will go dead, and when a port goes dead on the even side, the odd side equivalent goes dead as well. This is where things get a little hot and it caused the solder joint to go loose or something similar happened. That's what my guess would be on the issue, a lot of times they only mark the port as dead and shut it off. When they have many ports that are dead that they don't have any spares they typically switch out the switch altogether.
People do not want to pay for you to resolder a circuit board and check for cold solder joints, I try and speed things up. If I have not had to use many spares on the ports for repair, to keep the repair at a quick pace. I can change a power supply or I can change a board in them quickly. I haven't actually bothered to go through and see if it's a cold solder joint or if it's actually a dead port. I'm having to use my experience with other equipment and knowing that it more times than not, kills both ports on the same connector, it's probably a cold solder joint or something to do with where it's connecting to the motherboard. This would be the first place I would look.
I would rate Cisco Catalyst Switches stability a nine out of ten.
They are highly stable, they have never given me a problem.
How are customer service and support?
I've never had to talk with the Cisco technical support. Usually, if there is a problem I know how the switches are built, I can take them apart and put them together to fix them. For example, in the last Cisco solution I did fix, the power supply was overheating, and it would eventually shut the unit down or it would freeze. I let it cool off and came back when it was cool and took a power supply from one that the mainboard that was frozen, and put it in. It came right back up and it was working at the right temperature.
When it comes to technical support, I've never had to use them. What typically happens is the client calls technical support, technical support turns around dispatches a company that dispatches me and I go out there, fix the issue. I notify that company of their technical support, which may be Cisco's, or not, and inform them of the problem. The technical support double-checks the program and makes sure everything's up and operating.
Which solution did I use previously and why did I switch?
I have used other networking solutions previously, such as Aruba.
What other advice do I have?
I have found that the problems with Cisco Catalyst Switches are caused by the end-user putting equipment on it backward and various other similar user errors. Cisco Catalyst Switches does not have all the features in the web interface. I didn't see the web interface able to be controlled the solution well. You can bring up some information controls, you click a link, and everything's in it is confusing to me, they could improve it. The web application gives you the ability to change some settings, but not necessarily critical ones. There're some things that you have to do at the CLI that their application does not give you the ability to do.
I have VLANs that are set up in my office under a pfSense firewall. The VLANs are set up in the firewall, and it acts as a switch as well. The actual switches turn around and act as a router and then the Cisco Catalyst Switches recognize the VLANs, and process everything accordingly as if it was a Cisco solution. They integrate well will all other hardware.
I rate Cisco Catalyst Switches an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.