Skip to content

Aligned the sensors file for SN5640 platform#21715

Merged
wangxin merged 1 commit into
sonic-net:masterfrom
AharonMalkin:sensors
Jan 15, 2026
Merged

Aligned the sensors file for SN5640 platform#21715
wangxin merged 1 commit into
sonic-net:masterfrom
AharonMalkin:sensors

Conversation

@AharonMalkin

@AharonMalkin AharonMalkin commented Dec 16, 2025

Copy link
Copy Markdown
Contributor

Description of PR

Summary:
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

Type of change

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

Back port request

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

Approach

What is the motivation for this PR?

To align the expected sensors for sn5640.

How did you do it?

Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?

Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?

related to sn5640 NVIDIA system only.

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

Documentation

@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
@mssonicbld

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@AharonMalkin

Copy link
Copy Markdown
Contributor Author

Hey @r12f, cherry pick for 202412: Azure/sonic-mgmt.msft#934

@AharonMalkin

Copy link
Copy Markdown
Contributor Author

/azpw run

@mssonicbld

Copy link
Copy Markdown
Collaborator

/AzurePipelines run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@AharonMalkin

Copy link
Copy Markdown
Contributor Author

/azpw run

@mssonicbld

Copy link
Copy Markdown
Collaborator

/AzurePipelines run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@wangxin wangxin merged commit 35f7c69 into sonic-net:master Jan 15, 2026
23 checks passed
thisptr-sh pushed a commit to thisptr-sh/sonic-mgmt that referenced this pull request Jan 21, 2026
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

What is the motivation for this PR?
To align the expected sensors for sn5640.

How did you do it?
Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?
Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?
related to sn5640 NVIDIA system only.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: Priyansh Tratiya <ptratiya@microsoft.com>
AndoniSanguesa pushed a commit to AndoniSanguesa/sonic-mgmt that referenced this pull request Jan 21, 2026
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

What is the motivation for this PR?
To align the expected sensors for sn5640.

How did you do it?
Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?
Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?
related to sn5640 NVIDIA system only.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: Andoni Sanguesa <andoniesanguesa@gmail.com>
saravanan-nexthop pushed a commit to nexthop-ai/sonic-mgmt that referenced this pull request Jan 22, 2026
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

What is the motivation for this PR?
To align the expected sensors for sn5640.

How did you do it?
Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?
Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?
related to sn5640 NVIDIA system only.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: Saravanan Sellappa <saravanan@nexthop.ai>
ytzur1 pushed a commit to ytzur1/sonic-mgmt that referenced this pull request Feb 2, 2026
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

What is the motivation for this PR?
To align the expected sensors for sn5640.

How did you do it?
Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?
Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?
related to sn5640 NVIDIA system only.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: Yael Tzur <ytzur@nvidia.com>
AharonMalkin added a commit to AharonMalkin/sonic-mgmt that referenced this pull request Feb 12, 2026
This reverts commit 35f7c69.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
rraghav-cisco pushed a commit to rraghav-cisco/sonic-mgmt that referenced this pull request Feb 18, 2026
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

What is the motivation for this PR?
To align the expected sensors for sn5640.

How did you do it?
Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?
Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?
related to sn5640 NVIDIA system only.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: Raghavendran Ramanathan <rraghav@cisco.com>
anilal-amd pushed a commit to anilal-amd/anilal-forked-sonic-mgmt that referenced this pull request Feb 19, 2026
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

What is the motivation for this PR?
To align the expected sensors for sn5640.

How did you do it?
Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?
Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?
related to sn5640 NVIDIA system only.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: Zhuohui Tan <zhuohui.tan@amd.com>
aronovic pushed a commit to aronovic/sonic-mgmt that referenced this pull request Mar 3, 2026
…" (sonic-net#22379)

Signed-off-by: Mihut Aronovici <aronovic@cisco.com>
rraghav-cisco pushed a commit to rraghav-cisco/sonic-mgmt that referenced this pull request Mar 3, 2026
…" (sonic-net#22379)

Signed-off-by: Raghavendran Ramanathan <rraghav@cisco.com>
kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
<!--
 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
To support multi-asic platform, create bmp container per_namespace

##### Work item tracking
- Microsoft ADO **(number only)**:27588904

#### How I did it
move bmp.service from single into per namespace

#### 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
- [ ] 202305

#### 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)
aronovic pushed a commit to aronovic/sonic-mgmt that referenced this pull request Mar 10, 2026
…" (sonic-net#22379)

Signed-off-by: Mihut Aronovici <aronovic@cisco.com>
vrajeshe pushed a commit to vrajeshe/sonic-mgmt that referenced this pull request Mar 23, 2026
…" (sonic-net#22379)

Signed-off-by: Venkata Gouri Rajesh Etla <vrajeshe@cisco.com>
@r12f r12f added the Request for 202511 branch Request to backport a change to 202511 branch label Mar 26, 2026
selldinesh pushed a commit to selldinesh/sonic-mgmt that referenced this pull request Apr 1, 2026
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

What is the motivation for this PR?
To align the expected sensors for sn5640.

How did you do it?
Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?
Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?
related to sn5640 NVIDIA system only.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: selldinesh <dinesh.sellappan@keysight.com>
selldinesh pushed a commit to selldinesh/sonic-mgmt that referenced this pull request Apr 1, 2026
…" (sonic-net#22379)

Signed-off-by: selldinesh <dinesh.sellappan@keysight.com>
albertovillarreal-keys pushed a commit to albertovillarreal-keys/sonic-mgmt that referenced this pull request Apr 3, 2026
rraghav-cisco pushed a commit to rraghav-cisco/sonic-mgmt that referenced this pull request Apr 20, 2026
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

What is the motivation for this PR?
To align the expected sensors for sn5640.

How did you do it?
Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?
Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?
related to sn5640 NVIDIA system only.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: Raghavendran Ramanathan <rraghav@cisco.com>
rraghav-cisco pushed a commit to rraghav-cisco/sonic-mgmt that referenced this pull request Apr 20, 2026
…" (sonic-net#22379)

Signed-off-by: Raghavendran Ramanathan <rraghav@cisco.com>
selldinesh pushed a commit to selldinesh/sonic-mgmt that referenced this pull request Jun 11, 2026
This PR aligns the sensors yaml file to the updated sensors on sn5640 nvidia platform.
Sensor file updates exist here: Azure/sonic-buildimage-msft#1889

What is the motivation for this PR?
To align the expected sensors for sn5640.

How did you do it?
Modified the file according to Azure/sonic-buildimage-msft#1889

How did you verify/test it?
Ran the sensors test, 100% pass rate on sn5640

Any platform specific information?
related to sn5640 NVIDIA system only.

Signed-off-by: Aharon Malkin <amalkin@nvidia.com>
Signed-off-by: selldinesh <dinesh.sellappan@keysight.com>
selldinesh pushed a commit to selldinesh/sonic-mgmt that referenced this pull request Jun 11, 2026
…" (sonic-net#22379)

Signed-off-by: selldinesh <dinesh.sellappan@keysight.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants