Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell EMC SmartFabric OS10 User Guide Release 10.5.0

PFC configuration notes

  • PFC is supported for 802.1p, dot1p priority traffic, from 0 to 7. FCoE traffic traditionally uses dot1p priority 3 — iSCSI storage traffic uses dot1p priority 4.
  • Configure PFC for ingress traffic by using network-qos class and policy maps. For more information, see Quality of service. PFC-enabled traffic queues are treated as lossless queues. Configure the same network-qos policy map on all PFC-enabled ports. Configure required bandwidth for lossless traffic using ETS queuing (output) policies on egress interfaces.
  • In a network-qos policy-class map, use commands to generate PFC pause frames for matching class-map priorities:
    • Send pause frames for matching class-map traffic during congestion using the pause command.
    • (Optional) Enter user-defined values for the reserved ingress buffer-size of PFC class-map traffic, and the thresholds that are used to send XOFF and XON pause frames using the pause [buffer-size kilobytes pause-threshold kilobytes resume-threshold kilobytes]command.
    • Configure the matching dot1p values used to send pause frames using the pfc-cos command.
    • (Optional) Set the static and dynamic thresholds that determine the shared buffers available for PFC class-map traffic queues using the queue-limit thresh-mode command.
  • By default, the lossy ingress buffer handles all ingress traffic. When you enable PFC, dot1p ingress traffic competes for shared buffers in the lossless pool instead of the shared lossy pool. The number of lossless queues that are supported on an interface depends on the amount of available free memory in the lossy pool.
  • Use the priority-flow-control mode on command to enable PFC for FCoE and iSCSI traffic; for example, priority 3 and 4.
  • Enable DCBX on interfaces to detect and autoconfigure PFC/ETS parameters from peers.
  • PFC and 802.3x LLFC are disabled by default on an interface. You cannot enable PFC and LLFC simultaneously. LLFC ensures lossy traffic in best-effort transmission. Enable PFC to enable guarantee lossless FCoE and iSCSI traffic. PFC manages buffer congestion by pausing specified ingress dot1p traffic; LLFC pauses all data transmission on an interface. To enable LLFC, use the flowcontrol [receive | transmit] [on | off] command.
  • SYSTEM-QOS mode applies a service policy globally on all interfaces:
    • Create and apply a 1-to-1 802.1p-priority-to-traffic-class mapping on an interface or all interfaces in INTERFACE or SYSTEM-QOS mode.
    • Create and apply a 1-to-1 traffic-class-to-queue mapping on an interface or all interfaces in INTERFACE or SYSTEM-QOS mode.

Configure dot1p priority to traffic class mapping

Decide if you want to use the default 802.1p priority-to-traffic class (qos-group) mapping or configure a new map. The default dot1p to traffic class map in OS10 is shown below.

 Dot1p Priority : 0  1  2  3  4  5  6  7
  Traffic Class : 1  0  2  3  4  5  6  7
  • Apply the default trust map specifying that dot1p values are trusted in SYSTEM-QOS or INTERFACE mode.
    trust-map dot1p default
    
Configure a non-default dot1p-priority-to-traffic class mapping
  1. Configure a trust map of dot1p traffic classes in CONFIGURATION mode. A trust map does not modify ingress dot1p values in output flows.

    Assign a qos-group to trusted dot1p values in TRUST mode using 1-to-1 mappings. Dot1p priorities are 0 to 7. For a PFC traffic class, map only one dot1p value to a qos-group number; for Broadcom-based NPU platforms, the qos-group number and the dot1p value must be the same. A qos-group number is used only internally to classify ingress traffic classes.

    trust dot1p-map dot1p-map-name 
       qos-group {0-7} dot1p {0-7}
       exit
  2. Apply the trust dot1p-map policy to ingress traffic in SYSTEM-QOS or INTERFACE mode.
    trust-map dot1p trust-policy—map-name

Configure traffic-class-queue mapping

NOTE Z9332F-ON has different configurations for queue mapping. For more information, see Configure traffic-class to queue mapping for Z9332F-ON.
Decide if you want to use the default traffic-class-queue mapping or configure a nondefault traffic-class-to-queue mapping.
 Traffic Class : 0  1  2  3  4  5  6  7
         Queue : 0  1  2  3  4  5  6  7

If you are using the default traffic-class-to-queue map, no further configuration steps are necessary.

  1. Create a traffic-class-to-queue map in CONFIGURATION mode. Assign a traffic class (qos-group) to a queue in QOS-MAP mode using 1-to-1 mappings. For a PFC traffic class, map only one qos-group value to a queue number. A qos-group number is used only internally to classify ingress traffic.
    qos—map traffic-class tc-queue-map-name
       queue {0-7} qos-group {0-7}
       exit 
  2. Apply the traffic-class-queue map in SYSTEM-QOS or INTERFACE mode.
    qos-map traffic-class tc-queue-map-name

Configure traffic-class to queue mapping for Z9332F-ON

The Z9332F-ON supports 12 queues per Ingress Traffic Manager (ITM) in the front-panel ports. The 12 queues are divided into eight unicast (UC) and four multicast (MC) combinations. For multicast queues, MCQ index 0 to 2 are used for MC flows. MCQ index 3 sends control packets from the CPU.

By default, multicast traffic map in the following order:

TC0-TC2 : Q0

TC3-TC5 : Q1

TC6-TC7 : Q2

You can map different traffic classes of UC and MC traffics to different queues, based on the requirement.

Configure TC-to-queue mapping

OS10# show qos maps
Traffic-Class to Queue Map: sundar

Queue  Traffic Class  Type
---------------------------------------
3      1-3       				 Unicast
4      4,6,0          Unicast

Default TC-to-queue mapping format

The following is the format for Z9332F-ON:

Default Traffic-Class to Queue Map

Traffic Class  Queue Number 							Type
---------------------------------------------
0              0					              Unicast
0-2            0              					Multicast
1              1              					Unicast
3-5            1              					Multicast
2              2              					Unicast
6-7            2              					Multicast
3              3              					Unicast
4              4              					Unicast
5              5              					Unicast
6              6              					Unicast
7              7              					Unicast

The following is the default TC-to-Queue Mapping format:

Default Traffic-Class to Queue Map

Traffic-Class    Queue number      Type
----------------------------------------
0                   0              Both
1                   1              Both
2                   2              Both
3                   3              Both
4                   4              Both
5                   5              Both
6                   6              Both
7                   7              Both

View the interface PFC configuration

OS10# show interface ethernet 1/1/1 priority-flow-control details
ethernet1/1/1
Admin Mode : true
Operstatus: true
PFC Priorities: 4
Total Rx PFC Frames: 0
Total Tx PFC frames: 0
Cos    Rx               Tx
---------------------------------------
0      0              0
1      0              0
2      0              0
3      0              0
4      0              0
5      0              0
6      0              0
7      0              0

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\