Você está na página 1de 2

Cisco Catalyst 3560-X/3750-X QoS Design At-A-Glance

Role in Campus Network Trust DSCP Model Step 3: Configure Ingress Queuing
The Cisco Catalyst 3560-X & 3750-X series switches This model is configured with the mls qos trust dscp The ingress queuing model for the Cisco Catalyst
are well suited to the role of access switches in campus interface-configuration command. 3560-X/3750X is shown in Figure 2.
networks. As such, these switches may connect directly The Trust DSCP model configures the interface to Figure 2 Catalyst 3560-X/3750-X Ingress Queuing
to a variety of endpoints, as well as to distribution-layer statically accept and preserve the Layer 3 DSCP markings Model
switches, as shown in Figure 1. of all incoming packets. This model is suitable for
Figure 1 Cisco Catalyst 3560-X/3750-X Switches in a interfaces connecting to endpoints that can mark DSCP Application DSCP 1P1Q3T

Campus Network values and are administratively controlled (such as WLAN Network Control (CS7) EF
Q2
controllers) as well as for any uplinks to distribution layer Internetwork Control CS6
CS5
Priority Queue
CS4
switches. Switch ports that can be set to trust DSCP are VoIP EF
shown as yellow circles in Figure 1. CS7 Q1T3
Broadcast Video CS5
CS6
Conditional Trust Model Multimedia Conferencing AF4 CS3 Q1T2
This model is configured with the mls qos trust device Realtime Interactive CS4 AF4 Q1T1
IP interface-configuration command. Multimedia Streaming AF3 AF3

The Conditional Trust model configures the interface to Signaling CS3


Queue 1
dynamically accept markings from endpoints that have
290910

Transactional Data AF2 AF2 Non-Priority


met a specific condition (currently based on a successful Default Queue
Network Management CS2 CS2
Cisco Discovery Protocol identification). This model is
QoS Design Steps suitable for switch ports connecting to Cisco IP phones Bulk Data AF1 AF1

There are four main steps to configure QoS on Cisco (with the cisco-phone option), Cisco TelePresence Best Effort
Scavenger DF
CS1 CS1

227061
Catalyst 3560-X and 3750-X series switches: Systems (with the cts option), Cisco IP Video Surveillance Best Effort DF DF

1. Enable QoS cameras (with the ip-camera option), and Cisco Digital
Media Players (with the media-player option). This model Step 4: Configure Egress Queuing
2. Configure Ingress QoS Model(s):
is also suitable for PCs and untrusted devices, since the The egress queuing model for the Cisco Catalyst
– Trust DSCP Model ports connecting to such devices will remain in their 3560-X/3750X is shown in Figure 3..
– Conditional Trust Model default untrusted state. Switch ports that can be set to
conditional trust are shown as green circles in Figure 1. Figure 3 Catalyst 3560-X/3750-X Egress Queuing
– Service Policy Models Model
3. Configure Ingress Queuing Service Policy Models
Application DSCP 1P3Q3T
4. Configure Egress Queuing There may be cases where administrators require more
Network Control (CS7) AF1 Queue 4 Q4T2
detailed or granular policies on their ingress edges and as CS1 (5%)
Step 1: Globally Enable QoS such they may construct MQC-based policies to Internetwork Control CS6
Q4T1

Default Queue
QoS is globally enabled on the Cisco Catalyst 3560-X and implement classification, marking, and/or policing VoIP EF DF Queue 3 (35%)
3750-X with the mls qos command. policies. These policies are constructed with: Broadcast Video CS5
CS7 Q2T3
Step 2: Configure Ingress QoS Model(s) • class-maps which identify the flows using packet Multimedia Conferencing AF4
CS6
markings or by access-lists or other criteria Realtime Interactive CS4
The three most utilized ingress QoS models for campus CS3 Q2T2

networks are: • policy-maps which specify policy actions to be taken Multimedia Streaming AF3 Queue 2
(30%)
AF4 Q2T1
on a class-by-class basis Signaling CS3
• Trust DSCP Model AF3
• service-policy statements which apply a specific Transactional Data AF2
• Conditional Trust Model policy-map to an interface(s) and specify direction Network Management CS2
AF2
CS2
• Service Policy Models Bulk Data AF1
EF
Combinations of these ingress QoS models may be used Best Effort
Scavenger DF
CS1
CS5
Q1
Priority Queue

