Adding a new test to check TTL decap mode for VxLAN tunnels #21156
+253
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of PR
Summary:
Microsoft ADO ID: 35743773
This PR adds a new test to ensure that the TTL decap mode is set to pipe model for VxLAN tunnels. This means that when a T0 switch that is a VNet endpoint receives a VxLAN packet and decapsulates it, the TTL of the egress packet that is forwarded by the switch is set to the TTL of the inner ingress packet minus 1.
Type of change
Back port request
Approach
What is the motivation for this PR?
On some platforms, the TTL decap mode is set to the uniform model by default, which means that the TTL of the egress packet is set to the TTL of the outer ingress packet minus 1. There is a PR to fix the default behavior on SWSS: 3963
This PR checks that the TTL decap mode is pipe model.
How did you do it?
We setup the T0 switch as a VNet endpoint and then send a VxLAN packet to it. The switch is supposed to decapsulate the ingress packet and then route the inner packet. We check that the TTL of the forwarded inner packet is modified as expected.
How did you verify/test it?
I ran the test on a device that used uniform model. Once with the fix in 3963 and once without it. The image version on the device was 202505.
Without the fix:
With the fix:
Any platform specific information?
Currently, this test runs only on certain Cisco switches. More platforms will be added once the fix in sonic-swss is merged.
Supported testbed topology if it's a new test case?
T0 and its variations.