Qos-group: 0
frh: 8
drop-type: drop
cos: 0 1 2 3 4 5 6
xon xoff buffer-size
---------+---------+-----------
0 126720 151040
Queueing:
queue qos-group cos priority bandwidth mtu
--------+------------+--------------+---------+---------+----
ctrl-hi n/a 7 PRI 0 2400
ctrl-lo n/a 7 PRI 0 2400
2 0 0 1 2 3 4 5 6 WRR 100 9440
Queue limit: 0 bytes
Queue Statistics:
queue rx tx flags
------+---------------+---------------+-----
0 0 0 ctrl
1 0 0 ctrl
2 0 0 data
Port Statistics:
rx drop rx mcast drop rx error tx drop mux ovflow
---------------+---------------+---------------+---------------+--------------
0 0 0 0 InActive
Priority-flow-control enabled: no
Flow-control status: rx 0x0, tx 0x0, rx_mask 0x0
cos qos-group rx pause tx pause masked rx pause
-------+-----------+---------+---------+---------------
0 0 xon xon xon
1 0 xon xon xon
2 0 xon xon xon
3 0 xon xon xon
4 0 xon xon xon
5 0 xon xon xon
6 0 xon xon xon
7 n/a xon xon xon
•
Fabric Port Queuing Restrictions
◦
For FEXs that are connected to M-series uplinks, the queuing structure is different on FEX host
interfaces and FEX fabric interfaces. The M series queuing policies must be consistent with the
FEX queuing policies.
◦
DSCP-based queuing is not supported on M1 FEX fabric uplinks.
◦
You cannot modify the CoS 0-4 mappings in the default queue on M1 FEX fabric uplinks.
•
MTU
◦
FEX queue MTU configurations are derived from type network-QoS policy-map templates. MTU
changes are applied on cloned network-QoS policy maps. The MTU that is configured on a FEX
port must match the MTU in the network-QoS policy map so that the FEX MTU can be applied
to the FEX host interfaces. For more information, see the Cisco Nexus 7000 Series NX-OS Quality
of Service Configuration Guide.
Cisco Nexus 2000 Series NX-OS Fabric Extender Software Configuration Guide for Cisco Nexus 7000 Series
Switches, Release 5.2
18
Overview
FEX Queuing Support