Service Manual
• fpEgrQBuSnapshotTable
• fpIngPgBuSnapshotTable
• fpStatsPerPgTable
• pfcPerPrioTable
fpEgrQBuSnapshot
Table
This table fetches the BST statistics at Egress Port with respect to the buer used. This table displays the
Snapshot of the Buer cells used by Unicast and Multicast Data and Control Queues.
fpIngPgBuSnapsho
tTable
This table fetches the BST statistics at the Ingress Port with respect to the Shared Cells and the Headroom
cells used per Priority Group. The snapshot of the Ingress Shared cells used and the Ingress Headroom cells
used per Priority Group, when PFC is enabled, will be displayed in this table. This table is indexed by stack-
unit index, port number and the priority group number.
fpStatsPerPgTable This table fetches the Allocated Min cells, Shared cells and Headroom cells per Priority Group, the mode in
which the buer cells are allocated - Static or Dynamic and the Used Min Cells, Shared cells and Headroom
cells per Priority Group. The table fetches a value of 0 if the mode of allocation is Static and a value of 1 if
the mode of allocation is Dynamic. This table is indexed by stack-unit number, port number and priority
group number.
pfcPerPrioTable This table fetches the number of PFC frames transmitted (PFC Requests) and the number of PFC frames
received (PFC Indications) per priority on a per port basis. This table is indexed by the stack-unit index, port
number and priority.
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. The following is an
overview of the steps involved in conguring DCB.
• Enter global conguration mode to create a DCB map or edit PFC and ETS settings.
• 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, you can
congure either the peak rates or the committed rates. The 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.
• Repeat the above procedure to congure PFC and ETS trac handling for each priority group
• Specify the dot1p priority-to-priority group mapping for each priority. The priority group range is from 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.
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.
Data Center Bridging (DCB)
213










