Policy Types - Cisco Nexus 5000 Series Configuration Manual
Nx-os quality of service
Hide thumbs
Also See for Nexus 5000 Series:
- Cli configuration manual (660 pages) ,
- Configuration manual (334 pages) ,
- Command reference manual (196 pages)
Table of Contents
Advertisement
Policy Types
• FCoE system class (For the Cisco Nexus 5548 switch)
Policy Types
The Cisco Nexus 5000 Series switch supports a number of policy types. You create class maps in the policy
types.
There are three policy types. The following QoS parameters can be specified for each type of class:
• Type network-qos—A network-qos policy is used to instantiate system classes and associate parameters
Cisco Nexus 5000 Series NX-OS Quality of Service Configuration Guide
8
For the Cisco Nexus 5548 switch, the class-fcoe is not automatically created. Before you enable FCoE
on the Cisco Nexus 5548 switch running Cisco NX-OS Release 5.0(2)N1(1), you must enable class-fcoe
in the three types of qos policies:
◦ type qos policy maps
◦ type network-qos policy map (attached to system qos)
◦ type queuing policy map (class-fcoe must be configured with a non-zero bandwidth percentage
for input queuing policy maps.
When class-fcoe is not included in the qos policies, vFC interfaces do not come up and increased
drops occur.
The Cisco Nexus 5548 switch supports five user-defined classes and one default drop
Note
system class.
with those classes that are of system-wide scope.
◦Classification—The traffic that matches this class are as follows:
◦QoS Group—A class-map of type network-qos identifies a system-class and is matched by
its associated qos-group.
◦Policy—The actions that are performed on the matching traffic are as follows:
Note
A network-qos policy can only be attached to the system qos target.
◦MTU—The MTU that needs to be enforced for the traffic that is mapped to a system class.
Each system class has a default MTU and the system class MTU is configurable.
◦Multicast optimization—This configuration specifies if the performance of multicast traffic
mapped to this class will be optimized.
◦Pause no-drop—No drop specifies lossless service for the system class. Drop specifies that
tail drop is used (arriving packets are dropped when the queue reaches its allocated size)
when a queue for this system class is full.
Configuring QoS
OL-20921-01
- Quick Links:
- Verifying the Jumbo Mtu
Hide quick links:
Advertisement
Table of Contents
