-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Celestica DX010 32x100G #5162
Comments
@lguohan - Would it be possible to assist this this, as the same issue was raise in the MicrosoftDocs channel but there is no direct support for this topic. I am hoping that by bringing attention to the issue raised here, I can help the customer find the information they are seeking. Thank you, Mike. |
Please try to help , it's related to my work |
Any updates ? |
@willieken559099 I am working with a Networking team to figure this out....apologies for the delay. |
Thank you Michael |
[email protected] is a better place to ask this question. |
@zhenggen-xu is this supported by dynamic port breakout? |
Yes it's , the problem that the port doesn't light up when we change the speed to 10g and I believe that has to be done in the Bcm file first, that's why I am asking how to modify the Bcm file to use 10g |
OK, I don't think i have the context about your goals. What exactly you are trying to achieve overall, just change one port to a different speed? and What sonic version was used in your testing, and which hwsku? Before the dynamic port breakout feature (which was onboarded recently on master), to change the port breakout mode, e,g, from 32x100G to 96x25G/10G+16x50G, you will have to use different hwsku. With this PR: #4235 on master and latest code, you could change the port speed freely from 100G, 50G, 25G/10G etc on DX010. If it is not something you want to dynamically change all the time, I suggest to pick a right hwsku and start from there, where we have different bcmfiles predefined for each hwsku. |
How to configure Celestica seastone DX010 32x100G ports to use 10G in the BCM file ?
The text was updated successfully, but these errors were encountered: