Application Visibility And Control - Cisco Catalyst 6500-E Series Manual

Figure 18. CoPP with the Supervisor Engine 2T
In this example, 410,000 bits per second are being sent toward the CPU. However, the CoPP policy is configured
to allow only 10,000 bps of this type of traffic to reach the CPU. This rate is enforced across all forwarding engines
(PFC4s/DFC4s) in the system, thereby making sure that the maximum amount of traffic that will reach the CPU is
10,000 bps. CoPP can also be configured to enforce limitations based on the number of packets per second of a
specific traffic type, and a diverse set of counters is available to show how much traffic is being forwarded and
dropped by a particular policy. This allows the network administrator to see where changes in the policies might
need to be made if they are being to restrictive or too open.
All of the previously highlighted security features demonstrate why the Cisco Catalyst 6500-E with Supervisor
Engine 2T is the best choice for the backbone of the unified access campus architecture. When it comes to the
user security and segmentation (SGT/SGACL), infrastructure security (NDAC, CoPP), data security and integrity
(MACsec, MACsec over MPLS), and infrastructure segmentation (MPLS, VRF-Lite, EVN) requirements of BYOD,
video, and collaboration, no other backbone platform provides the scalability and feature functionality needed to
support these enablers of such an architecture.

Application Visibility and Control

With all of the different types of devices, users, and traffic that will be traversing networks supporting BYOD, video,
and collaboration, it becomes even more critical to have insight into that information so that the network
administrator can properly support the requirements of the user community. Figure 19 shows several use cases in
which the need for application visibility and control arises.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 18 of 28