Hi Murphy, I have another question when i tried to run custom controller with own component, it shows an error
my code is c1 = net.addController( 'c1', NOX, noxArgs="pyflow", port=6633 ) and the error given is controller_new = controller( name, **kwargs ) TypeError: __init__() got an unexpected keyword argument 'noxArgs' Any idea where i did wrong here? Thanks. Regards, Anthony On Sun, Jul 15, 2012 at 2:51 PM, Anthony Salim < [email protected]> wrote: > Hi Murphy, > > Yes it works if the cache timeout set to 0 but the switch only can take > certain number of flows depending on its capacity. > > Sorry i dont get about reinstall the flows from the controller? Thanks. > > Regards, > Anthony > > > On Fri, Jul 13, 2012 at 8:30 PM, Murphy McCauley < > [email protected]> wrote: > >> So if you disable the timeouts, a flow should remain in the table until >> it's removed or until the switch is reset. Is that not working somehow? >> >> Secondly, why don't you just reinstall these flows from the controller? >> >> I think I must be missing something. >> >> -- Murphy >> >> On Jul 13, 2012, at 5:27 AM, Anthony Salim wrote: >> >> Hi Murphy, >> >> Hmm the case is to have a cache storage of all the flows table because as >> we know, the switches only can keep flows for certain amount of time but >> once the timer expired, it will just disappear. So i am wondering what kind >> nox functionalities that i can use to create such cache. Thanks. >> >> Regards, >> Anthony >> >> On Fri, Jul 13, 2012 at 3:59 AM, Murphy McCauley < >> [email protected]> wrote: >> >>> In general, the only way to get a flow table into an OpenFlow switch is >>> to put one there from the controller. Sometimes there are special tools >>> (like dpctl / ovs-dpctl) which are capable of installing table entries too, >>> though this is switch-specific and not an OpenFlow thing. It's reasonable, >>> however, for the controller to know that when some switch connects, it >>> should immediately install some table. >>> >>> (I still don't really understand the use case for copying a flow table, >>> though, since the port numbers are liable to be wrong.) >>> >>> -- Murphy >>> >>> On Jul 11, 2012, at 9:10 PM, Anthony Salim wrote: >>> >>> Hi Murphy, >>> >>> How bout that if the switch is a mininet switches? can i say for example >>> add another mininet switch and store the flow table in it? Thanks. >>> >>> Regards, >>> Anthony >>> >>> On Thu, Jul 12, 2012 at 12:34 AM, Murphy McCauley < >>> [email protected]> wrote: >>> >>>> I'm not sure I understand the question. If you mean you want to have >>>> one switch install a flow in another switch, then no, because switches >>>> don't communicate amongst themselves -- only with controllers. In most >>>> cases a *copied* table entry wouldn't be that useful anyway since, for >>>> example, port numbers would likely be different on the different switches. >>>> >>>> It is, however, easy enough to install slightly different table entries >>>> on all your switches from the controller that all match the same traffic... >>>> >>>> -- Murphy >>>> >>>> On Jul 11, 2012, at 6:10 AM, Anthony Salim wrote: >>>> >>>> > Hi guys, >>>> > >>>> > Is there any function in openflow that can be used to duplicate >>>> (copy) flow table entries in the switches? Thanks. >>>> > >>>> > lets say if i have a flow with same source and destination, it will >>>> go through that switch flow table and forward the packet accordingly and >>>> also make a copy of flow entry in another flow table lets say another >>>> switch. >>>> > >>>> > Regards, >>>> > Anthony >>>> >>>> >>> >>> >> >> >
