[Nokia][pmon] Update Nokia sonic-platform submodule#2462
Closed
Pavan-Nokia wants to merge 4351 commits into
Closed
[Nokia][pmon] Update Nokia sonic-platform submodule#2462Pavan-Nokia wants to merge 4351 commits into
Pavan-Nokia wants to merge 4351 commits into
Conversation
Root cause:
On T2 device, the TO_BGP_PEER route-map sequence 60 was missing "on-match next", causing it to stop processing and preventing sequence 100 (CHECK_IDF_ISOLATION) from being reached.
Route → Seq 50 (tag contributing routes) → on-match next → Seq 60 (strip local anchor community) → STOP (no on-match next) → Seq 100 (CHECK_IDF_ISOLATION) ← NEVER REACHED!
This caused:
- IDF isolation to not work (no-export community not added)
- test_seq_idf_isolation.py to fail on T2
In disaggregated case, though only LT2 will have the peers with T1, we will see this issue consistently when UT2 is peered with T1, which has discovered the gaps in the templates. This gap is potential enough cause issues in other cases as well.
Resolution:
Add "on-match next" to sequence 60 in TO_BGP_PEER_V4/V6 route-maps to allow processing to continue to sequence 100 (CHECK_IDF_ISOLATION).
Route → Seq 50 (tag contributing routes) → on-match next → Seq 60 (strip local anchor community) → on-match next → Seq 100 (CHECK_IDF_ISOLATION) ← NOW REACHABLE
Tested the below testcases with this fix and it is passing.
- test_seq_idf_isolation.py
- test_prefix_list.py
- test_ipv6_nlri_over_ipv4.py
- test_bgp_update_timer.py
- test_route_flap.py
<!--
Please make sure you've read and understood our contributing guidelines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
** Make sure all your commits include a signature generated with `git commit -s` **
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx" or "resolves #xxxx"
Please provide the following information:
-->
#### Why I did it
##### Work item tracking
- Microsoft ADO **(number only)**:
#### How I did it
#### How to verify it
<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->
#### Which release branch to backport (provide reason below if selected)
<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [ ] 202505
- [x] 202511
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->
#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->
Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
#### A picture of a cute animal (not mandatory but encouraged)
…atically (#26692) #### Why I did it src/sonic-utilities ``` * b0cc77ff - (HEAD -> 202511, origin/202511) Enable express boot support for Marvell Teralynx platform (#4443) (2 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…tically (#26690) #### Why I did it src/sonic-sairedis ``` * 3f2cdff3 - (HEAD -> 202511, origin/202511) [202511] Upgrade SAI to v1.17.5 (Azure#1838) (16 minutes ago) [prabhataravind] * 00d08dde - [syncd]: Clean up ENI counter entries from COUNTERS_DB on ENI deletion (Azure#1841) (48 minutes ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
#### Why I did it Upgrade Broadcom xgs SAI version from 14.3.0.0.0.0.8.0 to 14.3.0.0.0.0.9.0. Changelog: - 14.3.0.0.0.0.9.0: Fix for - Preemphasis Settings Are Not Correctly Applied to Subordinated Interfaces ##### Work item tracking - Microsoft ADO **(number only)**: 37432955 #### How I did it Updated `LIBSAIBCM_XGS_VERSION` in `platform/broadcom/sai-xgs.mk` from `14.3.0.0.0.0.8.0` to `14.3.0.0.0.0.9.0`. #### How to verify it Load image on a DUT, all containers and BGP are up and running. ``` admin@bjw2-can-7260-2:~$ show version SONiC Software Version: SONiC.master-26632.1081721-c7383d15a SONiC OS Version: 13 Distribution: Debian 13.4 Kernel: 6.12.41+deb13-sonic-amd64 Build commit: c7383d15a Build date: Tue Apr 7 10:54:44 UTC 2026 Built by: azureuser@89343121c000000 Platform: x86_64-arista_7260cx3_64 HwSKU: Arista-7260CX3-D108C8 ASIC: broadcom ASIC Count: 1 Serial Number: JPA2403P33Z Model Number: DCS-7260CX3-64 Hardware Revision: 03.00 Uptime: 07:07:13 up 6 min, 1 user, load average: 1.82, 1.50, 0.79 Date: Thu 09 Apr 2026 07:07:13 admin@bjw2-can-7260-2:~$ docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES aa3a186dde3c docker-snmp:latest "/usr/bin/docker-snm…" 5 minutes ago Up 5 minutes snmp c156c44f725a docker-platform-monitor:latest "/usr/bin/docker_ini…" 5 minutes ago Up 5 minutes pmon 6a6d7b015ba0 docker-sonic-mgmt-framework:latest "/usr/local/bin/supe…" 5 minutes ago Up 5 minutes mgmt-framework a2a69f869212 docker-lldp:latest "/usr/bin/docker-lld…" 5 minutes ago Up 5 minutes lldp 90227a66a984 docker-sonic-gnmi:latest "/usr/local/bin/supe…" 5 minutes ago Up 5 minutes gnmi bc63f097192e docker-dhcp-relay:latest "/usr/bin/docker_ini…" 5 minutes ago Up 5 minutes dhcp_relay 719468639bcd docker-router-advertiser:latest "/usr/bin/docker-ini…" 6 minutes ago Up 6 minutes radv b119e221b2b1 docker-eventd:latest "/usr/local/bin/supe…" 6 minutes ago Up 6 minutes eventd 1b4e918a7740 docker-syncd-brcm:latest "/usr/local/bin/supe…" 6 minutes ago Up 6 minutes syncd b9cb2193233d docker-fpm-frr:latest "/usr/bin/docker_ini…" 6 minutes ago Up 6 minutes bgp 5b40c20a2413 docker-teamd:latest "/usr/local/bin/supe…" 6 minutes ago Up 6 minutes teamd 3ecf69cb429a docker-sysmgr:latest "/usr/local/bin/supe…" 6 minutes ago Up 6 minutes sysmgr 8dd8960fba80 docker-orchagent:latest "/usr/bin/docker-ini…" 6 minutes ago Up 6 minutes swss 9b654d3c9af7 docker-sonic-restapi:latest "/usr/local/bin/supe…" 6 minutes ago Up 6 minutes restapi add481ec5998 docker-database:latest "/usr/local/bin/dock…" 7 minutes ago Up 7 minutes database admin@bjw2-can-7260-2:~$ show ip bgp summary IPv4 Unicast Summary: BGP router identifier 10.1.0.32, local AS number 4200065100 vrf-id 0 BGP table version 6406 RIB entries 12808, using 1639424 bytes of memory Peers 4, using 96288 KiB of memory Peer groups 4, using 256 bytes of memory Neighbhor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd NeighborName ----------- --- ---------- --------- --------- -------- ----- ------ --------- -------------- -------------- 10.0.0.33 4 4200064600 3347 3380 6406 0 0 00:05:57 6400 ARISTA01T1 10.0.0.35 4 4200064600 3348 3380 6406 0 0 00:05:57 6400 ARISTA02T1 10.0.0.37 4 4200064600 3347 3380 6406 0 0 00:05:58 6400 ARISTA03T1 10.0.0.39 4 4200064600 3346 3380 6406 0 0 00:05:58 6400 ARISTA04T1 Total number of neighbors 4 ``` #### Which release branch to backport (provide reason below if selected) - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [x] 202511 #### Tested branch (Please provide the tested image version) - [x] master <!-- image version: SONiC.master-26632.1081721-c7383d15a --> #### Description for the changelog Upgrade Broadcom xgs SAI version to 14.3.0.0.0.0.9.0. Signed-off-by: zitingguo <zitingguo@microsoft.com> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
SAI 14.1 fixes for Arista-7060X6-64PE-B-P32O64 Arista-7060X6-64PE-B-P64 Followup to sonic-net/sonic-buildimage#25451 <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [ ] 202511 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
SAI 14.1 fixes for Arista-7060X6-64PE-B-C448O16 Arista-7060X6-64PE-B-C512S2 Arista-7060X6-64PE-B-O128 Followup to sonic-net/sonic-buildimage#25451 <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [ ] 202511 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
…12 (Azure#2166) ```<br>* 765bda4 - (HEAD -> 202512) Merge branch '202511' of https://github.com/sonic-net/sonic-buildimage into 202512 (2026-04-11) [Sonic Automation] * de9a265 - (head/202511) Fix buffer pool sizes for Arista-7060X6-64PE-B SKUs (#26707) (2026-04-11) [mssonicbld] * 75aa525 - Fix buffer pool sizes for Arista-7060X6-64PE-B SKUs (#26706) (2026-04-11) [mssonicbld] * 83e3081 - [Broadcom] Upgrade Broadcom xgs SAI version to 14.3.0.0.0.0.9.0 (#26708) (2026-04-11) [mssonicbld] * 9e5bd3e - [submodule] Update submodule sonic-sairedis to the latest HEAD automatically (#26690) (2026-04-10) [mssonicbld] * 8c4dbbb - [submodule] Update submodule sonic-utilities to the latest HEAD automatically (#26692) (2026-04-10) [mssonicbld] * 97c6e89 - test_seq_idf_isolation.py failure on T2 (#26606) (2026-04-09) [mssonicbld]<br>```
…6711) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it When DPU's are powered off and sensord restarts, we see the following error log. ` 2026 Mar 17 18:24:42.400471 sonic ERR pmon#sensord: Error getting sensor data: mlx5/#0: Kernel interface error ` ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it This PCI Adapter sensor is not relevant after the DPU is powered off. Thus, add it to ignore list when it is powered off. #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> When all DPU's are powered on: ``` mlx5-pci-0800 Adapter: PCI adapter asic: temp1_input: 60.000 temp1_crit: 91.000 temp1_highest: 60.000 -- mlx5-pci-0100 Adapter: PCI adapter asic: temp1_input: 68.000 temp1_crit: 91.000 temp1_highest: 68.000 -- mlx5-pci-0200 Adapter: PCI adapter asic: temp1_input: 64.000 temp1_crit: 91.000 temp1_highest: 65.000 -- mlx5-pci-0700 Adapter: PCI adapter asic: temp1_input: 71.000 temp1_crit: 91.000 temp1_highest: 73.000 ``` Turn off the DPU's and no error log is seen ``` root@sonic:/home/admin# config chassis modules shutdown DPU3 Shutting down chassis module DPU3 ``` #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [ ] 202511 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
…nderscore in dpu name, change main_dpu_ids to string (#26710) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> [yang][ssw] add dpu_vnet and dpu_vnet to global config table, allow underscore in dpu name, change main_dpu_ids to string sign-off: Jing Zhang zhangjing@microsoft.com #### Why I did it Otherwise yang validate would fail. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Update the smartswitch yang models. #### How to verify it UTs. <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [x] 202511 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
…lly (#26691) #### Why I did it src/sonic-swss ``` * f907511d - (HEAD -> 202511, origin/202511) Gracefully handle case when speed is not supported in setGearboxPortAttr (#4462) (30 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…atically (#26719) #### Why I did it src/sonic-utilities ``` * 902205a7 - (HEAD -> 202511, origin/202511) Show vnet route cli update on 202511 (#4448) (2 hours ago) [David Zhang] * 080ebf66 - Sfputil: don't abort eeprom-hexdump on single page read failure (#4447) (4 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…12 (Azure#2169) ```<br>* b7d38fc - (HEAD -> 202512) Merge branch '202511' of https://github.com/sonic-net/sonic-buildimage into 202512 (2026-04-12) [Sonic Automation] * 5248f44 - (head/202511) [submodule] Update submodule sonic-utilities to the latest HEAD automatically (#26719) (2026-04-11) [mssonicbld] * c984157 - [submodule] Update submodule sonic-swss to the latest HEAD automatically (#26691) (2026-04-11) [mssonicbld] * f0f582a - [yang][ssw] add dpu_vnet and dpu_vnet to global config table, allow underscore in dpu name, change main_dpu_ids to string (#26710) (2026-04-11) [mssonicbld] * 55327d4 - [SmartSwitch] [Mellanox] Ignore PCI sensors when DPU is power off (#26711) (2026-04-11) [mssonicbld]<br>```
…D automatically (#26727) #### Why I did it src/sonic-platform-daemons ``` * 3210710 - (HEAD -> 202511, origin/202511) [cmis] Optimize data path state machine by reducing the time spent checking the fast reboot flag (Azure#793) (23 hours ago) [Junchao-Mellanox] ``` #### How I did it #### How to verify it #### Description for the changelog
…12 (Azure#2172) ```<br>* 5c51b35 - (HEAD -> 202512) Merge branch '202511' of https://github.com/sonic-net/sonic-buildimage into 202512 (2026-04-13) [Sonic Automation] * a8e5fc3 - (head/202511) [submodule] Update submodule sonic-platform-daemons to the latest HEAD automatically (#26727) (2026-04-12) [mssonicbld]<br>```
…-syncd-b…" (#26730) This reverts commit 379a7a6. Signed-off-by: Liping Xu <108326363+lipxu@users.noreply.github.com>
Signed-off-by: bingwang <bingwang@microsoft.com>
#### Why I did it On Debian 13 (Trixie), `rsyslog.service` includes systemd sandboxing directives (`PrivateTmp`, `ProtectSystem`, `ProtectKernelTunables`, etc.) that add ~4 seconds of overhead per restart due to namespace setup/teardown. This causes syslog-dependent tests to fail by missing log messages during the extended restart window. Fixes #25382 #### How I did it Instead of always restarting rsyslog after generating the config, we now: 1. Generate the config to a unique temp file (`mktemp`) 2. Compare with the existing `/etc/rsyslog.conf` using `cmp -s` 3. **Config changed** (or first boot): install the new config and restart rsyslog 4. **Config unchanged**: send `SIGHUP` to rsyslog to re-open log files without a full restart The `SIGHUP` fallback is critical — it ensures rsyslog re-opens its file handles even when the config has not changed (needed after log rotation or `/var/log` remounts), while completely avoiding the 4-second namespace teardown/setup cycle. This preserves the upstream Trixie sandboxing directives. Additional hardening: - `mktemp` for unique temp files with `trap`-based cleanup on exit - Explicit first-boot handling (missing `/etc/rsyslog.conf`) - Error handling on `cp` failure (do not restart with stale config) #### How to verify it 1. Build a VS image with this change 2. Boot and verify rsyslog is running: `systemctl status rsyslog` 3. Run `config reload` — rsyslog should NOT restart (config unchanged), only SIGHUP: ``` journalctl -u rsyslog --since "1 min ago" # Should show rsyslog re-opening files, NOT a stop/start cycle ``` 4. Change a syslog config (e.g., add a remote server), run `config reload` — rsyslog should do a full restart 5. Run `syslog/test_logrotate.py` — both test cases should pass (SIGHUP re-opens files after /var/log remount) Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
…12 (Azure#2175) ```<br>* b174c71 - (HEAD -> 202512) Merge branch '202511' of https://github.com/sonic-net/sonic-buildimage into 202512 (2026-04-14) [Sonic Automation] * 66766f5 - (head/202511) [rsyslog] Fix Trixie restart delay with conditional restart (#26576) (2026-04-14) [mssonicbld] * 8b612d2 - Revert "[platform/broadcom]: Remove static warmboot mount from docker-syncd-b…" (#26730) (2026-04-13) [Liping Xu]<br>```
Signed-off-by: Anand Mehra (anamehra) <anamehra@cisco.com> <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it When some fabric asics may fail enumeration or detection on Supervisor, the CHASSIS_FABRIC_ASIC_INFO_TABLE may not contain keys for those asics. In such case, container_checker may not catch the issue for the expected dockers not up. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it This enhancement adds support for a platform-provided expected ASIC list as a fallback mechanism, ensuring that container_checker and system health monitoring can track expected running containers even when ASIC enumeration fails. The expected ASIC list is read from 'platform_expected_asic_list.conf' file. If not present, the dynamic CHASSIS_FABRIC_ASIC_INFO_TABLE is used. The platform will generate platform_expected_asic_list.conf dynamically based on the expected asics to be up based on FC presence. e.g.: cat /usr/share/sonic/device/x86_64-8800_rp-r0/platform_expected_asic_list.conf [0, 1, 4, 5, 6, 7, 8, 9, 10, 11, 13, 14] #### How to verify it Create /usr/share/sonic/device/<>/platform_expected_asic_list.conf file with various data as in the logs to validate. ``` Logs from system where asics in DB are 0, 1, 4, 5, 6, 7, 8, 9, 10, 11 Modified platform_expected_asic_list.conf to add 13 and 14 root@yy39-rp:/home/admin# cat /usr/share/sonic/device/x86_64-8800_rp-r0/platform_expected_asic_list.conf [0, 1, 4, 5, 6, 7, 8, 9, 10, 11, 13, 14] root@yy39-rp:/home/admin# container_checker Expected containers not running: teamd14, syncd13, swss13, swss14, teamd13, syncd14 Original list: root@yy39-rp:/home/admin# cat /usr/share/sonic/device/x86_64-8800_rp-r0/platform_expected_asic_list.conf [0, 1, 4, 5, 6, 7, 8, 9, 10, 11] root@yy39-rp:/home/admin# container_checker root@yy39-rp:/home/admin# Empty list root@yy39-rp:/home/admin# cat /usr/share/sonic/device/x86_64-8800_rp-r0/platform_expected_asic_list.conf [] root@yy39-rp:/home/admin# container_checker [4, 8, 0, 11, 7, 9, 1, 10, 5, 6] File not present root@yy39-rp:/home/admin# rm /usr/share/sonic/device/x86_64-8800_rp-r0/platform_expected_asic_list.conf root@yy39-rp:/home/admin# container_checker [4, 8, 0, 11, 7, 9, 1, 10, 5, 6] ``` <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [x] 202405 - [ ] 202411 - [ ] 202505 - [x] 202511 - [ ] #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it 202511 includes migration to Debian 13 from Debian 12. Previous kubelet cgroupdriver configuration was set to cgroupfs for compatibility with Debian 12. Debian 13 expects systemd cgroupdriver, so we explicitly configure systemd cgroupdriver in SONiC OSVersion >= 202511. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Fix contents of /etc/default/kubelet configuration file #### How to verify it Run test_k8s_join_disjoin.py on image built with updated /etc/default/kubelet configuration file <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [x] 202511 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Occasionally, the psutil lib will through error when trying to read name. Retrying fix the problem. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Retry the operation #### How to verify it Applied it on production machine and fixed the issue <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [x] 202505 - [x] 202511 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
…#26596) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it An inconsistency was found between sai_5600.xml in the SN5600 Simx platform (x86_64-nvidia_sn5600_simx-r0) and the non-Simx variant (x86_64-nvidia_sn5600-r0). ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it To avoid maintaining duplicate files, I replaced the duplicate file with a symlink pointing to the non-SimX variant. This ensures both platforms use the same correct source of truth. #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202205 - [ ] 202211 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
<!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Add BGP confederation support for disaggregated T2 devices (LowerSpineRouter, UpperSpineRouter, FabricSpineRouter) in SONiC. BGP confederations allow a large AS to be subdivided into smaller sub-ASes while appearing as a single AS to external peers. This is essential for scaling BGP in disaggregated T2 spine topologies. Additionally, this PR moves the remote-as configuration for VoQ chassis internal peers from per-neighbor (instance.conf.j2) to the peer-group level (peer-group.conf.j2). This is required for confederation setups where all VoQ chassis internal peers share the same ASN, simplifying configuration and aligning with best practices. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it - YANG model: Added a CONFED container under BGP_DEVICE_GLOBAL for BGP Confederation configuration. - FRR Jinja2 template to apply the BGP confederation configuration in FRR **Unit tests:** - YANG model tests: Added positive test (BGP_DEVICE_GLOBAL_CONFED) and negative test (BGP_DEVICE_GLOBAL_CONFED_INVALID_ASN) for the new CONFED container - sonic-bgpcfgd: Added 4 new test_sonic-cfggen.py tests covering confederation config generation for UpperT2 (single & multi-ASIC), LowerT2, and FabricT2 with corresponding JSON input and expected .conf output files - sonic-config-engine: Added 5 new test_frr.py tests covering confederation for UpperT2, UpperT2 multi-ASIC, LowerT2 (with both space and semicolon-separated peers), and FabricT2 - Updated VoQ chassis test data to reflect remote-as moving from instance to peer-group level #### How to verify it <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [x ] 202511 #### Tested branch (Please provide the tested image version) Testing internal on 20251111 image in MSFT lab <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
add 300m cable length for F2 T0 and T1 hwsku Signed-off-by: Fraser Gordon <fraserg@arista.com> Co-authored-by: Dashuai Zhang <164845223+sdszhang@users.noreply.github.com>
…#26685) <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md failure_prs.log skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it Adds InfluxDB to the docker-ptf container image so PTF-based HFT E2E tests can run with an InfluxDB instance available inside the container. ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Download and install the InfluxDB 2.x influxd binary into the PTF container during image build. Use Jinja2 template conditionals on CONFIGURED_ARCH to select the correct InfluxDB release tarball architecture. #### How to verify it Verified it in ptf container: ``` admin@ptf:~/influxdb2-2.8.0$ ./influxd 2026-03-23T05:24:31.089933Z info Welcome to InfluxDB {"log_id": "11nIH2xG000", "version": "v2.8.0", "commit": "40a633239e", "build_date": "2025-12-02T20:35:00Z", "log_level": "info"} 2026-03-23T05:24:31.110260Z info Resources opened {"log_id": "11nIH2xG000", "service": "bolt", "path": "/home/janetcui/.influxdbv2/influxd.bolt"} 2026-03-23T05:24:31.110352Z info Resources opened {"log_id": "11nIH2xG000", "service": "sqlite", "path": "/home/janetcui/.influxdbv2/influxd.sqlite"} 2026-03-23T05:24:31.114860Z info Bringing up metadata migrations {"log_id": "11nIH2xG000", "service": "KV migrations", "migration_count": 21} 2026-03-23T05:24:31.591523Z info Bringing up metadata migrations {"log_id": "11nIH2xG000", "service": "SQL migrations", "migration_count": 8} 2026-03-23T05:24:31.740554Z info Using data dir {"log_id": "11nIH2xG000", "service": "storage-engine", "service": "store", "path": "/home/janetcui/.influxdbv2/engine/data"} 2026-03-23T05:24:31.740654Z info Compaction settings {"log_id": "11nIH2xG000", "service": "storage-engine", "service": "store", "max_concurrent_compactions": 8, "throughput_bytes_per_second": 50331648, "throughput_bytes_per_second_burst": 50331648} 2026-03-23T05:24:31.740675Z info Open store (start) {"log_id": "11nIH2xG000", "service": "storage-engine", "service": "store", "op_name": "tsdb_open", "op_event": "start"} 2026-03-23T05:24:31.740759Z info Open store (end) {"log_id": "11nIH2xG000", "service": "storage-engine", "service": "store", "op_name": "tsdb_open", "op_event": "end", "op_elapsed": "0.086ms"} 2026-03-23T05:24:31.740793Z info Starting retention policy enforcement service {"log_id": "11nIH2xG000", "service": "retention", "check_interval": "30m"} 2026-03-23T05:24:31.740816Z info Starting precreation service {"log_id": "11nIH2xG000", "service": "shard-precreation", "check_interval": "10m", "advance_period": "30m"} 2026-03-23T05:24:31.741432Z info Starting query controller {"log_id": "11nIH2xG000", "service": "storage-reads", "concurrency_quota": 1024, "initial_memory_bytes_quota_per_query": 9223372036854775807, "memory_bytes_quota_per_query": 9223372036854775807, "max_memory_bytes": 0, "queue_size": 1024} 2026-03-23T05:24:31.744928Z info Configuring InfluxQL statement executor (zeros indicate unlimited). {"log_id": "11nIH2xG000", "max_select_point": 0, "max_select_series": 0, "max_select_buckets": 0} 2026-03-23T05:24:31.763104Z info Starting {"log_id": "11nIH2xG000", "service": "telemetry", "interval": "8h"} 2026-03-23T05:24:31.763240Z info Listening {"log_id": "11nIH2xG000", "service": "tcp-listener", "transport": "http", "addr": ":8086", "port": 8086} ``` <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [x] 202511 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
Enabled the interrupt for all 32 cores Packet corruption can be triggered for some devices manually and the interrupts will appear in syslog: 0:dnxc_interrupt_print_info: name=NBU_CrcTxChkErrInt, id=2036, index=0, block=12, unit=0, recurring_action=0 | Check Configuration | None Signed-off-by: Saravanan Sellappa <saravanan@nexthop.ai>
#### Why I did it On some image upgrade scenarios after sonic-installer install, docker.service can be socket-activated very early during first boot while platform package installation is still running in rc.local. Early Docker client access can now correctly activate dockerd through docker.socket. During this early first-boot window, the IPv6 ip6tables/nf_tables path may not yet be ready, causing dockerd initialization to fail. This failure cascades into dependency failures for: database.service config-setup.service interfaces-config.service Since config-setup.service and interfaces-config.service are oneshot services, they may not be automatically retriggered later even after Docker recovers normally, leaving management interface eth0 unconfigured until manual recovery. This change ensures Docker startup waits until the required IPv6 netfilter/iptables path is ready before dockerd initialization proceeds. The change only adds a lightweight Docker startup readiness check and does not affect normal steady-state boot behavior. Existing platforms that already have the required netfilter path ready are unaffected. #### How I did it Added a Docker startup readiness helper script: files/docker/docker-netfilter-ready.sh The helper waits until: ip6tables -w -t filter -L ip6tables -w -t nat -L complete successfully before allowing dockerd startup. Added the following to docker.service.conf: ExecStartPre=/usr/local/bin/docker-netfilter-ready.sh Installed the helper script into the target filesystem from build_debian.sh. #### How to verify it Install a new SONiC image using: sonic-installer install <image> Remove old config to force fresh first-boot initialization: rm -rf /host/old_config Reboot into the newly installed image. Verify Docker starts successfully without early dependency failures: systemctl status docker database config-setup interfaces-config --no-pager systemctl --failed --no-pager Verify management interface is configured automatically: show ip int | grep eth0 Verify no Docker ip6tables initialization failure appears in boot logs: journalctl -b -u docker -u database -u config-setup -u interfaces-config --no-pager #### Which release branch to backport (provide reason below if selected) - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [x] 202511 #### Tested branch (Please provide the tested image version) master #### Description for the changelog Fix first-boot image upgrade issue where early Docker socket activation could trigger Docker startup before the IPv6 netfilter/iptables path was ready, causing dependency failures for database/config services and leaving eth0 unconfigured after upgrade. #### UT log Before fix: First boot after sonic-installer install enters rc.local first-boot platform package installation. docker.service is activated early during first boot. Docker fails during IPv6 ip6tables/nf_tables initialization. database.service, config-setup.service, and interfaces-config.service hit dependency failures. Docker/database may later recover, but oneshot services may remain inactive. eth0 is not configured until manual recovery. Key log pattern: [FAILED] Failed to start docker.service - Docker Application Container Engine. [DEPEND] Dependency failed for database.service - Database container. [DEPEND] Dependency failed for config-setup.service - Config initialization and migration service. [DEPEND] Dependency failed for interfaces-config.service - Update interfaces configuration. show ip int: eth0 missing After fix: Docker startup waits until IPv6 ip6tables paths are usable. docker.service starts successfully during first boot. database.service, config-setup.service, and interfaces-config.service complete successfully. eth0 is configured automatically without manual recovery. Key log pattern: systemd: Started docker.service - Docker Application Container Engine. systemd: Started database.service - Database container. systemd: Finished config-setup.service - Config initialization and migration service. systemd: Finished interfaces-config.service - Update interfaces configuration. show ip int: eth0 1.2.21.43/16 up/up Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
#### Why I did it This [PR22428](sonic-net/sonic-buildimage#22428) has potentially introduced CRC error on the peer NIC connected to this TOR 7050CX3-32S during cold reboot upgrade to 202505 ##### Work item tracking - Microsoft ADO **(number only)**: #### How I did it Removed the SI settings for `COPPER25` media i.e 100G DAC cables #### How to verify it 1. Verified with brcm diag shell the 100G DAC cables are now using the old TX FIR settings 2. Tested this with multiple RX signal adaptation on the NIC side #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [X] 202511 #### Tested branch (Please provide the tested image version) <!-- - Please provide tested image version - e.g. - [x] 20201231.100 --> - [ ] <!-- image version 1 --> - [ ] <!-- image version 2 --> #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: Lawrence Lee <lawlee@microsoft.com>
…lly (#27503) #### Why I did it src/sonic-swss ``` * bc4d7626 - (HEAD -> 202511, origin/202511) [dash]: Add ENI OID mapping and DPU counter DB support (#4540) (#4590) (5 days ago) [Lawrence Lee] ``` #### How I did it #### How to verify it #### Description for the changelog
…atically (#27457) #### Why I did it src/sonic-utilities ``` * 9b578d64 - (HEAD -> 202511, origin/202511) Broadcom show techsupport comamnds update (#4560) (6 days ago) [mssonicbld] * b3feb8a7 - Added SPC5 and SN4280 SKUs (#4557) (7 days ago) [sschlafman] * 7c260355 - [Mellanox] [generate_dump] Collect SSD dump (#4553) (8 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…tically (#27486) #### Why I did it src/sonic-dash-api ``` * 2e975c0 - (HEAD -> 202511, origin/202511) [action] [PR:67] Update the order of keys in ha_scope_config (Azure#68) (6 days ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…12 (Azure#2357) ```<br>* 12f9e85 - (HEAD -> 202512) Merge branch '202511' of https://github.com/sonic-net/sonic-buildimage into 202512 (2026-05-28) [Sonic Automation] * bddefd1 - (head/202511) [submodule] Update submodule sonic-dash-api to the latest HEAD automatically (#27486) (2026-05-28) [mssonicbld] * 50b2214 - [submodule] Update submodule sonic-utilities to the latest HEAD automatically (#27457) (2026-05-28) [mssonicbld] * 7af4d4b - [submodule] Update submodule sonic-swss to the latest HEAD automatically (#27503) (2026-05-28) [mssonicbld] * 849c44c - Update DPU HWSKU context config to use DPU_COUNTERS_DB (#27499) (2026-05-27) [Lawrence Lee] * dd2355b - [7050CX3]Revert the media settings for 100G copper media (#27484) (2026-05-28) [mssonicbld] * 7c25ff4 - Wait for Docker netfilter readiness before startup (#27477) (2026-05-28) [mssonicbld] * f610646 - Q3D needs this interrupt enabled to detect packet corruption (#27501) (2026-05-27) [saravanan sellappa] * eeb05d3 - NH-5010 - Set GRUB timeout_style=countdown (#27500) (2026-05-28) [mssonicbld]<br>```
…nent ordering (#27523) Needed due to arista sonic-platform-module changes. <!-- Please make sure you've read and understood our contributing guidelines: https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md CODE_OF_CONDUCT.md LICENSE README.md SECURITY.md SUPPORT.md azure-pipelines failure_prs.log scripts skip_prs.log Make sure all your commits include a signature generated with `git commit -s` ** If this is a bug fix, make sure your description includes "fixes #xxxx", or "closes #xxxx" or "resolves #xxxx" Please provide the following information: --> #### Why I did it The platform.json is out of date, this change fixes the component ordering. #### How to verify it Run `platform_tests/api/test_component.py::TestComponentApi::test_get_name` on the updated skus to see it pass. <!-- If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012. --> #### Which release branch to backport (provide reason below if selected) <!-- - Note we only backport fixes to a release branch, *not* features! - Please also provide a reason for the backporting below. - e.g. - [x] 202006 --> - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [x] 202511 #### Tested branch (Please provide the tested image version) 202511 #### Description for the changelog <!-- Write a short (one line) summary that describes the changes in this pull request for inclusion in the changelog: --> <!-- Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU. --> #### Link to config_db schema for YANG module changes <!-- Provide a link to config_db schema for the table for which YANG model is defined Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md --> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
Add _PLATFORM makefile entry to arista firmware so UEFI/onie build picks it up
<!--
Please make sure you've read and understood our contributing guidelines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
** Make sure all your commits include a signature generated with `git commit -s` **
If this is a bug fix, make sure your description includes "fixes #xxxx", or
"closes #xxxx" or "resolves #xxxx"
Please provide the following information:
-->
#### Why I did it
##### Work item tracking
- Microsoft ADO **(number only)**:
#### How I did it
#### How to verify it
<!--
If PR needs to be backported, then the PR must be tested against the base branch and the earliest backport release branch and provide tested image version on these two branches. For example, if the PR is requested for master, 202211 and 202012, then the requester needs to provide test results on master and 202012.
-->
#### Which release branch to backport (provide reason below if selected)
<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [ ] 202505
- [ ] 202511
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
-->
#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->
Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
#### A picture of a cute animal (not mandatory but encouraged)
#### Why I did it Upgrade the xgs SAI version to 14.3.0.0.0.0.16.0 to include the following changes: - 14.3.0.0.0.0.15.0: Uplift SONIC-122179 to 14.3 — Assign L3 interface without QoS Setting for my sid transit scenario (L3 interface Qos Map was incorrectly assigned instead of Port qos map for transit case; create new L3 interface without qos setting and assign for transit case) - 14.3.0.0.0.0.16.0: Uplift SONIC-121867 to 14.3 — TH6: Support FP Everflow group creation ##### Work item tracking - Microsoft ADO **(number only)**: 38038391 #### How I did it Update the xgs SAI version in sai-xgs.mk file. #### How to verify it Load image on a DUT, all containers and bgp are up and running. #### Which release branch to backport (provide reason below if selected) - [x] 202511 Signed-off-by: zitingguo <zitingguo@microsoft.com> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
….3.0.0.0.0.16.0 (Azure#2366) #### Why I did it Upgrade the xgs SAI version to 14.3.0.0.0.0.16.0 to include the following changes: - 14.3.0.0.0.0.15.0: Uplift SONIC-122179 to 14.3 — Assign L3 interface without QoS Setting for my sid transit scenario (L3 interface Qos Map was incorrectly assigned instead of Port qos map for transit case; create new L3 interface without qos setting and assign for transit case) - 14.3.0.0.0.0.16.0: Uplift SONIC-121867 to 14.3 — TH6: Support FP Everflow group creation ##### Work item tracking - Microsoft ADO **(number only)**: 38038391 #### How I did it Update the xgs SAI version in sai-xgs.mk file. #### How to verify it Load image on a DUT, all containers and bgp are up and running. #### Which release branch to backport (provide reason below if selected) - [x] 202511 Signed-off-by: zitingguo <zitingguo@microsoft.com> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
…579) #### Why I did it Upgrade the xgs SAI version to 14.3.0.0.0.0.16.0 to include the following changes: - 14.3.0.0.0.0.15.0: Uplift SONIC-122179 to 14.3 — Assign L3 interface without QoS Setting for my sid transit scenario (L3 interface Qos Map was incorrectly assigned instead of Port qos map for transit case; create new L3 interface without qos setting and assign for transit case) - 14.3.0.0.0.0.16.0: Uplift SONIC-121867 to 14.3 — TH6: Support FP Everflow group creation ##### Work item tracking - Microsoft ADO **(number only)**: 38038391 #### How I did it Update the xgs SAI version in sai-xgs.mk file. #### How to verify it Load image on a DUT, all containers and bgp are up and running. #### Which release branch to backport (provide reason below if selected) - [x] 202511 Signed-off-by: zitingguo <zitingguo@microsoft.com> Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
…12 (Azure#2370) ```<br>* c56cf7f - (HEAD -> 202512) Merge branch '202511' of https://github.com/sonic-net/sonic-buildimage into 202512 (2026-05-29) [Sonic Automation] * e1be90d - (head/202511) [Broadcom] Upgrade Broadcom xgs SAI version to 14.3.0.0.0.0.16.0 (#27579) (2026-05-29) [mssonicbld] * 0f64729 - [arista]: Support arista FW for uefi images (#27578) (2026-05-28) [mssonicbld] * a0d27d6 - Arista 7280dr3a SKUs: Update platform.json to match the correct component ordering (#27523) (2026-05-28) [mssonicbld]<br>```
…AD automatically (Azure#2394) #### Why I did it src/sonic-utilities ``` * 364190c8 - (HEAD -> 202512, origin/202512) Merge pull request Azure#357 from mssonicbld/sonicbld/202512-merge (2 hours ago) [mssonicbld] * 10ab8651 - Merge branch '202511' of https://github.com/sonic-net/sonic-utilities into 202512 (2 hours ago) [Sonic Automation] * ae048e70 - Add remove operation for buffer_profile if remove entire profile. (#4585) (9 hours ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
#### Why I did it `port_config.ini` for the `Nokia-IXR7220-H6-O256` and `Nokia-IXR7220-H6-P128` hwskus have a single 1x100G management port. This change removes the second management port that had existed in previous iterations. ##### Work item tracking - Microsoft ADO **(number only)**: N/A #### How I did it For both the `Nokia-IXR7220-H6-O256` and `Nokia-IXR7220-H6-P128` hwskus: - Removed the stale `Ethernet1025` / `etp130` entry from `port_config.ini`. - Corrected `Ethernet1024` in `port_config.ini` to match `platform.json`: lanes `1026,1027,1028,1029`, index `129`, alias `etp129`, speed `100000`, fec `rs`. - Removed the `Ethernet1025` entry from `buffer_ports.j2`, since it referenced the same non-existent port. #### How to verify it - Confirm `Ethernet1025` no longer appears in `port_config.ini` or `buffer_ports.j2` for either hwsku. - On a `Nokia-IXR7220-H6-O256` DUT, `show interfaces status` shows `Ethernet1024` using lanes `1026,1027,1028,1029` at 100G (`etp129`) and no `Ethernet1025`. #### Which release branch to backport (provide reason below if selected) - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [ ] 202511 - [x] 202512 Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
…n O256/P128 (Azure#2407) #### Why I did it `port_config.ini` for the `Nokia-IXR7220-H6-O256` and `Nokia-IXR7220-H6-P128` hwskus have a single 1x100G management port. This change removes the second management port that had existed in previous iterations. ##### Work item tracking - Microsoft ADO **(number only)**: N/A #### How I did it For both the `Nokia-IXR7220-H6-O256` and `Nokia-IXR7220-H6-P128` hwskus: - Removed the stale `Ethernet1025` / `etp130` entry from `port_config.ini`. - Corrected `Ethernet1024` in `port_config.ini` to match `platform.json`: lanes `1026,1027,1028,1029`, index `129`, alias `etp129`, speed `100000`, fec `rs`. - Removed the `Ethernet1025` entry from `buffer_ports.j2`, since it referenced the same non-existent port. #### How to verify it - Confirm `Ethernet1025` no longer appears in `port_config.ini` or `buffer_ports.j2` for either hwsku. - On a `Nokia-IXR7220-H6-O256` DUT, `show interfaces status` shows `Ethernet1024` using lanes `1026,1027,1028,1029` at 100G (`etp129`) and no `Ethernet1025`. #### Which release branch to backport (provide reason below if selected) - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [ ] 202511 - [x] 202512 Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
#### Why I did it
Add port media TX FIR (preemphasis) and optics SI settings for the Nokia
7220 IXR-H6-128 platform. These files are required for stable link bring-up on this platform.
- `media_settings.json` provides per-port, per-speed `pre3/pre2/pre1/main/post1/post2`
TX FIR coefficients for the H6-128 OSFP/QSFP28.
- `optics_si_settings.json` provides `FixedInputEqTargetTx` overrides for the
EOPTOLINK `EO138HGPCT\d{2}SL1` LPO optics on the affected port range
(45–52, 77–84) at 100G_SPEED.
#### How I did it
1. Added `media_settings.json` under
`device/nokia/x86_64-nokia_ixr7220_h6_128-r0/` with the validated TX FIR
values for the H6-128 board.
2. Added `optics_si_settings.json` under the same directory with input-EQ
target overrides for the EOL LPO optics.
#### How to verify it
1. Build `sonic-buildimage` for the H6-128 target and confirm the image is
generated successfully.
2. Install the image on `x86_64-nokia_ixr7220_h6_128-r0` hardware and verify
all dockers come up:
- `show version`
- `show platform summary`
- `show interface status`
- `show interface transceiver eeprom`
3. Confirm the TX FIR values from `media_settings.json` are programmed on
the SerDes via bcm shell
4. Bring up optics on all 128 ports and confirm correct programming and link up and FDR/PRBS BER in range.
5. Bring up links with EOPTOLINK `EO138HGPCT*` LPO modules on ports
45–52 and 77–84 at 100G; confirm links train and stay up with FEC error
counters/PRBS BER in spec.
6. Run OC test with new media_settings.json changes.
#### Which release branch to backport (provide reason below if selected)
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411
- [ ] 202505
- [x] 202511
- [x] 202512
#### Description for the changelog
#### Link to config_db schema for YANG module changes
N/A
Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>
#### A picture of a cute animal (not mandatory but encouraged)
…tings.json (Azure#2408) #### Why I did it Add port media TX FIR (preemphasis) and optics SI settings for the Nokia 7220 IXR-H6-128 platform. These files are required for stable link bring-up on this platform. - `media_settings.json` provides per-port, per-speed `pre3/pre2/pre1/main/post1/post2` TX FIR coefficients for the H6-128 OSFP/QSFP28. - `optics_si_settings.json` provides `FixedInputEqTargetTx` overrides for the EOPTOLINK `EO138HGPCT\d{2}SL1` LPO optics on the affected port range (45–52, 77–84) at 100G_SPEED. #### How I did it 1. Added `media_settings.json` under `device/nokia/x86_64-nokia_ixr7220_h6_128-r0/` with the validated TX FIR values for the H6-128 board. 2. Added `optics_si_settings.json` under the same directory with input-EQ target overrides for the EOL LPO optics. #### How to verify it 1. Build `sonic-buildimage` for the H6-128 target and confirm the image is generated successfully. 2. Install the image on `x86_64-nokia_ixr7220_h6_128-r0` hardware and verify all dockers come up: - `show version` - `show platform summary` - `show interface status` - `show interface transceiver eeprom` 3. Confirm the TX FIR values from `media_settings.json` are programmed on the SerDes via bcm shell 4. Bring up optics on all 128 ports and confirm correct programming and link up and FDR/PRBS BER in range. 5. Bring up links with EOPTOLINK `EO138HGPCT*` LPO modules on ports 45–52 and 77–84 at 100G; confirm links train and stay up with FEC error counters/PRBS BER in spec. 6. Run OC test with new media_settings.json changes. #### Which release branch to backport (provide reason below if selected) - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [x] 202511 - [x] 202512 #### Description for the changelog #### Link to config_db schema for YANG module changes N/A Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com> #### A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: y7zhou <yi.1.zhou@nokia.com>
<!--
Please make sure you've read and understood our contributing guidelines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
** Make sure all your commits include a signature generated with `git
commit -s` **
If this is a bug fix, make sure your description includes "fixes #xxxx",
or
"closes #xxxx" or "resolves #xxxx"
Please provide the following information:
-->
#### Why I did it
Cherry-pick from [Nokia-IXR7220-IXR][H6-128]Update device files
[#27249](sonic-net/sonic-buildimage#27249)
##### Work item tracking
- Microsoft ADO **(number only)**:
#### How I did it
#### How to verify it
<!--
If PR needs to be backported, then the PR must be tested against the
base branch and the earliest backport release branch and provide tested
image version on these two branches. For example, if the PR is requested
for master, 202211 and 202012, then the requester needs to provide test
results on master and 202012.
-->
#### Which release branch to backport (provide reason below if selected)
<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->
- [ ] 201811
- [ ] 201911
- [ ] 202006
- [ ] 202012
- [ ] 202106
- [ ] 202111
- [ ] 202205
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under
sonic-utilities repo. where, Generic Config and Update feature has been
labelled as GCU.
-->
#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on
https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->
#### A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: paprakas <pavan.prakash@nokia.com>
<!--
Please make sure you've read and understood our contributing guidelines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md
** Make sure all your commits include a signature generated with `git
commit -s` **
If this is a bug fix, make sure your description includes "fixes #xxxx",
or
"closes #xxxx" or "resolves #xxxx"
Please provide the following information:
-->
#### Why I did it
Update sonic-platform submodule for Nokia platforms:
Cherry pick PR for
sonic-net/sonic-buildimage#27741
##### Work item tracking
- Microsoft ADO **(number only)**:
#### How I did it
#### How to verify it
<!--
If PR needs to be backported, then the PR must be tested against the
base branch and the earliest backport release branch and provide tested
image version on these two branches. For example, if the PR is requested
for master, 202211 and 202012, then the requester needs to provide test
results on master and 202012.
-->
#### Which release branch to backport (provide reason below if selected)
<!--
- Note we only backport fixes to a release branch, *not* features!
- Please also provide a reason for the backporting below.
- e.g.
- [x] 202006
-->
- [ ] 201811
- [ ] 201911
- [ ] 202006
- [ ] 202012
- [ ] 202106
- [ ] 202111
- [ ] 202205
- [ ] 202211
#### Tested branch (Please provide the tested image version)
<!--
- Please provide tested image version
- e.g.
- [x] 20201231.100
-->
- [ ] <!-- image version 1 -->
- [ ] <!-- image version 2 -->
#### Description for the changelog
<!--
Write a short (one line) summary that describes the changes in this
pull request for inclusion in the changelog:
-->
<!--
Ensure to add label/tag for the feature raised. example - PR#2174 under
sonic-utilities repo. where, Generic Config and Update feature has been
labelled as GCU.
-->
#### Link to config_db schema for YANG module changes
<!--
Provide a link to config_db schema for the table for which YANG model
is defined
Link should point to correct section on
https://github.com/Azure/sonic-buildimage/blob/master/src/sonic-yang-models/doc/Configuration.md
-->
#### A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: paprakas <pavan.prakash@nokia.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
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.
Why I did it
Cherry Pick PR for #27896
Update sonic-platform submodule for Nokia platforms:
Includes commits:
[H6-128]ports_notify add support for 2x100G
Work item tracking
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)