1 / 21

3.4: Using MQC for Implementing QoS

3.4: Using MQC for Implementing QoS. Objectives. Identify the features of each method for QoS policy implementation. Describe the guidelines for using CLI to implement QoS policy. Describe the Modular QoS Command Line (MQC). Methods for Implementing QoS Policy. Configuring QoS at the CLI.

Download Presentation

3.4: Using MQC for Implementing QoS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 3.4: Using MQC for Implementing QoS

  2. Objectives • Identify the features of each method for QoS policy implementation. • Describe the guidelines for using CLI to implement QoS policy. • Describe the Modular QoS Command Line (MQC)

  3. Methods for Implementing QoS Policy

  4. Configuring QoS at the CLI • Uses the CLI via console and Telnet • Traditional method • Nonmodular • Cannot separate traffic classification from policy definitions • Time-consuming and potentially error-prone task • Used to augment and fine-tune newer Cisco AutoQoS method

  5. Guidelines for Using the CLI Configuration Method • Build a traffic policy: Identify the traffic pattern. Classify the traffic. Prioritize the traffic. Select a proper QoS mechanism: Queuing Compression • Apply the traffic policy to the interface.

  6. For interactive traffic, you can use CQ and TCP header compression. • interface multilink • ip address 10.1.61.1 255.255.255.0 • load-interval 30 • custom-queue-list 1 • ppp multilink • ppp multilink fragment-delay 10 • ppp multilink interleave • multilink-group 1 • ip tcp header-compression iphc-format • ! • queue-list 1 protocol ip 2 tcp 23 Legacy CLI QoS Example

  7. Modular QoS CLI • A command syntax for configuring QoS policy • Reduces configuration steps and time • Configures policy, not “raw” per-interface commands • Uniform CLI across major Cisco IOS platforms • Uniform CLI structure for all QoS features • Separates classification engine from the policy

  8. Modular QoS CLI Components

  9. Step 1: Creating Class Maps:“What Traffic Do We Care About?” • Each class is identified using a class map. • A traffic class contains three major elements: A case-sensitive name A series of match commands An instruction on how to evaluate the match commands if more than one match command exists in the traffic class • Class maps can operate in two modes: Match all: All conditions have to succeed. Match any: At least one condition must succeed. • The default mode is match all.

  10. Enter class-map configuration mode. Specify the matching strategy. router(config)# class-map [match-all | match-any] class-map-name router(config-cmap)# match any match not match-criteria router(config-cmap)# description description Configuring Class Maps • Use at least one condition to match packets. • Use descriptions in large and complex configurations. The description has no operational meaning.

  11. Standard ACL Classifying Traffic with ACLs router(config)# access-list access-list-number {permit | deny | remark} source [mask] • Extended ACL router(config)# access-list access-list-number {permit | deny} protocolsourcesource-wildcard [operatorport] destinationdestination-wildcard [operatorport] [established] [log] • Use an ACL as a match criterion router(config-cmap)# match access-group access-list-number

  12. Step 2: Policy Maps: “What Will Be Done to This Traffic?” • A policy map defines a traffic policy, which configures the QoS features associated with a traffic class that was previously identified using a class map. • A traffic policy contains three major elements: A case-sensitive name A traffic class The QoS policy that is associated with that traffic class • Up to 256 traffic classes can be associated with a single traffic policy. • Multiple policy maps can be nested to influence the sequence of QoS actions.

  13. router(config)# policy-map policy-map-name router(config-pmap)# class {class-name | class-default} router(config-pmap)# class class-namecondition Configuring Policy Maps • Enter policy-map configuration mode. Policy maps are identified by a case-sensitive name. • Enter the per-class policy configuration mode by using the name of a previously configured class map. Use the class-default name to configure the policy for the default class. • Optionally, you can define a new class map by entering the condition after the name of the new class map. Uses the match-any strategy.

  14. router(config-if)# service-policy {input | output} policy-map-name Step 3: Attaching Service Policies: “Where Will This Policy Be Implemented?” • Attach the specified service policy map to the input or output interface class-map HTTP match protocol http ! policy-map PM class HTTP bandwidth 2000 class class-default bandwidth 6000 ! interface Serial0/0 service-policy output PM Service policies can be applied to an interface for inbound or outbound packets

  15. Modular QoS CLI Configuration Example router(config)# class-map match-any business-critical-traffic router(config-cmap)# match protocol http url “*customer*” router(config-cmap)# match protocol http url citrix router(config)# policy-map myqos policy router(config-pm am)# class business-critical-traffic router(config-pm am-c)# bandwidth 1000 router(config)# interface serial 0/0 router(config-if)# service-policy output myqos policy 1 2 3

  16. Boolean Nesting Goal Goal: Find books that cover the salaries of either football players or hockey players. Solution: Boolean (salaries AND [football players OR hockey players]).

  17. MQC Example • Voice traffic needs priority, low delay, and constant bandwidth. • Interactive traffic needs bandwidth and low delay.

  18. MQC Configuration hostname Office ! class-map VoIP match access-group 100 class-map Application match access-group 101 ! policy-map QoS-Policy class VoIP priority 100 class Application bandwidth 25 class class-default fair-queue ! interface Serial0/0 service-policy output QoS-Policy ! access-list 100 permit ip any any precedence 5 access-list 100 permit ip any any dscp ef access-list 101 permit tcp any host 10.1.10.20 access-list 101 permit tcp any host 10.1.10.40 Classification QoS Policy QoS Policy on Interface Classification

  19. router# show class-map router# show policy-map router# show policy-map interface typenumber Basic Verification Commands • Display the class maps • Display the policy maps • Display the applied policy map on the interface

  20. Summary • There are 4 basic ways to implement QoS policy on Cisco devices: CLI, MQC, AutoQoS and SDM. Choosing a method will depend on the complexity of the network on the expertise of the administrator. • The Cisco MQC offers significant advantages over the legacy CLI method for implementing QoS. By using MQC, a network administrator can significantly reduce the time and effort it takes to configure QoS in a complex network. • There are three steps to follow when configuring QoS using Cisco MQC configuration. Each step answers a question concerning the classes assigned to different traffic flows: What traffic do we care about? What will happen to the classified traffic? Where will the policy apply?

  21. Self Check • What is a class map? • How many class maps can be configured on a Cisco router? • What is a traffic policy? • What are the 3 basic elements of a traffic policy? • What command is used to assign a policy map to an interface?

More Related