Flowvisor can certainly cause issues which don't generally come up under non-Flowvisor use. The first thing you might do is see if you can find out which version of Flowvisor is being run and see if this is a known issue. Bug FLOWVISOR-133, for example, describes something which could certainly cause the behavior you're seeing (though it's now quite old).
The next thing you can do to try to understand what's happening is to capture the OpenFlow traffic (you can use POX's openflow.debug component or tcpdump or wireshark or whatever) and examine it. You can associate the errors with the specific OpenFlow command that caused them and see if there's anything noteworthy. Looking at the timestamps, the number of events, the specific messages which caused the errors, etc. -- Murphy On Oct 9, 2014, at 3:24 PM, Farzaneh Pakzad <f.pak...@uq.edu.au> wrote: > Hi Murphy, > > Thanks a lot for your reply. > > Regarding to the first question: > > What components were you running in POX? > I ran the openflow.discovery component of pox to detect the switches and > links between them. (I also ran the forwarding.l2_learning switch and again I > get this error: OFPBRC_BUFFER_UNKNOWN and other Openflow error messages such > as flow mod failed ) > > And the second one: > And is OFELIA raw hardware or are you running under Flowvisor? > OFELIA is running under Flowvisor according to the below information from > this link: > > http://www.fibre-ict.eu/index.php/cmf/ofelia > > “In order to slice the OpenFlow resources to support multiple experiments and > users, the Expedient system, from which OFELIA inherits some of the most > important features, make use of 4 layers: at the bottom are OpenFlow > switches, then on top of them, the Flowvisor, the Opt-In Manager, and finally > the OpenFlow Expedient connector. The Flowvisor is the most necessary part to > isolate and support multiple experiments. At an abstract level, Flowvisor is > a transparent proxy between many islands with OpenFlow switches and OpenFlow > controllers used in a certain slice. Basically, the Flowvisor(s) present in > each island (or provider) monitors OpenFlow protocol messages from and to the > controllers, ensuring that each slice defined by the FlowSpace (a set of > header values defined to isolate experiments) operates on traffic within that > space.” > > Best regards, > Farzaneh > > > From: Murphy McCauley [mailto:murphy.mccau...@gmail.com] > Sent: Thursday, 9 October 2014 5:10 PM > To: Farzaneh Pakzad > Cc: pox-dev@lists.noxrepo.org > Subject: Re: [pox-dev] OFPBRC_BUFFER_UNKNOWN in OFELIA testbed > > It might be much easier with more information. What components were you > running in POX? And is OFELIA raw hardware or are you running under > Flowvisor? > > -- Murphy > > On Oct 8, 2014, at 6:57 PM, Farzaneh Pakzad <f.pak...@uq.edu.au> wrote: > > > Hello everybody, > > I don't know if it is a relevant question to ask here: > I am trying to do OpenFlow topology discovery (with pox) in real testbed > called OFELIA. > I've chosen some switches form one of the island to run the test. > After I did all the settings, the controller started to work and detect the > switches and links between them. > However, in the meantime there are some openflow error messages and warnings > as well. These errors are as follow: > > """ > ERROR:openflow.of_01:[00-00-00-00-00-02|512 2] OpenFlow Error: > [00-00-00-00-00-02|512 2] Error: header: > [00-00-00-00-00-02|512 2] Error: version: 1 > [00-00-00-00-00-02|512 2] Error: type: 1 (OFPT_ERROR) > [00-00-00-00-00-02|512 2] Error: length: 28 > [00-00-00-00-00-02|512 2] Error: xid: 0 > [00-00-00-00-00-02|512 2] Error: type: OFPET_BAD_REQUEST (1) > [00-00-00-00-00-02|512 2] Error: code: OFPBRC_BUFFER_UNKNOWN (8) > [00-00-00-00-00-02|512 2] Error: datalen: 16 > [00-00-00-00-00-02|512 2] Error: 0000: 01 0d 00 10 00 00 00 18 9e 11 2d 2c > 00 06 00 00 |..........-,....| > """ > > """ > INFO:packet:(lldp tlv parse) warning TLV data too short to parse (86) > INFO:packet:(lldp parse) error parsing TLV > """ > Would you please help me with that? > > I would like to know if anyone had this problem before > and what makes this problem to happen and if I can solve it or not? > > Thank you all. > > Farzaneh
