Users Guide

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.
Generation of PFC for a Priority for Untagged Packets
In order to generate PFC for a particular priority for untagged packets, and conguring PFC for that priority, you should nd the queue
number associated with priority from TABLE 1 and Associate a DCB map to forward the matched DSCP packet to that queue. PFC frames
gets generated with PFC priority associated with the queue when the queue gets congested.
Congure Enhanced Transmission Selection
ETS provides a way to optimize bandwidth allocation to outbound 802.1p classes of converged Ethernet trac.
Dierent trac types have dierent service needs. Using ETS, you can create groups within an 802.1p priority class to congure dierent
treatment for trac with dierent bandwidth, latency, and best-eort needs.
For example, storage trac is sensitive to frame loss; interprocess communication (IPC) trac is latency-sensitive. ETS allows dierent
trac types to coexist without interruption in the same converged link by:
• Allocating a guaranteed share of bandwidth to each priority group.
• Allowing each group to exceed its minimum guaranteed bandwidth if another group is not fully using its allotted bandwidth.
Creating an ETS Priority Group
An ETS priority group species the range of 802.1p priority trac to which a QoS output policy with ETS settings is applied on an egress
interface. Before conguring ETS, use the cam-acl l2acl 2 ipv4acl 0 ipv6acl 0 ipv4qos 2 l2qos 0 l2pt 0
ipmacacl 0 vman-qos 0 fcoeacl 2 etsacl 1 iscsi 2 command to allocate the appropriate CAM region for ETS.
1 Congure a DCB Map.
CONFIGURATION mode
dcb-map dcb-map-name
The dcb-map-name variable can have a maximum of 32 characters.
2 Create an ETS priority group.
CONFIGURATION mode
Data Center Bridging (DCB)
259