Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Aaron Rosen
I get the same exact error after doing a fresh build (and after commenting out that line) ./nox_core -i ptcp:6633 discovery switch NOX 0.9.1~full~beta (nox_core), compiled Jun 22 2011 21:50:51 Compiled with OpenFlow 0x01 1|discovery|ERR:lldp chassis ID subtype is 4 not 'local', ignoring Than

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Aaron Rosen
Hi Murphy, I did a branch checkout of what i had but I'm doing a completely clean one now. (I'll let you know those results shortly). Also there is a flowvisor in between. I've attached a packet in of this type. Wireshark is also claiming they are malformed. Thanks, Aaron On Wed, Jun 22, 201

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Murphy McCauley
Did you clone a totally clean branch? I don't immediately see a way that the current destiny code could generate this. Maybe it's just relaying them? Or are you using FlowVisor? Can you see these packets being sent TO the controller (wrapped in a packet_in)? Try commenting out the send_openf

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Aaron Rosen
Hi Murphy, I pulled in all your changes on destiny and am having the same issue. In wireshark the chassis ID subtype is 1. I've attached a packet_out OFP+LLDP case it helps. Thanks for your help! Aaron On Wed, Jun 22, 2011 at 8:01 PM, Murphy McCauley wrote: > I've just pushed a couple cleanups

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Murphy McCauley
I've just pushed a couple cleanups and fixes to destiny (including the aforementioned patch). Why don't you pull destiny again and see what the results are? If you continue getting the "lldp chassis ID subtype is 4 not 'local', ignoring" message, it's time to fire up Wireshark with the OpenFlo

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Aaron Rosen
Also, I just checked out destiny to try it there and when I run my code I get the following error: 3|pyrt|ERR:unable to invoke a Python event handler: Traceback (most recent call last): File "./nox/lib/util.py", line 136, in f ret = f.cb(event.datapath_id, attrs) File "./nox/netapps/d

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Aaron Rosen
Hi Murphy, It looks like the patch git applied fine. Changing that line yields the following output: 00453|discovery|ERR:lldp chassis ID subtype is 4 not 'local', ignoring Thanks, Aaron On Wed, Jun 22, 2011 at 6:16 PM, Murphy McCauley wrote: > Hm.  Maybe this is bitrot.  Please check that th

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Murphy McCauley
Hm. Maybe this is bitrot. Please check that the first part of the patch got applied and wasn't rejected. Specifically, line 65ish should be: cid.fill(chassis_id.SUB_LOCAL, array.array('B', 'dpid:' + hex(long(dpid)) [2:-1])) If it is, try replacing the log message around line 268 with somethin

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Aaron Rosen
Hi Murphy, After applying the patch I'm getting the following messages from nox: 00396|discovery|ERR:lldp chassis ID subtype is not 'local', ignoring 00397|discovery|ERR:lldp chassis ID subtype is not 'local', ignoring 00398|discovery|ERR:lldp chassis ID subtype is not 'local', ignoring Thanks

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Aaron Rosen
Hi Murphy you are right, I was mistaken on the dpid. I've applied this patch and still seeing the same results. (I am using zaku perhaps i should switch to destiny and try?). checking 492581376499901568 inport 41 False Any ideas? Thanks, Aaron On Wed, Jun 22, 2011 at 5:42 PM, Murphy McCau

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Murphy McCauley
You say your DPID is actually 00:26:f1:3f:e4:80, but... I am guessing (and hoping) that you're wrong. I am guessing it's actually 06:d6:00:26:f1:3f:e4:80 (which is 492581376499901568, BTW). So I think you're hitting a longstanding bug in discovery where it doesn't work right with DPIDs over 48

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Aaron Rosen
Hi Murphy, I managed to get it running but I can't seem to get it working correctly: In discovery.py I've uncommented line 334 to print the following: print 'Sending packet out of ',longlong_to_octstr(dp), ' port ',str(port) >From that I see: Sending packet out of 06:d6:00:26:f1:3f:e4:80 port

Re: [nox-dev] Using Discovery Module

2011-06-22 Thread Murphy McCauley
Try putting discovery before mymodule on the commandline (or, better, making mymodule depend on discovery in its meta.json). -- Murphy On Tuesday, June 21, 2011 01:52:18 PM Aaron Rosen wrote: > Or maybe doing > > from nox.netapps.discovery import discovery > if(self.resolve(discovery).is_switch

Re: [nox-dev] Using Discovery Module

2011-06-21 Thread Aaron Rosen
Or maybe doing from nox.netapps.discovery import discovery if(self.resolve(discovery).is_switch_only_port(self, dpid, port) ? Though if I import discovery in this manner I end up with the following error after nox starts: Current state: ERROR Required state: INSTALLED Dep

[nox-dev] Using Discovery Module

2011-06-21 Thread Aaron Rosen
Hello, I would like to use: ./nox/netapps/discovery/discovery.py to find interconnected links. I'm running nox in the following way ./nox_core -v -i ptcp:6644 mymodule discovery When doing this I see discovery messages getting printed out. Now In mymodule I believe I should be calling: is_swit