P. 1
Configuring Qos

Configuring Qos

|Views: 36|Likes:
Published by Magdalena Martínez

More info:

Published by: Magdalena Martínez on Aug 13, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

05/14/2013

pdf

text

original

CH A P T E R

27

Configuring QoS
This chapter describes how to configure quality of service (QoS) by using automatic QoS (auto-QoS) commands or by using standard QoS commands on the Catalyst 2960 switch. With QoS, you can provide preferential treatment to certain types of traffic at the expense of others. Without QoS, the switch offers best-effort service to each packet, regardless of the packet contents or size. It sends the packets without any assurance of reliability, delay bounds, or throughput. You can configure QoS only on physical ports. Configure the QoS settings, such as classification, queueing, and scheduling, and apply a trusted class of service (CoS) or a CoS override setting.

Note

For complete syntax and usage information for the commands used in this chapter, see the command reference for this release. This chapter consists of these sections:
• • •

Understanding QoS, page 27-1 Configuring Standard QoS, page 27-8 Displaying Standard QoS Information, page 27-18

The switch supports some of the modular QoS CLI (MQC) commands. For more information about the MQC commands, see the “Modular Quality of Service Command-Line Interface Overview” at this site: http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter0918 6a00800bd908.html

Understanding QoS
Typically, networks operate on a best-effort delivery basis, which means that all traffic has equal priority and an equal chance of being delivered in a timely manner. When congestion occurs, all traffic has an equal chance of being dropped. When you configure the QoS feature, you can select specific network traffic, prioritize it according to its relative importance, and use congestion-management and congestion-avoidance techniques to provide preferential treatment. Implementing QoS in your network makes network performance more predictable and bandwidth utilization more effective. The QoS implementation is based on the Differentiated Services (Diff-Serv) architecture, an emerging standard from the Internet Engineering Task Force (IETF). This architecture specifies that each packet is classified upon entry into the network.

Catalyst 2960 Switch Software Configuration Guide OL-13563-01

27-1

