wrr_traffic_test

DP-1.9: WRR traffic test

Summary

Verify that DUT forwards AF3, AF2, AF1, BE0 and BE1 traffic based on WRR weight.

QoS traffic test setup:

• Topology:

  • 2 input interfaces and 1 output interface with the same port speed. The interface can be a physical interface or LACP bundle interface with the same aggregated speed.

    ATE port 1
        |
       DUT--------ATE port 3
        |
    ATE port 2
  

• Traffic classes:

  • We will use 7 traffic classes NC1, AF4, AF3, AF2, AF1, BE0 and BE1.

• Traffic types:

  • All the traffic tests apply to both IPv4 and IPv6 traffic.

• Queue types:

  • NC1 will have strict priority queues
    • AF4/AF3/AF2/AF1/BE1/BE0 will use WRR queues.
  • NC1 and AF4 will have strict priority queues with NC1 having higher priority.
    • AF3, AF2, AF1, BE1 and BE0 will use WRR queues.

• 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

Procedure

• Connect DUT port-1 to ATE port-1, DUT port-2 to ATE port-2 and DUT port-3 to ATE port-3.

• Configure WRR for AF3, AF2, AF1, BE0 and BE1 with weight 64, 16, 4, 1 and 1 respectively.

• AF3 vs AF2 traffic test

  • Non-oversubscription traffic test case

  Traffic class	Interface1(line rate %)	Interface2(line rate %)	Rx from interface1(%)	Rx from interface2(%)
  AF3	40	40	100	100
  AF2	10	10	100	100

  • Oversubscription traffic test case 1

  Traffic class	Interface1(line rate %)	Interface2(line rate %)	Rx from interface1(%)	Rx from interface2(%)
  AF3	80	80	50	50
  AF2	10	10	100	100

  • Oversubscription traffic test case 2

  Traffic class	Interface1(line rate %)	Interface2(line rate %)	Rx from interface1(%)	Rx from interface2(%)
  AF3	40	40	100	100
  AF2	20	20	50	50

  • Oversubscription traffic test case 3

  Traffic class	Interface1(line rate %)	Interface2(line rate %)	Rx from interface1(%)	Rx from interface2(%)
  AF3	50	50	80	80
  AF2	50	50	20	20

• Repeat the above 3 oversubscription test cases between traffic classes

  • AF2 vs AF1
  • AF1 vs BE1
  • BE1 vs BE0

Config parameter coverage

• Classifiers

  • /qos/classifiers/classifier/config/name
  • /qos/classifiers/classifier/config/type
  • /qos/classifiers/classifier/terms/term/actions/config/target-group
  • /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/config/id

• 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/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
  • /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/config/weight

Telemetry parameter coverage

• /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

OpenConfig Path and RPC Coverage

The below yaml defines the OC paths intended to be covered by this test. OC paths used for test setup are not listed here.

paths:
  ## Config paths:
  /qos/forwarding-groups/forwarding-group/config/name:
  /qos/forwarding-groups/forwarding-group/config/output-queue:
  /qos/queues/queue/config/name:
  /qos/classifiers/classifier/config/name:
  /qos/classifiers/classifier/config/type:
  /qos/classifiers/classifier/terms/term/actions/config/target-group:
  /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/config/id:
  /qos/interfaces/interface/output/queues/queue/config/name:
  /qos/interfaces/interface/input/classifiers/classifier/config/name:
  /qos/interfaces/interface/output/scheduler-policy/config/name:
  /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:
  /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/config/weight:

  ## State paths:
  /qos/forwarding-groups/forwarding-group/state/name:
  /qos/forwarding-groups/forwarding-group/state/output-queue:
  /qos/queues/queue/state/name:
  /qos/classifiers/classifier/state/name:
  /qos/classifiers/classifier/state/type:
  /qos/classifiers/classifier/terms/term/actions/state/target-group:
  /qos/classifiers/classifier/terms/term/conditions/ipv4/state/dscp-set:
  /qos/classifiers/classifier/terms/term/conditions/ipv6/state/dscp-set:
  /qos/classifiers/classifier/terms/term/state/id:
  /qos/interfaces/interface/output/queues/queue/state/name:
  /qos/interfaces/interface/input/classifiers/classifier/state/name:
  /qos/interfaces/interface/output/scheduler-policy/state/name:
  /qos/scheduler-policies/scheduler-policy/state/name:
  /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/state/priority:
  /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/state/sequence:
  /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/state/type:
  /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/state/id:
  /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/state/input-type:
  /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/state/queue:
  /qos/scheduler-policies/scheduler-policy/schedulers/scheduler/inputs/input/state/weight:

rpcs:
  gnmi:
    gNMI.Set:
      Replace: