Users Guide
ETS Operation with DCBx
The following section describes DCBx negotiation with peer ETS devices.
In DCBx negotiation with peer ETS devices, ETS conguration is handled as follows:
• ETS TLVs are supported in DCBx versions CIN, CEE, and IEEE2.5.
• The DCBx port-role congurations determine the ETS operational parameters (refer to Congure a DCBx Operation).
• ETS congurations received from TLVs from a peer are validated.
• If there is a hardware limitation or TLV error:
– DCBx operation on an ETS port goes down.
– New ETS congurations are ignored and existing ETS congurations are reset to the default ETS settings.
• ETS operates with legacy DCBx versions as follows:
– In the CEE version, the priority group/trac class group (TCG) ID 15 represents a non-ETS priority group. Any priority group
congured with a scheduler type is treated as a strict-priority group and is given the priority-group (TCG) ID 15.
Conguring ETS in a DCB Map
A switch supports the use of a DCB map in which you congure enhanced transmission selection (ETS) setting. To congure ETS
parameters, you must apply a DCB map on an interface.
ETS Conguration Notes
ETS provides a way to optimize bandwidth allocation to outbound 802.1p classes of converged Ethernet trac. Dierent trac types have
dierent service needs. Using ETS, you can create groups within an 802.1p priority class to congure dierent treatment for tracs with
dierent bandwidth, latency, and best-eort needs.
When you congure ETS in a DCB map:
• The DCB map associates a priority group with a PFC operational mode (on or o) and an ETS scheduling and bandwidth allocation. You
can apply a DCB map on multiple egress ports.
• Use the ETS conguration associated with 802.1p priority trac in a DCB map in DCBx negotiation with ETS peers.
• Trac in priority groups is assigned to strict-queue or weighted round-robin (WRR) scheduling in an ETS conguration and is managed
using the ETS bandwidth-assignment algorithm. Dell EMC Networking OS de-queues all frames of strict-priority trac before servicing
any other queues. A queue with strict-priority trac can starve other queues in the same port.
• ETS-assigned bandwidth allocation and strict-priority scheduling apply only to data queues, not to control queues.
• Dell EMC Networking OS supports hierarchical scheduling on an interface. The control trac on Dell EMC Networking OS is redirected
to control queues as higher priority trac with strict priority scheduling. After the control queues drain out, the remaining data trac is
scheduled to queues according to the bandwidth and scheduler conguration in the DCB map. The available bandwidth calculated by
the ETS algorithm is equal to the link bandwidth after scheduling non-ETS higher-priority trac.
• The conguration of bandwidth allocation and strict-queue scheduling is not supported at the same time for a priority group.
• Bandwidth assignment: By default, equal bandwidth is assigned to each dot1p priority in a priority group. To congure the bandwidth
assigned to the port queues associated with dot1p priorities in a priority group, use the bandwidth percentage parameter. The sum of
the bandwidth allocated to all priority groups in a DCB map must be 100% of the bandwidth on the link. You must allocate at least 1% of
the total bandwidth to each priority group.
• Scheduling of priority trac: dot1p priority trac on the switch is scheduled to the current queue mapping. dot1p priorities within the
same queue must have the same trac properties and scheduling method.
Data Center Bridging (DCB)
287










