Setup Guide

Step Task Command Command Mode
You cannot apply a DCB map on
an interface that has been
already congured for PFC using
thepfc priority command
or which is already congured for
lossless queues (pfc no-drop
queues command).
Conguring PFC without a DCB Map
In a network topology that uses the default ETS bandwidth allocation (assigns equal bandwidth to each priority), you can also enable PFC
for specic dot1p-priorities on individual interfaces without using a DCB map. This type of DCB conguration is useful on interfaces that
require PFC for lossless trac, but do not transmit converged Ethernet trac.
Table 17. Conguring PFC without a DCB Map
Step Task Command Command Mode
1 Enter interface conguration
mode on an Ethernet port.
interface
{tengigabitEthernet slot/
port |fortygigabitEthernet
slot/port}
CONFIGURATION
2 Enable PFC on specied
priorities. Range: 0-7. Default:
None.
Separate priority values with a
comma. Specify a priority range
with a dash, for example: pfc
priority 3,5-7
1 You cannot congure PFC
using the pfc priority
command on an interface
on which a DCB map has
been applied or which is
already congured for
lossless queues (pfc no-
drop queues
command).
pfc priority priority-
range
INTERFACE
Conguring Lossless Queues
DCB also supports the manual conguration of lossless queues on an interface after you disable PFC mode in a DCB map and apply the
map on the interface. The conguration of no-drop queues provides exibility for ports on which PFC is not needed, but lossless trac
should egress from the interface.
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.
Data Center Bridging (DCB)
273