Configuring Ingress Port Cos - Cisco Nexus 7000 Series Configuration Manual

Configuring Queuing and Scheduling on M-Series I/O Modules
The system-defined policy maps default-in-policy and default-out-policy are attached to all ports to which
you do not apply a queuing policy map. The default policy maps cannot be configured. For more information
about the default policy maps, see
This example shows that if you downgrade from Release 4.0(3) to Release 4.0(2) and enter the show
running-configuration command, the input default queuing policy has an unknown enum in the display:
switch# show running-config
version 4.0(2)
...
...
policy-map type queuing default-in-policy
class type queuing unknown enum 0
queue-limit percent 50
bandwidth percent 80
class type queuing unknown enum 0
queue-limit percent 50
bandwidth percent 20
If you copy and paste this configuration into any Cisco NX-OS release, the device sends errors while executing
all the commands starting from the policy-map type queuing default-in-policy command. You can ignore
these errors because they do not affect the performance of the device.

Configuring Ingress Port CoS

To make a port untrusted, set the CoS value to a static value.
Note • By default, ports are trusted (trust CoS) and the CoS field is not modified. When you configure the ingress
• For the untagged bridged traffic, a Cisco Nexus 7000 Series device ignores the Differentiated Services
• By default, Layer 3 ports trust DSCP and also copy the DSCP value to CoS.
You use the ingress default queues from the system-defined queue classes for the type of module to which
you want to apply the policy map. For the list of system-defined class maps for each type of module, see
6: System-Defined Type queuing Class Maps, on page
The CoS values set using this procedure apply to all packets that ingress the specified interfaces, not just to
the class-default packets. If you set the CoS value, the device modifies the value before ingress queuing and
scheduling so the CoS-modified packets are classified differently.
Note If you want to change the system-defined queuing class maps, you must either modify the configured queuing
policies or create new queuing policies and attach these policies to the affected interfaces. If you fail to do
so, you can render the default queuing or the configured queuing policies invalid, which might affect the
interfaces in multiple VDCs.
port CoS value, the port becomes untrusted.
Code Point (DSCP) and queues on ingress and egress directions, if the CoS value is 0.
Table 8: System-Defined Queuing Policy Maps, on page
15.
Cisco Nexus 7000 Series NX-OS Quality of Service Configuration Guide
Configuring Ingress Port CoS
18.
Table
95