L2 vxlan HLD #376
Open
L2 vxlan HLD #376
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
High level design for Sonic Vxlan
* [watremark] Add watermark HLD Signed-off-by: Mykola Faryma <mykolaf@mellanox.com>
Added a direct link for Slack discussion group for more comfortable UX
Signed-off-by: shine <shine.chen@nephosinc.com>
prsunny
reviewed
May 6, 2019
|
|
||
| In layer 2 Vxlan, the tunnel map is VLAN to VNI. Layer 2 Vxlan is not supported completely, current state is TBD(To Be Done). The mainly shortcomings of L2 Vxlan are: | ||
|
|
||
| - Not specify the encap type when creating tunnel; The encap type is MAP_TO_INVALID, must be VLAN_ID_TO_VNI. |
There was a problem hiding this comment.
May be we should add a role attribute to config_db entry, "encap_decap", "encap_only" or "decap_only". Currently there is a use-case for L2 Vxlan as "decap_only" tunnels and hence MAP_TO_INVALID
|
|
||
| **Notice: The flows represented by red arrow are newly added by this project.** | ||
|
|
||
| - Flow 1：vxlanmgrd reads VXLAN related configuration from CONFIG_DB, creates VXLAN tunnel and its bridge portsave parameters. |
There was a problem hiding this comment.
Can we have the flow in UML sequence for clarity? Please refer Vxlan HLD.
AlanYoush
reviewed
Oct 12, 2020
|
|
||
| - When creating vxlan tunnel, create its bridge port. If VXLAN tunnel without bridge port, FDB MAC can not be learnt from or set to VXLAN tunnel in ASIC. | ||
| - Add the tunnel name map to counter table, so that the ‘show mac’ command can display the FDB learnt from VXLAN tunnel. | ||
| - Send command to Linux kernel to create L2 VXLAN tunnel interface. |
There was a problem hiding this comment.
Would BUM Forwarding of Vxlan Tunnel be supported?
|
We have another HLD that covers EVPN and L2 Vxlan - #437. This document is slightly out of scope. |
yxieca
force-pushed
the
master
branch
2 times, most recently
from
8498931 to
8837dc2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MSFT has implement basic L3 vxlan in vnet scenario. Here we add L2 vxlan based on their work.