Full Mesh Traffic Sanity verification #14803
Conversation
…ns/conditional_mark/__init__.py
|
@sreejithsreekumaran please fill all the sections of the commit message |
It will be raised as a separate PR
Please check. I have updated now |
|
New PR #14885 for logfile suffix. |
| def get_tcp_port(): | ||
| val = 1234 | ||
| while True: | ||
| if val == 65535: |
There was a problem hiding this comment.
why we need to remove this line?
There was a problem hiding this comment.
@kevinskwang Strange, I got email notification only today for this comment.
-
The modulo operation ((val + 10) % 65535) will always yield values between 0 and 65534. Hence, val will never actually reach 65535.
-
The updated logic where the ports reset to 1234 after reaching 65534 is for our requirement of needing an infinite supply of ports. This approach effectively reuses port numbers in a cyclic manner, ensuring that we always have ports available without hitting a hard limit, which is crucial in scenarios like full-mesh traffic sanity testing.
2 participants
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
ptf64 topology is used to have 64 ports of the DUT connected
to 64 PTF ports.
How did you verify/test it?
Ran the test on a T1 ptf-64 topology
Any platform specific information?
This is a Cisco specific test case
Supported testbed topology if it's a new test case?
Documentation