hit counter script

Cisco 7604 Configuration Manual page 617

Ios software configuration guide
Hide thumbs Also See for 7604:
Table of Contents

Advertisement

Chapter 41
Configuring PFC QoS
Egress DSCP Mutation with a PFC3
With a PFC3, you can configure 15 egress DSCP mutation maps to mutate the
before it is written in the egress ToS byte. You can attach egress DSCP mutation maps to any interface
that PFC QoS supports.
Note
Egress ToS Byte
Except when
final internal or mutated DSCP value and sends it to the egress port to be written into IP packets. For
trust DSCP and untrusted IP traffic, the ToS byte includes the original two least-significant bits from the
received ToS byte.
The internal or mutated DSCP value can mimic an IP precedence value (see the
DSCP Values" section on page
Egress PFC QoS Interfaces
You can attach an output policy map to a Layer 3 interface (either a LAN port configured as a Layer 3
interface or a VLAN interface) to apply a policy map to egress traffic.
Note
Egress ACL Support for Remarked DSCP
Egress ACL support for remarked DSCP is also known as packet recirculation.
Note
With a PFC3, Release 12.2(18)SXE and later releases support egress ACL support for remarked DSCP,
which enables IP precedence-based or DSCP-based egress QoS filtering to use any IP precedence or
DSCP policing or marking changes made by ingress PFC QoS.
Without egress ACL support for remarked DSCP, egress QoS filtering uses received IP precedence or
DSCP values; it does not use any IP precedence or DSCP changes made by ingress PFC QoS as the result
of policing or marking.
The PFC3 provides egress PFC QoS only for Layer 3-switched and routed traffic on egress Layer 3
interfaces (either LAN ports configured as Layer 3 interfaces or VLAN interfaces).
You configure egress ACL support for remarked DSCP on ingress Layer 3 interfaces (either LAN ports
configured as Layer 3 interfaces or VLAN interfaces).
OL-4266-08
If you configure egress DSCP mutation, PFC QoS does not derive the egress CoS value from the
mutated DSCP value.
The PFC2 does not support egress DSCP mutation.
DSCP transparency
Output policies do not support microflow policing.
With a PFC3, you cannot apply microflow policing to ARP traffic.
You cannot set a trust state in an output policy.
Cisco 7600 Series Router Cisco IOS Software Configuration Guide, Release 12.2SX
is enabled, PFC QoS creates a ToS byte for egress IP traffic from the
41-56).
Understanding How PFC QoS Works
internal DSCP
value
"IP Precedence and
41-15

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

761376067609-s7600 series

Table of Contents