Руководство По Проектированию для Cisco Cisco Nexus 5010 Switch
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 65 of 119
Traffic Classification with Fabric Extenders
The Cisco Nexus 2200 platform hardware can classify traffic based on the ACL on the fabric extender itself, but as
of Cisco NX-OS 5.1(3)N1(1), this capability is not configured, so for all fabric extenders, traffic classification is
based on CoS (Figure 26).
You can either set the HIF ports to specify a given value for untagged cos or let the CoS set by the server
determine the queue to which the traffic goes:
●
Traffic tagged with a given CoS is classified based on that CoS (the CoS value is used by the fabric
extender), and as a result the traffic is inserted into the queue associated with that CoS on the fabric
extender.
●
Untagged traffic can be classified by using the untagged cos command for an interface (but this setting
does not override the server CoS value).
●
After the traffic reaches the Cisco Nexus 5000 Series ports, it can be reclassified based on ACL matching
and so can be remarked.
Figure 26. Traffic Classification with Fabric Extenders
For the reverse direction, N2H traffic, you need to set the CoS for every QoS group so that the fabric extender can
properly queue and prioritize the traffic.
For instance, if you want the classes that were previously called VideoAndSignaling, Critical Data, and so on be
correctly scheduled based on the queuing policy for N2H traffic, then you need to configure network-qos policy to
assign a CoS to the traffic as follows:
policy-map type network-qos globalnetworkpolicy
class type network-qos VideoAndSignaling
set cos 4
class type network-qos Scavenger
set cos 1