Addendum
guaranteed buffer reduces the total available shared buffer to 7,787 KB. This shared buffer can be used for
lossy and lossless traffic.
The default behavior causes up to a maximum of 6.6 MB to be used for PFC-related traffic. The remaining
approximate space of 1 MB can be used by lossy traffic. You can allocate all the remaining 1 MB to
lossless PFC queues. If you allocate in such a way, the performance of lossy traffic is reduced and
degraded. Although you can allocate a maximum buffer size, it is used only if a PFC priority is configured
and applied on the interface.
The number of lossless queues supported on the system is dependent on the availability of total buffers
for PFC. The default configuration in the system guarantees a minimum of 52 KB per queue if all the 128
queues are congested. However, modifying the buffer allocation per queue impacts this default behavior.
By default the total available buffer for PFC is 6.6 MB and when you configure dynamic ingress buffering,
a minimum of least 52 KB per queue is used when all ports are congested. By default, the system enables
a maximum of 2 lossless queues on the S4810, S4820T, and MXL platforms, and a maximum of 1 lossless
queue on the S6000 platform.
This default behavior is impacted if you modify the total buffer available for PFC or assign static buffer
configurations to the individual PFC queues.
Interworking of DCB Map With DCB Buffer Threshold
Settings
DCB map functionality is supported on the S4810, S4820T, S6000, I/O Aggregator, and MXL platforms.
The dcb-input and dcb-output configuration commands are deprecated. You must use the dcp-map
command to create a DCB map to configure priority flow control (PFC) and enhanced transmission
selection (ETS) on Ethernet ports that support converged Ethernet traffic.
You can configure the dcb-buffer-threshold command and its related parameters only on ports with
either auto configuration or dcb-map configuration. This command is not supported on existing front-
panel interfaces or stack ports that are configured with the
dcb-input or dcb-output commands.
Similarly, if dcb-buffer-threshold configuration is present on any interface or a stack port, dcb-input or
dcb-ouput policy cannot be applied on those interfaces.
Example: When dcb-buffer-threshold is applied on interfaces or stack ports with dcb-input or dcb-
output policy, the following error message is displayed:
%Error: dcb-buffer-threshold not supported on interfaces with deprecated
commands
Example: When dcb-input or dcb-output is configured on interfaces or stack ports with dcb-buffer
threshold policy:
%Error: Deprecated command is not supported on interfaces with dcb-buffer-
threshold configured
You must not modify the service-class dot1p mappings when any buffer-threshold-policy is configured
on the system.
S4810-1(conf)#service-class dot1p-mapping dot1p0 3
% Error: PFC buffer-threshold policies conflict with dot1p mappings. Please
remove all dcb-buffer-threshold policies to change mappings.
The show dcb command has been enhanced to display the following additional buffer-related
information:
S4810-YU-MR-FTOS (conf)#do show dcb
dcb Status : Enabled
PFC Queue Count : 2 --Indicate the PFC queue configured.
Data Center Bridging (DCB)
101