Re: [nox-dev] Flow expired events in NOX
I'm seeing another issue. I'm getting flow expired message even before a flow is started. I'm getting the flow expired messages when the switch is trying to connect to NOX. Please see the prints below. Why is flow expiry messages coming? 00041|openflow|DBG:Passive tcp interface bound to port 6633 00042|nox|INFO:nox bootstrap complete 00043|openflow|DBG:Passive tcp interface received connection 00044|openflow|DBG:stream: negotiated OpenFlow version 0x01 (we support versions 0x01 to 0x01 inclusive, peer no later than version 0x01) 00045|nox|DBG:Success sending in 'sending switch config' 00046|nox|DBG:Success sending in 'receiving features reply' 00047|nox|DBG:Success receiving in 'receiving features reply' 00048|nox|DBG:Success sending in 'receiving ofmp capability reply' 00049|nox|DBG:Success receiving in 'receiving ofmp capability reply' 00050|nox|DBG:Datapath 0036fb31fe75 sent error in response to capability reply, assuming no management support 00051|nox|DBG:No switch auth module registered, auto-approving switch 00052|nox|DBG:Registering switch with DPID = 36fb31fe75 00053|nox.coreapps.examples.pyswitch|INFO:Switch 36fb31fe75 has joined the network 00054|openflow-event|DBG:received flow expired event from 0036fb31fe75 00055|openflow-event|DBG:received flow expired event from 0036fb31fe75 00056|openflow-event|DBG:received flow expired event from 0036fb31fe75 00057|openflow-event|DBG:received flow expired event from 0036fb31fe75 00058|openflow|DBG:Passive tcp interface received connection 00059|openflow|DBG:stream: negotiated OpenFlow version 0x01 (we support versions 0x01 to 0x01 inclusive, peer no later than version 0x01) 00060|nox|DBG:Success sending in 'sending switch config' 00061|nox|DBG:Success sending in 'receiving features reply' 00062|nox|DBG:Success receiving in 'receiving features reply' 00063|nox|DBG:Success sending in 'receiving ofmp capability reply' 00064|nox|DBG:Success receiving in 'receiving ofmp capability reply' 00065|nox|DBG:Datapath 0036fb31fe76 sent error in response to capability reply, assuming no management support 00066|nox|DBG:No switch auth module registered, auto-approving switch 00067|nox|DBG:Registering switch with DPID = 36fb31fe76 00068|nox.coreapps.examples.pyswitch|INFO:Switch 36fb31fe76 has joined the network 00069|openflow-event|DBG:received flow expired event from 0036fb31fe76 00070|openflow-event|DBG:received flow expired event from 0036fb31fe76 00071|openflow-event|DBG:received flow expired event from 0036fb31fe76 00072|openflow-event|DBG:received flow expired event from 0036fb31fe76 Thanks & Regards, Candy On Thu, Oct 20, 2011 at 3:26 PM, kk yap wrote: > Hi, > > Try changing src/include/openflow-default.hh. Hope this is what you > are looking for. > > Regards > KK > > On 20 October 2011 13:42, Candy Floss wrote: > > Thanks for the reply. I'm not running discovery module. The idle time out > is > > set for 5 secs and the hard timeout is set to 0(i.e. permanent). These > are > > the parameters that are in the code by default. I have not changed > anything. > > > > Regards, > > Candy > > > > On Thu, Oct 20, 2011 at 1:39 PM, Kyriakos Zarifis > > > wrote: > >> > >> Hi, > >> are you running 'discovery' or any other application that has discovery > as > >> a dependency? > >> If so, the packet_ins you see are most probably the control (LLDP) > packets > >> sent by discovery to discover neighbors. > >> ( http://noxrepo.org/noxwiki/index.php/Discovery ) > >> the flow expiration time is set from the controller, when you send the > >> flow_mods. The flow_mod includes arguments to set hard/idle timeout for > the > >> entry. 'Idle timeout' means the entry will expire X seconds after no > >> matching traffic has hit the switch, 'hard timeout' means it will expire > in > >> X seconds no matter what. > >> (Section 5.5.3 > >> in http://www.openflow.org/documents/openflow-spec-v1.0.0.pdf) > >> > >> On Thu, Oct 20, 2011 at 1:27 PM, Candy Floss wrote: > >>> > >>> I have copnnected NOX and two switches. Sometimes when I connect the > >>> switch to the NOX I see packet_in event in addition to datapath_join > event. > >>> This is happening randomly. Not able to find a pattern when this > eaxctly > >>> happens but it happens most of teh time. I'm not starting any flows but > I > >>> still see packet_in event coming continously. What could be the reason? > >>> > >>> And also when I start the flow I see flow expired event on NOX in 1-2 > >>> secs. Where can I
Re: [nox-dev] Flow expired events in NOX
Thanks for the reply. I'm not running discovery module. The idle time out is set for 5 secs and the hard timeout is set to 0(i.e. permanent). These are the parameters that are in the code by default. I have not changed anything. Regards, Candy On Thu, Oct 20, 2011 at 1:39 PM, Kyriakos Zarifis wrote: > Hi, > > are you running 'discovery' or any other application that has discovery as > a dependency? > If so, the packet_ins you see are most probably the control (LLDP) packets > sent by discovery to discover neighbors. > ( http://noxrepo.org/noxwiki/index.php/Discovery ) > > the flow expiration time is set from the controller, when you send the > flow_mods. The flow_mod includes arguments to set hard/idle timeout for the > entry. 'Idle timeout' means the entry will expire X seconds after no > matching traffic has hit the switch, 'hard timeout' means it will expire in > X seconds no matter what. > (Section 5.5.3 in > http://www.openflow.org/documents/openflow-spec-v1.0.0.pdf) > > On Thu, Oct 20, 2011 at 1:27 PM, Candy Floss wrote: > >> I have copnnected NOX and two switches. Sometimes when I connect the >> switch to the NOX I see packet_in event in addition to datapath_join event. >> This is happening randomly. Not able to find a pattern when this eaxctly >> happens but it happens most of teh time. I'm not starting any flows but I >> still see packet_in event coming continously. What could be the reason? >> >> And also when I start the flow I see flow expired event on NOX in 1-2 >> secs. Where can I change the default timeout? Do I have to change in NOX or >> in openflow switch? >> >> Thanks & Regards, >> Candy >> >> ___ >> 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] Flow expired events in NOX
I have copnnected NOX and two switches. Sometimes when I connect the switch to the NOX I see packet_in event in addition to datapath_join event. This is happening randomly. Not able to find a pattern when this eaxctly happens but it happens most of teh time. I'm not starting any flows but I still see packet_in event coming continously. What could be the reason? And also when I start the flow I see flow expired event on NOX in 1-2 secs. Where can I change the default timeout? Do I have to change in NOX or in openflow switch? Thanks & Regards, Candy ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[nox-dev] Cannot see the flow table
I have the following configuration NOX - eth0 - 192.168.10.1/24 Switch 1 - eth0- 192.168.10.2/24 Switch 2 - eth0 - 192.168.10.3/24 Host 1 - eth0 - 192.168.10.4/24 Host2 - eth0 - 192.168.10.5/24 NOX | |--| switch1 switch2 | | host1host2 All of them are connected to VLAN(including host1 and host2). I ran the pyswitch module on NOX and secchan on switches. Switches are connected to NOX. When I ping from host1 to host2 the ping works but I cannot see any flow tables on switches. I used dumpflow command to see flow tables. Where did I go wrong? Is my configuration right? Regards, Candy ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Running NOX on VmWare
The messages are coming from the virtual machine. The network is getting flooded and the machine goes down so I'm not able to capture what messages are getting generated. My purpose is to configure NOX and test it. For that I have configured one Virtual machine as NOX and the other as open switch in the VmWare server. I do not have a physical switch, I have configured one virtual machine as a Switch. I will be adding more VMs but first I want to establish a connection between switch and NOX. Thanks, Candy On Mon, Sep 19, 2011 at 1:05 PM, Murphy McCauley wrote: > I don't think we have enough information to answer your question. > > Which ARP messages are you talking about? What machine are they coming > from and what are they asking for? > > And what's your purpose here? Are you going to add more VMs and connect > them to virtual ports on VM2? (As you've described it, you seem to have a > switch that isn't switching anything.) > > -- Murphy > > On Sep 14, 2011, at 11:01 AM, Candy Floss wrote: > > > I have created two virtual machines in VmWare server. I have configured > one machine as NOX controller and one as open switch. I added the routes and > I'm able to ping each other. But when I start the NOX and the open switch > the ARP messages are getting flooded on the machine. I have configured > unique MAC address for each of the machines. My configuration is like this > > > > on VmWare server > > Virtual Machine 1 : Nox Controller > > > > eth0 192.170.35.1 netmask 255.255.0.0 > > > > Virtual Machine 2: Open Switch 1 > > > > eth0 192.170.40.1 netmask 255.255.0.0 > > > > Why the ARP messages flooding? Is my configuration right? > > > > > > Thanks, > > Candy > > > > ___ > > 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
Re: [nox-dev] NOX web interface not opening
ies: 00047|nox|INFO:nox bootstrap complete Thanks, Candy On Thu, Sep 15, 2011 at 5:55 PM, Murphy McCauley wrote: > This looks like a bug. In webserver.py around line 268, change the two > update_iff_changed lines... > > if arr[0] == "ssl_port": > update_iff_changed(p, 'ssl_port', [int(arr[1])]) > elif arr[0] == "port": > update_iff_changed(p, 'port', [int(arr[1])]) > > (You're inserting two pairs of brackets.) > > -- Murphy > > On Sep 15, 2011, at 5:13 PM, Candy Floss wrote: > > Thanks for the reply. > > I opened a browser and started the nox_core as given below. This is the > error I got. > > /nox/build/src# ./nox_core -v -v webserver=port=8080 dummywebpage > > 1|nox|INFO:Starting nox_core (/nox/build/src/.libs/lt-nox_core) > > 2|pyrt|DBG:Loading a component description file > 'nox/coreapps/pyrt/meta.json'. > > 3|pyrt|DBG:Loading a component description file > 'nox/coreapps/testharness/meta.json'. > > 4|pyrt|DBG:Loading a component description file > 'nox/coreapps/simple_py_app/meta.json'. > > 5|pyrt|DBG:Loading a component description file > 'nox/coreapps/simple_c_py_app/meta.json'. > > 6|pyrt|DBG:Loading a component description file > 'nox/coreapps/coretests/meta.json'. > > 7|pyrt|DBG:Loading a component description file > 'nox/coreapps/switch/meta.json'. > > 8|pyrt|DBG:Loading a component description file > 'nox/coreapps/messenger/meta.json'. > > 9|pyrt|DBG:Loading a component description file > 'nox/coreapps/examples/meta.json'. > > 00010|pyrt|DBG:Loading a component description file > 'nox/coreapps/examples/t/meta.json'. > > 00011|pyrt|DBG:Loading a component description file > 'nox/coreapps/hub/meta.json'. > > 00012|pyrt|DBG:Loading a component description file > 'nox/coreapps/snmp/meta.json'. > > 00013|pyrt|DBG:Loading a component description file > 'nox/coreapps/simple_c_app/meta.json'. > > 00014|pyrt|DBG:Loading a component description file > 'nox/netapps/discovery/meta.json'. > > 00015|pyrt|DBG:Loading a component description file > 'nox/netapps/monitoring/meta.json'. > > 00016|pyrt|DBG:Loading a component description file > 'nox/netapps/flow_fetcher/meta.json'. > > 00017|pyrt|DBG:Loading a component description file > 'nox/netapps/tablog/meta.json'. > > 00018|pyrt|DBG:Loading a component description file > 'nox/netapps/networkstate/meta.json'. > > 00019|pyrt|DBG:Loading a component description file > 'nox/netapps/switchstats/meta.json'. > > 00020|pyrt|DBG:Loading a component description file > 'nox/netapps/data/meta.json'. > > 00021|pyrt|DBG:Loading a component description file > 'nox/netapps/user_event_log/meta.json'. > > 00022|pyrt|DBG:Loading a component description file > 'nox/netapps/storage/meta.json'. > > 00023|pyrt|DBG:Loading a component description file > 'nox/netapps/storage/t/meta.json'. > > 00024|pyrt|DBG:Loading a component description file > 'nox/netapps/hoststate/meta.json'. > > 00025|pyrt|DBG:Loading a component description file > 'nox/netapps/lavi/meta.json'. > > 00026|pyrt|DBG:Loading a component description file > 'nox/netapps/tests/meta.json'. > > 00027|pyrt|DBG:Loading a component description file > 'nox/netapps/spanning_tree/meta.json'. > > 00028|pyrt|DBG:Loading a component description file > 'nox/netapps/flowtracer/meta.json'. > > 00029|pyrt|DBG:Loading a component description file > 'nox/netapps/routing/meta.json'. > > 00030|pyrt|DBG:Loading a component description file > 'nox/netapps/authenticator/meta.json'. > > 00031|pyrt|DBG:Loading a component description file > 'nox/netapps/switch_management/meta.json'. > > 00032|pyrt|DBG:Loading a component description file > 'nox/netapps/bindings_storage/meta.json'. > > 00033|pyrt|DBG:Loading a component description file > 'nox/netapps/bindings_storage/t/meta.json'. > > 00034|pyrt|DBG:Loading a component description file > 'nox/netapps/topology/meta.json'. > > 00035|pyrt|DBG:Loading a component description file > 'nox/netapps/route/meta.json'. > > 00036|pyrt|DBG:Loading a component description file > 'nox/webapps/webservice/meta.json'. > > 00037|pyrt|DBG:Loading a component description file > 'nox/webapps/miscws/meta.json'. > > 00038|pyrt|DBG:Loading a component description file > 'n
Re: [nox-dev] NOX web interface not opening
eployer: Current state: INSTALLED Required state: INSTALLED Dependencies: 00044|nox|DBG:python: Current state: INSTALLED Required state: INSTALLED Dependencies: 00045|nox|ERR:Cannot change the state of 'webserver' to INSTALLED: 'webserver' ran into an error: cannot install the Python component: Traceback (most recent call last): File "./nox/webapps/webserver/webserver.py", line 320, in install return self.reconfigure() File "./nox/webapps/webserver/webserver.py", line 360, in reconfigure self.reconfigure_listeners(0, self.defaults) File "./nox/webapps/webserver/webserver.py", line 383, in reconfigure_listeners if len(list) > 0: self.siteConfig[key] = list[0] TypeError: object of type 'int' has no len() Thanks, Candy On Thu, Sep 15, 2011 at 4:15 PM, Murphy McCauley wrote: > You do have to actually open up a browser and look at it. I think it > defaults to port 80, which you probably can't use unless you're root. If > you want to change it... I can't remember exactly, but I think maybe... > nox_core -v -v webserver=port=8080 dummywebpage would do it. > > (You may want to use -v -v to make sure you get any debugging messages.) > > -- Murphy > > On Sep 15, 2011, at 4:09 PM, Candy Floss wrote: > > > I tried starting NOX web interface with the command > > ./nox_core -v dummywebpage > > > > It gave prints Loading component and listed some modules. Last statement > was > > 0043|nox|INFO:nox bootstrap compelete > > > > After that i did not see any web interface opening. > > > > Thanks, > > Candy > > > > ___ > > 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 web interface not opening
I tried starting NOX web interface with the command ./nox_core -v dummywebpage It gave prints Loading component and listed some modules. Last statement was 0043|nox|INFO:nox bootstrap compelete After that i did not see any web interface opening. Thanks, Candy ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[nox-dev] Add/Delete flows in nox controller
I'm a newbie to open flow. I have a doubt regarding the flows. From the documentation of NOX I understood that we start the nox-core from the NOX controller and on the open switch we add the secure channel to NOX controller. Where do we add and delete flows? Is there a command in NOX controller to add and delete flows? If so how do I do it? Or do we have to write code in NOX controller to add and delete flows. If so in which module do we do it? Thanks, Candy ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[nox-dev] Running NOX on VmWare
I have created two virtual machines in VmWare server. I have configured one machine as NOX controller and one as open switch. I added the routes and I'm able to ping each other. But when I start the NOX and the open switch the ARP messages are getting flooded on the machine. I have configured unique MAC address for each of the machines. My configuration is like this on VmWare server Virtual Machine 1 : Nox Controller eth0 192.170.35.1 netmask 255.255.0.0 Virtual Machine 2: Open Switch 1 eth0 192.170.40.1 netmask 255.255.0.0 Why the ARP messages flooding? Is my configuration right? Thanks, Candy ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[nox-dev] CLI for NOX
Is there any CLI for NOX where in I can give the commands to configure NOX without having to change the scripts. Regards, Candy ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
