Cisco Cisco Nexus 5010 Switch Guida Alla Progettazione
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 31 of 119
class-map type queuing Scavenger
match qos-group 2
class-map type queuing VideoAndSignaling
match qos-group 4
policy-map type queuing globalqueuingpolicy
class type queuing CriticalData
bandwidth percent 6
class type queuing Scavenger
bandwidth percent 1
class type queuing VideoAndSignaling
bandwidth percent 20
system qos
service-policy type queuing output globalqueuingpolicy
Something is missing from the preceding configuration. If you apply it on a Cisco Nexus 5010 or 5020, the
configuration is rejected. The reason for the rejection is that the default allocation for class-default is 50 percent of
the bandwidth, and the default allocation for class-fcoe is also 50 percent of the bandwidth.
You can fix the configuration by adding the class-default settings (class-default exists by default):
policy-map type queuing globalqueuingpolicy
class type queuing CriticalData
bandwidth percent 6
class type queuing Scavenger
bandwidth percent 1
class type queuing VideoAndSignaling
bandwidth percent 20
class type queuing class-default
bandwidth percent 10
Jumbo Frames
Jumbo frames are an important feature in 10 Gigabit Ethernet data centers because they allow servers to fully use
the available bandwidth with less CPU utilization than with regular Ethernet frames.
The jumbo frames implementation on the Cisco Nexus 5000 Series is designed to allow multiple MTUs for different
traffic classes on the same link.
Global Jumbo Frames Configuration
Jumbo frames on the Cisco Nexus 5000 Series are configured as part of the QoS configuration for system classes.
Jumbo frames configuration is performed as follows:
policy-map type network-qos jumbo
class type network-qos class-default
mtu 9000
system qos