Reference Guide

60 | Data Center Bridging (DCB)
www.dell.com | support.dell.com
• Traffic in priority groups is assigned to strict-queue or WERR scheduling in an ETS output policy and
is managed using the ETS bandwidth-assignment algorithm. FTOS de-qeues all frames of
strict-priority traffic before servicing any other queues. A queue with strict-priority traffic can starve
other queues in the same port.
• ETS-assigned bandwidth allocation and scheduling apply only to data queues, not to control queues.
• FTOS supports hierarchical scheduling on an interface. FTOS control traffic is redirected to control
queues as higher priority traffic with strict priority scheduling. After control queues drain out, the
remaining data traffic is scheduled to queues according to the bandwidth and scheduler configuration
in the ETS output policy. The available bandwidth calculated by the ETS algorithm is equal to the link
bandwidth after scheduling non-ETS higher-priority traffic.
• By default, equal bandwidth is assigned to each port queue and each dot1p priority in a priority group.
• By default, equal bandwidth is assigned to each priority group in the ETS output policy applied to an
egress port. The sum of auto-configured bandwidth allocation to dot1p priority traffic in all ETS
priority groups is 100%.
• dot1p priority traffic on the switch is scheduled according to the default dot1p-queue mapping. dot1p
priorities within the same queue should have the same traffic properties and scheduling method.
• A priority group consists of 802.1p priority values that are grouped together for similar bandwidth
allocation and scheduling, and that share the same latency and loss requirements. All 802.1p priorities
mapped to the same queue should be in the same priority group.
• By default:
— All 802.1p priorities are grouped in priority group 0.
— 100% of the port bandwidth is assigned to priority group 0. The complete bandwidth is
equally assigned to each priority class so that each class has 12 to 13%.
• The maximum number of priority groups supported in ETS output policies on an interface is equal
to the number of data queues (4) on the port. The 802.1p priorities in a priority group can map to
multiple queues.
• A DCB output policy is created to associate a priority group with an ETS output policy with
scheduling and bandwidth configuration, and applied on egress ports.
• The ETS configuration associated with 802.1p priority traffic in a DCB output policy is used in
DCBx negotiation with ETS peers.
• When an ETS output policy is applied to an interface, ETS-configured scheduling and bandwidth
allocation take precedence over any auto-configured settings in the QoS output policies.
• ETS is enabled by default with the default ETS configuration applied (all dot1p priorities in the
same group with equal bandwidth allocation).
ETS Operation with DCBx
In DCBx negotiation with peer ETS devices, ETS configuration is handled as follows:
• ETS TLVs are supported in DCBx versions CIN, CEE, and IEEE2.5.
• ETS operational parameters are determined by the DCBX port-role configurations.
• ETS configurations received from TLVs from a peer are validated.
• In case of a hardware limitation or TLV error:
• DCBx operation on an ETS port goes down.