Yes, you are right that none of the current OVS vendor extensions are initiated from the switch-side. I saw the message from Namgon on the OpenFlow mailing list, and an older version of OVS (0.99.0) is being used. That version contains our first stab at a management protocol, which used OpenFlow for framing and initiated connections from the switch. In later versions, we replaced that with a JSON-RPC management protocol that runs on port 6632/TCP.
I would recommend that Namgon upgrade to a newer version, since there have been a lot of improvements since that release. That will also probably make your issue go away. Obviously, I can't commit to never having any switch-side initiation of vendor extensions, but we don't have any plans for them at the moment. --Justin On Jul 6, 2010, at 12:14 PM, Rob Sherwood wrote: > Hi, > > It looks like OVS is the first switch to make use of OpenFlow vendor > extension messages and it's tickling some bugs in the FlowVisor. > > Can someone sanity check my understanding of what OVS is doing? > > AFAICT, OVS only uses vendor extension messages in response to > something the controller sends: is that correct? For example, there > is some vendor request from the controller and OVS gives the response > (critically, the response has the same transaction ID as the request)? > The reason why I'm asking is that FV keeps track of OpenFlow > transaction ids (XIDs) and uses them to map responses back to the > requesting slice. I believe that mechanism will work here (at least, > how OVS currently uses vendor extension messages), but I wanted to > drop a quick sanity check to the list first. > > If OVS sends unsolicited vendor extension messages, then I will have > to do something more complicated to support them on FV. > > Thanks in advance, > > - Rob > . > > PS Fwiw, http://www.openflowswitch.org/bugs/flowvisor/ticket/123 > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
