Setup Guide

PFC on priority level.
Queue : 0 0 0 1 2 3 3 3 -> On Egress interface[Port B] we used no-drop queues.
Lossless trac egresses out the no-drop queues. Ingress 802.1p trac from PFC-enabled peers is automatically mapped to the no-drop
egress queues.
When conguring lossless queues on a port interface, consider the following points:
• By default, no lossless queues are congured on a port.
• A limit of two lossless queues is supported on a port. If the number of lossless queues congured exceeds the maximum supported limit
per port (two), an error message is displayed. Recongure the value to a smaller number of queues.
• If you congure lossless queues on an interface that already has a DCB map with PFC enabled (pfc on), an error message is displayed.
Table 18. Conguring Lossless Queues on a Port Interface
Step Task Command Command Mode
1 Enter INTERFACE Conguration mode.
interface interface-type
CONFIGURATION
2
Open a DCB map and enter DCB map conguration mode.
dcb-map name
INTERFACE
3
Disable PFC.
no pfc mode on
DCB MAP
4
Return to interface conguration mode.
exit
DCB MAP
5
Apply the DCB map, created to disable the PFC operation,
on the interface
dcb-map {name | default}
INTERFACE
6
Congure the port queues that still function as no-drop
queues for lossless trac. For the dot1p-queue
assignments.
The maximum number of lossless queues globally supported
on a port is 2.
You cannot congure PFC no-drop queues on an interface
on which a DCB map with PFC enabled has been applied,
or which is already congured for PFC using the pfc
priority command.
Range: 0-3. Separate queue values with a comma; specify a
priority range with a dash; for example: pfc no-drop queues
1,3 or pfc no-drop queues 2-3 Default: No lossless queues
are congured.
pfc no-drop
queuesqueue-range
INTERFACE
Conguring PFC Asymmetric
The interface is designed to honor incoming pause frames (lossy and lossless) on all priorities. However, the interface will only generate
pause frames on priorities that are congured to be lossless (typically priorities 3 and 4). Any received pause frames are reected in the
appropriate counters, and PFC watchdog accounts for pause frames on all priorities.
Data Center Bridging (DCB)
273