Allow for the speed change in NH-5010 by updating the config_db.json by arpit-nexthop · Pull Request #25423 · sonic-net/sonic-buildimage

arpit-nexthop · 2026-02-10T21:23:33Z

Prereq PRs:

sonic-net/sonic-platform-daemons#728
sonic-net/sonic-swss#4113

Why I did it

Prereq changes:
This commit first moves all current signal integrity settings for gearboxes into the media_settings file in the
device/nexthop/x86_64-nexthop_5010-r0 directory. It also removes the older configuration via gearbox_config.json so that we only have a single source of truth for all signal integrity configuration on this platform.

Automate generation of ASIC, gearbox, and PHY configs for different port speeds, instead of maintaining HWSKUs which are inflexible. 2) Derive configuration from platform files:
a) port_speed.json (port speed profiles + ASIC/gearbox mapping)
b) Q3D_ports.json (ASIC core/PM → lanes/port names)
c) CONFIG_DB.PORT (actual ports, speeds, indices, lanes)
Add validation so invalid lane/speed combinations are caught early (before swss brings up ports).

Work item tracking

Microsoft ADO (number only):

How I did it

Changed docker image template to provide rw permission to hwsku directory to allow for the config generation. 2) The hwsku-init runs everytime the swss starts and generates the configuration file. 3) Introduced a common hwsku pipeline:
a) Dataclasses for ASIC ports, gearbox ports, speed profiles, and CONFIG_DB entries.
b) Loaders for:
port_speed.json → per-port speed profiles + ASIC/gearbox mapping.
Q3D_ports.json → core/PM → port → lane map.
CONFIG_DB PORT table (or a JSON dump) → typed port map.
c) Generators for:
Gearbox interfaces list.
Per‑PHY phy_config.json content.
ASIC specific config
d) A run() method that:
Calls platform-specific ASIC config generation.
Renders Jinja2 templates into nh5010.bcm, gearbox_config.json, and phy*_config.json, with a fallback to defaults/ on error.
Currently supports:
(400G-4, 100G-2) ASIC config, (400G-8, 100G-4) front port on the ports 1-32.
(400G-4, 100G-4) ASIC and front port config (no gearbox) on ports 33-64.

How to verify it

Validated it on mix of 100G and 400G interface:

root@humm119:/usr/share/sonic/device/x86_64-nexthop_5010-r0/NH-5010-F-O64# show interface status
    Interface            Lanes    Speed    MTU    FEC    Alias    Vlan    Oper    Admin                                             Type    Asym PFC
