Cisco Catalyst Switches Review
Overall Satisfaction with Cisco Catalyst Switches
We use the Catalyst range as our access, distribution and internal core routing layer. This pretty much makes up the core of our campus network with recent upgrades to 10 Gig and some movement for 40 Gig within our data center.
We like the idea that we have a lot of control within our layer two environment and are able to implement many security functions within our switching layer.
We like the idea that we have a lot of control within our layer two environment and are able to implement many security functions within our switching layer.
Pros
- Spanning-Tree - The ability to handle loops and BPDU Guards is unmatched in my opinion. We heavily rely on this functionality to mitigate some layer 2 issues we sometimes face.
- Syslogs and SNMP - We love the detail at which we can obtain syslog information and filter based on levels. Much of our troubleshooting of faults with the detailed SNMP traps assist in mitigating issues early.
- L3 Switching - I love the fact that we can easily do routing and switching within the same unit, and for our internal core operations, it's perfect. High-speed port density are coupled with routing into a single unit on the larger Catalyst switches.
Cons
- For the larger Catalyst 6800 and even the older 6500 switches, while Netflow is supported within the units, experience in these areas has been unsatisfying sometimes. We noticed the supervisor engines over time ramp up their CPU utilization which can cause performance issues. Perhaps take this into account and tailor your Netflow sample configurations differently for the Catalysts.
- The switching component is always the most expensive area within any investment. It's a justification of capability and resilience over cost, so if you want to be assured of your operations, go Cisco Catalyst.
- The challenge is not within the actual Catalyst product line but more within the cabling infrastructure that links into the technology as well as choosing the right switch based on your scenario. This comes with experience and reading a lot of Cisco Design Guides.
For me, essentially it came down to integration and a good understanding of our switching environment. To use other brands would have meant managing two different sets of codes or scripts for the same functions. It would work if you could get the configuration correct, but Cisco just worked out better in regards to features and handling layer 2 security concerns.

Comments
Please log in to join the conversation