Hi Michael Pls see inline
From: discuss <discuss-boun...@openvswitch.org<mailto:discuss-boun...@openvswitch.org>> on behalf of Michael Kashin <mmkas...@gmail.com<mailto:mmkas...@gmail.com>> Date: Sunday, May 15, 2016 at 6:46 PM To: "discuss@openvswitch.org<mailto:discuss@openvswitch.org>" <discuss@openvswitch.org<mailto:discuss@openvswitch.org>> Subject: [ovs-discuss] hardware vtep handling of ARP I'm using Openstack's L2gw plugin This plugin works with the ML2 plugin to configure cumulus VX switch. I can get my VM to ping the "baremetal" IP connected to cumulus's switchport. However, the reverse doesn't quite work. When my baremetal IP sends an ARP for MAC of the VM it doesn't get a response. Could you provide a simple network diagram ? Is hw vtep OVS supposed to respond to ARP locally? If by “hw vtep OVS” you mean the ovs-vtep vtep simulator written in Python, then the answer is NO ovs-vtep does not presently program arp responders Without a simple diagram, I can’t be sure what you want to do, but my guess is that the arp responder that you want is the ovs programming functionality provided by the Neutron ML2 plugin. If that’s the case, then you should redirect your question. Here's the simplified version of how OVSDB was provisioned by the Openstack's L2gw agent: Mcast_Macs_Local table: unknown-dst -> Locator Set "X" Physical_Locator_Set table: Locator_set "X" -> Locator [Y] Physical_Locator table: Locator "Y" -> dst_ip "Z", where dst_ip "Z" is the local VTEP IP (loopback interface on cumulus VX) Ovs-vtep programs the mcast_macs_local table for unknown-dst initially which is just mac to locator set mapping, not arp mapping http://openvswitch.org/support/dist-docs/vtep.5.pdf
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
