forked from openconfig/featureprofiles
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create a Readme file for DP-1.15 Egress Strict Priority scheduler (op…
…enconfig#3043) * Create a Readme file for DP-1.15 Egress Strict Priority scheduler
- Loading branch information
1 parent
55e8690
commit 0ee03fe
Showing
2 changed files
with
230 additions
and
0 deletions.
There are no files selected for viewing
224 changes: 224 additions & 0 deletions
224
feature/qos/otg_tests/egress_strict_priority_scheduler_test/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,224 @@ | ||
| # DP-1.15: Egress Strict Priority scheduler | ||
|
|
||
| ## Summary | ||
|
|
||
| This test validates the proper functionality of an egress strict priority scheduler on a network device. By configuring multiple priority queues with specific traffic classes and generating traffic loads that exceed interface capacity, we will verify that the scheduler adheres to the strict priority scheme, prioritizing higher-priority traffic even under congestion. | ||
|
|
||
| ## Testbed type | ||
|
|
||
| * [`featureprofiles/topologies/atedut_4.testbed`](https://github.com/openconfig/featureprofiles/blob/main/topologies/atedut_4.testbed) | ||
|
|
||
| ## Procedure | ||
|
|
||
| ### Test environment setup | ||
|
|
||
| * DUT has 2 ingress ports and 1 egress port with the same port speed. The | ||
| interface can be a physical interface or LACP bundle interface with the | ||
| same aggregated speed. | ||
|
|
||
| ``` | ||
| | | ---- | ATE Port 1 | | ||
| [ ATE Port 3 ] ---- | DUT | | | | ||
| | | ---- | ATE Port 2 | | ||
| ``` | ||
|
|
||
| * Traffic classes: | ||
|
|
||
| * We will use 6 traffic classes NC1, AF4, AF3, AF2, AF1 and BE1. | ||
|
|
||
| * Traffic types: | ||
|
|
||
| * All the traffic tests apply to both IPv4 and IPv6 and also MPLS traffic. | ||
|
|
||
| * Queue types: | ||
|
|
||
| * NC1/AF4/AF3/AF2/AF1/BE1 will have strict priority queues (be1 - priority 6, af1 - priority 5, ..., nc1 - priority 1) | ||
|
|
||
| * Test results should be independent of the location of interfaces. For | ||
| example, 2 input interfaces and output interface could be located on | ||
|
|
||
| * Same ASIC-based forwarding engine | ||
| * Different ASIC-based forwarding engine on same line card | ||
| * Different ASIC-based forwarding engine on different line cards | ||
|
|
||
| * Test results should be the same for port speeds 100G and 400G. | ||
|
|
||
| * Counters should be also verified for each test case: | ||
|
|
||
| * /qos/interfaces/interface/output/queues/queue/state/transmit-pkts | ||
| * /qos/interfaces/interface/output/queues/queue/state/dropped-pkts | ||
| * transmit-pkts should be equal to the number of Rx pkts on Ixia port | ||
| * dropped-pkts should be equal to diff between the number of Tx and the | ||
| number Rx pkts on Ixia ports | ||
|
|
||
| * Latency: | ||
|
|
||
| * Should be < 100000ns | ||
|
|
||
| #### Configuration | ||
|
|
||
| * Forwarding Classes: Configure six forwarding classes (be1, af1, af2, af3, af4, nc1) based on the classification table provided. | ||
| * Egress Scheduler: Apply a multi-level strict-priority scheduling policy on the desired egress interface. Assign priorities to each forwarding class according to the strict priority test traffic tables (be1 - priority 6, af1 - priority 5, ..., nc1 - priority 1). | ||
|
|
||
| * Classification table | ||
|
|
||
| IPv4 TOS | IPv6 TC | MPLS EXP | Forwarding class | ||
| ------------- | ----------------------- | ----------------------- | --------------------- | ||
| 0 | 0-7 | 0 | be1 | ||
| 1 | 8-15 | 1 | af1 | ||
| 2 | 16-23 | 2 | af2 | ||
| 3 | 24-31 | 3 | af3 | ||
| 4,5 | 32-47 | 4,5 | af4 | ||
| 6,7 | 48-63 | 6,7 | nc1 | ||
|
|
||
| ### DP-1.15.1: Egress Strict Priority scheduler for IPv4 Traffic | ||
|
|
||
| * Traffic Generation: | ||
| * Traffic Profiles: Define traffic profiles for each forwarding class using the ATE, adhering to the linerates (%) specified in the strict priority test traffic tables. | ||
|
|
||
| * Strict Priority Test traffic table for ATE Port 1 | ||
|
|
||
| Forwarding class | Priority | Traffic linerate (%) | Frame size | Expected Loss % | ||
| ----------------- |--------------------- | --------------------------- |--------------------- | ----------------------------------- | ||
| be1 | 6 | 12 | 512 | 100 | ||
| af1 | 5 | 12 | 512 | 100 | ||
| af2 | 4 | 10 | 512 | 50 | ||
| af3 | 3 | 12 | 512 | 0 | ||
| af4 | 2 | 30 | 512 | 0 | ||
| nc1 | 1 | 1 | 512 | 0 | ||
|
|
||
| * Strict Priority Test traffic table for ATE Port 2 | ||
|
|
||
| Forwarding class | Priority | Traffic linerate (%) | Frame size | Expected Loss % | ||
| ----------------- |--------------------- | --------------------------- |--------------------- | ----------------------------------- | ||
| be1 | 6 | 12 | 512 | 100 | ||
| af1 | 5 | 12 | 512 | 100 | ||
| af2 | 4 | 10 | 512 | 50 | ||
| af3 | 3 | 12 | 512 | 0 | ||
| af4 | 2 | 30 | 512 | 0 | ||
| nc1 | 1 | 1 | 512 | 0 | ||
|
|
||
|
|
||
| * Verification: | ||
| * Loss Rate: Capture packet loss for every generated flow and verify that loss for each flow does not exceed expected loss specified in the tables above. | ||
| * Telemetry: Utilize OpenConfig telemetry parameters to validate that per queue dropped packets statistics corresponds (with error margin) to the packet loss reported for every flow matching that particular queue. | ||
|
|
||
| ### DP-1.15.2: Egress Strict Priority scheduler for IPv6 Traffic | ||
|
|
||
| * Traffic Generation: | ||
| * Traffic Profiles: Define traffic profiles for each forwarding class using the ATE, adhering to the linerates (%) specified in the strict priority test traffic tables. | ||
|
|
||
| * Strict Priority Test traffic table for ATE Port 1 | ||
|
|
||
| Forwarding class | Priority | Traffic linerate (%) | Frame size | Expected Loss % | ||
| ----------------- |--------------------- | --------------------------- |--------------------- | ----------------------------------- | ||
| be1 | 6 | 12 | 512 | 100 | ||
| af1 | 5 | 12 | 512 | 100 | ||
| af2 | 4 | 10 | 512 | 50 | ||
| af3 | 3 | 12 | 512 | 0 | ||
| af4 | 2 | 30 | 512 | 0 | ||
| nc1 | 1 | 1 | 512 | 0 | ||
|
|
||
| * Strict Priority Test traffic table for ATE Port 2 | ||
|
|
||
| Forwarding class | Priority | Traffic linerate (%) | Frame size | Expected Loss % | ||
| ----------------- |--------------------- | --------------------------- |--------------------- | ----------------------------------- | ||
| be1 | 6 | 12 | 512 | 100 | ||
| af1 | 5 | 12 | 512 | 100 | ||
| af2 | 4 | 10 | 512 | 50 | ||
| af3 | 3 | 12 | 512 | 0 | ||
| af4 | 2 | 30 | 512 | 0 | ||
| nc1 | 1 | 1 | 512 | 0 | ||
|
|
||
|
|
||
| * Verification: | ||
| * Loss Rate: Capture packet loss for every generated flow and verify that loss for each flow does not exceed expected loss specified in the tables above. | ||
| * Telemetry: Utilize OpenConfig telemetry parameters to validate that per queue dropped packets statistics corresponds (with error margin) to the packet loss reported for every flow matching that particular queue. | ||
|
|
||
| ### DP-1.15.3: Egress Strict Priority scheduler for MPLS Traffic | ||
|
|
||
| * Traffic Generation: | ||
| * Traffic Profiles: Define traffic profiles for each forwarding class using the ATE, adhering to the linerates (%) specified in the strict priority test traffic tables. | ||
|
|
||
| * Strict Priority Test traffic table for ATE Port 1 | ||
|
|
||
| Forwarding class | Priority | Traffic linerate (%) | Frame size | Expected Loss % | ||
| ----------------- |--------------------- | --------------------------- |--------------------- | ----------------------------------- | ||
| be1 | 6 | 12 | 512 | 100 | ||
| af1 | 5 | 12 | 512 | 100 | ||
| af2 | 4 | 10 | 512 | 50 | ||
| af3 | 3 | 12 | 512 | 0 | ||
| af4 | 2 | 30 | 512 | 0 | ||
| nc1 | 1 | 1 | 512 | 0 | ||
|
|
||
| * Strict Priority Test traffic table for ATE Port 2 | ||
|
|
||
| Forwarding class | Priority | Traffic linerate (%) | Frame size | Expected Loss % | ||
| ----------------- |--------------------- | --------------------------- |--------------------- | ----------------------------------- | ||
| be1 | 6 | 12 | 512 | 100 | ||
| af1 | 5 | 12 | 512 | 100 | ||
| af2 | 4 | 10 | 512 | 50 | ||
| af3 | 3 | 12 | 512 | 0 | ||
| af4 | 2 | 30 | 512 | 0 | ||
| nc1 | 1 | 1 | 512 | 0 | ||
|
|
||
|
|
||
| * Verification: | ||
| * Loss Rate: Capture packet loss for every generated flow and verify that loss for each flow does not exceed expected loss specified in the tables above. | ||
| * Telemetry: Utilize OpenConfig telemetry parameters to validate that per queue dropped packets statistics corresponds (with error margin) to the packet loss reported for every flow matching that particular queue. | ||
|
|
||
| ## OpenConfig Path and RPC Coverage | ||
|
|
||
| The below yaml defines the OC paths intended to be covered by this test. | ||
|
|
||
| ```yaml | ||
| paths: | ||
| ## Config paths | ||
| ### Classifiers | ||
| /qos/classifiers/classifier/config/name: | ||
| /qos/classifiers/classifier/config/type: | ||
| /qos/classifiers/classifier/terms/term/config/id: | ||
| /qos/classifiers/classifier/terms/term/conditions/ipv4/config/dscp-set: | ||
| /qos/classifiers/classifier/terms/term/conditions/ipv6/config/dscp-set: | ||
| /qos/classifiers/classifier/terms/term/conditions/mpls/config/traffic-class: | ||
| /qos/classifiers/classifier/terms/term/actions/config/target-group: | ||
|
|
||
| ### Forwarding Groups | ||
| /qos/forwarding-groups/forwarding-group/config/name: | ||
| /qos/forwarding-groups/forwarding-group/config/output-queue: | ||
|
|
||
| ### Queue | ||
| /qos/queues/queue/config/name: | ||
|
|
||
| ### Interfaces | ||
| /qos/interfaces/interface/input/classifiers/classifier/config/type: | ||
| /qos/interfaces/interface/input/classifiers/classifier/config/name: | ||
| /qos/interfaces/interface/output/queues/queue/config/name: | ||
| /qos/interfaces/interface/output/scheduler-policy/config/name: | ||
|
|
||
| ### Scheduler policy | ||
| /qos/scheduler-policies/scheduler-policy/config/name: | ||
| /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/config/priority: | ||
| /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/config/sequence: | ||
| /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/config/type: | ||
| /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/config/id: | ||
| /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/config/input-type: | ||
| /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/config/queue: | ||
|
|
||
| ## State paths | ||
| /qos/interfaces/interface/output/queues/queue/state/name: | ||
| /qos/interfaces/interface/output/queues/queue/state/transmit-pkts: | ||
| /qos/interfaces/interface/output/queues/queue/state/transmit-octets: | ||
| /qos/interfaces/interface/output/queues/queue/state/dropped-pkts: | ||
| /qos/interfaces/interface/output/queues/queue/state/dropped-octets: | ||
|
|
||
| rpcs: | ||
| gnmi: | ||
| gNMI.Set: | ||
| gNMI.Subscribe: | ||
| ``` | ||
| ## Minimum DUT platform requirement | ||
| * MFF - A modular form factor device containing LINECARDs, FABRIC and redundant CONTROLLER_CARD components | ||
| * FFF - fixed form factor |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters