Cisco Catalyst 3560-X Series, Software Configuration Manual

Page: 57 / 1538

1-15
Catalyst 3750-X and 3560-X Switch Software Configuration Guide
OL-25303-03
Chapter 1 Overview
Software Features
QoS and CoS Features
• Automatic QoS (auto-QoS) to simplify the deployment of existing QoS features by classifying
traffic and configuring egress queues
•
Cross-stack QoS for configuring QoS features to all switches in a switch stack rather than on an
individual-switch basis (only Catalyst 3750-X switches)
• Auto-QoS enhancements that add automatic configuration classification of traffic flow from video
devices, such as the Cisco Telepresence System and Cisco Surveillance Camera.
•
Classification
– IP type-of-service/Differentiated Services Code Point (IP ToS/DSCP) and IEEE 802.1p CoS
marking priorities on a per-port basis for protecting the performance of mission-critical
applications
–
IP ToS/DSCP and IEEE 802.1p CoS marking based on flow-based packet classification
(classification based on information in the MAC, IP, and TCP/UDP headers) for
high-performance quality of service at the network edge, allowing for differentiated service
levels for different types of network traffic and for prioritizing mission-critical traffic in the
network
– Trusted port states (CoS, DSCP, and IP precedence–both IPv4 and IPv6) within a QoS domain
and with a port bordering another QoS domain
–
Trusted boundary for detecting the presence of a Cisco IP Phone, trusting the CoS value
received, and ensuring port security
• Policing
–
Traffic-policing policies on the switch port for managing how much of the port bandwidth
should be allocated to a specific traffic flow
– If you configure multiple class maps for a hierarchical policy map, each class map can be
associated with its own port-level (second-level) policy map. Each second-level policy map can
have a different policer.
–
Aggregate policing for policing traffic flows in aggregate to restrict specific applications or
traffic flows to metered, predefined rates
• Out-of-Profile
–
Out-of-profile markdown for packets that exceed bandwidth utilization limits
• Ingress queueing and scheduling
–
Two configurable ingress queues for user traffic (one queue can be the priority queue)
– Weighted tail drop (WTD) as the congestion-avoidance mechanism for managing the queue
lengths and providing drop precedences for different traffic classifications
–
Shaped round robin (SRR) as the scheduling service for specifying the rate at which packets are
sent to the stack or internal ring (sharing is the only supported mode on ingress queues)
• Egress queues and scheduling
–
Four egress queues per port
– WTD as the congestion-avoidance mechanism for managing the queue lengths and providing
drop precedences for different traffic classifications