FCoE Cookbook for HP Virtual Connect Version 4.20 Firmware Enhancements May 2014

142
QoS on Nexus 5500 series
On the Nexus 5500 series, enabling the FCoE feature does not create automatically no-drop policies like on the Nexus
5000 series, so before enabling FCoE, it is necessary to configure the QoS policies manually by including class-fcoe in
each of the following policy types:
 Network-Qos
 Queuing
 Qos
The following is an example of a service policy that needs to be configured:
o class-map type qos class-fcoe
o class-map type queuing class-fcoe
o match qos-group 1
o class-map type queuing class-all-flood
o match qos-group 2
o class-map type queuing class-ip-multicast
o match qos-group 2
o class-map type network-qos class-fcoe
o match qos-group 1
o class-map type network-qos class-all-flood
o match qos-group 2
o class-map type network-qos class-ip-multicast
o match qos-group 2
o system qos
o service-policy type qos input fcoe-default-in-policy
o service-policy type queuing input fcoe-default-in-policy
o service-policy type queuing output fcoe-default-out-policy
o service-policy type network-qos fcoe-default-nq-policy
To verify the FCoE system class is active on the interface connected to VC, enter:
 show queuing interface Ethernet 1/5