What is our primary use case?
My main use case for Cisco Catalyst Switches began with the initial Catalyst series, then I moved to the iOS, XE, and then to data center Nexus switches, so I currently use the switches and Nexus series.
Cisco Catalyst Switches primarily connect the data center to end-user devices such as wireless access points, all end-user devices, VLANs, user VLANs, printers, and other equipment.
Cisco Catalyst Switches fit into the path between those users and my data center by having defined port ranges for end-user computers, printer ports, lab ports, and other devices, with access series coming to distribution switches, distribution to core switches, and core to data center switches.
How has it helped my organization?
Cisco Catalyst Switches have positively impacted my organization since I am a partner for Cisco, delivering these solutions across multiple customers, which helps customers have a cost-effective solution for branch offices.
Cisco is one of the very high-end products I recommend, and normally customers do not have any issues with the devices themselves. I implement standard setups across customers and have had 99% success without issues unless there is a bug or something.
What is most valuable?
Cisco Catalyst Switches offer a lot of integration features with Nexus, DNA, and other data center capabilities. While Catalyst switches have fewer features compared to data center switches, they are definitely cheaper, and end-user devices is where I can keep them. Fewer features exist in access layer switches while data center switches are more for traffic distribution and core switches, which should have more features such as loop-free and Spanning Tree.
The most valuable features of Catalyst in my access layer are stacking, VLANs, uplinks, downlinks, trunk configurations, LACP ports, and other devices and aggregation protocols.
These features make day-to-day operations easier for my team because the devices are prestaged and ready for users to connect to devices, and I do not experience many issues with those configurations unless the user requests a different VLAN. I have integrated the access switches to the one X authentication as well, which includes MAC and other types of authentication that allow for dynamic assignment of the VLAN.
Regarding Cisco Catalyst Switches' AI capabilities, I think the governance and security are very good, and I really like the security features in Cisco Catalyst Switches platforms. I do not think there is an issue even with the newer integration of Cisco platforms with MAC and authentication and all kinds of features; it is actually building very well.
I have integrated Python and Ansible scripts into my switch provisioning workflows to automate the standard templates for deploying Cisco switches, which is really helpful for staging devices and site configurations for the sites I have.
What needs improvement?
Cisco Catalyst Switches are already a very improved product, and the newer iOS integrates with all the new features, making it a very strong device for Cisco since switching is a crucial part of Cisco's product line.
Cisco's old console port is one thing Cisco should improve. It should be a USB-C port that works across all stations and switch platforms, whereas newer switches from Meraki or other vendors have better ports. The older models should definitely be updated since Nexus is better, but for the old Catalyst switches, the console port is actually one of the issues I experience.
Cisco Catalyst Switches are very good, as Cisco is improving its product line very effectively.
For how long have I used the solution?
I have been using Cisco Catalyst Switches for around 20 years.
What do I think about the scalability of the solution?
Cisco Catalyst Switches are very scalable, allowing me to integrate multiple switches in the same fabric of connectivity by using Cisco distribution. I can stack the switches in the back end, perform LACP, and integrate switches with any other devices.
How are customer service and support?
Customer support for Cisco is amazing; 99% of the time, the person who picks up the call resolves the issue, so TAC support is outstanding.
I would rate the customer support a nine.
Which solution did I use previously and why did I switch?
I used to use all those solutions, but Cisco is very good, and they are a partner with me now.
What was our ROI?
I have definitely seen a return on investment, as both money and time are saved with Ansible and automation or scripting along with the standard templates across the switching platform, allowing customers to save a lot of time with template provisioning for the switches instead of paying a person for each individual switch and staging.
What's my experience with pricing, setup cost, and licensing?
The setup cost for Cisco Catalyst Switches is not much, although licensing is a bit expensive, but it is still a good option in the market across the product line.
Which other solutions did I evaluate?
Before choosing Cisco Catalyst Switches, I evaluated other options including Dell and HP.
What other advice do I have?
I would rate Cisco Catalyst Switches a nine on a scale of 1 to 10.
I give Cisco Catalyst Switches a nine because I am very happy with the product and very happy with the Cisco product line, as it provides a very nice switching environment and platform.
The accuracy and reliability of its output stand at 99.999%.
Cisco Catalyst Switches are primarily deployed in my organization on-premises, or if it is Cisco Meraki, then it is on the Cisco Meraki cloud.
My advice for others looking into using Cisco Catalyst Switches is to go for Cisco switching since it is one of the best switching platforms available in the market; it is very reliable, highly capable, and does the job it is supposed to do.
Which deployment model are you using for this solution?
On-premises