Cisco Cisco Nexus 5010 Switch Guida Alla Progettazione
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 34 of 119
service-policy type qos input jumbo-per-port
service-policy type network-qos mp-nq-jumbo-per-port
interface Ethernet105/1/9
description interface_with_jumbo
untagged cos 5
switchport access vlan 50
You can verify that the configuration of jumbo frames was successful by running the show queuing interface
<fabric extender interface> command:
Ethernet105/1/9 queuing information:
Input buffer allocation:
Qos-group: 0 5 (shared)
frh: 8
drop-type: drop
cos: 0 1 2 3 4 5 6
xon xoff buffer-size
---------+---------+-----------
0 126720 151040
Queuing:
queue qos-group cos priority bandwidth mtu
--------+------------+--------------+---------+---------+----
2 0 0 1 2 3 4 6 WRR 50 1600
7 5 5 WRR 0 9120
Multicast Optimize Feature
Like unicast traffic, multicast traffic is queued on the ingress unified port controller to wait for a grant from the
scheduler. Multicast traffic can be queued either based on the traffic class (one queue for each traffic class) or
based on the outgoing interface list (the list of interfaces subscribed to that multicast group). With the first type of
queuing, a multicast frame is put into one of 8 queues. With the second type of queuing, a multicast frame is put
into one of 120 virtual output queues (VoQs).
By using 120 VoQs to queue multicast traffic based on the outgoing interface list, you achieve better multicast
performance for line-rate multicast throughput and reduce the chances for head-of-line blocking because all frames
in a given queue are associated with the same list of egress interfaces.
The multicast optimize feature allows multicast traffic to be queued into the 120 VoQs available on the Cisco Nexus
5500 platform. The multicast optimize feature can be enabled for only one QoS group (or traffic class), and by
default it is enabled for class-default.
If traffic classification is based on CoS (or DSCP or ACL), and if some multicast traffic may be associated with a
different QoS group than class-default, the traffic is queued according to the first scheme that was described. In
this case, multicast traffic is queued based on the QoS group in one of the 8 queues associated with the traffic
class and not into one of the 120 VoQs.