Quality Of Service - Cisco Nexus 1000V Deployment Manual

Figure 33.
In the service profile used to create infrastructure vNICs, fabric failover is enabled, and Host Control is set to
None. This configuration is used because of infrastructure traffic is going directly to the Cisco UCS vNIC. For this
traffic type, configure the CoS markings in the Cisco UCS service profile.

Quality of Service

Another distinguishing feature of Cisco UCS is the capability of the VIC to perform CoS-based queuing in
hardware. CoS is a value marked on Ethernet packets to indicate the priority in the network. The Cisco UCS VIC
has eight traffic queues, which use CoS values of 0 through 7. The VIC also allows the network administrator to
specify a minimum bandwidth that must be reserved for each CoS during congestion. This setting allows the
physical Ethernet adapter to be shared by multiple vNICs and helps ensure a minimum bandwidth during
congestion.
You should create separate classes of service for storage, live migration, cluster, host management and virtual
machine data. Table 1 shows an example in which data from the different vNICs is segmented into different
classes.
Table 1 Sample QoS Classification and Bandwidth Reservation.
Table 1.
Traffic Type
Host Management and Cluster
Live Migration
Storage
Virtual Machine Data Low Priority
Virtual Machine Data High Priority
For all virtual machine interfaces (vEths) connected to the Cisco Nexus 1000V, the classification and CoS marking
must be configured on the Cisco Nexus 1000V. The Cisco Nexus 1000V offers detailed QoS classification (based
on Layer 2, Layer 3, and Layer 4 headers), allowing the administrator to prioritize certain application flows. This
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Host Control Set to Full for Cisco Nexus 1000V Uplink vNICs
Virtual Machine Data High Priority
COS
2
1
3
4
5
Minimum Bandwidth (Gbps)
10
10
40
10
30
Page 40 of 48