Conversation
High level design for Sonic Vxlan
doc/vxlan/Vxlan_hld.md
Outdated
There was a problem hiding this comment.
It's already supported as vni and vlan. Check https://github.com/Azure/sonic-swss/blob/master/orchagent/vxlanorch.h#L56
doc/vxlan/Vxlan_hld.md
Outdated
There was a problem hiding this comment.
Probably it's better to have one name of the attribute to refer to vni? I'd put vni here.
jipanyang
left a comment
There was a problem hiding this comment.
Is there case that vxlan packet gets trapped to hostif?
If the answer is yes, what will the packet format be like and how to handle it?
doc/vxlan/Vxlan_hld.md
Outdated
There was a problem hiding this comment.
For the schemas defined here, are they for appDB or configDB?
There was a problem hiding this comment.
better to specify this clearly.
There was a problem hiding this comment.
I noticed that VNI to VLAN map is added to config DB, while VNI to virtual router map is added to app DB.
Is there a reason for separating these two types of tunnel maps?
There was a problem hiding this comment.
Yes, the idea is to have VxlanOrch only deal with Tunnel configurations (Encap/Decap etc). The peering must be required only by VRF/RouterOrch.
|
for vxlan decap flow, how you decide which pipeline the packet take after decap, l2 or l3? |
doc/vxlan/Vxlan_hld.md
Outdated
There was a problem hiding this comment.
the comment should be the destination address
doc/vxlan/Vxlan_hld.md
Outdated
There was a problem hiding this comment.
Only one vxlan_tunnel per vnet?
doc/vxlan/Vxlan_hld.md
Outdated
There was a problem hiding this comment.
What will be the total number of routes to be supported ? Can that be added to this table as well. - thx
High level design for Sonic Vxlan
High level design for Sonic Vxlan