-------------  ---------------  -------  -----  -----  -------  ------  ------  -------  -----------------------------------------------  ----------
    Ethernet0            96,97     100G   9100     rs     etp1  routed      up       up                                  QSFP28 or later         N/A
    Ethernet4          100,101     100G   9100     rs     etp2  routed      up       up                                  QSFP28 or later         N/A
    Ethernet8  104,105,106,107     400G   9100     rs     etp3  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet12          108,109     100G   9100     rs     etp4  routed      up       up                                  QSFP28 or later         N/A
   Ethernet16  112,113,114,115     400G   9100     rs     etp5  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet20          116,117     100G   9100     rs     etp6  routed      up       up                                  QSFP28 or later         N/A
   Ethernet24          120,121     100G   9100     rs     etp7  routed      up       up                                  QSFP28 or later         N/A
   Ethernet28          124,125     100G   9100     rs     etp8  routed      up       up                                  QSFP28 or later         N/A
   Ethernet32      56,57,58,59     400G   9100     rs     etp9  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet36      60,61,62,63     400G   9100     rs    etp10  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet40            48,49     100G   9100     rs    etp11  routed      up       up                                  QSFP28 or later         N/A
   Ethernet44            52,53     100G   9100     rs    etp12  routed      up       up                                  QSFP28 or later         N/A
   Ethernet48      40,41,42,43     400G   9100     rs    etp13  routed    down       up                                              N/A         N/A
   Ethernet52      44,45,46,47     400G   9100     rs    etp14  routed    down       up                                              N/A         N/A
   Ethernet56      32,33,34,35     400G   9100     rs    etp15  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet60      36,37,38,39     400G   9100     rs    etp16  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet64  128,129,130,131     400G   9100     rs    etp17  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet68  132,133,134,135     400G   9100     rs    etp18  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet72  136,137,138,139     400G   9100     rs    etp19  routed    down       up                                              N/A         N/A
   Ethernet76  140,141,142,143     400G   9100     rs    etp20  routed    down       up                                              N/A         N/A
   Ethernet80          144,145     100G   9100     rs    etp21  routed      up       up                                  QSFP28 or later         N/A
   Ethernet84  148,149,150,151     400G   9100     rs    etp22  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet88          152,153     100G   9100     rs    etp23  routed      up       up                                  QSFP28 or later         N/A
   Ethernet92  156,157,158,159     400G   9100     rs    etp24  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
   Ethernet96          216,217     100G   9100     rs    etp25  routed      up       up                                  QSFP28 or later         N/A
  Ethernet100  220,221,222,223     400G   9100     rs    etp26  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
  Ethernet104          208,209     100G   9100     rs    etp27  routed      up       up                                  QSFP28 or later         N/A
  Ethernet108  212,213,214,215     400G   9100     rs    etp28  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
  Ethernet112  200,201,202,203     400G   9100     rs    etp29  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
  Ethernet116  204,205,206,207     400G   9100     rs    etp30  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
  Ethernet120  192,193,194,195     400G   9100     rs    etp31  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
  Ethernet124  196,197,198,199     400G   9100     rs    etp32  routed      up       up  QSFP-DD Double Density 8X Pluggable Transceiver         N/A
  Ethernet128      64,65,66,67     400G   9100     rs    etp33  routed      up       up                         QSFP+ or later with CMIS         N/A
  Ethernet132      68,69,70,71     400G   9100     rs    etp34  routed      up       up                         QSFP+ or later with CMIS         N/A
  Ethernet136      72,73,74,75     400G   9100     rs    etp35  routed    down       up                                              N/A         N/A
  Ethernet140      76,77,78,79     400G   9100     rs    etp36  routed    down       up                                              N/A         N/A
  Ethernet144      80,81,82,83     100G   9100     rs    etp37  routed      up       up                                  QSFP28 or later         N/A
  Ethernet148      84,85,86,87     100G   9100     rs    etp38  routed      up       up                                  QSFP28 or later         N/A
  Ethernet152      88,89,90,91     400G   9100     rs    etp39  routed    down       up                                              N/A         N/A
  Ethernet156      92,93,94,95     400G   9100     rs    etp40  routed    down       up                                              N/A         N/A
  Ethernet160      24,25,26,27     100G   9100     rs    etp41  routed    down       up                                              N/A         N/A
  Ethernet164      28,29,30,31     100G   9100     rs    etp42  routed      up       up                                  QSFP28 or later         N/A
  Ethernet168      16,17,18,19     100G   9100     rs    etp43  routed    down       up                                              N/A         N/A
  Ethernet172      20,21,22,23     100G   9100     rs    etp44  routed      up       up                                  QSFP28 or later         N/A
  Ethernet176        8,9,10,11     100G   9100     rs    etp45  routed      up       up                                  QSFP28 or later         N/A
  Ethernet180      12,13,14,15     100G   9100     rs    etp46  routed    down       up                                              N/A         N/A
  Ethernet184          0,1,2,3     100G   9100     rs    etp47  routed      up       up                                  QSFP28 or later         N/A
  Ethernet188          4,5,6,7     100G   9100     rs    etp48  routed    down       up                                              N/A         N/A
  Ethernet192  160,161,162,163     400G   9100     rs    etp49  routed    down       up                                              N/A         N/A
  Ethernet196  164,165,166,167     400G   9100     rs    etp50  routed    down       up                                              N/A         N/A
  Ethernet200  168,169,170,171     400G   9100     rs    etp51  routed    down       up                                              N/A         N/A
  Ethernet204  172,173,174,175     400G   9100     rs    etp52  routed    down       up                                              N/A         N/A
  Ethernet208  176,177,178,179     400G   9100     rs    etp53  routed    down       up                                              N/A         N/A
  Ethernet212  180,181,182,183     400G   9100     rs    etp54  routed    down       up                                              N/A         N/A
  Ethernet216  184,185,186,187     400G   9100     rs    etp55  routed    down       up                                              N/A         N/A
  Ethernet220  188,189,190,191     400G   9100     rs    etp56  routed    down       up                                              N/A         N/A
  Ethernet224  248,249,250,251     400G   9100     rs    etp57  routed    down       up                                              N/A         N/A
  Ethernet228  252,253,254,255     400G   9100     rs    etp58  routed    down       up                                              N/A         N/A
  Ethernet232  240,241,242,243     400G   9100     rs    etp59  routed    down       up                                              N/A         N/A
  Ethernet236  244,245,246,247     400G   9100     rs    etp60  routed    down       up                                              N/A         N/A
  Ethernet240  232,233,234,235     400G   9100     rs    etp61  routed      up       up                         QSFP+ or later with CMIS         N/A
  Ethernet244  236,237,238,239     400G   9100     rs    etp62  routed      up       up                         QSFP+ or later with CMIS         N/A
  Ethernet248  224,225,226,227     400G   9100     rs    etp63  routed    down       up                                              N/A         N/A
  Ethernet252  228,229,230,231     400G   9100     rs    etp64  routed    down       up                                              N/A         N/A
  Ethernet256  256,257,258,259     100G   9100     rs    etp65  routed    down       up                                              N/A         N/A
  Ethernet260  260,261,262,263     100G   9100     rs    etp66  routed    down       up                                              N/A         N/A
