Hello, I think I figured out the answers to my questions. I need some additional clarifications on the OvS vtep functionality. We are moving away from kernel Vxlan to OvS/OvS-DPDK. Kernel Vxlan supports both point-to-point and point-to-multipoint implementation and we have used that in our current implementation. With OvS/OvS-DPDK it is point-to-point only, I don't see a way to do point-2-multipoint even when using ovs-vtep/vtep-ctl. Wanted to know if it's possible and any reference available?
Thanks. On Mon, Jun 22, 2020 at 5:27 PM Ravi Kerur <[email protected]> wrote: > Hello OvS team, > > I am looking into vtep functionality and trying to map it to OvS DPDK as > most of our usage is with OvS-DPDK. > > http://docs.openvswitch.org/en/latest/howto/vtep/ > > Some clarifications... > > In section simulating NVC > > $vtep-ctl bind-ls br0 p0 0 ls0 > <--- What is '0' is it port-id of eth1? > > $ vtep-ctl set Logical_Switch ls0 tunnel_key=33 > <---- '33' is some random number or has significance? > > Thanks. > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
