[Nexthop] NH-5010 Platform Support#24169
Conversation
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command. |
9b9392d to
8051e1e
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
device/nexthop/x86_64-nexthop_5010-r0/NH-5010-F-O32-C32/port_config.ini
Outdated
Show resolved
Hide resolved
|
@arlakshm to review |
device/nexthop/x86_64-nexthop_5010-r0/NH-5010-F-O32-C32/BALANCED/buffers_defaults_t2.j2
Outdated
Show resolved
Hide resolved
device/nexthop/x86_64-nexthop_5010-r0/NH-5010-F-O32-C32/BALANCED/buffers_defaults_t2.j2
Show resolved
Hide resolved
device/nexthop/x86_64-nexthop_5010-r0/NH-5010-F-O64/port_config.ini
Outdated
Show resolved
Hide resolved
device/nexthop/x86_64-nexthop_5010-r0/NH-5010-F-O64/port_config.ini
Outdated
Show resolved
Hide resolved
| @@ -0,0 +1,3 @@ | |||
| [Unit] | |||
| Wants=pmon.service | |||
There was a problem hiding this comment.
why do we need this change?
There was a problem hiding this comment.
One of the main reasons is to ensure thermal control starts before swss begins enabling interfaces.
There was a problem hiding this comment.
this change means the swss will not start till pmon is started? @judyjoseph for viz...
There was a problem hiding this comment.
Another reason we added this is because if xcvrd programs the xcvrs after the port is enabled the link could flap. Ideally there is a generic solution where orchagent keeps the port disabled until xcvrd has programmed the xcvr. Until something like that is implemented we're adding this as a temporary improvement for Nexthop platforms.
device/nexthop/x86_64-nexthop_5010-r0/NH-5010-F-O64/nh5010-default.bcm
Outdated
Show resolved
Hide resolved
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
60b4a8a to
6e9b4a3
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
| @@ -0,0 +1,3 @@ | |||
| [Unit] | |||
| Wants=pmon.service | |||
There was a problem hiding this comment.
this change means the swss will not start till pmon is started? @judyjoseph for viz...
| {%- macro generate_qos_bypass_port_list(PORT_QOS_BYPASS) %} | ||
| {# Generate list of ports #} | ||
| {%- for port_idx in range(256, 261, 4) %} | ||
| {%- if PORT_QOS_BYPASS.append("Ethernet%d" % (port_idx)) %}{%- endif %} | ||
| {%- endfor %} | ||
| {%- endmacro %} |
There was a problem hiding this comment.
Priority group related config is not supported on management ports, SAI throws an error. The change made in the buffers_defaults_t2.j2 is to skip programming it on those ports.
Error thrown by SAI
SAI_API_PORT:brcm_sai_set_port_attribute:3764 PG config not supported, Port:257 type is MGMT port
2025 Oct 15 22:51:03.494097 ERR syncd#syncd: :- sendApiResponse: api SAI_COMMON_API_SET failed in syncd mode: SAI_STATUS_ATTR_NOT_SUPPORTED_0
2025 Oct 15 22:51:03.494119 ERR syncd#syncd: :- processQuadEvent: VID: oid:0x1000000000041 RID: oid:0x100000101
8982016 to
863e6e8
Compare
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
* add device dir for nh-5010 * add sonic-platform-modules-nexthop support for nh-5010 * more nh-5010 device dir changes * remove eeprom utils change * additional nh platform support changes * macsec property and tap changes * Update adm1266 test to use pd-plugin.json from nh-5010 * use nh_powercycle for nh platforms * address review comments * update top level build files * remove spi module from pddf json * follow-up cleanup after resolving merge conflict * empty commit to retrigger checks --------- Co-authored-by: Louis Maliyam <louis@nexthop.ai>
* add device dir for nh-5010 * add sonic-platform-modules-nexthop support for nh-5010 * more nh-5010 device dir changes * remove eeprom utils change * additional nh platform support changes * macsec property and tap changes * Update adm1266 test to use pd-plugin.json from nh-5010 * use nh_powercycle for nh platforms * address review comments * update top level build files * remove spi module from pddf json * follow-up cleanup after resolving merge conflict * empty commit to retrigger checks --------- Co-authored-by: Louis Maliyam <louis@nexthop.ai> Signed-off-by: Feng Pan <fenpan@microsoft.com>
* add device dir for nh-5010 * add sonic-platform-modules-nexthop support for nh-5010 * more nh-5010 device dir changes * remove eeprom utils change * additional nh platform support changes * macsec property and tap changes * Update adm1266 test to use pd-plugin.json from nh-5010 * use nh_powercycle for nh platforms * address review comments * update top level build files * remove spi module from pddf json * follow-up cleanup after resolving merge conflict * empty commit to retrigger checks --------- Co-authored-by: Louis Maliyam <louis@nexthop.ai> Signed-off-by: xiaweijiang <xiaweijiang@microsoft.com>
Why I did it
Adds support for the Nexthop NH-5010 platform
Work item tracking
How I did it
Add platform changes to:
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