Connectivity Guide

ETS conguration notes
• ETS is supported on Layer2 (L2) 802.1p priority (dot1p 0 to 7) and Layer 3 (L3) DSCP (0 to 63) trac. FCoE trac uses dot1p priority
3 — iSCSI storage trac uses dot1p priority 4.
• Apply these maps and policies on interfaces:
– Trust maps — OS10 interfaces do not honor the L2 and L3 priority elds in ingress trac by default. Create a trust map to honor
dot1p and DSCP classes of lossless trac. A trust map does not change ingress dot1p and DSCP values in egress ows. In a trust
map, assign a qos-group trac class to trusted dot1p/DSCP values. A qos-group number is used only internally to schedule
classes of ingress trac.
– QoS map — Create a QoS map to assign trusted dot1p and DSCP trac classes to lossless queues.
– Ingress trust policy — Congure a service policy to trust dot1p values in ingress trac.
– Egress queuing policy — Congure ETS for egress trac by assigning bandwidth to matching lossless queues in queuing class
and policy maps.
• Apply both PFC network-qos (input) and ETS queuing (output) policies on an interface to ensure lossless transmission.
• An ETS-enabled interface operates with dynamic weighted round robin (DWRR) or strict priority scheduling.
• OS10 control trac is sent to control queues, which have a strict priority that is higher than data trac queues. ETS-allocated
bandwidth is not supported on a strict priority queue. A strict priority queue receives bandwidth only from DCBX type, length, values
(TLVs).
• The CEE/IEEE2.5 versions of ETS TLVs are supported. ETS congurations are received in a TLV from a peer.
Congure ETS
ETS provides trac prioritization for lossless storage, latency-sensitive, and best-eort data trac on the same link.
• Congure classes of dot1p and DSCP trac and assign them to lossless queues. Use the class-trust class map to honor ingress dot1p
and DSCP trac.
• Allocate guaranteed bandwidth to each lossless queue. An ETS queue can exceed the amount of allocated bandwidth if another queue
does not use its share.
ETS is disabled by default on all interfaces.
1 Congure trust maps of dot1p and DSCP values in CONFIGURATION mode. A trust map does not modify ingress values in output
ows. Assign a qos-group, trac class from 0 to 7, to trusted dot1p/DSCP values in TRUST mode. A qos-group number is used
only internally to schedule classes of ingress trac. Enter multiple
dot1p and dscp values in a hyphenated range or separated by
commas.
trust dot1p-map dot1p-map-name
qos-group {0-7} dot1p {0-7}
exit
trust dscp-map
dscp-map-name
qos-group {0-7} dscp {0-63}
exit
2 Congure a QoS map with trusted trac-class (qos-group) to lossless-queue mapping in CONFIGURATION mode. Assign one or
more qos-groups, from 0 to 7, to a specied queue in QOS-MAP mode. Enter multiple qos-group values in a hyphenated range or
separated by commas. Enter multiple
queue qos-group entries, if necessary.
qos-map traffic-class queue-map-name
queue {0-7} qos-group {0-7}
exit
3 Apply the default trust map specifying that dot1p and dscp values are trusted in SYSTEM-QOS or INTERFACE mode.
trust-map {dot1p | dscp} default
4 Create a queuing class map for each ETS queue in CONFIGURATION mode. Enter match queue criteria in CLASS-MAP mode.
class—map type queuing class—map-name
match queue {0-7}
exit
1094
Converged data center services