Currently, we are using the Cisco 5585 and the Firepowers, and the Firepower IPS, which comes as part of the firewall module, and the switching and the routing. For switching, we have the Catalyst and the core switch, the big one, which is 8800, and also 68 series. I have experience working with Cisco products and Cisco solutions many times. I used to work on Cisco at the beginning, but nowadays I am on another platform. At this time, I am in a particular administrator position. From time to time, I am driving some standards of a Cisco product. We have UCS, ASA 5585, and Firepower.
Team Head of IT Security at China Everbright Bank, HK branch
Real User
Top 10
Sep 1, 2026
Our use case for using Catalyst 8000 Edge Platforms is that we were establishing a new equipment room for the relocation from the old building to the new building.
Major use cases for Catalyst 8000 Edge Platforms are primarily for SD-WAN Edge devices, application-aware routing, and it combines routing and security since this is a one-box solution integrated with a firewall, IPS, IDS, and URL filtering, along with VPN IPsec and segmentation concepts. When analyzing performance of Catalyst 8000 Edge Platforms, I'm looking at network WAN performance metrics for mission-critical applications, measuring metrics such as latency, jitter, packet loss, RTT value, and also using SLA-based routing for path selection. In terms of application performance metrics, Catalyst 8000 Edge Platforms uses Deep Packet Inspection, focusing on application response time, per application latency, jitter, loss, and throughput per application. In terms of analytics and telemetry, we are using NETCONF or SNMP polling. We monitor interface statistics, loss, latency, jitter, application performance, CPU, and memory utilization. If we have an IPsec tunnel, we're also monitoring telemetry such as tunnel health, alongside routing and control plane status using vManage or ThousandEyes.
Learn what your peers think about Catalyst 8000 Edge Platforms. Get advice and tips from experienced pros sharing their opinions. Updated: September 2026.
Catalyst 8000 Edge Platforms advance edge computing and network management, enhancing connectivity and performance. Known for scalability, these platforms suit enterprises needing seamless integration and reliability in diverse environments.These platforms cater to modern networking demands, enabling robust connectivity and efficient data processing at the edge. Designed for adaptability, Catalyst 8000 integrates with existing systems, offering a versatile solution for network expansion....
Currently, we are using the Cisco 5585 and the Firepowers, and the Firepower IPS, which comes as part of the firewall module, and the switching and the routing. For switching, we have the Catalyst and the core switch, the big one, which is 8800, and also 68 series. I have experience working with Cisco products and Cisco solutions many times. I used to work on Cisco at the beginning, but nowadays I am on another platform. At this time, I am in a particular administrator position. From time to time, I am driving some standards of a Cisco product. We have UCS, ASA 5585, and Firepower.
Our use case for using Catalyst 8000 Edge Platforms is that we were establishing a new equipment room for the relocation from the old building to the new building.
Major use cases for Catalyst 8000 Edge Platforms are primarily for SD-WAN Edge devices, application-aware routing, and it combines routing and security since this is a one-box solution integrated with a firewall, IPS, IDS, and URL filtering, along with VPN IPsec and segmentation concepts. When analyzing performance of Catalyst 8000 Edge Platforms, I'm looking at network WAN performance metrics for mission-critical applications, measuring metrics such as latency, jitter, packet loss, RTT value, and also using SLA-based routing for path selection. In terms of application performance metrics, Catalyst 8000 Edge Platforms uses Deep Packet Inspection, focusing on application response time, per application latency, jitter, loss, and throughput per application. In terms of analytics and telemetry, we are using NETCONF or SNMP polling. We monitor interface statistics, loss, latency, jitter, application performance, CPU, and memory utilization. If we have an IPsec tunnel, we're also monitoring telemetry such as tunnel health, alongside routing and control plane status using vManage or ThousandEyes.