Ets Operation With Dcbx - Dell Force10 S4810P Configuration Manual

FTOS Behavior:
Create a DCB output policy to associate a priority group with an ETS output policy with scheduling and
bandwidth configuration. You can apply a DCB output policy on multiple 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 you apply an ETS output policy to an interface, ETS-configured scheduling and bandwidth
allocation take precedence over any configured settings in the QoS output policies.
To remove an ETS output policy from an interface, use the
DCB and ETS are both disabled by default. When DCB is enabled, ETS is enabled on all interfaces
that have the default ETS configuration applied.
If you disable ETS in an output policy applied to an interface (the
previously configured QoS settings at the interface or global level take effect. If QoS settings are
configured at the interface or global level and in an output policy map (the
command), the QoS configuration in the output policy take precedence.

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 (see
DCBx Operation).
• 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.
• New ETS configurations are ignored and existing ETS configurations are reset to the previously
configured ETS output policy on the port or to the default ETS settings if no ETS output policy
was previously applied.
• ETS operates with legacy DCBx versions as follows:
• In the CEE version, the priority group/traffic class group (TCG) ID 15 represents a non-ETS
priority group. Any priority group configured with a scheduler type is treated as a strict-priority
group and is given the priority-group (TCG) ID 15.
• The CIN version supports two types of strict-priority scheduling:
— Group strict priority: Allows a single priority flow in a priority group to increase its
bandwidth usage to the bandwidth total of the priority group. A single flow in a group can
use all the bandwidth allocated to the group.
— Link strict priority: Allows a flow in any priority group to increase to the maximum link
bandwidth.
CIN supports only the dot1p priority-queue assignment in a priority group. To configure a dot1p
priority flow in a priority group to operate with link strict priority, you must configure:
- The dot1p priority for strict-priority scheduling (
Queueing)
no dcb-policy output policy-name
no ets mode on
service-policy output
command;
strict-priority
Data Center Bridging (DCB) | 319
command.
command), any
Configuring
Strict-priority