The modular QoS CLI (MQC).

  • MQC step 1 allows us to create various classifications (class map)
  • MQC step 2 allows us to create a policy (Policy Map)
  • MQC step 3 apply a policy to an interface (inbound or outbound) (Service Policy)

Class Maps;

categories of traffic

contains 3 major elements; case sensitive name, match commands & instruction on how to evaluate these match commands

Class maps can operate in 2 modes

  • Match all (this is the default match)
  • Match any

Configuring class maps;

  • router(config)# class-map [match-all | match-any]
  • router(config-cmap)# match              # use at least one condition to match packets
  • router(config-cmap)# description
  • router(config-cmap)# match not     # the not keyword inverts the condition
  • router(config-cmap)# match class-map    # a class map can use another for classification
  • router(config-cmap)# match any            # can be used to match all packets

show class-map [class-map]

Configuring policy maps;

  • router(config)# policy-map
  • router(config-pmap)# class {class-name | class-default}    #enter the per class policy configuration mode
  • router(config-pmap)# class condition # optionally you can define a new class map by entering the condition after the name  of the new class-map
  • router(config-pmap)# description
  • router(config-pmap-c)#    # Per-class service policies are configured with in the per-class policy-map configuration mode. MQC supports CBFWQ, Low-latency queueing, class-based policing, class-based shaping, class-based marking.
  • router(config-pmap-c)# service-policy <policy -map-name>   # policy maps usually applied to interfaces but nested policy maps can be applied directly inside other policy maps to influence seq of QoS actions.

show policy-map [policy-map]

show policy-map interface [input|output]

Configuring service-policy;

  • router(config-if)# service-policy {input | output}
Show Comments

Get the latest posts delivered right to your inbox.