227062
at the same time. Best Effort DF CS4
Campus Cisco Catalyst 3560-X/3750-X QoS Design At-A-Glance

EtherChannel QoS Cisco Validated Design


QoS policies on the Cisco Catalyst 3560-X/3750-X are The Cisco Validated Design for Cisco Catalyst 3650-X and
configured on the physical port-member interfaces only 3750-X series switches in the role of an access switch in a
(and not on the logical Port-Channel interface). campus network is presented below.

Step 1: Enable QoS: Step 3 :Configure Ingress Queuing


mls qos mls qos srr-queue input priority-queue 2 bandwidth 30
mls qos srr-queue input bandwidth 70 30 Ingress Queue and
mls qos srr-queue input buffers 90 10 Threshold Tuning
Step 2: Configure Ingress QoS Model :
mls qos srr-queue input threshold 1 80 90
Trust DSCP Model : mls qos srr-queue input cos-map queue 1 threshold 1 0 1 2
Ingress
mls qos trust dscp mls qos srr-queue input cos-map queue 1 threshold 2 3
CoS-to-Queue
mls qos srr-queue input cos-map queue 1 threshold 3 6 7 Mapping
Conditional Trust Model : mls qos srr-queue input cos-map queue 2 threshold 1 4 5
mls qos trust device cisco-phone or mls qos srr-queue input dscp-map queue 1 threshold 1 0 8 10 12 14
mls qos trust device cts or mls qos srr-queue input dscp-map queue 1 threshold 1 16 18 20 22
mls qos srr-queue input dscp-map queue 1 threshold 1 26 28 30 34 36 38 Ingress
mls qos trust device ip-camera or DSCP-to-Queue
mls qos trust device media-player mls qos srr-queue input dscp-map queue 1 threshold 2 24 Mapping
mls qos srr-queue input dscp-map queue 1 threshold 3 48 56
Service Policy Models : mls qos srr-queue input dscp-map queue 2 threshold 3 32 40 46
[class-maps omitted for brevity]
Step 4 : Configure Egress Queuing
policy-map MARKING-POLICY mls qos queue-set output 1 buffers 15 30 35 20
class VOIP mls qos queue-set output 1 threshold 1 100 100 100 100
set dscp ef Egress Queue and
mls qos queue-set output 1 threshold 2 80 90 100 400 Threshold Tuning
class MULTIMEDIA-CONFERENCING mls qos queue-set output 1 threshold 3 100 100 100 400
set dscp af41 mls qos queue-set output 1 threshold 4 60 100 100 400
class SIGNALING mls qos srr-queue output cos-map queue 1 threshold 3 4 5
set dscp cs3 mls qos srr-queue output cos-map queue 2 threshold 1 2
class TRANSACTIONAL-DATA Egress
mls qos srr-queue output cos-map queue 2 threshold 2 3 CoS-to-Queue
set dscp af21 mls qos srr-queue output cos-map queue 2 threshold 3 6 7 Mapping
class BULK-DATA mls qos srr-queue output cos-map queue 3 threshold 3 0
set dscp af11 mls qos srr-queue output cos-map queue 4 threshold 3 1
class SCAVENGER mls qos srr-queue output dscp-map queue 1 threshold 3 32 40 46
set dscp cs1 mls qos srr-queue output dscp-map queue 2 threshold 1 16 18 20 22
class DEFAULT mls qos srr-queue output dscp-map queue 2 threshold 1 26 28 30 34 36 38
set dscp default Egress
mls qos srr-queue output dscp-map queue 2 threshold 2 24 DSCP-to-Queue
mls qos srr-queue output dscp-map queue 2 threshold 3 48 56 Mapping
service-policy input MARKING-POLICY
mls qos srr-queue output dscp-map queue 3 threshold 3 0
mls qos srr-queue output dscp-map queue 4 threshold 1 8
mls qos srr-queue output dscp-map queue 4 threshold 2 10 12 14
Note : The Service-Policy Model can be expanded to
include policing.
queue-set 1
srr-queue bandwidth share 1 30 35 5 Egress Queuing
Interface-Specific Commands
priority-queue out

290911
Note: Highlighted commands are interface specific; otherwise these are global.
For more details, see Campus QoS Design 4.0:
http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSCampus_40.html
And the Cisco Press book: End-to-End QoS Network Design (Second Edition)-Chapter 14

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.