Re: [nox-dev] NOX error

2012-02-18 Thread Kyriakos Zarifis
Is there a meta.json in the build tree?
"nox/build/src/nox/coreapps/examples/" ?
(not in "nox/src/nox/coreapps/examples/")

if it is there, maybe its contents have changed and are in wrong format -
feel free to paste it

On Sat, Feb 18, 2012 at 7:47 AM, Baraki Halefom  wrote:

> anyone familiar with the following error.
>
> 2|pyrt|ERR:Can't load and parse 'nox/coreapps/examples/meta.json
>
>  the meta.json file has all the required dependency lists
>
>
>
>
> --
>
>
> Baraki H. Abay
> Department of Math and Computer science
> North Carolina Central University
> Durham, 27707 NC
>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev


[nox-dev] NOX error

2012-02-18 Thread Baraki Halefom
anyone familiar with the following error.

2|pyrt|ERR:Can't load and parse 'nox/coreapps/examples/meta.json

 the meta.json file has all the required dependency lists




-- 


Baraki H. Abay
Department of Math and Computer science
North Carolina Central University
Durham, 27707 NC
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev


Re: [nox-dev] NOX Error

2011-01-12 Thread Syed Akbar Mehdi
Thanks Murphy, Kyriakos. That is exactly the problem. Actually the data I am
using has about 1400 TCP connection initiations. Whenever a SYNACK is
received, I set the flow specifically for that connection with an idle
timeout of 1 sec. The data is for almost a whole day and most of these flows
are short-lived. I dumped the flow table at one point while the datapath was
complaining with the flow table full message and there were 57 flows.

The spec does not say anything about the maximum number of flows in a table
(or at least I could not find that). Also, all the flows that I am adding
are going into table 1, which might be because of the fact that all of them
have the same priority.

Regards,
Akbar

On Wed, Jan 12, 2011 at 7:15 PM, Murphy McCauley  wrote:

> 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
>
>


-- 
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


Re: [nox-dev] NOX Error

2011-01-12 Thread Murphy McCauley
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


Re: [nox-dev] NOX Error

2011-01-12 Thread Kyriakos Zarifis
Hi Syed,

type=3 corresponds to "OFPET_FLOW_MOD_FAILED", and code=0 to
"OFPFMFC_ALL_TABLES_FULL"

Any reason why the flow table would be indeed full?


On Wed, Jan 12, 2011 at 3:45 PM, Syed Akbar Mehdi <
akbar.me...@seecs.nust.edu.pk> 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


[nox-dev] NOX Error

2011-01-12 Thread Syed Akbar Mehdi
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