Cisco Catalyst 4500 Series, Software Configuration Manual

Page: 1174 / 2086

44-78
Catalyst 4500 Series Switch, Cisco IOS Software Configuration Guide - Cisco IOS XE 3.9.xE and IOS 15.2(5)Ex
Chapter 44 Configuring Quality of Service
Configuring QoS on a Standalone Supervisor Engine 6-E/6L-E or Supervisor Engine 7-E/7L-E/8-E
Switch(config)# interface gigabitEthernet3/1
Switch(config-if)# service-policy input p1
Switch(config-if)# exit
Use the show commands described in the QoS section to display the policy-map configuration and
interface specific policy-map statistics.
Example 3
Assume that there are two active flows on FastEthernet interface 6/1:
With the following configuration, each flow is policed to 1000000 bps with an allowed 9000 burst value.
Switch(config)#
flow record r1
Switch(config-flow-record)# match ipv4 source address
Switch(config-flow-record)# match ipv4 destination address
Switch(config-flow-record)#
match transport tcp source-port
Switch(config-flow-record)# match transport tcp destination-port
Switch(config-flow-record)# match transport udp source-port
Switch(config-flow-record)#
match transport udp destination-port
Switch(config-flow-record)# exit
Switch(config)# class-map match-all c1
Switch(config-cmap)#
match flow record r1
Switch(config-cmap)# exit
Switch(config)# policy-map p1
Switch(config-pmap)#
class c1
Switch(config-pmap-c)# police 1000000 9000
Switch(config-pmap-c)# exit
Switch(config-pmap)#
exit
Switch(config)# interface fastEthernet 6/1
Switch(config-if)# service-policy input p1
Switch(config-if)#
end
Configuration Guidelines
The general guidelines for creating, configuring, modifying, deleting a flow based QoS policy and
attaching (and detaching) a flow based QoS policy to a supported target is the same as described in the
QoS section. The following description and restriction applies to Flow based QoS policy:
•
A classmap can have multiple match statements but only one FNF flow record can be specified in a
class-map.
•
A flow record must have at least one key field before it can be used in a classmap. Non-key fields
can be present in the flow record. However, all the non-key fields are ignored by microflow QoS.
Only key-fields are used for flow creation.
• If a FNF flow record is referenced in any class-map, the flow record cannot be modified. Remove
the flow record from all classmaps before modifying it.
•
A classmap with a FNF flow record must be configured as match-all ; traffic hitting the class-map
must satisfy all match criteria in the class-map.
Table 44-4
SrcIp
DStIp IPProt SrcL4Port DstL4Port
192.168.10.10 192.168.20.20 20 6789 81
192.168.10.10 192.168.20.20 20 6789 21