Test SRv6 dataplane uN behavior#16660
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| self.connected = False | ||
| self.ptfhost = ptfhost | ||
| self._init_ptf_dataplane(ptf_ip, ptf_nn_port, device_num, ptf_port_set) | ||
| self._init_ptf_dataplane(ptf_ip, ptf_ipv6, ptf_nn_port, device_num, ptf_port_set) |
There was a problem hiding this comment.
because the ptf_ipv6 attribute is currently missing in ptfadapter fixture. And in this test case, we need to use the ipv6 address of ptf container as the source ipv6 address.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
BYGX-wcr
force-pushed
the
test-srv6-traffic
branch
from
7625019 to
ee5f208
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
tests/srv6/test_srv6_dataplane.py
Outdated
| time.sleep(5) | ||
|
|
||
| for i in range(0, 10): | ||
| injected_pkt = simple_ipv6_sr_packet( |
There was a problem hiding this comment.
let's send packet without SRH also.
There was a problem hiding this comment.
added parametrization to achieve this goal
| skip: | ||
| reason: "Only target mellanox platform with 202412 image at this time" | ||
| conditions: | ||
| - "asic_type in ['mellanox'] and release in ['202412']" |
There was a problem hiding this comment.
let's add Broadcom also here.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
hi @BYGX-wcr , any dependent PR that we need to merge before this one? |
To the best of my knowledge, no. |
r12f
added
Request for msft-202412 Branch
and removed
Request for msft-202412 Branch
Cherry Pick Conflict_msft-202412
labels
I see. I have tried to pull some of the SRv6 changes in, but still conflicting, then this looks like a legit conflict. Do you mind helping create a manual cherry pick PR to 202412? |
Check the cherry-pick PR below: The conflict happened on the conditional marker file. |
|
manual picked into 202412. |
r12f
added
Approved for msft-202412 Branch
and removed
Cherry Pick Conflict_msft-202412
labels
Test SRv6 dataplane uN and uN +USD behavior
Test SRv6 dataplane uN and uN +USD behavior
Test SRv6 dataplane uN behavior (sonic-net#16660)
4 participants
Description of PR
Summary: Test the basic uN forwarding and decap behavior of SRv6
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation