Item #1: flowtracer and monitoring both do per flow statistics. You might want to examine how they do it (they use pylibopenflow to craft an OpenFlow message).
Item #2: As I mentioned in response to your previous message, you must be using the destiny branch of NOX (not zaku) to use OFPAT_ENQUEUE. Please upgrade. -- Murphy On Jan 9, 2012, at 9:45 PM, Amit Tewari wrote: > Hi, > > I am currently using NOX 0.9.0(zaku)~full~beta contrlooer for my openvswitch > 1.2.2 on openflow 1.0 > > I have developed certain api’s using /lib/core.py file . > I am able to get table statictics and port statistics of switch on nox. > > ISSUE: > I want to extract per flow statistics , queue statistics on nox . but I am > unable to find api’s and handlers for it. > I want to support ENQUEUE action also, but when I use send_flow_command api > it returns error. > Self.ctxt.send_flow_command with action argument as OFPAT_ENQUEUE then > make_actions_array routine returns error “action not supported” > > In make_actions_array routine only testing is for OFPAT_OUTPUT action type. > > Although lib/openflow.py contains all flags and operations as per openflow > 1.0 spec. > > Please let me know how I can meet support these features using nox, or I need > to use different nox version ? > > Regards > Amit Tewari > NHST > > DISCLAIMER: > ----------------------------------------------------------------------------------------------------------------------- > > The contents of this e-mail and any attachment(s) are confidential and > intended > for the named recipient(s) only. > It shall not attach any liability on the originator or NECHCL or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect the > opinions of NECHCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, > distribution and / or publication of > this message without the prior written consent of the author of this e-mail > is > strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. . > ----------------------------------------------------------------------------------------------------------------------- > _______________________________________________ > 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
