Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Understanding Default CoS Scheduling and Classification

    If you do not configure hierarchical scheduling on an interface, the switch uses the default classifiers for ingress traffic and the default schedulers for egress traffic. Default scheduling and classification handle all traffic types (best effort, FCoE, no-loss, network-control, and multidestination traffic).

    Hierarchical scheduling groups egress queues (priorities, configured as forwarding classes) into priority groups (forwarding class sets). If you use only the default traffic scheduling and classification, the switch automatically creates a default priority group that contains all of the priorities (forwarding classes, which represent output queues) and assigns 100 percent of the port output bandwidth to that priority group. The forwarding classes (queues) in the default forwarding class set receive bandwidth based on the default classifier settings. The default priority group is transparent. It does not appear in the configuration and is used for Data Center Bridging Capability Exchange (DCBX) protocol advertisement.

    Note: If you explicitly configure one or more priority groups on an interface, any forwarding class that is not assigned to a priority group on that interface receives no bandwidth. This means that if you configure hierarchical scheduling on an interface, every forwarding class (priority) that you want to forward traffic on that interface must belong to a forwarding class set (priority group).

    The following sections describe:

    Default Classification

    The default classifiers assign unicast and multicast best-effort and network-control ingress traffic to forwarding classes and loss priorities. The QFX Series applies default unicast IEEE 802.1, unicast DSCP, and multidestination classifiers to each interface that does not have explicitly configured classifiers. If you explicitly configure one type of classifier but not other types of classifiers, the system uses only the configured classifier and does not use default classifiers for other types of traffic. There are two different default unicast IEEE 802.1 classifiers, a trusted classifier for ports that are in trunk mode or tagged-access mode, and an untrusted classifier for ports that are in access mode.

    Table 1 shows the default mapping of IEEE 802.1 code-point values to unicast forwarding classes and loss priorities for ports in trunk mode or tagged-access mode.

    Table 1: Default IEEE 802.1 Unicast Classifiers for Ports in Trunk Mode or Tagged-Access Mode (Trusted Classifier)

    Code Point

    Forwarding Class

    Loss Priority

    be (000)

    best-effort

    low

    be1 (001)

    best-effort

    low

    ef (010)

    best-effort

    low

    ef1 (011)

    fcoe

    low

    af11 (100)

    no-loss

    low

    af12 (101)

    best-effort

    low

    nc1 (110)

    network-control

    low

    nc2 (111)

    network-control

    low

    Table 2 shows the default mapping of IEEE 802.1p code-point values to unicast forwarding classes and loss priorities for ports in access mode (all incoming traffic is mapped to best-effort forwarding classes).

    Table 2: Default IEEE 802.1 Unicast Classifiers for Ports in Access Mode (Untrusted Classifier)

    Code Point

    Forwarding Class

    Loss Priority

    000

    best-effort

    low

    001

    best-effort

    low

    010

    best-effort

    low

    011

    best-effort

    low

    100

    best-effort

    low

    101

    best-effort

    low

    110

    best-effort

    low

    111

    best-effort

    low

    Table 3 shows the default mapping of IEEE 802.1 code-point values to multidestination (multicast, broadcast, and destination lookup fail traffic) forwarding classes and loss priorities.

    Table 3: Default IEEE 802.1 Multidestination Classifiers

    Code Point

    Forwarding Class

    Loss Priority

    be (000)

    mcast

    low

    be1 (001)

    mcast

    low

    ef (010)

    mcast

    low

    ef1 (011)

    mcast

    low

    af11 (100)

    mcast

    low

    af12 (101)

    mcast

    low

    nc1 (110)

    mcast

    low

    nc2 (111)

    mcast

    low

    Table 4 shows the default mapping of DSCP code-point values to unicast forwarding classes and loss priorities for DSCP IP and DCSP IPv6.

    Table 4: Default DSCP IP and IPv6 Unicast Classifiers

    Code Point

    Forwarding Class

    Loss Priority

    ef (101110)

    best-effort

    low

    af11 (001010)

    best-effort

    low

    af12 (001100)

    best-effort

    low

    af13 (001110)

    best-effort

    low

    af21 (010010)

    best-effort

    low

    af22 (010100)

    best-effort

    low

    af23 (010110)

    best-effort

    low

    af31 (011010)

    best-effort

    low

    af32 (011100)

    best-effort

    low

    af33 (011110)

    best-effort

    low

    af41 (100010)

    best-effort

    low

    af42 (100100)

    best-effort

    low

    af43 (100110)

    best-effort

    low

    be (000000)

    best-effort

    low

    cs1 (001000)

    best-effort

    low

    cs2 (010000)

    best-effort

    low

    cs3 (011000)

    best-effort

    low

    cs4 (100000)

    best-effort

    low

    cs5 (101000)

    best-effort

    low

    nc1 (110000)

    network-control

    low

    nc2 (111000)

    network-control

    low

    Note: There are no default DSCP IP or IPv6 multidestination classifiers for multidestination traffic. DSCP IPv6 multidestination classifiers are not supported for multidestination traffic.

    Default Scheduling

    The default schedulers allocate egress bandwidth resources to unicast and multicast best-effort and network-control egress traffic as shown in Table 5:

    Table 5: Default Scheduler Configuration

    Default Scheduler and Queue Number

    Guaranteed Rate (Minimum Bandwidth)

    Shaping Rate (Maximum Bandwidth)

    Excess Bandwidth Sharing

    Priority

    Best-effort scheduler (queue 0)

    5%

    None

    5%

    Low

    FCoE scheduler (queue 3)

    35%

    None

    35%

    Low

    No-loss scheduler (queue 4)

    35%

    None

    35%

    Low

    Network-control scheduler (queue 7)

    5%

    None

    5%

    Low

    Multidestination scheduler (queue 8)

    20%

    None

    20%

    Low

    Note: The minimum guaranteed bandwidth rate also determines the amount of excess (extra) bandwidth that the queue can share. Extra bandwidth is allocated to queues in proportion to the minimum guaranteed bandwidth rate of each queue.

    Default DCBX Advertisement

    When you configure hierarchical scheduling on an interface, DCBX advertises each priority group, the priorities in each priority group, and the bandwidth properties of each priority and priority group.

    If you do not configure hierarchical scheduling on an interface, DCBX advertises the automatically created default priority group and its priorities. DCBX also advertises the default bandwidth allocation of the priority group, which is 100 percent of the port bandwidth.

    Default Scheduling and Classification Summary

    If you do not configure hierarchical scheduling on an interface:

    • Default classifiers classify ingress traffic.
    • Default schedulers schedule egress traffic.
    • DCBX advertises a single default priority group with 100 percent of the port bandwidth allocated to that priority group. All priorities (forwarding classes) are assigned to the default priority group and receive bandwidth based on their default schedulers. The default priority group is generated automatically and is not user-configurable.

    Published: 2012-07-31