Enabled 30m for URH and LRH device types#27894
Merged
Merged
Conversation
Signed-off-by: venky <venky@nexthop.ai>
Collaborator
|
/azp run Azure.sonic-buildimage |
|
Azure Pipelines successfully started running 1 pipeline(s). |
saravanan-nexthop
approved these changes
Jun 15, 2026
YatishSVC
approved these changes
Jun 15, 2026
vmittal-msft
approved these changes
Jun 15, 2026
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
5 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
This is a cherry pick from master PR: #27186
In the ports2cable macro, the cable_length value needs to be updated to 30m for the following device neighbor types, which were previously missing:
upperspinerouter_spinerouter
upperspinerouter_lowerspinerouter
This PR adds support for these missing neighbor types and sets the corresponding cable_length to 30m.
Work item tracking
How I did it
Changed the types in corresponding buffers_default files.
How to verify it
For those neighbor types, it should pick up the 30m cable_length for lossless profiles.
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)