[openstack-dev] [l2gw] How to handle correctly unknown-dst traffic
Saverio Proto
saverio.proto at switch.ch
Tue Aug 15 08:10:10 UTC 2017
> The ucast-mac-remote table is filled with information that don't match
> your comments. In my environment, I have created only one neutron
> network, one l2gw instance and one l2gw connection. However, the mac
> reflected in that table corresponds to the dhcp port of the Neutron
> network (I've checked the mac on the dhcp namespace and it's the same).
> I've created several VMs in different compute nodes and there is only
> one line there. Could you check again the MAC address?
Hello,
I confirm I have one line per VM
root at l2gw-0:/# vtep-ctl list-remote-macs
ee87db33-1b3a-42e9-bc09-02747f8a0ad5
ucast-mac-remote
fa:16:3e:6b:6e:d1 -> vxlan_over_ipv4/10.1.1.161
fa:16:3e:7f:18:77 -> vxlan_over_ipv4/10.1.0.126
fa:16:3e:90:7f:f9 -> vxlan_over_ipv4/10.1.1.177
fa:16:3e:c2:7b:da -> vxlan_over_ipv4/10.1.1.167
fa:16:3e:ca:ad:c6 -> vxlan_over_ipv4/10.1.0.126
fa:16:3e:f0:21:01 -> vxlan_over_ipv4/10.1.1.175
I have the indication of the mac address of the VM, and the IP address
of the hypervisor where it is hosted.
> In my setup I get this automatically:
>
> mcast-mac-remote
> unknown-dst -> vxlan_over_ipv4/192.0.2.6 <http://192.0.2.6>
>
> If you're using the agent, it might be a bug.
I am running Openstack Newton, on what version is based your PoC ?
thank you
Saverio
More information about the OpenStack-dev
mailing list