Ethernet-Rec0              621      10G   9100   none  Recirc0  routed      up       up                                              N/A         N/A

Which release branch to backport (provide reason below if selected)

Tested branch (Please provide the tested image version)

master

SONiC OS Version: 13
OCP SAI Header Version: 1.17.1
Vendor SAI Version: 14.1.0.1.0.0.0.0
Vendor SDK Version: sdk-6.5.34-SP1
Distribution: Debian 13.3
Kernel: 6.12.41+deb13-sonic-amd64
Build commit: e73351b0e6
Build date: Mon Feb  9 23:36:58 UTC 2026
Built by: ubuntu@ip-172-31-13-36

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

mssonicbld · 2026-02-10T21:23:41Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-10T21:23:54Z

Azure Pipelines successfully started running 1 pipeline(s).

Why I did it 1) Automate generation of ASIC, gearbox, and PHY configs for different port speeds, instead of maintaining HWSKUs which are inflexible. 2) Derive configuration from platform files: a) port_speed.json (port speed profiles + ASIC/gearbox mapping) b) Q3D_ports.json (ASIC core/PM → lanes/port names) c) CONFIG_DB.PORT (actual ports, speeds, indices, lanes) 3) Add validation so invalid lane/speed combinations are caught early (before swss brings up ports). How I did it 1) Changed docker image template to provide rw permission to hwsku directory to allow for the config generation. 2) The hwsku-init runs everytime the swss starts and generates the configuration file. 3) Introduced a common hwsku pipeline: a) Dataclasses for ASIC ports, gearbox ports, speed profiles, and CONFIG_DB entries. b) Loaders for: port_speed.json → per-port speed profiles + ASIC/gearbox mapping. Q3D_ports.json → core/PM → port → lane map. CONFIG_DB PORT table (or a JSON dump) → typed port map. c) Generators for: Gearbox interfaces list. Per‑PHY phy_config.json content. ASIC specific config d) A run() method that: Calls platform-specific ASIC config generation. Renders Jinja2 templates into nh5010.bcm, gearbox_config.json, and phy*_config.json, with a fallback to defaults/ on error. 4) Currently supports: (400G-4, 100G-2) ASIC config, (400G-8, 100G-4) front port on the ports 1-32. (400G-4, 100G-4) ASIC and front port config (no gearbox) on ports 33-64. This commit moves all current signal integrity settings for gearboxes into the media_settings file in the device/nexthop/x86_64-nexthop_5010-r0 directory. It also removes the older configuration via gearbox_config.json so that we only have a single source of truth for all signal integrity configuration on this platform. Signed-off-by: arpit-nexthop <arpit@nexthop.ai> Signed-off-by: arpit-nexthop <arpit@nexthop.ai>

mssonicbld · 2026-02-11T17:21:10Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-11T17:21:25Z

Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: arpit-nexthop <arpit@nexthop.ai>

mssonicbld · 2026-02-17T19:39:10Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-17T19:39:23Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-17T21:52:51Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-17T21:53:04Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-18T16:59:25Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-18T16:59:38Z

