Cisco 7604 Configuration Manual page 684
Ios software configuration guide
Hide thumbs
Also See for 7604:
- Configuration manual (742 pages) ,
- Installation manual (324 pages) ,
- User manual (98 pages)
Table of Contents
Advertisement
Configuring PFC QoS
Command
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:
Router# configure terminal
Enter configuration commands, one per line.
Router(config)# interface fastethernet 5/36
Router(config-if)# service-policy input pmap1
Router(config-if)# end
Cisco 7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SX
41-82
Do not attach a service policy to a port that is a member of an EtherChannel.
With DFCs installed, PFC2 does not support VLAN-based QoS: you cannot enter the mls qos
vlan-based command or attach service policies to VLAN interfaces.
PFC QoS supports the output keyword only with a PFC3 and only on Layer 3 interfaces (either LAN
ports configured as Layer 3 interfaces or VLAN interfaces). With a PFC3, 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.
Aggregate policing works independently on each DFC-equipped switching module and
independently on the PFC, which supports any non-DFC-equipped switching modules. Aggregate
policing does not combine flow statistics from different DFC-equipped switching modules. You can
display aggregate policing statistics for each DFC-equipped switching module and for the PFC and
any non-DFC-equipped switching modules supported by the PFC.
Each PFC or DFC polices independently, which might affect QoS features being applied to traffic
that is distributed across the PFC and any DFCs. Examples of these QoS feature are:
–
Policers applied to a port channel interface.
Policers applied to a switched virtual interface.
–
Egress policers applied to either a Layer 3 interface or an SVI. Note that PFC QoS performs
–
egress policing decisions at the ingress interface, on the PFC or ingress DFC.
Policers affected by this restriction deliver an aggregate rate that is the sum of all the independent
policing rates.
With a PFC3, 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.
Purpose
Exits configuration mode.
Verifies the configuration.
End with CNTL/Z.
Chapter 41
Configuring PFC QoS
OL-4266-08
- Quick Links:
- Supported Hardware and Software
Hide quick links:
Advertisement
Chapters
Table of Contents
