08 Cisco Catalyst 2960 QoS Design AAG
08 Cisco Catalyst 2960 QoS Design AAG
08 Cisco Catalyst 2960 QoS Design AAG
Role in Campus Network Trust DSCP Model Step 3: Configure Egress Queuing
The Cisco Catalyst 2960-X series switches are well This model is configured with the mls qos trust dscp The egress queuing model for the Cisco Catalyst
suited to the role of access switches in campus interface-configuration command. 2960-X is shown in Figure 2..
networks. As such, these switches may connect directly The Trust DSCP model configures the interface to Figure 2 Catalyst 2960-X Egress Queuing Model
to a variety of endpoints, as well as to distribution-layer statically accept and preserve the Layer 3 DSCP markings
switches, as shown in Figure 1. of all incoming packets. This model is suitable for
Figure 1 Cisco Catalyst 2960-X Switches in a Campus interfaces connecting to endpoints that can mark DSCP Application DSCP 1P3Q3T
Network values and are administratively controlled (such as WLAN Network Control (CS7) AF1 Queue 4 Q4T2
(5%)
controllers) as well as for any uplinks to distribution layer Internetwork Control CS6
CS1 Q4T1
switches. Switch ports that can be set to trust DSCP are VoIP EF Default Queue
DF Queue 3 (35%)
shown as yellow circles in Figure 1. Broadcast Video CS5
CS7 Q2T3
Conditional Trust Model Multimedia Conferencing AF4
CS6
This model is configured with the mls qos trust device Realtime Interactive CS4
CS3 Q2T2
IP interface-configuration command. Multimedia Streaming AF3 Queue 2
AF4 (30%) Q2T1
The Conditional Trust model configures the interface to Signaling CS3
AF3
dynamically accept markings from endpoints that have
290910
227062
Best Effort DF CS4
Cisco Catalyst 2960-X series switches: Systems (with the cts option), Cisco IP Video Surveillance
1. Enable QoS cameras (with the ip-camera option), and Cisco Digital
Media Players (with the media-player option). This model EtherChannel QoS
2. Configure Ingress QoS Model(s):
is also suitable for PCs and untrusted devices, since the
– Trust DSCP Model ports connecting to such devices will remain in their QoS policies on the Cisco Catalyst 2960-X are
default untrusted state. Switch ports that can be set to configured on the physical port-member interfaces only
– Conditional Trust Model
conditional trust are shown as green circles in Figure 1. (and not on the logical Port-Channel interface).
– Service Policy Models
3. Configure Egress Queuing Service Policy Models
There may be cases where administrators require more
detailed or granular policies on their ingress edges and as
Step 1: Globally Enable QoS such they may construct MQC-based policies to
QoS is globally enabled on the Cisco Catalyst 2960-X implement classification, marking, and/or policing
with the mls qos command. policies. These policies are constructed with:
Step 2: Configure Ingress QoS Model(s) • class-maps which identify the flows using packet
markings or by access-lists or other criteria
The three most utilized ingress QoS models for campus
networks are: • policy-maps which specify policy actions to be taken
on a class-by-class basis
• Trust DSCP Model
• service-policy statements which apply a specific
• Conditional Trust Model policy-map to an interface(s) and specify direction
• Service Policy Models
Combinations of these ingress QoS models may be used
at the same time.
Campus Cisco Catalyst 3560-X/3750-X QoS Design At-A-Glance
290911
class TRANSACTIONAL-DATA
set dscp af21
class BULK-DATA
set dscp af11
class SCAVENGER
set dscp cs1
class DEFAULT
set dscp default
Note: Highlighted commands are interface specific; otherwise these are global.
Copyright © 2015 Cisco Systems, Inc. All rights reserved. Cisco, the Cisco logo, Cisco Systems, and the Cisco Systems logo are registered trademarks or trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.