5 KB) 3 bits used for CoS Layer 2 802. On ports configured as Layer 2 ISL trunks. Classification can also be carried in the Layer 2 frame. all traffic is in IEEE 802. or both.1Q and 802. Switches and routers along the path can use the class information to limit the amount of resources allocated per traffic class.1Q trunks.1p CoS value in the three least-significant bits. These special bits in the Layer 2 frame are described here and shown in Figure 27-1. Implementing QoS in your network can be a simple or complex task and depends on the QoS features offered by your internetworking devices.. detailed examination of the packet. you can construct an end-to-end QoS solution.Chapter 27 Understanding QoS Configuring QoS The classification is carried in the IP packet header. On ports configured as Layer 2 IEEE 802. Layer 2 IEEE 802. Layer 2 CoS values range from 0 for low priority to 7 for high priority. using 6 bits from the deprecated IP type of service (ToS) field to carry the classification (class) information. which are called the User Priority bits. Detailed examination of the packet is expected to happen closer to the edge of the network so that the core switches and routers are not overloaded with this task. (24. the traffic types and patterns in your network. If all devices along a path provide a consistent per-hop behavior. Prioritization bits in Layer 2 frames: • Layer 2 Inter-Switch Link (ISL) frame headers have a 1-byte User field that carries an IEEE 802.. • • • Note IPv6 QoS is not supported in this release. The class information in the packet can be assigned by end hosts or by switches or routers along the way.1p Frame Preamble Start frame delimiter DA SA Tag PT Data FCS FCS (4 bytes) 3 bits used for CoS (user priority) Layer 3 IPv4 and routers that access the Internet rely on the class information to provide the same All switches Packet forwarding treatment to packets with the same class information and different treatment to packets with different class information.1Q frame headers have a 2-byte Tag Control Information field that carries the CoS value in the three most-significant bits. The behavior of an individual device when handling traffic in the DiffServ architecture is called per-hop behavior. Catalyst 2960 Switch Software Configuration Guide 27-2 OL-13563-01 . all traffic is in ISL frames. and the granularity of control that you need over incoming and outgoing traffic.1Q frames except for traffic in the native VLAN. based on a configured policy. QoS Classification Layers in Frames and Packets Figure 27-1 Encapsulated Packet Layer 2 header IP header Data Layer 2 ISL Frame ISL header (26 bytes) Encapsulated frame 1. Other frame types cannot carry Layer 2 CoS values.

Classification is enabled only if QoS is globally enabled on the switch. make the packets comply with the configured resource usage limits (police and mark). the packet is dropped. Queueing evaluates the QoS label and the corresponding CoS value to select into which of the two ingress queues to place a packet. Queueing is enhanced with the weighted tail-drop (WTD) algorithm. For more information. For more information. By default. QoS is globally disabled. The QoS label identifies all QoS actions to be performed on the packet and from which queue the packet is sent. a congestion-avoidance mechanism. If the threshold is exceeded. During classification. Catalyst 2960 Switch Software Configuration Guide OL-13563-01 201792 27-3 . see the “Queueing Overview” section on page 27-4. Because congestion can occur when multiple ingress ports simultaneously send data to an egress port. Figure 27-2 Basic QoS Model Classification Classification is the process of distinguishing one kind of traffic from another by examining the fields in the packet. Figure 27-2 shows the basic QoS model.Chapter 27 Configuring QoS Understanding QoS Basic QoS Model To implement QoS. see the “Queueing Overview” section on page 27-4. The switch maps the CoS in the packet to a QoS label to distinguish one kind of traffic from another. The QoS label that is generated identifies all future QoS actions to be performed on this packet. Actions at the ingress port include classifying traffic and queueing: • Classifying a distinct path for a packet by associating it with a QoS label. For more information. WTD differentiates traffic classes and subjects the packets to different thresholds based on the QoS label. assign a label to indicate the given quality of service as the packets move through the switch. see the “Classification” section on page 27-3. the packet is dropped. the switch performs a lookup and assigns a QoS label to the packet. If the threshold is exceeded. so no classification occurs. and provide different treatment (queue and schedule) in all situations where resource contention exists. • The action at the egress port is queueing: Queueing evaluates the QoS packet label and the corresponding CoS value before selecting which of the four egress queues to use. the switch must distinguish packets or flow from one another (classify). The switch also needs to ensure that traffic sent from it meets a specific traffic profile (shape).

the packet is sent to the ingress queueing and scheduling stages. For information about the CoS ingress queue threshold maps. see the “Queueing on Ingress Queues” section on page 27-5. as shown in Figure 27-3. see the “Queueing on Egress Queues” section on page 27-7. For non-IP traffic. policed.1Q frame headers carry the CoS value in the 3 most-significant bits of the Tag Control Information field. you have this classification option: Trust the CoS value in the incoming frame (configure the port to trust CoS). For information about the CoS egress queue threshold maps. You specify which fields in the frame or packet that you want to use to classify incoming traffic. The label is mapped according to the trust setting and the packet type. Catalyst 2960 Switch Software Configuration Guide 27-4 90563 OL-13563-01 .Chapter 27 Understanding QoS Configuring QoS The QoS label is based on the CoS value in the packet and decides the queueing and scheduling actions to perform on the packet. For configuration information on port trust states. Weighted Tail Drop Both the ingress and egress queues use an enhanced version of the tail-drop congestion-avoidance mechanism called weighted tail drop (WTD). CoS values range from 0 for low priority to 7 for high priority. Because multiple ingress ports can simultaneously send packets to an egress port and cause congestion. Layer 2 IEEE 802. Layer 2 ISL frame headers carry the CoS value in the 3 least-significant bits of the 1-byte User field. see the “Configuring Classification Using Port Trust States” section on page 27-11. ingress queues are located after the packet is classified. outbound queues are located after the internal ring. After classification. Queueing Overview The switch has queues at specific points to help prevent congestion. WTD is implemented on queues to manage the queue lengths and to provide drop precedences for different traffic classifications. Figure 27-3 Ingress and Egress Queue Location Policer Policer Marker Marker Ingress queues Internal ring Egress queues sify Traffic SRR SRR Policer Policer Marker Marker Because the total inbound bandwidth of all ports can exceed the bandwidth of the internal ring. and marked and before packets are forwarded into the switch fabric.

Catalyst 2960 Switch Software Configuration Guide OL-13563-01 201793 Send packet to the internal ring. buffer allocation. Determine ingress queue number. If the threshold is exceeded for that QoS label (the space available in the destination queue is less than the size of the frame). Figure 27-4 Queueing Flowchart for Ingress Ports Start Read QoS label (CoS value). and WTD thresholds. WTD uses the assigned QoS label for the frame to subject it to different thresholds. Are thresholds being exceeded? No Yes Drop packet.Chapter 27 Configuring QoS Understanding QoS As a frame is enqueued to a particular queue. see the “Mapping CoS Values to an Ingress Queue” section on page 27-14 and the “Mapping CoS Values to an Egress Queue and to a Threshold ID” section on page 27-17. the switch drops the frame. 27-5 . For more information. Queueing on Ingress Queues Figure 27-4 shows the queueing and scheduling flowchart for ingress ports. Note Shaped round robin (SRR) services the priority queue for its configured share before servicing the other queue. Queue the packet.

you map CoS values to an ingress queue and map CoS values to a threshold ID.Chapter 27 Understanding QoS Configuring QoS The switch supports two configurable ingress queues. You assign each packet that flows through the switch to a queue and to a threshold. You can display the CoS input queue threshold map by using the show mls qos maps privileged EXEC command. Each queue has three predefined default drop thresholds that are not changeable.. You can combine the commands described in this section to prioritize traffic by placing packets with particular CoSs into certain queues. The switch uses two nonconfigurable queues for traffic that is essential for proper network operation. see the “Weighted Tail Drop” section on page 27-4. The expedite queue has guaranteed bandwidth. For more information about how WTD works. You use the mls qos srr-queue input cos-map queue queue-id {cos1. see the “Configuring Ingress Queue Characteristics” section on page 27-14. Table 27-1 Ingress Queue Types Queue Type1 Normal Function User traffic that is considered to be normal priority. WTD Thresholds The queues use WTD to support distinct drop percentages for different traffic classes. Priority Queueing The priority queue should be used for traffic (such as voice) that requires guaranteed delivery because this queue is guaranteed part of the bandwidth regardless of the load on the internal ring.. For configuration information. which are serviced by SRR only in shared mode. Expedite 1. Specifically. You can use the mls qos srr-queue input cos-map global configuration command.. You can configure the bandwidth required for this traffic as a percentage of the total traffic by using the mls qos srr-queue input priority-queue global configuration command. You can configure the bandwidth required for this traffic as a percentage of the total traffic. You can configure three different thresholds to differentiate among the flows. SRR services the priority queue for its configured weight as specified by the bandwidth keyword in the mls qos srr-queue input priority-queue queue-id bandwidth weight global configuration command. High-priority user traffic such as differentiated services expedited forwarding or voice traffic. Catalyst 2960 Switch Software Configuration Guide 27-6 OL-13563-01 . Table 27-1 describes the queues..cos8} global configuration command.cos8 | threshold threshold-id cos1.

All traffic exiting the switch flows through one of these four queues and is subjected to a threshold based on the QoS label assigned to the packet.Chapter 27 Configuring QoS Understanding QoS Queueing on Egress Queues Figure 27-5 shows the queueing and scheduling flowchart for egress ports. These queues are assigned to a queue set. Rewrite CoS value as appropriate. Read QoS label (CoS value). Note If the expedite queue is enabled. Catalyst 2960 Switch Software Configuration Guide OL-13563-01 201794 27-7 . SRR services it until it is empty before servicing the other three queues. Send the packet out the port. one of which (queue 1) can be the egress expedite queue. Done Each port supports four egress queues. Are thresholds being exceeded? No Yes Drop packet. Figure 27-5 Queueing Flowchart for Egress Ports Start Receive packet from the internal ring. Queue the packet. Determine egress queue number and threshold based on the label.

only an indication of the assigned CoS value is carried along. see the “Weighted Tail Drop” section on page 27-4. Traffic characteristics and needs of your network. You can display the CoS output queue threshold map by using the show mls qos maps privileged EXEC command.. The queues use WTD to support distinct drop percentages for different traffic classes. you map CoS values to an egress queue and map CoS values to a threshold ID. Each queue has three predefined default drop thresholds that are not changeable.cos8} global configuration command. The switch detects whether the target queue has not consumed more buffers than its reserved amount (under limit). You use the mls qos srr-queue output cos-map queue queue-id {cos1.Chapter 27 Configuring Standard QoS Configuring QoS The buffer space is divided between the common pool and the reserved pool. page 27-16 (optional) Catalyst 2960 Switch Software Configuration Guide 27-8 OL-13563-01 . WTD Thresholds You can assign each packet that flows through the switch to a queue and to a threshold. Configuring Standard QoS Before configuring standard QoS.. whether it has consumed all of its maximum buffers (over limit). If there are no free buffers in the common pool or if the queue is over limit. If the queue is not over limit. For more information about how WTD works. However. and whether the common pool is empty (no free buffers) or not empty (free buffers).. page 27-11 (required Configuring Ingress Queue Characteristics. to prevent any queue or port from consuming all the buffers and depriving other queues. These sections contain this configuration information: • • • • • Default Standard QoS Configuration.. Packet modifications can occur during this process.cos8 | threshold threshold-id cos1. The switch uses a buffer allocation scheme to reserve a minimum amount of buffers for each egress queue. you must have a thorough understanding of these items: • • • • The types of applications used and the traffic patterns on your network. page 27-9 Enabling QoS Globally. Is the traffic bursty? Do you need to reserve bandwidth for voice and video streams? Bandwidth requirements and speed of the network. Packet Modification A packet is classified. and queued to provide QoS. page 27-14 (optional) Configuring Egress Queue Characteristics. the packet is not modified at this stage. Specifically. policed. page 27-11 (required) Configuring Classification Using Port Trust States. the switch drops the frame. classification involves assigning a QoS label to a packet based on the CoS of the received packet. and to control whether to grant buffer space to a requesting queue. For IP and non-IP packets. the switch can allocate buffer space from the reserved pool or from the common pool (if it is not empty). Location of congestion points in the network.

Chapter 27 Configuring QoS Configuring Standard QoS Default Standard QoS Configuration QoS is disabled. The default port trust state on all ports is untrusted. Default Ingress Queue Configuration Table 27-2 shows the default ingress queue configuration when QoS is enabled. 2. There is no concept of trusted or untrusted ports because the packets are not modified (the CoS and IP precedence values in the packet are not changed). SRR services the priority queue for its configured share before servicing the other queue. 7 Queue ID–Threshold ID 1–1 2–1 1–1 Catalyst 2960 Switch Software Configuration Guide OL-13563-01 27-9 . The default ingress and egress queue settings are described in the “Default Ingress Queue Configuration” section on page 27-9 and the “Default Egress Queue Configuration” section on page 27-10. Table 27-2 Default Ingress Queue Configuration Feature Buffer allocation Bandwidth allocation 1 Priority queue bandwidth WTD drop threshold 1 WTD drop threshold 2 2 Queue 1 90 percent 4 0 100 percent 100 percent Queue 2 10 percent 4 10 100 percent 100 percent 1. Traffic is switched in pass-through mode (packets are switched without any rewrites and classified as best effort without any policing). Table 27-3 Default CoS Input Queue Threshold Map CoS Value 0–4 5 6. traffic is classified as best effort (the CoS value is set to 0) without any policing. When QoS is enabled with the mls qos global configuration command and all other QoS settings are at their defaults. The bandwidth is equally shared between the queues. Queue 2 is the priority queue. Table 27-3 shows the default CoS input queue threshold map when QoS is enabled. SRR sends packets in shared mode only.

there is no support for it at the VLAN or switch virtual interface level. Table 27-5 Default CoS Output Queue Threshold Map CoS Value 0. All ports are mapped to queue-set 1. Catalyst 2960 Switch Software Configuration Guide 27-10 OL-13563-01 . A shaped weight of zero means that this queue is operating in shared mode. 1 2. try to make changes when traffic is at a minimum. Table 27-5 shows the default CoS output queue threshold map when QoS is enabled. 3 4 5 6. One quarter of the bandwidth is allocated to each queue. therefore. Control traffic (such as spanning-tree bridge protocol data units [BPDUs] and routing update packets) received by the switch are subject to all ingress QoS processing. Table 27-4 Default Egress Queue Configuration Feature Buffer allocation WTD drop threshold 1 WTD drop threshold 2 Reserved threshold Maximum threshold SRR shaped weights (absolute) 1 SRR shared weights 2 Queue 1 25 percent 100 percent 100 percent 50 percent 400 percent 25 25 Queue 2 25 percent 200 percent 200 percent 50 percent 400 percent 0 25 Queue 3 25 percent 100 percent 100 percent 50 percent 400 percent 0 25 Queue 4 25 percent 100 percent 100 percent 50 percent 400 percent 0 25 1. The port bandwidth limit is set to 100 percent and rate unlimited. 2. 7 Queue ID–Threshold ID 2–1 3–1 4–1 1–1 4–1 General QoS Guidelines These are general QoS guidelines: • • • You configure QoS only on physical ports.Chapter 27 Configuring Standard QoS Configuring QoS Default Egress Queue Configuration Table 27-4 shows the default egress queue configuration for each queue-set when QoS is enabled. You are likely to lose data when you change queue settings.

configure terminal mls qos Step 3 Step 4 Step 5 end show mls qos copy running-config startup-config Return to privileged EXEC mode. page 27-11 Configuring the CoS Value for an Interface. Figure 27-6 shows a sample network topology. use the no mls qos global configuration command. page 27-13 Configuring the Trust State on Ports within the QoS Domain Packets entering a QoS domain are classified at the edge of the QoS domain. QoS runs with the default settings described in the “Default Standard QoS Configuration” section on page 27-9. follow these steps to enable QoS.Chapter 27 Configuring QoS Configuring Standard QoS Enabling QoS Globally By default. and the “Queueing on Egress Queues” section on page 27-7. Verify your entries. (Optional) Save your entries in the configuration file. Enable QoS globally. This procedure is required. Catalyst 2960 Switch Software Configuration Guide OL-13563-01 27-11 . the “Queueing on Ingress Queues” section on page 27-5. When the packets are classified at the edge. Beginning in privileged EXEC mode. To disable QoS. the switch port within the QoS domain can be configured to one of the trusted states because there is no need to classify the packets at every switch within the QoS domain. Depending on your network configuration. Command Step 1 Step 2 Purpose Enter global configuration mode. Configuring Classification Using Port Trust States These sections describe how to classify incoming traffic by using port trust states. • • • Configuring the Trust State on Ports within the QoS Domain. QoS is disabled on the switch. you must perform one or more of these tasks. page 27-13 Enabling DSCP Transparency Mode.

(Optional) Save your entries in the configuration file. Catalyst 2960 Switch Software Configuration Guide 27-12 101236 P3 P1 OL-13563-01 . For an untagged packet. Valid interfaces include physical ports. Specify the port to be trusted. configure terminal interface interface-id Step 3 mls qos trust [cos] Step 4 Step 5 Step 6 end show mls qos interface copy running-config startup-config Return to privileged EXEC mode. the port default CoS value is used.Chapter 27 Configuring Standard QoS Configuring QoS Figure 27-6 Port Trusted States within the QoS Domain Trusted interface Trunk Traffic classification performed here IP Trusted boundary Beginning in privileged EXEC mode. The keyword has this meanings: cos—Classifies an ingress packet by using the packet CoS value. Verify your entries. Configure the port trust state. The default port CoS value is 0. follow these steps to configure the port to trust the classification of the traffic that it receives: Command Step 1 Step 2 Purpose Enter global configuration mode. the default is cos. If no keyword is specified. By default. the port is not trusted. and enter interface configuration mode.

Verify your entries. and the DSCP-to-DSCP mutation map. Beginning in privileged EXEC mode. CoS override is disabled. (Optional) Save your entries in the configuration file. Even if a port was previously set to trust CoS or IP precedence. It affects only the DSCP field of a packet at egress. The default is 0. If an incoming packet is tagged. Valid interfaces include physical ports. By default. and the DSCP field in the outgoing packet is based on the QoS configuration. Configure the default CoS value for the port. If the packet is untagged. By default. specify a default CoS value to be assigned to a port. see the “Configuring the CoS Value for an Interface” section on page 27-13. Catalyst 2960 Switch Software Configuration Guide OL-13563-01 27-13 . For information on how to change the default CoS value. and enter interface configuration mode. • Step 4 Step 5 Step 6 end show mls qos interface copy running-config startup-config Return to privileged EXEC mode.Chapter 27 Configuring QoS Configuring Standard QoS To return a port to its untrusted state. follow these steps to define the default CoS value of a port or to assign the default CoS to all incoming packets on the port: Command Step 1 Step 2 Purpose Enter global configuration mode. and all the incoming CoS values are assigned the default CoS value configured with this command. • configure terminal interface interface-id mls qos cos {default-cos | override} Step 3 For default-cos. The switch modifies the DSCP field in an incoming packet. The CoS range is 0 to 7. including the port trust setting. Specify the port to be configured. policing and marking. Enabling DSCP Transparency Mode The switch supports the Differentiated Services Code Point (DSCP) transparency feature. Configuring the CoS Value for an Interface QoS assigns the CoS value specified with the mls qos cos interface configuration command to untagged frames received on trusted and untrusted ports. the default CoS value becomes the packet CoS value. the CoS value of the packet is modified with the default CoS of the port at the ingress port. use the no mls qos trust interface configuration command. Use the override keyword to override the previously configured trust state of the incoming packet and to apply the default port CoS value to the port on all incoming packets. Use the override keyword when all incoming packets on specified ports deserve higher or lower priority than packets entering from other ports. use the no mls qos cos {default-cos | override} interface configuration command. this command overrides the previously configured trust state. DSCP transparency is disabled. To return to the default setting.

The switch also uses the internal DSCP value to select an egress queue and a threshold. configure terminal mls qos no mls qos rewrite ip dscp end copy running-config startup-config show mls qos interface [interface-id] Verify your entries. use the mls qos rewrite ip dscp global configuration command. The switch is configured to not modify the DSCP field of the IP packet. DSCP transparency is still enabled. page 27-14 (optional) Configuring the Ingress Priority Queue. If you enter the no mls qos rewrite ip dscp global configuration command to enable DSCP transparency and then enter the mls qos trust cos interface configuration command. You will need to make decisions about these characteristics: • • Which packets are assigned by CoS value to each queue? Is there traffic (such as voice) that should be given high priority? These sections contain this configuration information: • • Mapping CoS Values to an Ingress Queue. Catalyst 2960 Switch Software Configuration Guide 27-14 OL-13563-01 . To configure the switch to modify the DSCP value based on the trust setting by disabling DSCP transparency. Regardless of the DSCP transparency configuration. which the switch uses to generate a CoS value that represents the priority of the traffic. you might need to perform all of the tasks in the next sections. Enable DSCP transparency. If you disable QoS by using the no mls qos global configuration command. the CoS and DSCP values are not changed (the default QoS setting). Return to privileged EXEC mode. (Optional) Save your entries in the configuration file.Chapter 27 Configuring Standard QoS Configuring QoS If DSCP transparency is enabled by using the no mls qos rewrite ip dscp command. page 27-15 (optional) Mapping CoS Values to an Ingress Queue You can prioritize traffic by placing packets with particular CoSs into certain queues and adjusting the queue thresholds so that packets with lower priorities are dropped. Configuring Ingress Queue Characteristics Depending on the complexity of your network and your QoS solution. the switch modifies the internal DSCP value of the packet. follow these steps to enable DSCP transparency on a switch: Command Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Purpose Enter global configuration mode. Beginning in privileged EXEC mode. Enable QoS globally. and the DSCP field in the outgoing packet is the same as that in the incoming packet. the switch does not modify the DSCP field in the incoming packet.

The drop-threshold percentage for threshold 3 is predefined. enter up to eight values. which needs minimum delay and jitter). It is set to the queue-full state.. By default. Verify your entries. Configuring the Ingress Priority Queue You should use the priority queue only for traffic that needs to be expedited (for example. To return to the default CoS input queue threshold map. • • • configure terminal mls qos srr-queue input cos-map queue queue-id threshold threshold-id cos1. voice traffic. and 7 are mapped to queue 1 and threshold 1.cos8.. The CoS input queue threshold map shows the CoS value in the top row and the corresponding queue ID and threshold ID in the second row. CoS value 5 is mapped to queue 2 and threshold 1. the range is 1 to 2. queue 2 and threshold 2 (2-2). SRR shares the remaining bandwidth with both ingress queues and services them as specified by the weights configured with the mls qos srr-queue input bandwidth weight1 weight2 global configuration command. Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. This procedure is optional. Command Step 1 Step 2 Purpose Enter global configuration mode. and separate each value with a space. The range is 0 to 7.Chapter 27 Configuring QoS Configuring Standard QoS Beginning in privileged EXEC mode. and the queues are full and dropping frames). To return to the default WTD threshold percentages..cos8 For queue-id. CoS values 0 to 4. use the no mls qos srr-queue input cos-map global configuration command. the range is 1 to 3.. use the no mls qos srr-queue input threshold queue-id global configuration command. Step 3 Step 4 end show mls qos maps Return to privileged EXEC mode. For threshold-id. for example. For cos1. SRR services the priority queue for its configured weight as specified by the bandwidth keyword in the mls qos srr-queue input priority-queue queue-id bandwidth weight global configuration command. Catalyst 2960 Switch Software Configuration Guide OL-13563-01 27-15 . The priority queue is guaranteed part of the bandwidth to reduce the delay and jitter under heavy network traffic on an oversubscribed ring (when there is more traffic than the backplane can carry. 6. Map CoS values to an ingress queue and to a threshold ID. Then. follow these steps to map CoS values to an ingress queue and to set WTD thresholds.

or both) should be used? Catalyst 2960 Switch Software Configuration Guide 27-16 OL-13563-01 . the range is 1 to 2. Step 3 Step 4 end show mls qos interface queueing or show mls qos input-queue Return to privileged EXEC mode. To return to the default setting. assign the bandwidth percentage of the internal ring. and how much reserved and maximum memory is needed for the traffic type? How much of the fixed buffer space is allocated to the queue-set? Does the bandwidth of the port need to be rate limited? How often should the egress queues be serviced and which technique (shaped. and 10 percent of the bandwidth is allocated to it. Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. You will need to make decisions about these characteristics: • • • • • Which packets are mapped by CoS value to each queue and threshold ID? What drop percentage thresholds apply to the queue-set (four egress queues per port). Then SRR equally shares the remaining 90 percent of the bandwidth between queues 1 and 2 by allocating 45 percent to each queue: Switch(config)# mls qos srr-queue input priority-queue 1 bandwidth 10 Switch(config)# mls qos srr-queue input bandwidth 4 4 Configuring Egress Queue Characteristics Depending on the complexity of your network and your QoS solution. for example. By default. the priority queue is queue 2. Queue 1 is the priority queue with 10 percent of the bandwidth allocated to it. mls qos srr-queue input priority-queue queue-id bandwidth 0. The amount of bandwidth that can be guaranteed is restricted because a large value affects the entire ring and can degrade performance. follow these steps to configure the priority queue. For bandwidth weight. Command Step 1 Step 2 Purpose Enter global configuration mode. set the bandwidth weight to 0. This procedure is optional. shared. use the no mls qos srr-queue input priority-queue queue-id global configuration command. This example shows how to assign the ingress bandwidths to the queues. Verify your entries. The bandwidth ratios allocated to queues 1 and 2 is 4/(4+4). The range is 0 to 40. • • configure terminal mls qos srr-queue input priority-queue queue-id bandwidth weight For queue-id.Chapter 27 Configuring Standard QoS Configuring QoS Beginning in privileged EXEC mode. To disable priority queueing. Assign a queue as the priority queue and guarantee bandwidth on the internal ring if the ring is congested. you might need to perform all of the tasks in the next sections. SRR services queue 1 (the priority queue) first for its configured 10 percent of the bandwidth.

. Map CoS values to an egress queue and to a threshold ID. page 27-18 (optional) Configuration Guidelines Follow these guidelines when the expedite queue is enabled or the egress queues are serviced based on their SRR weights: • • • If the egress expedite queue is enabled. page 27-17 (optional) Configuring the Egress Expedite Queue. the range is 1 to 4. The drop-threshold percentage for threshold 3 is predefined. and separate each value with a space. Catalyst 2960 Switch Software Configuration Guide OL-13563-01 27-17 . For cos1. CoS values 4. enter up to eight values. By default. and SRR services this queue in shaped mode. If the egress expedite queue is disabled and the SRR shaped and shared weights are configured.. page 27-17 Mapping CoS Values to an Egress Queue and to a Threshold ID. it overrides the SRR shaped and shared weights for queue 1. Command Step 1 Step 2 Purpose Enter global configuration mode. Step 3 end Return to privileged EXEC mode. You should change them only when you have a thorough understanding of the egress queues and if these settings do not meet your QoS solution. This procedure is optional.Chapter 27 Configuring QoS Configuring Standard QoS These sections contain this configuration information: • • • • Configuration Guidelines. follow these steps to map CoS values to an egress queue and to a threshold ID. CoS value 5 is mapped to queue 1 and threshold 1.. CoS values 2 and 3 are mapped to queue 3 and threshold 1. For threshold-id. and 7 are mapped to queue 4 and threshold 1. the range is 1 to 3. 6. Note The egress queue default settings are suitable for most situations..cos8 For queue-id. CoS values 0 and 1 are mapped to queue 2 and threshold 1. SRR services this queue in shared mode. It is set to the queue-full state. If the egress expedite queue is disabled and the SRR shaped weights are not configured. Mapping CoS Values to an Egress Queue and to a Threshold ID You can prioritize traffic by placing packets with particular costs of service into certain queues and adjusting the queue thresholds so that packets with lower priorities are dropped. the shaped mode overrides the shared mode for queue 1. • • • configure terminal mls qos srr-queue output cos-map queue queue-id threshold threshold-id cos1. Beginning in privileged EXEC mode. page 27-18 (optional) Displaying Standard QoS Information.cos8. The range is 0 to 7.

When you configure this command.Chapter 27 Displaying Standard QoS Information Configuring QoS Command Step 4 Purpose Verify your entries. show mls qos maps Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file. SRR services this queue until it is empty before servicing the other queues. Catalyst 2960 Switch Software Configuration Guide 27-18 OL-13563-01 . the SRR weight and queue size ratios are affected because there is one less queue participating in SRR. Enable the egress expedite queue. follow these steps to enable the egress expedite queue. for example. which is disabled by default. Enable QoS on a switch. use the no mls qos srr-queue output cos-map global configuration command. Specify the egress port. Verify your entries. use the no priority-queue out interface configuration command. This procedure is optional. To disable the egress expedite queue. Configuring the Egress Expedite Queue You can ensure that certain packets have priority over all others by queuing them in the egress expedite queue. and enter interface configuration mode. This example shows how to enable the egress expedite queue. Switch(config)# interface gigabitethernet0/1 Switch(config-if)# priority-queue out Switch(config-if)# end Displaying Standard QoS Information To display standard QoS information. To return to the default CoS output queue threshold map. use one or more of the privileged EXEC commands in Table 27-6: Table 27-6 Commands for Displaying Standard QoS Information Command show mls qos Purpose Display global QoS configuration information. The CoS output queue threshold map shows the CoS value in the top row and the corresponding queue ID and threshold ID in the second row. Command Step 1 Step 2 Step 3 Step 4 Purpose Enter global configuration mode. queue 2 and threshold 2 (2-2). configure terminal mls qos interface interface-id priority-queue out Step 5 Step 6 Step 7 end show running-config copy running-config startup-config Return to privileged EXEC mode. Beginning in privileged EXEC mode. (Optional) Save your entries in the configuration file.

Chapter 27 Configuring QoS Displaying Standard QoS Information Table 27-6 Commands for Displaying Standard QoS Information (continued) Command show mls qos maps [cos-input-q | cos-output-q] show running-config | include rewrite Purpose Display QoS mapping information. Display the CoS transparency setting. Catalyst 2960 Switch Software Configuration Guide OL-13563-01 27-19 .

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->