[Mellanox][Dual-Tor][DSCP remapping]Fix a test issue for the dualtor tunnel monitor for Nvidia platforms#9625
Conversation
When the inner/outer dscps are 2/2 or 6/6, the packet is not mapped to queue according to the mapping configuration. And such packets are not expected in production, skip the queue check for them. Change-Id: I8f02d086d2f9eb010684e1ac41cf1abfe6ca2788
36dae3d to
e276137
Compare
|
@bingwang-ms kindly reminder. the test fix should be part of 202305. |
|
If the inner DSCP is 2 or 6, the outer DSCP should be 0. Is that right? Why the tunnel_monitor doesn't work? DSCP_TO_TC_MAP: TC_TO_DSCP_MAP: |
|
Hi @bingwang-ms , |
|
@bingwang-ms kindly reminder, this fix is needed also for 202305 |
|
Hi @bingwang-ms , could you approve the PR or let me know if you still have any concerns? |
|
@congh-nvidia Sorry I missed the review. So what's the outer DSCP value if the inner DSCP is 2 or 6? |
|
Hi @bingwang-ms , on Nvidia platforms the inner dscp 2/6 will be encapsulated with outer dscp 2/6 on the standby tor. |
…onic-net#9625) When the inner/outer dscps are 2/2 or 6/6, the packet is not mapped to queue according to the mapping configuration. And such packets are not expected in production, skip the queue check for them. Change-Id: I8f02d086d2f9eb010684e1ac41cf1abfe6ca2788
|
Cherry-pick PR to 202311: #11299 |
…onic-net#9625) When the inner/outer dscps are 2/2 or 6/6, the packet is not mapped to queue according to the mapping configuration. And such packets are not expected in production, skip the queue check for them. Change-Id: I8f02d086d2f9eb010684e1ac41cf1abfe6ca2788
|
Cherry-pick PR to 202305: #11300 |
…9625) When the inner/outer dscps are 2/2 or 6/6, the packet is not mapped to queue according to the mapping configuration. And such packets are not expected in production, skip the queue check for them. Change-Id: I8f02d086d2f9eb010684e1ac41cf1abfe6ca2788
…9625) When the inner/outer dscps are 2/2 or 6/6, the packet is not mapped to queue according to the mapping configuration. And such packets are not expected in production, skip the queue check for them. Change-Id: I8f02d086d2f9eb010684e1ac41cf1abfe6ca2788
Description of PR
Summary:
Fixes # (#9624)
On Nvidia platforms, when the inner/outer DSCPs are 2/2 or 6/6, the tunnel packet is not mapped based on the mapping configuration to queue 1 (they will be mapped to queue 2 and 6).
And we have confirmed with MSFT that such packets are not expected in production.
So, skip the queue check for them.
Type of change
Back port request
Approach
What is the motivation for this PR?
Fix test issue (#9624)
How did you do it?
Skip the queue check in tunnel monitor on Nvidia platforms when dscp is 2/2 or 6/6
How did you verify/test it?
Run test on 4600C dualtor setup, passed.
Any platform specific information?
Only for Nvidia platforms.
Supported testbed topology if it's a new test case?
Documentation