Amin mentioned this to me yesterday -- there appears to be a bug in Open 
vSwitch 1.2.1 where packet outs get dropped when the input port is none or 
controller (which are the two that make any sense for the LLDP packets that 
discovery sends).  This actually should be showing up on Open vSwitch's log.

A workaround is to just set the port to some large number.  In discovery.py 
something like line 331 is:
self.send_openflow_packet(dp, packets[dp][port].tostring(), port)

Try changing it to:
self.send_openflow_packet(dp, packets[dp][port].tostring(), port, 100)

With any luck, that'll fix it.

-- Murphy

On Sep 15, 2011, at 10:25 AM, Lucas Henrique Mauricio wrote:

> Hello guys,
> 
> One of the interfaces in each VM is configured as internal network in 
> VirtualBox. This means that if these interfaces are in the same internal 
> network, I only net to put them in the same subnet to connect them. So, what 
> I do in OpenvSwitch is the following:
> - Create a bridge br0 and put eth2 of VM1 in it.
> - Set the controller (NOX, that is in the physical machine) of br0
> - Set a ip for br0
> - Next, I do the same for the other VM, putting br0 in the same subnet of the 
> previous machine.
> 
> Doing this, one machine can ping the other. I put some prints in 
> gui/topology.py as Kyriakos told me to do. I printed links and srcid and it's 
> empty. I took a look at spanning_tree messages in NOX GUI and it said that 
> could not find the srcid. This makes me think that openvswitch is not telling 
> NOX some information about topology.
> 
> I have installed original openflow in these VMs as well and when I ran it.. 
> Suprise.. Links showed up! And those prints in topology.py informed me about 
> links and srcid.
> 
> Maybe I am configurating something wrong in openvswitch.. =(( 
> 
> 2011/9/14 Kyriakos Zarifis <kyr.zari...@gmail.com>
> The error message you get when you close the application is a known issue (it 
> doesn't really affect anything)
> 
> You are correct about flowtracer.py. (I didn't remember we had separated the 
> feature into its own component). Try running that one, I just tested it on my 
> end.
> It won't show anything too meaningful until we figure out why the links are 
> not drawn. This might require some debugging on your side:
> 1) First, are you sure there are indeed links there? Have you tried to test 
> connectivity? 
> 2) If pings etc work, then try to take a look at LAVI's messages to see that 
> it actually sees the links. (LAVI is the backend that advertises the topology 
> to the gui). 
> 3) On the gui side, you can add some print statements in "got_topo_msg()" in 
> the file src/gui/topology.py (around line 755), to make sure that link 
> advertisement messages are received. I.e. add a "print jsonmsg" and make sure 
> messages with the field "links" are received. 
> 
> 
> 
> On Wed, Sep 14, 2011 at 5:04 AM, Lucas Henrique Mauricio 
> <lhmauri...@poli.ufrj.br> wrote:
> Hello!
> 
> I don't have physical access to the computer I'm working on it now but the 
> error messages I have are:
> - Something with a qt4 sql library (Solved downloading libqt4-sql-sqlite)
> - When exiting the NOX GUI, it shows an error message telling something about 
> it didn't finish a connection (maybe I'm wrong), something will cease to 
> work. I don't remember clearly the correct error message. =(
> - When I try to use spanning tree without executing it with nox it gives a 
> series of python errors that I think that can be easily solved executing 
> spanning_tree.
> 
> There is a flowtracer.py but you told me to run sample_routing instead. Is it 
> correct?
> 
> 
> 
> 2011/9/13 Murphy McCauley <jam...@nau.edu>
> Oh, duh, of course the spanning tree component needs to be running.  Haha, 
> thanks Kyriakos.
> 
> One more note is that if you run sample_routing, *don't* run pyswitch.
> 
> -- Murphy
> 
> 
> On Sep 13, 2011, at 6:15 PM, Kyriakos Zarifis wrote:
> 
>> Hi there,
>>  
>> for stp and flowtracer, the respective relevant NOX components need to be 
>> running
>> If I recall correctly, the names of these components are 'spanning_tree" and 
>> "sample_routing"
>> 
>> The haven't been thoroughly tested, but worked fine last time I checked. 
>> They won't do much anyway if the links don't show up. Do you get any error 
>> messages in the terminal where you started the GUI?
>> 
>> On Tue, Sep 13, 2011 at 10:21 PM, Murphy McCauley <jam...@nau.edu> wrote:
>> I had a vague memory about components, so I looked it up.  Maybe this 
>> applies?
>> http://noxrepo.org/pipermail/nox-dev/2011-August/007951.html
>> 
>> For links -- did you add "discovery" to your NOX commandline?
>> 
>> STP and Flowtracer... I am not sure if these are implemented.  You might 
>> take a glance at the code to see if you can tell.  I'm not an expert in the 
>> GUI.  Maybe Kyriakos can jump in here. :)
>> 
>> -- Murphy
>> 
>> On Sep 13, 2011, at 9:44 AM, Lucas Henrique Mauricio wrote:
>> 
>>> Hello Murphy.
>>> 
>>> You were right about debugging messages as well.. Using -v -v did make 
>>> these messages to show up in the GUI.
>>> 
>>> But I still have problems with the links and the components.. 
>>> 
>>> STP and Flowtracer are not working as well but maybe I only need to run 
>>> some functions with nox, right?
>>> 
>>> Thanks
>>> 
>>> 2011/9/12 Murphy McCauley <jam...@nau.edu>
>>> The quick answer about -v -v can be gotten with "./nox_core --help":
>>>   -v, --verbose           make console log verbose (shows INFO messages -- 
>>> use twice for DBG)
>>> 
>>> The longer answer is that -v -v puts it into "very verbose" mode.  NOX's 
>>> logging can actually be configured with quite a lot of flexibility through 
>>> several mechanisms, including at runtime... but the GUI doesn't currently 
>>> know anything about that.  In general, you probably DO want all levels of 
>>> log messages to be sent to the GUI so that you can then use the GUI's 
>>> filtering mechanism (which lets you filter them after the fact).  This 
>>> really should be the default for the GUI, and I have a local branch which 
>>> does this, so it's quite possible we'll see it in a future version of NOX.
>>> 
>>> About the Components section being empty... if I recall correctly (and it's 
>>> entirely possible that I don't), the Components section is populated by 
>>> watching the DBG messages about component loading when NOX starts up.  With 
>>> only one -v, they never get to the GUI.
>>> 
>>> -- Murphy
>>> 
>>> On Sep 12, 2011, at 7:34 PM, Lucas Henrique Mauricio wrote:
>>> 
>>>> I figured it out how to solve the missing library. You were right, it's 
>>>> libqt4-sql-sqlite.
>>>> 
>>>> About this -v -v, what's the point? hehe I'll try tomorrow but I don't 
>>>> understand what it's gonna change.. Could you explain, please?
>>>> 
>>>> One last thing, what do you think about the fact that components button 
>>>> doesn't show anything?
>>>> 
>>>> Thanks for your replies!
>>>> 
>>>> 2011/9/12 Murphy McCauley <jam...@nau.edu>
>>>> It looks like you're missing Qt's sqlite interface.  Try installing it.  
>>>> On Ubuntu I think this is in the libqt4-sql-sqlite package.
>>>> 
>>>> I think to get links to show up, you'll need to run discovery as well, and 
>>>> you should probably run nox_core with -v -v:
>>>> ./nox_core -v -v -i ptcp:2525 monitoring discovery pyswitch
>>>> 
>>>> Hope that helps.
>>>> 
>>>> -- Murphy
>>>> 
>>>> On Sep 12, 2011, at 12:58 PM, Lucas Henrique Mauricio wrote:
>>>> 
>>>> > Hello everybody,
>>>> >
>>>> > I have NOX running at my host pc and two openvswitch switches running on 
>>>> > two different VirtualBox virtual machines. I created a bridge between 
>>>> > the two VMs and set NOX as controller of this bridge.
>>>> >
>>>> > At my host, I run "./nox_core -v -i ptcp:2525 monitoring pyswitch" and 
>>>> > "./nox-gui". The NOX GUI shows the two VMs but don't link than, even 
>>>> > when I am pinging one another. When I look at the terminal, I see this:
>>>> > root@meier:~/nox/src# ./nox-gui.py
>>>> > QSqlDatabase: QSQLITE driver not loaded
>>>> > QSqlDatabase: available drivers: QMYSQL3 QMYSQL
>>>> > QSqlQuery::exec: database not open
>>>> > QSqlQuery::exec: database not open
>>>> >
>>>> > I think that maybe that's why NOX GUI doesn't show links between 
>>>> > switches and no debugging messages. If I click "component" button, it 
>>>> > shows a list without any components..
>>>> >
>>>> > What am I doing wrong?
>>>> >
>>>> > Best regards
>>>> >
>>>> > -
>>>> > Lucas Henrique Mauricio
>>>> >
>>>> > Universidade Federal do Rio de Janeiro
>>>> > Escola Politécnica
>>>> > Engenharia Eletrônica e de Computação
>>>> > _______________________________________________
>>>> > nox-dev mailing list
>>>> > nox-dev@noxrepo.org
>>>> > http://noxrepo.org/mailman/listinfo/nox-dev
>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Lucas Henrique Mauricio
>>>> 
>>>> Universidade Federal do Rio de Janeiro
>>>> Escola Politécnica
>>>> Engenharia Eletrônica e de Computação
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Lucas Henrique Mauricio
>>> 
>>> Universidade Federal do Rio de Janeiro
>>> Escola Politécnica
>>> Engenharia Eletrônica e de Computação
>> 
>> 
>> _______________________________________________
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev
>> 
>> 
> 
> 
> 
> 
> -- 
> Lucas Henrique Mauricio
> 
> Universidade Federal do Rio de Janeiro
> Escola Politécnica
> Engenharia Eletrônica e de Computação
> 
> 
> 
> 
> -- 
> Lucas Henrique Mauricio
> 
> Universidade Federal do Rio de Janeiro
> Escola Politécnica
> Engenharia Eletrônica e de Computação

_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev

Reply via email to