-
Notifications
You must be signed in to change notification settings - Fork 31
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
[Chassis] Linecards init fails if the max_cores > 16 #77
Closed
Comments
From the error logs. this seems to be vendor independent resource issue for voqs. Looking whether there is soc property setting that is set in arista skus that would make it arista sku specific. |
rlhui
pushed a commit
to sonic-net/sonic-buildimage
that referenced
this issue
Feb 24, 2023
…max cores (#13831) To support 64 cores on arista skus. Fixes aristanetworks/sonic#77 Remapped recycle ports to lowers core port ids and set appl_param_nof_ports_per_modid to 64.
kenneth-arista
pushed a commit
to kenneth-arista/sonic-buildimage
that referenced
this issue
Mar 1, 2023
…ax cores (sonic-net#13831) To support 64 cores on arista skus. Fixes aristanetworks/sonic#77 Remapped recycle ports to lowers core port ids and set appl_param_nof_ports_per_modid to 64.
yxieca
pushed a commit
to sonic-net/sonic-buildimage
that referenced
this issue
Mar 2, 2023
…ax cores (#13831) (#14033) To support 64 cores on arista skus. Fixes aristanetworks/sonic#77 Remapped recycle ports to lowers core port ids and set appl_param_nof_ports_per_modid to 64. Co-authored-by: Sambath Kumar Balasubramanian <63021927+skbarista@users.noreply.github.com>
Closing as the required changes have merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Arista 7800 linecards, the sai_switch_create fails with below error, if the value
max_cores
in the DEVICE_METADATA > 16if the
max_cores
<=16 the sai_switch_create is fine.We should support
max_cores
= 64.Calculation: 16 lc * 2 asic per lc * 2 cores per asic
Note: This issue seems to be specific to Arista. Other platforms do not have this issue.
Non-working Config
Working config
The text was updated successfully, but these errors were encountered: