Enabling Dscp Transparency Mode; Configuring The Dscp Trust State On A Port Bordering Another Qos Domain - Cisco 3020 - Catalyst Blade Switch Configuration Manual

Chapter 27 Configuring QoS

Enabling DSCP Transparency Mode

The switch supports the DSCP transparency feature. It affects only the DSCP field of a packet at egress.
By default, DSCP transparency is disabled. The switch modifies the DSCP field in an incoming packet,
and the DSCP field in the outgoing packet is based on the quality of service (QoS) configuration,
including the port trust setting, policing and marking, and the DSCP-to-DSCP mutation map.
If DSCP transparency is enabled by using the no mls qos rewrite ip dscp command, the switch does not
modify the DSCP field in the incoming packet, and the DSCP field in the outgoing packet is the same as
that in the incoming packet.
Regardless of the DSCP transparency configuration, the switch modifies the internal DSCP value of the
packet, which the switch uses to generate a class of service (CoS) value that represents the priority of
the traffic. The switch also uses the internal DSCP value to select an egress queue and threshold.
Beginning in privileged EXEC mode, follow these steps to enable DSCP transparency on a switch:
Command
Step 1
configure terminal
Step 2 mls qos
Step 3 no mls qos rewrite ip dscp
Step 4 end
Step 5
show mls qos interface [interface-id] Verify your entries.
Step 6 copy running-config startup-config
To configure the switch to modify the DSCP value based on the trust setting or on an ACL by disabling
DSCP transparency, use the mls qos rewrite ip dscp global configuration command.
If you disable QoS by using the no mls qos global configuration command, the CoS and DSCP values
are not changed (the default QoS setting).
If you enter the no mls qos rewrite ip dscp global configuration command to enable DSCP transparency
and then enter the mls qos trust [cos | dscp] interface configuration command, DSCP transparency is
still enabled.

Configuring the DSCP Trust State on a Port Bordering Another QoS Domain

If you are administering two separate QoS domains between which you want to implement QoS features
for IP traffic, you can configure the switch ports bordering the domains to a DSCP-trusted state as shown
in Figure
stage of QoS. If the two domains use different DSCP values, you can configure the
DSCP-to-DSCP-mutation map to translate a set of DSCP values to match the definition in the other
domain.
OL-8915-01
Purpose
Enter global configuration mode.
Enable QoS globally.
Enable DSCP transparency. The switch is configured to not modify the
DSCP field of the IP packet.
Return to privileged EXEC mode.
(Optional) Save your entries in the configuration file.
27-13. Then the receiving port accepts the DSCP-trusted value and avoids the classification
Cisco Catalyst Blade Switch 3020 for HP Software Configuration Guide
Configuring Standard QoS
27-39