Azure Pipelines successfully started running 1 pipeline(s).

arpit-nexthop · 2026-02-18T17:50:43Z

@arlakshm
The PR is failing the check

 python.flask.security.xss.audit.direct-use-of-jinja2.direct-use-of-jinja2
          Detected direct use of jinja2. If not done properly, this may bypass HTML escaping which opens up
          the application to cross-site scripting (XSS) vulnerabilities. Prefer using the Flask method     
          'render_template()' and templates with a '.html' extension in order to prevent XSS.              
          Details: https://sg.run/RoKe                                                                     
                                                                                                           
          348┆ env = Environment(
          349┆     loader=FileSystemLoader(template_dir),
          350┆     autoescape=select_autoescape(["html", "xml"])
          351┆ ) # nosemgrep: python.flask.security.xss.audit.direct-use-of-jinja2.direct-use-of-jinja2
                            
  BLOCKING CODE RULES FIRED:
    python.flask.security.xss.audit.direct-use-of-jinja2.direct-use-of-jinja2

Since the script is not generating html or xml file, we can ignore the warning. Please suggest what should be the way to mark this file in ignore list for this warning.

mssonicbld · 2026-02-18T22:58:10Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-18T22:58:22Z

Azure Pipelines successfully started running 1 pipeline(s).

files/build_templates/docker_image_ctl.j2

device/nexthop/x86_64-nexthop_5010-r0/NH-5010-F-O64/hwsku-init

mssonicbld · 2026-02-19T23:19:34Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-19T23:19:45Z

Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: arpit-nexthop <arpit@nexthop.ai>

mssonicbld · 2026-02-24T21:23:49Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-24T21:24:03Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-02-25T18:01:58Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-02-25T18:02:09Z

Azure Pipelines failed to run 1 pipeline(s).

azure-pipelines · 2026-03-05T18:47:07Z

Azure Pipelines successfully started running 1 pipeline(s).

tjchadaga · 2026-03-05T20:21:46Z

