Dell S6000-ON Switch User Manual


  Open as PDF
of 1100
 
these mappings are identical. This section discusses the Dell Networking OS configurations needed for
above PFC generation and honoring mechanism to work for the untagged packets.
PRIORITY to PG mapping (PRIO2PG) is on the ingress for each port. By default, all priorities are mapped
to PG7. A priority for which PFC has to be generated is assigned to a PG other than PG7 (say PG6) and
buffer watermark is set on PG6 so as to generate PFC.
In ingress, the buffers are accounted at per PG basis and would indicate the number of the packets that
has ingress this port PG but still queued up in egress pipeline. However, there is no direct mapping
between the PG and Queue.
Packet is assigned an internal priority on the ingress pipeline based on the queue to which it is destined.
This Internal-priority to Queue mapping has been modified and enhanced as follows for the device:
Table 15. Priority to Queue Mapping
Internal-
priority
0 1 2 3 4 5 6 7
Queue
2 0 1 3 4 5 6 7
Default dot1p to queue configuration is as follows:
Table 16. Dot1p to Queue Mapping
Packet-
Dot1p
0 1 2 3 4 5 6 7
Queue
2 0 1 3 4 5 6 7
PFC and ETS Configuration Examples
This section contains examples of how to configure and apply DCB policies on an interface.
Using PFC to Manage Converged Ethernet Traffic
To use PFC for managing converged Ethernet traffic, use the following command:
dcb-map stack-unit all dcb-map-name
Operations on Untagged Packets
The below is example for enabling PFC for priority 2 for tagged packets. Priority (Packet Dot1p) 2 will be
mapped to PG6 on PRIO2PG setting. All other Priorities for which PFC is not enabled are mapped to
default PG – PG7.
Classification rules on ingress (Ingress FP CAM region) matches incoming packet-dot1p and assigns an
internal priority (to select queue as per Table 1 and Table 2).
264
Data Center Bridging (DCB)