Skip to content

[action] [PR:21340] stabilize test_dscp_to_queue_mapping and skip warm-reboot step on smartswitch#22022

Merged
vmittal-msft merged 1 commit intosonic-net:202511from
mssonicbld:cherry/202511/21340
Feb 2, 2026
Merged

[action] [PR:21340] stabilize test_dscp_to_queue_mapping and skip warm-reboot step on smartswitch#22022
vmittal-msft merged 1 commit intosonic-net:202511from
mssonicbld:cherry/202511/21340

Conversation

@mssonicbld
Copy link
Collaborator

Description of PR

  1. To mitigate the impact of noise packets, flush the PTF dataplane before sending and verifying packets
  2. Increase the timeout in case ptf can not handle all packets in the buffer during 1 second, when he ptf buffer has a lot of packets
  3. Skip warm-reboot on smartswitch

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
  • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202205
  • 202305
  • 202311
  • 202405
  • 202411
  • 202505

Approach

What is the motivation for this PR?

Stabilize test_dscp_to_queue_mapping

How did you do it?

  1. To mitigate the impact of noise packets, flush the PTF dataplane before sending and verifying packets
  2. Increase the timeout in case ptf can not handle all packet in the buffer during 1 second, the ptf buffer has a lot of packets

How did you verify/test it?

run test_dscp_to_queue_mapping

Any platform specific information?

Any

Supported testbed topology if it's a new test case?

Documentation

1. To mitigate the impact of noise packets, flush the PTF dataplane before sending and verifying packets
2. Increase the timeout in case ptf can not handle all packet in the buffer during 1 second, the ptf buffer has a lot of packets
@mssonicbld
Copy link
Collaborator Author

Original PR: #21340

@vmittal-msft vmittal-msft merged commit 15128f2 into sonic-net:202511 Feb 2, 2026
5 checks passed
lakshmi-nexthop pushed a commit to lakshmi-nexthop/sonic-mgmt that referenced this pull request Feb 11, 2026
1. To mitigate the impact of noise packets, flush the PTF dataplane before sending and verifying packets
2. Increase the timeout in case ptf can not handle all packet in the buffer during 1 second, the ptf buffer has a lot of packets

Co-authored-by: Jibin Bao <jbao@nvidia.com>
Signed-off-by: Lakshmi Yarramaneni <lakshmi@nexthop.ai>
fraserg-arista pushed a commit to fraserg-arista/sonic-mgmt that referenced this pull request Feb 24, 2026
<!--
Please make sure you've read and understood our contributing guidelines;
https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md

Please provide following information to help code review process a bit easier:
-->
### Description of PR
<!--
- Please include a summary of the change and which issue is fixed.
- Please also include relevant motivation and context. Where should reviewer start? background context?
- List any dependencies that are required for this change.
-->

Summary:
Fixes same issue in [sonic-net#22022](sonic-net/sonic-buildimage#22022) by updating the peer T0's ASN to 4 bytes ASN number.

### Type of change

<!--
- Fill x for your type of change.
- e.g.
- [x] Bug fix
-->

- [ ] Bug fix
- [ ] Testbed and Framework(new/improvement)
- [ ] New Test case
 - [ ] Skipped for non-supported platforms
- [ ] Test case improvement

### Back port request
- [ ] 202012
- [ ] 202205
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411

### Approach
#### What is the motivation for this PR?
Fix topo error.

#### How did you do it?

#### How did you verify/test it?

```
admin@sonic:~$ show ip bgp summary

IPv4 Unicast Summary:
BGP router identifier 10.1.0.32, local AS number 65100 vrf-id 0
BGP table version 2
RIB entries 3, using 672 bytes of memory
Peers 12, using 8903712 KiB of memory
Peer groups 5, using 320 bytes of memory

Neighbhor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName
----------- --- ---------- --------- --------- -------- ----- ------ --------- -------------- --------------
10.0.0.57 4 64600 0 0 0 0 0 never Active ARISTA01T1
10.0.0.59 4 64600 0 0 0 0 0 never Active ARISTA02T1
10.0.0.61 4 64600 0 0 0 0 0 never Active ARISTA03T1
10.0.0.63 4 64600 0 0 0 0 0 never Active ARISTA04T1
10.0.0.65 4 64600 0 0 0 0 0 never Active ARISTA05T1
10.0.0.67 4 64600 0 0 0 0 0 never Active ARISTA06T1
10.0.0.69 4 64600 0 0 0 0 0 never Active ARISTA07T1
10.0.0.71 4 64600 0 0 0 0 0 never Active ARISTA08T1
10.0.0.157 4 4200000000 0 0 0 0 0 never Active ARISTA01PT0
10.0.0.159 4 4200000001 0 0 0 0 0 never Active ARISTA02PT0
10.0.0.161 4 4200000002 0 0 0 0 0 never Active ARISTA03PT0
10.0.0.163 4 4200000003 0 0 0 0 0 never Active ARISTA04PT0

Total number of neighbors 12
admin@sonic:~$ show ipv6 bgp summary

IPv6 Unicast Summary:
BGP router identifier 10.1.0.32, local AS number 65100 vrf-id 0
BGP table version 2
RIB entries 3, using 672 bytes of memory
Peers 12, using 8903712 KiB of memory
Peer groups 5, using 320 bytes of memory

Neighbhor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName
----------- --- ---------- --------- --------- -------- ----- ------ --------- -------------- --------------
fc00::7a 4 64600 0 0 0 0 0 never Active ARISTA03T1
fc00::7e 4 64600 0 0 0 0 0 never Active ARISTA04T1
fc00::8a 4 64600 0 0 0 0 0 never Active ARISTA07T1
fc00::8e 4 64600 0 0 0 0 0 never Active ARISTA08T1
fc00::17a 4 4200000002 0 0 0 0 0 never Active ARISTA03PT0
fc00::17e 4 4200000003 0 0 0 0 0 never Active ARISTA04PT0
fc00::72 4 64600 0 0 0 0 0 never Active ARISTA01T1
fc00::76 4 64600 0 0 0 0 0 never Active ARISTA02T1
fc00::82 4 64600 0 0 0 0 0 never Active ARISTA05T1
fc00::86 4 64600 0 0 0 0 0 never Active ARISTA06T1
fc00::172 4 4200000000 0 0 0 0 0 never Active ARISTA01PT0
fc00::176 4 4200000001 0 0 0 0 0 never Active ARISTA02PT0

Total number of neighbors 12
admin@sonic:~$
```

#### Any platform specific information?

#### Supported testbed topology if it's a new test case?

### Documentation
<!--
(If it's a new feature, new test case)
Did you update documentation/Wiki relevant to your implementation?
Link to the wiki page?
-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants