Re: [nox-dev] OpenFlow 0x98

2009-12-18 Thread kk yap 
Hi,

Would you need some features in OpenFlow v0.9 from the NetFPGA?  If
yes, switch to the openflow-0.9 branch for wire-compatibility.  Be
warned that this branch is very much in alpha-status.

Regards
KK

2009/12/18  :
> I am trying to use the NetFPGA OpenFlow module with NOX, and unfortunately I 
> can only get this working on 0x98, which is why I'm trying to get NOX 
> speaking 0x98...
>
> On Fri 18/12/09 03:40, "kk yap" yap...@gmail.com wrote:
>> Hi,
>>
>> This is probably because --with-openflow is somewhat hard to maintain.
>> We are doing away with it for further versions.
>>
>> If you do not need any specific feature in 0x98, I would recommend
>> going with 0x97 in
>> * openflowswitch.org/openflow (release/0.8.9)
>> * noxrepo.org/nox (do not use --with-openflow option in configure)
>>
>> If you need some particular feature beyond v0.8.9, let us know.  We
>> can figure something out then.
>>
>> Hope this is helpful.
>>
>> Regards
>> KK
>>
>>
>> 2009/12/17  > citonion.com>:
>> Sorry for double-message KK: replied rather than
>> replied all, using an email client I've never used before!
>>
>> > I'm using NOX straight from git://noxrepo.org/nox - `git log` shows the 
>> > last
>> commit as:
>>
>> > da...@bruckner
>> :~/nox$ git log
>> commit
>> 24800254eac4a8c25de091f6fc8562ad4fdb1cce
>> Author: Martin Casado > ra.com>
>> Date:   Fri Mar 6 22:10:01 2009 -0800
>> >
>> >    Bugfix submitted by Ye Deng
>> >
>> > I've tried against OpenFlow 0.8.9r2 from this tar:
>> http://openflowswitch.org/downloads/openflow-0.8.9~2.tar.gz as well as 
>> 0.9.0r1 from this tar:
>> http://openflowswitch.org/downloads/openflow-0.9.0-rev1.tar.gz and OpenFlow
>> (1.0) straight from git://openflowswitch.org/openflow with last
>> commit:
>>
>> > da...@bruckner
>> :~/openflow$ git log
>> commit
>> 951f4ca9f573afda40c7c9b17c2e8cc2f801ae7a
>> Author: Justin Pettit > cira.com>
>> Date:   Mon Dec 7 23:45:02 2009 -0800
>> >
>> >    Add new OpenFlow error messages for 1.0
>> release.
>>
>> > The quoted compile error is against the git openflow
>> release, though I get similar ones against openflow 0.9.0, referring to
>> expire events not existing.
>>
>> > Compiling against 0.9.8 I get told:
>> >
>> > ../../../src/lib/openflow.cc: In member function
>> ‘int vigil::Openflow_connection::send_add_snat(uint16_t, uint32_t,
>> uint32_t, uint16_t, uint16_t, uint16_t, uint16_t, vigil::ethernetaddr,
>> uint16_t)’:
>> ../../../src/lib/openflow.cc:612: error: ‘struct
>> nx_snat_config’ has no member named ‘mac_addr’
>>
>> > I am always compiling using:
>> >
>> > make clean && ../configure --with-python=yes
>> --with-openflow=/home/daw63/openflow && make
>>
>> > with /home/daw63/openflow being a symlink to the
>> relevant release I'm trying to use.
>>
>> > Thanks for getting back to me,
>> >
>> > Daniel
>> >
>> > On Thu 17/12/09 23:30 , kk yap  wrote::
>> >
>> > Hi Daniel,
>> >
>> > Are you compiling NOX for OpenFlow v0.9?
>>  Basically, I would like to
>> know where and how you got the OpenFlow source. That
>> will help in
>> resolving your question.
>> >
>> > Regards
>> > KK
>> >
>> > 2009/12/17  ...@illi
>> citonion.com>:
>>> Hi,
>> >>
>> >> I'm trying to get a version of NOX which is
>> compatible with OpenFlow 0x98.  Compiling the version from 
>> git://noxrepo.org/nox or git://noxrepo.org/noxcore both give me compile
>> errors about undefined classes when setting --with-openflow to any of
>> 0.8.9r2, 0.9.0 or the openflow git.  Can anyone point me at somewhere I
>> can get a newer version of NOX?
>>>
>> >> The specific compiler errors I'm getting
>> (against openflow from git) are:
>>>
>> >> In file included from
>> ../../../src/lib/openflow-event.cc:43:
>>> ../../../src/include/flow-expired.hh: At global
>> scope:
>>> ../../../src/include/flow-expired.hh:43: error:
>> ISO C++ forbids declaration of ‘ofp_flow_expired’ with no
>> type
>>> ../../../src/include/flow-expired.hh:43: error:
>> expected ‘,’ or ‘...’ before ‘*’ token
>>> ../../../src/include/flow-expired.hh:58: error:
>> ISO C++ forbids declaration of ‘ofp_flow_expired’ with no
>> type
>>> ../../../src/include/flow-expired.hh:58: error:
>> expected ‘;’ before ‘*’ token
>>> ../../../src/include/flow-expired.hh:62: error:
>> expected ‘;’ before ‘static’
>>> ../../../src/include/flow-expired.hh: In member
>> function ‘virtual const ofp_match* vigil::Flow_expired_event::get_flow()
>> const’:
>>> ../../../src/include/flow-expired.hh:55: error:
>> ‘get_flow_expired’ was not declared in this scope
>>> ../../../src/include/flow-expired.hh: At global
>> scope:
>>> ../../../src/include/flow-expired.hh:69: error:
>> ISO C++ forbids declaration of ‘ofp_flow_expired’ with no
>> type
>>> ../../../src/include/flow-expired.hh:69: error:
>> expected ‘,’ or ‘...’ before ‘*’ token
>>> ../../../src/include/flow-expired.hh: In
>> constructor
>> ‘vigil::Flow_expired_event::Flow_expired_event(vigil::datapathid,
>> int)’:
>>> ../../../src/include/flow-expired.hh:71: error:
>> ‘ofe’ was not declared in thi

