Cisco Catalyst 3750 Command Reference Manual page 285
Hide thumbs
Also See for Catalyst 3750:
- Command reference manual (1154 pages) ,
- Software configuration manual (926 pages) ,
- Hardware installation manual (231 pages)
Table of Contents
Advertisement
Chapter 2
Catalyst 3750 Switch Cisco IOS Commands
policy-map
Only one policy map per ingress port or SVI is supported. You can apply the same policy map to multiple
physical ports or SVIs.
In software releases earlier than Cisco IOS Release 12.2(25)SE, you can apply a policy map and
configure policing only on physical ports. You can configure the trust state, set a new DSCP or IP
precedence value in the packet, or define an individual or aggregate policer. For more information, see
the "Policing on Physical Ports" section in the "Configuring QoS" chapter of the software configuration
guide for this release.
In Cisco IOS Release 12.2(25)SE or later, you can apply a nonhierarchical policy maps to physical ports
or to SVIs. A nonhierarchical policy map is the same as a port-based policy maps in software releases
earlier than Cisco IOS Release 12.2(25)SE. However, a hierarchical policy map can only be applied to
SVIs.
A hierarchical policy map has two levels. The first level, the VLAN level, specifies the actions to be
taken against a traffic flow on an SVI. The second level, the interface level, specifies the actions to be
taken against the traffic on the physical ports that belong to the SVI and are specified in the
interface-level policy map.
In a primary VLAN-level policy map, you can only configure the trust state or set a new DSCP or IP
precedence value in the packet. In a secondary interface-level policy map, you can only configure
individual policers on physical ports that belong to the SVI.
After the hierarchical policy map is attached to an SVI, an interface-level policy map cannot be modified
or removed from the hierarchical policy map. A new interface-level policy map also cannot be added to
the hierarchical policy map. If you want these changes to occur, the hierarchical policy map must first
be removed from the SVI.
For more information about hierarchical policy maps, see the "Policing on SVIs" section in the
"Configuring QoS" chapter of the software configuration guide for this release.
Examples
This example shows how to create a policy map called policy1. When attached to the ingress port, it
matches all the incoming traffic defined in class1, sets the IP DSCP to 10, and polices the traffic at an
average rate of 1 Mbps and bursts at 20 KB. Traffic exceeding the profile is marked down to a DSCP
value obtained from the policed-DSCP map and then sent.
Switch(config)# policy-map policy1
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set dscp 10
Switch(config-pmap-c)# police 1000000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
This example shows how to configure multiple classes in a policy map called policymap2:
Switch(config)# policy-map policymap2
Switch(config-pmap)# class class1
Switch(config-pmap-c)# set dscp 10
Switch(config-pmap-c)# police 100000 20000 exceed-action policed-dscp-transmit
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class2
Switch(config-pmap-c)# trust dscp
Switch(config-pmap-c)# police 100000 20000 exceed-action drop
Switch(config-pmap-c)# exit
Switch(config-pmap)# class class3
Switch(config-pmap-c)# set dscp 0 (no policer)
Switch(config-pmap-c)# exit
Catalyst 3750 Switch Command Reference
2-257
78-16181-03
Advertisement
Table of Contents
