12-07-2012 06:52 AM - edited 03-07-2019 10:27 AM
I am looking to implement a QoS policy on a pair of Nexus 5548 UPs. FCoE is a factor here. I have created the following configuration and would like to get a few pairs of eyes to take a look at this for a quick sanity check.
I'd appreciate a quick look at this to help make sure this config is valid. Also, I realize I'm applying an MTU of 9216 to all classes right now, this will be phased out incrementally.
class-map type qos match-all class-platinum
match cos 5
class-map type qos match-all class-gold
match cos 4
class-map type qos class-fcoe
match cos 3
class-map type qos match-all class-silver
match cos 2
class-map type qos match-all class-bronze
match cos 1
class-map type queuing class-platinum
match qos-group 5
class-map type queuing class-gold
match qos-group 4
class-map type queuing class-silver
match qos-group 3
class-map type queuing class-bronze
match qos-group 2
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type queuing class-fcoe
match qos-group 1
policy-map type qos system-level-qos
class class-platinum
set qos-group 5
class class-gold
set qos-group 4
class class-silver
set qos-group 3
class class-bronze
set qos-group 2
class class-fcoe
set qos-group 1
class class-default
policy-map type queuing egress_queueing_policy
class type queuing class-platinum
priority
class type queuing class-gold
bandwidth percent 20
class type queuing class-silver
bandwidth percent 20
class type queuing class-bronze
bandwidth percent 20
class type queuing class-fcoe
bandwidth percent 0
class type queuing class-default
bandwidth percent 40
class-map type network-qos class-platinum
match qos-group 5
class-map type network-qos class-gold
match qos-group 4
class-map type network-qos class-silver
match qos-group 3
class-map type network-qos class-bronze
match qos-group 2
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
class-map type network-qos class-fcoe
match qos-group 1
policy-map type network-qos system-level-qos
class type network-qos class-platinum
queue-limit 30000 bytes
mtu 9216
set cos 5
class type network-qos class-gold
queue-limit 30000 bytes
mtu 9216
set cos 4
class type network-qos class-silver
queue-limit 30000 bytes
mtu 9216
set cos 2
class type network-qos class-bronze
queue-limit 30000 bytes
mtu 9216
set cos 1
class type network-qos class-fcoe
pause no-drop
set cos 3
mtu 2158
class type network-qos class-default
mtu 9216
multicast-optimize
system qos
service-policy type network-qos system-level-qos
service-policy type qos input system-level-qos
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output egress_queueing_policy
12-11-2012 04:43 AM
Hi Matt
few Qs:
1) Dont U think that while U have "fcoe-default" queuing input policy U will operate only with two qos-groups (0 & 1) by default?
2) Dont U think that definition for queuing on egress for class-fcoe leaves nothing for FCoE in worst case (I mean band per 0)?
3) finally, why U set cos N in the network-qos policy while your network-qos classes are matched with qos-groups and therefore already must be mutched and marked with qos input policy?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide