Setup Guide

Default dot1p to queue conguration is as follows:
Table 22. Dot1p to Queue Mapping
Packet-Dot1p Queue
0 2
1 0
2 1
3 3
4 4
5 5
6 6
7 7
PFC and ETS Conguration Examples
This section contains examples of how to congure and apply DCB policies on an interface.
Using PFC to Manage Converged Ethernet Trac
To use PFC for managing converged Ethernet trac, 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.
Classication 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).
The internal Priority assigned for the packet by Ingress FP is used by the memory management unit (MMU) to assign the packet to right
queue by indexing the internal-priority to queue map table (TABLE 1) in hardware.
PRIO2COS setting for honoring the PFC protocol packets from the Peer switches is as per above Packet-Dot1p->queue table (Table 2).
The packets that come in with packet-dot1p 2 alone will be assigned to PG6 on ingress.
The packets that come in with packet-dot1p 2 alone will use Q1 (as per dot1p to Queue classication – Table 2) on the egress port.
• When Peer sends a PFC message for Priority 2, based on above PRIO2COS table (TABLE 2), Queue 1 is halted.
• Queue 1 starts buering the packets with Dot1p 2. This causes PG6 buer counter to increase on the ingress, since P-dot1p 2 is
mapped to PG6.
• As the PG6 watermark threshold is reached, PFC will be generated for dot1p 2.
278
Data Center Bridging (DCB)