Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QoS-1.1 - Validate Ingress traffic classification #1785

Open
wants to merge 59 commits into
base: main
Choose a base branch
from

Conversation

charantejag504
Copy link
Contributor

@charantejag504 charantejag504 commented Jun 23, 2023

QoS-1.1 - Validate Ingress traffic classification.

  • Configure DUT with ingress and egress routed interfaces.
  • Configure QOS classifiers to match packets arriving on DUT ingress interface to
    corresponding forwarding class according to classification table.
  • Configure packet re-marking for configured classes according to the marking table.
  • One-by-one send flows containing every TOS/TC/EXP value in the classification table.
  • For every flow sent, verify match-packets counters on the DUT ingress interface ( Introduced a new deviation MatchedPacketsOctetsUnsupported as this is not supported by some vendors)
  • Verify that no traffic drops in all flows.

@charantejag504 charantejag504 requested review from a team as code owners June 23, 2023 23:29
@OpenConfigBot
Copy link

OpenConfigBot commented Jun 23, 2023

Pull Request Functional Test Report for #1785 / f49905a

Virtual Devices

Device Test Test Documentation Job Raw Log
Arista cEOS status
QoS-1.1: Ingress traffic classification Test
Cisco 8000E status
QoS-1.1: Ingress traffic classification Test
Cisco XRd status
QoS-1.1: Ingress traffic classification Test
Juniper ncPTX status
QoS-1.1: Ingress traffic classification Test
Nokia SR Linux status
QoS-1.1: Ingress traffic classification Test
Openconfig Lemming status
QoS-1.1: Ingress traffic classification Test

Hardware Devices

Device Test Test Documentation Raw Log
Arista 7808 status
QoS-1.1: Ingress traffic classification Test
Cisco 8808 status
QoS-1.1: Ingress traffic classification Test
Juniper PTX10008 status
QoS-1.1: Ingress traffic classification Test
Nokia 7250 IXR-10e status
QoS-1.1: Ingress traffic classification Test

Help

@mohanasm mohanasm added the anCX label Jun 27, 2023
@greg-dennis
Copy link
Contributor

And please resolve any conversations for comments that are addressed

@charantejag504
Copy link
Contributor Author

I have resolved all the comments addressed, I will address other open comments in the next commit.

sachendras
sachendras previously approved these changes Jul 26, 2023
sachendras
sachendras previously approved these changes Sep 8, 2023
Copy link
Contributor

@greg-dennis greg-dennis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please resolve branch conflicts

Copy link
Contributor

@greg-dennis greg-dennis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving for Go quality

@r4huluk r4huluk added the new-requirement-pr The PR introduces a new test scenario/requirement. label Nov 9, 2023
@sugrimov
Copy link
Contributor

A new readme PR for this test: #3020

Please wait until it is submitted and adjust this PR accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
anCX juniper-pr new-requirement-pr The PR introduces a new test scenario/requirement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants