-
Notifications
You must be signed in to change notification settings - Fork 243
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
Sonic docs refresh and introduction of sonic-vm #2120
Conversation
@adam-kulagowski do you have an example how ports are mapped in Sonic? something based on this
|
This will create a Update: the non continuity in SONiC naming is OK. In VM, SONiC assumes that each interface has 4 lanes, and leaves space for potential cable-breakout :) |
@adam-kulagowski can you please drop here a quick memo on how save the configuration that will be suitable for |
Could You please elaborate? I'm not sure what do You expect. An example configuration that we use looks like this:
And is 1:1 copy from After that any changes done in VM can be exported with If I misunderstood please let me know. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2120 +/- ##
==========================================
- Coverage 53.73% 53.55% -0.19%
==========================================
Files 163 164 +1
Lines 11632 11675 +43
==========================================
+ Hits 6250 6252 +2
- Misses 4507 4547 +40
- Partials 875 876 +1
|
this was exactly what was missing. Added this to the documentation. Ty |
No description provided.