@arpit-nexthop - since one of the prereq PRs (sonic-net/sonic-platform-daemons#728) is not merged to master, is it safe to merge this PR?

If not, please raise another PR with this change for 202511, so we can go ahead and merge that

arpit-nexthop · 2026-03-05T21:46:39Z

@arpit-nexthop - since one of the prereq PRs (sonic-net/sonic-platform-daemons#728) is not merged to master, is it safe to merge this PR?

If not, please raise another PR with this change for 202511, so we can go ahead and merge that

@tjchadaga It is okay to merge, we are already working to get master merged (sonic-net/sonic-platform-daemons#728) (should happen in a couple of days). Only thing it will temporarily break on master would be the serdes settings. Since immediately we are not running tests on master, we can merge this.

Signed-off-by: arpit-nexthop <arpit@nexthop.ai>

mssonicbld · 2026-03-06T19:14:38Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-06T19:14:52Z

Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: arpit-nexthop <arpit@nexthop.ai>

mssonicbld · 2026-03-08T15:56:58Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-08T15:57:10Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-03-09T17:54:45Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-09T17:55:00Z

Azure Pipelines successfully started running 1 pipeline(s).

arlakshm · 2026-03-09T17:56:13Z

/azpw ms_conflict

mssonicbld · 2026-03-10T20:17:02Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-10T20:17:16Z

Azure Pipelines successfully started running 1 pipeline(s).

mssonicbld · 2026-03-11T15:37:42Z

/azp run Azure.sonic-buildimage

azure-pipelines · 2026-03-11T15:37:57Z

Azure Pipelines successfully started running 1 pipeline(s).

arpit-nexthop · 2026-03-11T16:36:37Z

Consistently hitting
#26130
#25695

vmittal-msft · 2026-03-12T17:14:01Z

@yxieca @rlhui Can you please help merge ?

mssonicbld · 2026-03-12T17:16:42Z

Cherry-pick PR to 202511: #26150

arpit-nexthop requested a review from lguohan as a code owner February 10, 2026 21:23

arpit-nexthop force-pushed the nh5010.speed_change branch from 04353da to eca63de Compare February 11, 2026 17:21

Ignore flask warning as the j2 generation is not for html

b915a95

Signed-off-by: arpit-nexthop <arpit@nexthop.ai>

Merge branch 'master' into nh5010.speed_change

c761e48

Merge branch 'master' into nh5010.speed_change

7cab600

Merge branch 'master' into nh5010.speed_change

65cda14

arlakshm reviewed Feb 19, 2026

View reviewed changes

files/build_templates/docker_image_ctl.j2 Outdated Show resolved Hide resolved

device/nexthop/x86_64-nexthop_5010-r0/NH-5010-F-O64/hwsku-init Show resolved Hide resolved

Merge branch 'master' into nh5010.speed_change

60746f8

jinja2 warning ignore to correct line

58e1962

Signed-off-by: arpit-nexthop <arpit@nexthop.ai>

Merge branch 'master' into nh5010.speed_change

125c8d3

arlakshm approved these changes Mar 5, 2026

View reviewed changes

Trigger CI/CD build

4c0cf8f

Signed-off-by: arpit-nexthop <arpit@nexthop.ai>

Trigger CI/CD build

cc76e3b

Signed-off-by: arpit-nexthop <arpit@nexthop.ai>

Merge branch 'sonic-net:master' into nh5010.speed_change

134d0ec

Merge branch 'sonic-net:master' into nh5010.speed_change

403bcf7

Merge branch 'sonic-net:master' into nh5010.speed_change

b96f8e8

vmittal-msft approved these changes Mar 12, 2026

View reviewed changes

rlhui merged commit bddd246 into sonic-net:master Mar 12, 2026
20 checks passed

github-project-automation bot moved this to Done in SONiC Chassis Mar 12, 2026

mssonicbld mentioned this pull request Mar 12, 2026

[action] [PR:25423] Allow for the speed change in NH-5010 by updating the config_db.json #26150

Merged

8 tasks

mssonicbld added the Created PR to 202511 Branch label Mar 12, 2026

mssonicbld added Included in 202511 Branch and removed Created PR to 202511 Branch labels Mar 13, 2026

Conversation

arpit-nexthop commented Feb 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Prereq PRs:

Why I did it

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)

Uh oh!

mssonicbld commented Feb 10, 2026

Uh oh!

azure-pipelines bot commented Feb 10, 2026

Uh oh!

mssonicbld commented Feb 11, 2026

Uh oh!

azure-pipelines bot commented Feb 11, 2026

Uh oh!

mssonicbld commented Feb 17, 2026

Uh oh!

azure-pipelines bot commented Feb 17, 2026

Uh oh!

mssonicbld commented Feb 17, 2026

Uh oh!

azure-pipelines bot commented Feb 17, 2026

Uh oh!

mssonicbld commented Feb 18, 2026

Uh oh!

azure-pipelines bot commented Feb 18, 2026

Uh oh!

arpit-nexthop commented Feb 18, 2026

Uh oh!

mssonicbld commented Feb 18, 2026

Uh oh!

azure-pipelines bot commented Feb 18, 2026

Uh oh!

Uh oh!

Uh oh!

mssonicbld commented Feb 19, 2026

Uh oh!

azure-pipelines bot commented Feb 19, 2026

Uh oh!

mssonicbld commented Feb 24, 2026

Uh oh!

azure-pipelines bot commented Feb 24, 2026

Uh oh!

mssonicbld commented Feb 25, 2026

Uh oh!

azure-pipelines bot commented Feb 25, 2026

Uh oh!

azure-pipelines bot commented Mar 5, 2026

Uh oh!

tjchadaga commented Mar 5, 2026

Uh oh!

arpit-nexthop commented Mar 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mssonicbld commented Mar 6, 2026

Uh oh!

azure-pipelines bot commented Mar 6, 2026

Uh oh!

mssonicbld commented Mar 8, 2026

Uh oh!

azure-pipelines bot commented Mar 8, 2026

Uh oh!

mssonicbld commented Mar 9, 2026

Uh oh!

azure-pipelines bot commented Mar 9, 2026

Uh oh!

arlakshm commented Mar 9, 2026

Uh oh!

mssonicbld commented Mar 10, 2026

Uh oh!

azure-pipelines bot commented Mar 10, 2026

Uh oh!

mssonicbld commented Mar 11, 2026

arpit-nexthop commented Feb 10, 2026 •

edited

Loading

arpit-nexthop commented Mar 5, 2026 •

edited

Loading