Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[202205][Buffer] Added cable length config to buffer config template for EdgeZoneAggregator #14538

Conversation

developfast
Copy link
Contributor

@developfast developfast commented Apr 5, 2023

Why I did it

SONiC currently does not identify 'EdgeZoneAggregator' neighbor. As a result, the buffer profile attached to those interfaces uses the default cable length which could cause ingress packet drops due to insufficient headroom. Hence, there is a need to update the buffer templates to identify such neighbors and assign the same cable length as used by the T1.

How I did it

Modified the buffer template to identify EdgeZoneAggregator as a neighbor device type and assign it the same cable length as a T1/leaf router.

How to verify it

Unit tests pass, and manually checked on a 7260 to see the changes take effect.

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

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111
  • 202205
  • 202211

Description for the changelog

[Buffer] Added cable length config to buffer config template for EdgeZoneAggregator. Original PR to master: #14280

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

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

@developfast developfast changed the title [Buffer] Added cable length config to buffer config template for EdgeZoneAggregator - 202205 [202205][Buffer] Added cable length config to buffer config template for EdgeZoneAggregator Apr 6, 2023
@yxieca yxieca merged commit 82873c2 into sonic-net:202205 Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants