Administrator Guide
– No bandwidth limit or no ETS processing
• Bandwidth allocated by the ETS algorithm is made available after strict-priority groups are serviced. If a priority group does not
use its allocated bandwidth, the unused bandwidth is made available to other priority groups.
• For ETS trac selection, an algorithm is applied to priority groups using:
– Strict priority shaping
– ETS shaping
• ETS uses the DCB MIB IEEE 802.1azd2.5.
Conguring DCB Maps and its Attributes
This topic contains the following sections that describe how to congure a DCB map, apply the congured DCB map to a port,
congure PFC without a DCB map, and congure lossless queues.
DCB Map: Conguration Procedure
A DCB map consists of PFC and ETS parameters. By default, PFC is not enabled on any 802.1p priority and ETS allocates equal
bandwidth to each priority. To congure user-dened PFC and ETS settings, you must create a DCB map.
Step Task Command Command Mode
1
Enter global conguration mode to create a DCB map or
edit PFC and ETS settings.
dcb-map name
CONFIGURATION
2
Congure the PFC setting (on or o) and the ETS
bandwidth percentage allocated to trac in each priority
group, or whether the priority group trac should be
handled with strict priority scheduling. You can enable PFC
on a maximum of two priority queues on an interface.
Enabling PFC for dot1p priorities makes the corresponding
port queue lossless. The sum of all allocated bandwidth
percentages in all groups in the DCB map must be 100%.
Strict-priority trac is serviced rst. Afterwards,
bandwidth allocated to other priority groups is made
available and allocated according to the specied
percentages. If a priority group does not use its allocated
bandwidth, the unused bandwidth is made available to
other priority groups.
Example: priority-group 0 bandwidth 60 pfc o priority-
group 1 bandwidth 20 pfc on priority-group 2 bandwidth
20 pfc on priority-group 4 strict-priority pfc o
Repeat this step to congure PFC and ETS trac handling
for each priority group.
priority-group
group_num {bandwidth
percentage | strict-priority} pfc
{on | o}
DCB MAP
3
Specify the dot1p priority-to-priority group mapping for
each priority. Priority-group range: 0 to 7. All priorities that
map to the same queue must be in the same priority
group.
Leave a space between each priority group number. For
example: priority-pgid 0 0 0 1 2 4 4 4 in which priority
group 0 maps to dot1p priorities 0, 1, and 2; priority group 1
maps to dot1p priority 3; priority group 2 maps to dot1p
priority 4; priority group 4 maps to dot1p priorities 5, 6, and
7.
priority-pgid
dot1p0_group_num
dot1p1_group_num
dot1p2_group_num
dot1p3_group_num
dot1p4_group_num
dot1p5_group_num
dot1p6_group_num
dot1p7_group_num
DCB MAP
Important Points to Remember
• If you remove a dot1p priority-to-priority group mapping from a DCB map (no priority pgid command), the PFC and ETS
parameters revert to their default values on the interfaces on which the DCB map is applied. By default, PFC is not applied on
specic 802.1p priorities; ETS assigns equal bandwidth to each 802.1p priority.
FC Flex IO Modules
901