Cisco WS-SUP32-GE-3B - Supervisor Engine 32 Software Configuration Manual page 601

Chapter 38 Configuring PFC QoS
This example shows how to verify the configuration:
Router# show policy-map max-pol-ipp5
Policy Map max-pol-ipp5
class
class ipp5
policed-dscp-transmit
policed-dscp-transmit
Router#
Attaching a Policy Map to an Interface
To attach a policy map to an interface, perform this task:
Command
Step 1
Router(config)# interface {{vlan vlan_ID} |
1
{type slot/port[.subinterface]} | {port-channel
number[.subinterface]}}
Step 2
Router(config-if)# service-policy [input |
output] policy_map_name
Router(config-if)# no service-policy [input |
output] policy_map_name
Step 3
Router(config-if)# end
Step 4
Router# show policy-map interface {{vlan vlan_ID}
1
| {type slot/port} | {port-channel number}}
1. type = ethernet, fastethernet, gigabitethernet, or tengigabitethernet
When attaching a policy map to an interface, note the following information:
•
•
•
•
•
•
•
This example shows how to attach the policy map named pmap1 to Fast Ethernet port 5/36:
OL-11439-03
ipp5
police flow 10000000 10000 conform-action set-prec-transmit 6 exceed-action
trust precedence
police 2000000000 2000000 2000000 conform-action set-prec-transmit 6 exceed-action
Do not attach a service policy to a port that is a member of an EtherChannel.
PFC QoS supports the output keyword only with a PFC3B and only on Layer 3 interfaces (either
LAN ports configured as Layer 3 interfaces or VLAN interfaces). With a PFC3B, you can attach
both an input and an output policy map to a Layer 3 interface.
VLAN-based or port-based PFC QoS on Layer 2 ports is not relevant to policies attached to Layer
3 interfaces with the output keyword.
Policies attached with the output keyword do not support microflow policing.
You cannot attach a policy map that configures a trust state with the service-policy output
command.
Filtering based on IP precedence or DSCP in policies attached with the output keyword uses the
received IP precedence or DSCP values. Filtering based on IP precedence or DSCP in policies
attached with the output keyword is not based on any IP precedence or DSCP changes made by
ingress QoS.
With a PFC3B, when you apply both ingress policing and egress policing to the same traffic, both
the input policy and the output policy must either mark down traffic or drop traffic. PFC QoS does
not support ingress markdown with egress drop or ingress drop with egress markdown.
Catalyst Supervisor Engine 32 PISA Cisco IOS Software Configuration Guide, Release 12.2ZY
Purpose
Selects the interface to configure.
Attaches a policy map to the interface.
Removes the policy map from the interface.
Exits configuration mode.
Verifies the configuration.
Configuring PFC QoS
38-67