Verify BFD traffic egress queue and default ToS#10048
Verify BFD traffic egress queue and default ToS#10048prabhataravind merged 4 commits intosonic-net:masterfrom
Conversation
|
The pre-commit check detected issues in the files touched by this pull request. Detailed pre-commit check results: To run the pre-commit checks locally, you can follow below steps:
|
d65f150
* BFD queue 7 test * Fixed sanity checks * Addressed comments * Update bfd_responder to check BFD packet's ToS value
…10083) (sonic-net#13672) #### Why I did it Cherry pick from sonic-net#10083 It is to fix the issue sonic-net#10048 When building .raw image, for instance, target/sonic-broadcom.raw, it will generate a .bin image, target/sonic-broadcom.bin, as the intermediate file. The intermediate file is a build target which may contains different dependencies with the raw one. #### How I did it Rename the intermediate file.
Description of PR
Verify BFD traffic egressing out of Queue 7.
Verify BFD traffic from DUT with default ToS 192.
Summary:
Fixes # (issue)
When the BFD state is up, check queue counters to validate BFD packets using queue 7.
Modified bfd_responder to check the received packet's ToS value.
Type of change
improvement
Approach
What is the motivation for this PR?
To verify egress queue of BFD traffic and default ToS of BFD packets.
How did you do it?
Use DUT's 'show queue counter ' and check for non-zero packets in queue 7.
Check captured BFD packet's ToS value.