[nox-dev] make check errors

2009-12-18 Thread Ashish Agarwal 
I got NOX 0.6 compiled and then ran some of the tests mentioned in the
documentation. Some fail and some succeed so I'm wondering if my
installation worked or not. The tests I ran are:

./nox_core -h  -- this works fine
make check -- fails as shown below
./nox_core tests -- fails with errors shown below
./nox_core -v -i pgen:10 packetdump -- seems to have run fine if I'm
correctly understanding the output shown below

Thank you.

$ make check

g++ -DHAVE_CONFIG_H -I. -I../../../src/tests -I../..
 -DPKGDATADIR=\"/usr/local/share/nox\" -DPKGLIBDIR=\"/usr/local/bin/tests\"
-DPKGLOCALSTATEDIR=\"/usr/local/var/nox\"
-DPKGSYSCONFDIR=\"/usr/local/etc/nox\" -include ../../config.h -I
../../../src/include -I../../../src/include/openflow -I/usr/include
-I/usr/include/xercesc -I/usr/include -D_GNU_SOURCE=1   -D_REENTRANT
-D__STDC_LIMIT_MACROS=1 -D__STDC_FORMAT_MACROS=1 -D__STDC_CONSTANT_MACROS=1
-D_GLIBCXX_CONCEPT_CHECKS=1 -D_GLIBCXX_DEBUG=1 -D_GLIBCXX_DEBUG_PEDANTIC=1
-I   -fno-omit-frame-pointer -Wall -Wno-sign-compare -Winit-self
-Wformat-nonliteral -Wformat-security -g -O2 -MT test-coop-preblock-hook.o
-MD -MP -MF .deps/test-coop-preblock-hook.Tpo -c -o
test-coop-preblock-hook.o ../../../src/tests/test-coop-preblock-hook.cc
../../../src/tests/test-coop-preblock-hook.cc: In function ‘void
thread1_hook()’:
../../../src/tests/test-coop-preblock-hook.cc:32: error: ‘printf’ was not
declared in this scope
../../../src/tests/test-coop-preblock-hook.cc: In function ‘void thread1()’:
../../../src/tests/test-coop-preblock-hook.cc:40: error: ‘printf’ was not
declared in this scope
../../../src/tests/test-coop-preblock-hook.cc: In function ‘void thread2()’:
../../../src/tests/test-coop-preblock-hook.cc:52: error: ‘printf’ was not
declared in this scope
make[5]: *** [test-coop-preblock-hook.o] Error 1
make[5]: Leaving directory `/home/ashish/local/nox/build/src/tests'
make[4]: *** [check-am] Error 2
make[4]: Leaving directory `/home/ashish/local/nox/build/src/tests'
make[3]: *** [check] Error 2
make[3]: Leaving directory `/home/ashish/local/nox/build/src/tests'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory `/home/ashish/local/nox/build/src'
make[1]: *** [check] Error 2
make[1]: Leaving directory `/home/ashish/local/nox/build/src'
make: *** [check-recursive] Error 1

$ ./nox_core tests
NOX 0.8.0~full~beta (nox_core), compiled Dec 18 2009 18:34:14
Compiled with OpenFlow 0x97 (exp)
1|nox|ERR:Application 'pytstorage' description not found.

$ ./nox_core -v -i pgen:10 packetdump
1|nox|INFO:Starting nox_core
(/home/ashish/local/nox/build/src/.libs/lt-nox_core)
2|pyrt|DBG:Loading a component description file
'nox/coreapps/testharness/meta.xml'.
3|pyrt|DBG:Loading a component description file
'nox/coreapps/hub/meta.xml'.
4|pyrt|DBG:Loading a component description file
'nox/coreapps/pyrt/meta.xml'.
5|pyrt|DBG:Loading a component description file
'nox/coreapps/examples/meta.xml'.
6|pyrt|DBG:Loading a component description file
'nox/coreapps/examples/t/meta.xml'.
7|pyrt|DBG:Loading a component description file
'nox/coreapps/coretests/meta.xml'.
8|pyrt|DBG:Loading a component description file
'nox/coreapps/simple_c_py_app/meta.xml'.
9|pyrt|DBG:Loading a component description file
'nox/coreapps/simple_c_app/meta.xml'.
00010|pyrt|DBG:Loading a component description file
'nox/coreapps/switch/meta.xml'.
00011|pyrt|DBG:Loading a component description file
'nox/netapps/flow_fetcher/meta.xml'.
00012|pyrt|DBG:Loading a component description file
'nox/netapps/user_event_log/meta.xml'.
00013|pyrt|DBG:Loading a component description file
'nox/netapps/authenticator/meta.xml'.
00014|pyrt|DBG:Loading a component description file
'nox/netapps/switchstats/meta.xml'.
00015|pyrt|DBG:Loading a component description file
'nox/netapps/storage/meta.xml'.
00016|pyrt|DBG:Loading a component description file
'nox/netapps/storage/t/meta.xml'.
00017|pyrt|DBG:Loading a component description file
'nox/netapps/routing/meta.xml'.
00018|pyrt|DBG:Loading a component description file
'nox/netapps/topology/meta.xml'.
00019|pyrt|DBG:Loading a component description file
'nox/netapps/bindings_storage/meta.xml'.
00020|pyrt|DBG:Loading a component description file
'nox/netapps/bindings_storage/t/meta.xml'.
00021|pyrt|DBG:Loading a component description file
'nox/netapps/data/meta.xml'.
00022|pyrt|DBG:Loading a component description file
'nox/netapps/switch_management/meta.xml'.
00023|pyrt|DBG:Loading a component description file
'nox/netapps/tests/meta.xml'.
00024|pyrt|DBG:Loading a component description file
'nox/netapps/discovery/meta.xml'.
00025|pyrt|DBG:Loading a component description file
'nox/webapps/webservice/meta.xml'.
00026|pyrt|DBG:Loading a component description file
'nox/webapps/webserver/meta.xml'.
00027|pyrt|DBG:Loading a component description file
'nox/webapps/miscws/meta.xml'.
00028|pycomponent|DBG:Importing Python module
nox.coreapps.examples.packetdump
00029|nox|DBG:Application installation repo

Re: [nox-dev] problem downloading nox

2009-12-18 Thread Martin Casado 
Doh! Yes, thats a type-o. My fault, and thanks for pointing that out.  
I'll update it.




It's just a typo in the command. It should say git "clone".

On Fri, Dec 18, 2009 at 4:25 PM, Ashish Agarwal > wrote:


$ git pull git://noxrepo.org/nox 
fatal: Not a git repository (or any of the parent directories): .git

Is this path correct? This is what is given on the website. Thanks.




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



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

Re: [nox-dev] A general question regarding discovery module

2009-12-18 Thread Martin Casado 

Yeah, it could be due to high-loss from load (unfortunately).

You could try increasing the timeout value in discovery.py.  If you 
don't have dynamic link events, this should be able to survive temporary 
timeouts.


What switches are you using?


In my program the discovery module times out links sometimes, causing
my program not working well. I will debug to find out details why the
link fails. Actually they are not supposed to fail. Maybe it's because
of huge data.

On Fri, Dec 18, 2009 at 8:41 AM, Martin Casado  wrote:
  

The goal is to detect link failures, so one would hope that would be the
most common failure mode.



I assume LLDP packets are sent periodically. If there is no LLDP, what
will be the most possible reason? The controller or the switch is too
busy?

On Thu, Dec 17, 2009 at 3:07 PM, Martin Casado  wrote:

  

Discovery times out links when no LLDP packets have been received over
some
timeout period.  Timer values are documented within discovery.py.




It seems this module will periodically construct the topology. I dont
know why it will periodically time_out the links. I want to know in
what situations the links will time_out.
Thanks.

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


  





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

Re: [nox-dev] problem downloading nox

2009-12-18 Thread Ashish Agarwal 
It's just a typo in the command. It should say git "clone".

On Fri, Dec 18, 2009 at 4:25 PM, Ashish Agarwal wrote:

> $ git pull git://noxrepo.org/nox
> fatal: Not a git repository (or any of the parent directories): .git
>
> Is this path correct? This is what is given on the website. Thanks.
>
>
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

[nox-dev] problem downloading nox

2009-12-18 Thread Ashish Agarwal 
$ git pull git://noxrepo.org/nox
fatal: Not a git repository (or any of the parent directories): .git

Is this path correct? This is what is given on the website. Thanks.
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Re: [nox-dev] A general question regarding discovery module

2009-12-18 Thread kk yap 
Hi Guanyao,

If by huge data, you mean you are jamming the links with data, then
yes that could be the issue.  The LLDP packet can be dropped and cause
intermittent link timeout.

Regards
KK

2009/12/18 Guanyao Huang :
> In my program the discovery module times out links sometimes, causing
> my program not working well. I will debug to find out details why the
> link fails. Actually they are not supposed to fail. Maybe it's because
> of huge data.
>
> On Fri, Dec 18, 2009 at 8:41 AM, Martin Casado  wrote:
>> The goal is to detect link failures, so one would hope that would be the
>> most common failure mode.
>>
>>> I assume LLDP packets are sent periodically. If there is no LLDP, what
>>> will be the most possible reason? The controller or the switch is too
>>> busy?
>>>
>>> On Thu, Dec 17, 2009 at 3:07 PM, Martin Casado  wrote:
>>>

 Discovery times out links when no LLDP packets have been received over
 some
 timeout period.  Timer values are documented within discovery.py.


>
> It seems this module will periodically construct the topology. I dont
> know why it will periodically time_out the links. I want to know in
> what situations the links will time_out.
> Thanks.
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>
>


>>
>>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>

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

Re: [nox-dev] A general question regarding discovery module

2009-12-18 Thread Guanyao Huang 
In my program the discovery module times out links sometimes, causing
my program not working well. I will debug to find out details why the
link fails. Actually they are not supposed to fail. Maybe it's because
of huge data.

On Fri, Dec 18, 2009 at 8:41 AM, Martin Casado  wrote:
> The goal is to detect link failures, so one would hope that would be the
> most common failure mode.
>
>> I assume LLDP packets are sent periodically. If there is no LLDP, what
>> will be the most possible reason? The controller or the switch is too
>> busy?
>>
>> On Thu, Dec 17, 2009 at 3:07 PM, Martin Casado  wrote:
>>
>>>
>>> Discovery times out links when no LLDP packets have been received over
>>> some
>>> timeout period.  Timer values are documented within discovery.py.
>>>
>>>

 It seems this module will periodically construct the topology. I dont
 know why it will periodically time_out the links. I want to know in
 what situations the links will time_out.
 Thanks.

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


>>>
>>>
>
>

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

Re: [nox-dev] A general question regarding discovery module

2009-12-18 Thread Martin Casado 
The goal is to detect link failures, so one would hope that would be the 
most common failure mode.



I assume LLDP packets are sent periodically. If there is no LLDP, what
will be the most possible reason? The controller or the switch is too
busy?

On Thu, Dec 17, 2009 at 3:07 PM, Martin Casado  wrote:
  

Discovery times out links when no LLDP packets have been received over some
timeout period.  Timer values are documented within discovery.py.



It seems this module will periodically construct the topology. I dont
know why it will periodically time_out the links. I want to know in
what situations the links will time_out.
Thanks.

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

  




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

Re: [nox-dev] OpenFlow 0x98

2009-12-18 Thread nox 
I am trying to use the NetFPGA OpenFlow module with NOX, and unfortunately I 
can only get this working on 0x98, which is why I'm trying to get NOX speaking 
0x98...

On Fri 18/12/09 03:40, "kk yap" yap...@gmail.com wrote:
> Hi,
> 
> This is probably because --with-openflow is somewhat hard to maintain.
> We are doing away with it for further versions.
> 
> If you do not need any specific feature in 0x98, I would recommend
> going with 0x97 in
> * openflowswitch.org/openflow (release/0.8.9)
> * noxrepo.org/nox (do not use --with-openflow option in configure)
> 
> If you need some particular feature beyond v0.8.9, let us know.  We
> can figure something out then.
> 
> Hope this is helpful.
> 
> Regards
> KK
> 
> 
> 2009/12/17   citonion.com>:
> Sorry for double-message KK: replied rather than
> replied all, using an email client I've never used before!
>
> > I'm using NOX straight from git://noxrepo.org/nox - `git log` shows the last
> commit as:
>
> > da...@bruckner
> :~/nox$ git log
> commit
> 24800254eac4a8c25de091f6fc8562ad4fdb1cce
> Author: Martin Casado  ra.com>
> Date:   Fri Mar 6 22:10:01 2009 -0800
> >
> >    Bugfix submitted by Ye Deng
> >
> > I've tried against OpenFlow 0.8.9r2 from this tar:
> http://openflowswitch.org/downloads/openflow-0.8.9~2.tar.gz as well as 
> 0.9.0r1 from this tar:
> http://openflowswitch.org/downloads/openflow-0.9.0-rev1.tar.gz and OpenFlow
> (1.0) straight from git://openflowswitch.org/openflow with last
> commit:
>
> > da...@bruckner
> :~/openflow$ git log
> commit
> 951f4ca9f573afda40c7c9b17c2e8cc2f801ae7a
> Author: Justin Pettit  cira.com>
> Date:   Mon Dec 7 23:45:02 2009 -0800
> >
> >    Add new OpenFlow error messages for 1.0
> release.
>
> > The quoted compile error is against the git openflow
> release, though I get similar ones against openflow 0.9.0, referring to
> expire events not existing.
>
> > Compiling against 0.9.8 I get told:
> >
> > ../../../src/lib/openflow.cc: In member function
> ‘int vigil::Openflow_connection::send_add_snat(uint16_t, uint32_t,
> uint32_t, uint16_t, uint16_t, uint16_t, uint16_t, vigil::ethernetaddr,
> uint16_t)’:
> ../../../src/lib/openflow.cc:612: error: ‘struct
> nx_snat_config’ has no member named ‘mac_addr’
>
> > I am always compiling using:
> >
> > make clean && ../configure --with-python=yes
> --with-openflow=/home/daw63/openflow && make
>
> > with /home/daw63/openflow being a symlink to the
> relevant release I'm trying to use.
>
> > Thanks for getting back to me,
> >
> > Daniel
> >
> > On Thu 17/12/09 23:30 , kk yap  wrote::
> >
> > Hi Daniel,
> >
> > Are you compiling NOX for OpenFlow v0.9?
>  Basically, I would like to
> know where and how you got the OpenFlow source. That
> will help in
> resolving your question.
> >
> > Regards
> > KK
> >
> > 2009/12/17  ...@illi
> citonion.com>:
>> Hi,
> >>
> >> I'm trying to get a version of NOX which is
> compatible with OpenFlow 0x98.  Compiling the version from 
> git://noxrepo.org/nox or git://noxrepo.org/noxcore both give me compile
> errors about undefined classes when setting --with-openflow to any of
> 0.8.9r2, 0.9.0 or the openflow git.  Can anyone point me at somewhere I
> can get a newer version of NOX?
>>
> >> The specific compiler errors I'm getting
> (against openflow from git) are:
>>
> >> In file included from
> ../../../src/lib/openflow-event.cc:43:
>> ../../../src/include/flow-expired.hh: At global
> scope:
>> ../../../src/include/flow-expired.hh:43: error:
> ISO C++ forbids declaration of ‘ofp_flow_expired’ with no
> type
>> ../../../src/include/flow-expired.hh:43: error:
> expected ‘,’ or ‘...’ before ‘*’ token
>> ../../../src/include/flow-expired.hh:58: error:
> ISO C++ forbids declaration of ‘ofp_flow_expired’ with no
> type
>> ../../../src/include/flow-expired.hh:58: error:
> expected ‘;’ before ‘*’ token
>> ../../../src/include/flow-expired.hh:62: error:
> expected ‘;’ before ‘static’
>> ../../../src/include/flow-expired.hh: In member
> function ‘virtual const ofp_match* vigil::Flow_expired_event::get_flow()
> const’:
>> ../../../src/include/flow-expired.hh:55: error:
> ‘get_flow_expired’ was not declared in this scope
>> ../../../src/include/flow-expired.hh: At global
> scope:
>> ../../../src/include/flow-expired.hh:69: error:
> ISO C++ forbids declaration of ‘ofp_flow_expired’ with no
> type
>> ../../../src/include/flow-expired.hh:69: error:
> expected ‘,’ or ‘...’ before ‘*’ token
>> ../../../src/include/flow-expired.hh: In
> constructor
> ‘vigil::Flow_expired_event::Flow_expired_event(vigil::datapathid,
> int)’:
>> ../../../src/include/flow-expired.hh:71: error:
> ‘ofe’ was not declared in this scope
>> ../../../src/lib/openflow-event.cc: At global
> scope:
>> ../../../src/lib/openflow-event.cc:68: error:
> ISO C++ forbids declaration of ‘ofp_flow_expired’ with no
> type
>> ../../../src/lib/openflow-event.cc:68: error:
> expected ‘,’ or ‘...’ before ‘*’ token
>> ../../../src/lib/openflow-event.cc: In function
> ‘vigil::Event*::handle_flow_expired(vigil::da

Re: [nox-dev] A general question regarding discovery module

2009-12-18 Thread kk yap 
Hi Guanyao,

Does no LLDP means "no LLDP sent" or "no LLDP received"?  Take a look
at wireshark.

Regards
KK

2009/12/18 Guanyao Huang :
> I assume LLDP packets are sent periodically. If there is no LLDP, what
> will be the most possible reason? The controller or the switch is too
> busy?
>
> On Thu, Dec 17, 2009 at 3:07 PM, Martin Casado  wrote:
>> Discovery times out links when no LLDP packets have been received over some
>> timeout period.  Timer values are documented within discovery.py.
>>
>>> It seems this module will periodically construct the topology. I dont
>>> know why it will periodically time_out the links. I want to know in
>>> what situations the links will time_out.
>>> Thanks.
>>>
>>> ___
>>> nox-dev mailing list
>>> nox-dev@noxrepo.org
>>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>>
>>
>>
>
> ___
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>

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

Re: [nox-dev] A general question regarding discovery module

2009-12-18 Thread Guanyao Huang 
I assume LLDP packets are sent periodically. If there is no LLDP, what
will be the most possible reason? The controller or the switch is too
busy?

On Thu, Dec 17, 2009 at 3:07 PM, Martin Casado  wrote:
> Discovery times out links when no LLDP packets have been received over some
> timeout period.  Timer values are documented within discovery.py.
>
>> It seems this module will periodically construct the topology. I dont
>> know why it will periodically time_out the links. I want to know in
>> what situations the links will time_out.
>> Thanks.
>>
>> ___
>> nox-dev mailing list
>> nox-dev@noxrepo.org
>> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>>
>
>

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