unknown-dst is not used for Layer 2 BUM traffic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-l2gw |
New
|
Undecided
|
Unassigned |
Bug Description
In the HARDWARE_VTEP spec it is stated that:
The keyword unknown-dst is used as a special ``Ethernet
address’’ that indicates the locations to which packets in a
logical switch whose destination addresses do not otherwise
appear in Ucast_Macs_Remote (for unicast addresses) or
Mcast_Macs_Remote (for multicast addresses) should be sent.
Same for Ucast_Macs_Local and Mcast_Macs_Local.
This means that if a broadcast or unknown, mac (BUM) is to be sent to specific destination(s), then these destinations
Physical_Locator entry in the OVSDB need to be referenced by unknown-dst mac either in the Ucast_Macs_Remote or by Mcast_Macs_Remote.
Currently networking_l2gw, do not populate this entry in the OVSDB, leaving it up to the switch, to implement whatever behavior it chooses.
The hardware vtep switch should only act according to what it was instructed by the DB entries. Flooding will only happen on ports referenced by unknown-dst entry.
I would suggest to extend the l2-gateway-
The implementation will insert an entry with unknown-dst in the Mcast_Macs_Remote and Ucast_Macs_Remote table , with a reference to the relevant Physical_Locator.
The HARDWARE_VTEP switch should translated this entry as an instruction to include this port for BUM
Is this duplicate of https:/ /bugs.launchpad .net/networking -l2gw/+ bug/1475251?