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

Add 7170 sai port configurations #2049

Closed
wants to merge 1 commit into from

Conversation

zzhiyuan
Copy link
Contributor

- What I did
Board lane map is created from Arista data.
Port configuration is of default 64x100G.

- How I did it

- How to verify it
No way to test the configuration yet without Barefoot follow-up.

- Description for the changelog

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

@zzhiyuan zzhiyuan closed this Sep 13, 2018
stephenxs added a commit to stephenxs/sonic-buildimage that referenced this pull request Dec 14, 2021
5d5c169 [bulk mode] Fix bulk conflict when in case there are both remove and set operations (sonic-net#2071)
8bbdbd2 Fix SRV6 NHOP CRM object type (sonic-net#2072)
ef5b35f [vstest] VS test failure fix after fabric port orch PR merge (sonic-net#1811)
89ea538 Supply the missing ingress/egress port profile list in document (sonic-net#2064)
8123437 [pfc_detect] fix RedisReply errors (sonic-net#2040)
b38f527 [swss][CRM][MPLS] MPLS CRM Nexthop - switch back to using SAI OBJECT rather than SWITCH OBJECT
ae061e5 create debug_shell_enable config to enable debug shell (sonic-net#2060)
45e446d [cbf] Fix max FC value (sonic-net#2049)
b1b5b29 Initial p4orch pytest code. (sonic-net#2054)

Signed-off-by: Stephen Sun <stephens@nvidia.com>
theasianpianist pushed a commit to theasianpianist/sonic-buildimage that referenced this pull request Feb 5, 2022
What I did
Fixed the maximum FC value allowed by a switch.

Why I did it
There was a bit of confusion when I first wrote this, thinking the attribute should return the maximum FC value allowed by the switch, not the maximum number of FC classes. Because of this, the actual maximum FC value allowed is one less than the current one because we're counting from 0. As such, if the switch reports the maximum number of FCs is 255, the actual FC value must be in the 0-254 range.

How I verified it
Updated the existing UTs
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.

2 participants