flowvisor
flowvisor copied to clipboard
opennetworkinglab
Peer flowvisors have issues with slicing LLDP traffic
A flowvisor can slice LLDP traffic for packet-ins that they have marked as belonging to a specific slice; however, if a packet-in goes between two OpenFlow networks with different flowvisors (i.e. peer flowvisors), it will be marked with the slice name that is at the first FV, which is not necessarily the same as the slice name which is at the second FV.
Currently in GENI, FOAM makes FV slices using a UUID that corresponds to a GENI sliver, which is unique per-FOAM instance across a given GENI slice, so the FV slice names will always be different at peer FVs.
There was some discussion of this problem on #158. Note that the maintainer of FOAM should be involved in the discussion of how to solve this issue. One solution may be to ensure that the FV slice name is the same across federated FlowVisors, but that may cause problems in GENI.
Smilar to Issue15 or Issue158. Fixed by standardizing the way LLDP is handled with proper formation of TLVs. Fixed in 1.2 Committed in 6685bf82d59abf09fa1b80f23509ac8d5d7849ed
We discussed this ticket on #openflow-discuss, and we decided that this should be re-opened. I can't actually re-open tickets for this repo. Can someone else do it?
Have to further analyse if FlowVisor can fix it and if it can what would be the approach, but the problem still exists at GPO.