Service Manual

Lossless trac egresses out the no-drop queues. Ingress dot1p trac from PFC-enabled interfaces is automatically mapped to the
no-drop egress queues.
1. Enter INTERFACE Conguration mode.
CONFIGURATION mode
interface type slot/port/subport
2. Congure the port queues that will still function as no-drop queues for lossless trac.
INTERFACE mode
pfc no-drop queues queue-range
For the dot1p-queue assignments, refer to the dot1p Priority-Queue Assignment table.
The maximum number of lossless queues globally supported on the switch is two.
The range is from 0 to 7. Separate the queue values with a comma; specify a priority range with a dash; for example, pfc no-
drop queues 1,7 or pfc no-drop queues 2-7.
The default: No lossless queues are congured.
NOTE: Dell Networking OS Behavior: By default, no lossless queues are congured on a port.
A limit of two lossless queues is supported on a port. If the amount of priority trac that you congure to be paused exceeds the
two lossless queues, an error message displays.
In S6000, any pfc-dot1p priorities congured on a given interface need not be the same across the system. In other words, lossless
queue limit is applicable on a per-port level and not on the global-cong context. For example, one of the Te/Fo interfaces can have
pfc-dot1p priorities as 2 and 3. Whereas, the other Te/Fo interface(s) can have its pfc-dot1p priorities as 4 and 5.
It is the user responsibility to have symmetric PFC congurations on the interfaces involved in a particular PFC-enabled trac-ow
to obtain lossless behavior.
Congure Enhanced Transmission Selection
ETS provides a way to optimize bandwidth allocation to outbound 802.1p classes of converged Ethernet trac.
Dierent trac types have dierent service needs. Using ETS, you can create groups within an 802.1p priority class to congure
dierent treatment for trac with dierent bandwidth, latency, and best-eort needs.
For example, storage trac is sensitive to frame loss; interprocess communication (IPC) trac is latency-sensitive. ETS allows
dierent trac types to coexist without interruption in the same converged link by:
• Allocating a guaranteed share of bandwidth to each priority group.
• Allowing each group to exceed its minimum guaranteed bandwidth if another group is not fully using its allotted bandwidth.
ETS Prerequisites and Restrictions
The following prerequisites and restrictions apply when you congure ETS bandwidth allocation or queue scheduling.
• Conguring ETS bandwidth allocation or a queue scheduler for dot1p priorities in a priority group is applicable if the DCBx version
used on a port is CIN (refer to Conguring DCBx).
• When allocating bandwidth or conguring a queue scheduler for dot1p priorities in a priority group on a DCBx CIN interface, take
into account the CIN bandwidth allocation (refer to Conguring Bandwidth Allocation for DCBx CIN) and dot1p-queue mapping.
NOTE: The IEEE 802.1Qaz, CEE, and CIN versions of ETS are supported.
220
Data Center Bridging (DCB)