Data plane VXLAN HLD - initial version #1
Conversation
| In small-scale datacenters, to reduce costs instead of BGP deployement, L3 forwarding could be based, either, on static configuration or usage of simpler protocol (such as OSPF or IS-IS). | ||
|
|
||
| Thus, in these cases, pure Layer2 VNI provides simple, flexible and cost-efficient solution. | ||
|
|
There was a problem hiding this comment.
controller base vxlan network – supported by cisco / vmware
edge data centers
| leaf vni { | ||
| mandatory true; | ||
| type stypes:vnid_type; | ||
| } |
There was a problem hiding this comment.
this mean per leaf and map one remove vtep ?
There was a problem hiding this comment.
Yes, it is either this or list of vni's per remote VTEP
|
|
||
| VXLAN_REMOTE_VTEP_TABLE|{{remote_vtep_name}} | ||
| "src_ip" : {{ipv4_address}} | ||
|
|
There was a problem hiding this comment.
this can be refered as rempte ip ?
There was a problem hiding this comment.
you mean change the name from "src_ip" to "remote_ip" ? Done
| In the current implementation P2MP tunnel creation flow exist with the exception of a bridgeport not created for P2MP tunnel. To support using P2MP tunnel for L2 purposes a bridge port is created for the P2MP tunnel object. | ||
|
|
||
| * Can/should it be supported in case of data plane tunnel ? | ||
|
|
There was a problem hiding this comment.
please explain the npon creating brg port , i think i does create on tunnel termination
if we support p2mp it means that user must configure every mac statically so i dont think this is needed
There was a problem hiding this comment.
Brigdeport explanation is taken from old HLD by mistake.
I rephrased the section, please changed text.
No description provided.