Greetings.
Please take a look at https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Network-Mgmt/3-2/b_UCSM_Network_Mgmt_Guide_3_2.pdf which covers a lot of UCSM related QOS/COS settings.
The UCSM allows you to define your QOS classes.
"A quality of service (QoS) policy assigns a system class to the outgoing traffic for a vNIC or vHBA. This
system class determines the quality of service for that traffic. For certain adapters, you can also specify
additional controls on the outgoing traffic, such as burst and rate.
You must include a QoS policy in a vNIC policy or vHBA policy and then include that policy in a service profile to configure the vNIC or vHBA"
If your case, it sounds like you are already marking different classes at the dVS/OS level, rather than have the service profile/vnic mark the traffic as it egresses the vnic. For this, you will then want to configure a QOS policy that is assigned to the vnics, and is set to "Host control = FULL"
Host Control field:
Whether Cisco UCS controls the class of service (CoS). This can be one of the following:
• None—Cisco UCS uses the CoS value associated with the priority selected in the Priority drop-down list regardless of the CoS value assigned by the host.
• Full—If the packet has a valid CoS value assigned by the host, Cisco UCS uses that value. Otherwise, Cisco UCS uses the CoS value associated with the priority selected in the Priority drop-down list.
So, you'll allow your OS/virtual switch level do the actual marking, but you still need to define the QOS classes and policies so the UCSM can treat your traffic with the appropriate prioritization.
Thanks,
Kirk...
