I think type 3 code 0 is failure to add a flow because you already have too many, but you can look it up in the OpenFlow specification. The data that goes with an error depends on the error. In the case of failure to add a flow, I think it just returns the flow mod message to you (or at least the beginning of it). In zaku, I think the data just gets thrown away, but I recently pushed a patch that lets you retrieve it in destiny. I have a vague memory that the data count might also include the error packet size or something, so if you're using C++ you should watch out for that (I think in Python you can just len() the buffer and get the right answer).
-- Murphy On Jan 12, 2011, at 5:45 AM, Syed Akbar Mehdi wrote: > Hi, > > While running some captured network data through an openflow switch running > on a Linux box, I get the following error messages at the controller: > > 00015|openflow-event|ERR:received Openflow error packet from > dpid=002320b77f72: type=3, code=0, 80 bytes of data > > What is meant by the type = 3, code = 0 ? Also does the 80 bytes mean that > the packet at the switch that caused it to send this error to the controller > was 80 bytes in size? > > -- > Regards, > Syed Akbar Mehdi, > School of EECS (SEECS), > National University of Sciences and Technology (NUST), > Pakistan. > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org _______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
