Re: [nox-dev] Problem when trying to run nox

[Nicholas Bastin]

On Sat, Oct 16, 2010 at 21:42, James "Murphy" McCauley wrote:

> I got the configure output off-list, and as expected, Python is disabled
> (and therefore discovery).  In this case, it's because Twisted isn't
> available, which I have seen cause confusion before.  When configuring with
> Python *not disabled*, we should probably make that actually stop configure
> rather than just print a warning, as the warning is a pretty subtle way of
> indicating that basically nothing is going to work.
>

Possibly we should update that wiki page - on some debian-based
distributions "apt-get install python" will install python-dev, and on some
it won't.

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

[nox-dev] Should NOX requires Python (Re: Problem when trying to run nox)

[kk yap]

Hi,

On a tangential note, I am wondering if NOX should require Python.  I
can run a network perfectly fine with NOX using only C/C++, if not for
discovery.  Of course, discovery can re-coded in C/C++ and I would be
all set.  Wonder if anyone will feel passionately about this.

Regards
KK

On 16 October 2010 21:42, James "Murphy" McCauley  wrote:
> I got the configure output off-list, and as expected, Python is disabled
> (and therefore discovery).  In this case, it's because Twisted isn't
> available, which I have seen cause confusion before.  When configuring with
> Python *not disabled*, we should probably make that actually stop configure
> rather than just print a warning, as the warning is a pretty subtle way of
> indicating that basically nothing is going to work.
> -- Murphy
> On Oct 16, 2010, at 9:15 PM, Nicholas Bastin wrote:
>
> On Sat, Oct 16, 2010 at 21:03, Nicholas Bastin  wrote:
>>
>> On Sat, Oct 16, 2010 at 18:25, Yu Yang, Calvin  wrote:
>>>
>>> I followed exactly the instruction on the
>>> web: http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup
>>
>> I suspect the problem is that those instructions tell you to just invoke
>> './boot.sh', which only gives you the core and does not include discovery.
>>  Rebuild using ./boost.sh --apps-net and you should be fine.
>
> I take that back - the default *should* be to build everything (core,
> netapps, webapps) if you pass no arguments (at least in Zaku).  Probably
> best to paste your ./boot.sh and configure output here and see if we can
> figure out what happened.  What platform is this on?
>
> --
> Nick
> ___
> 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] Problem when trying to run nox

[James "Murphy" McCauley]

I got the configure output off-list, and as expected, Python is disabled (and 
therefore discovery).  In this case, it's because Twisted isn't available, 
which I have seen cause confusion before.  When configuring with Python *not 
disabled*, we should probably make that actually stop configure rather than 
just print a warning, as the warning is a pretty subtle way of indicating that 
basically nothing is going to work.

-- Murphy

On Oct 16, 2010, at 9:15 PM, Nicholas Bastin wrote:

> On Sat, Oct 16, 2010 at 21:03, Nicholas Bastin  wrote:
> On Sat, Oct 16, 2010 at 18:25, Yu Yang, Calvin  wrote:
> I followed exactly the instruction on the web: 
> http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup
> 
> I suspect the problem is that those instructions tell you to just invoke 
> './boot.sh', which only gives you the core and does not include discovery.  
> Rebuild using ./boost.sh --apps-net and you should be fine.
> 
> I take that back - the default *should* be to build everything (core, 
> netapps, webapps) if you pass no arguments (at least in Zaku).  Probably best 
> to paste your ./boot.sh and configure output here and see if we can figure 
> out what happened.  What platform is this on?
> 
> --
> Nick
> ___
> 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 when trying to run nox

[Nicholas Bastin]

On Sat, Oct 16, 2010 at 21:03, Nicholas Bastin  wrote:

> On Sat, Oct 16, 2010 at 18:25, Yu Yang, Calvin  wrote:
>
>> I followed exactly the instruction on the web:
>> http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup
>>
>
> I suspect the problem is that those instructions tell you to just invoke
> './boot.sh', which only gives you the core and does not include discovery.
>  Rebuild using ./boost.sh --apps-net and you should be fine.
>

I take that back - the default *should* be to build everything (core,
netapps, webapps) if you pass no arguments (at least in Zaku).  Probably
best to paste your ./boot.sh and configure output here and see if we can
figure out what happened.  What platform is this on?

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

Re: [nox-dev] Problem when trying to run nox

[Nicholas Bastin]

On Sat, Oct 16, 2010 at 18:25, Yu Yang, Calvin  wrote:

> I followed exactly the instruction on the web:
> http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup
>

I suspect the problem is that those instructions tell you to just invoke
'./boot.sh', which only gives you the core and does not include discovery.
 Rebuild using ./boost.sh --apps-net and you should be fine.

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

Re: [nox-dev] Problem when trying to run nox

[James McCauley]

Can you post the output from configure and/or make?
On Oct 16, 2010 6:26 PM, "Yu Yang, Calvin"  wrote:
> Hi,
>
> I was following the instruction for implementing the openflow network, and
> when I came to the step "setting up the controller", problem came when I
try
> to run it.
> I did the "make" step and it ran well. But then something weird happened:
>
> debian:/nox/build/src# ./nox_core -i ptcp:6633 routing
> Nox 0.9.0(zaku)~full~beta (nox_core), compiled Oct 6 2010 22:57:47
> Compiled with OpenFlow 0x01
> 1|nox|ERR:Application 'discovery' description not found.
>
> Can anyone help me out?
> The new version of Nox should be compatible with OpenFlow v1.0 right?
>
> I followed exactly the instruction on the web:
>
http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup
> --
> Regards,
> Calvin
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

[nox-dev] Problem when trying to run nox

[Yu Yang, Calvin]

Hi,

I was following the instruction for implementing the openflow network, and
when I came to the step "setting up the controller", problem came when I try
to run it.
I did the "make" step and it ran well. But then something weird happened:

debian:/nox/build/src# ./nox_core -i ptcp:6633 routing
Nox 0.9.0(zaku)~full~beta (nox_core), compiled Oct 6 2010 22:57:47
Compiled with OpenFlow 0x01
1|nox|ERR:Application 'discovery' description not found.

Can anyone help me out?
The new version of Nox should be compatible with OpenFlow v1.0 right?

I followed exactly the instruction on the web:
http://www.openflowswitch.org/foswiki/bin/view/OpenFlow/Deployment/HOWTO/LabSetup#4_Controller_Setup
-- 
Regards,
Calvin
___
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Re: [nox-dev] Dpids disconnecting

[Rob Sherwood]

FYI, this problem was tracked down to a config problem, not a flowvisor or
nox bug ;-)

- Rob
.


On Sat, Oct 16, 2010 at 1:51 AM, Niky Riga  wrote:

> Hi KK,
>
> Attached are nox's log files.
> * pathlet.out : the log file when I run the pathlet controller on the slice
> * pyswitch.out : the log file when I run the pyswitch module on the same
> slice
>
> Thanks,
> Niky
>
>
> kk yap wrote:
>
>> Can someone send the pcap file on the list, so that people can
>> actually start doing real investigation here?  If it is too big, send
>> to Nick Bastin? (Sorry, Nick...)
>>
>> I would still like to see the NOX's output.
>>
>> Regards
>> KK
>>
>> On 15 October 2010 21:36, Rob Sherwood  wrote:
>>
>>
>>> Sorry... the "..." meant more packet_in's.
>>>
>>> - Rob
>>> .
>>>
>>>
>>> On Fri, Oct 15, 2010 at 9:15 PM, kk yap  wrote:
>>>
>>>
 < ERROR (vendor unsupported)
 < PACKET_IN (lldp)
 
 and then disconnect

 Can I know the model of the switch, and what ... means?  The front
 part looks correct at a glance.  I am wondering why there is a LLDP
 without any packet out though.

 Regards
 KK

 PS>> Way to solve this:
 email
 more email
 
 solved

 :)

 On 15 October 2010 21:10, Rob Sherwood 
 wrote:


> KK: I've looked through the tcpdumps and the sequence is:
>
>
>> HELLO
>>
>>
> < HELLO
>
>
>> FEATURE_REQUEST
>>
>>
> < FEATURE_REPLY
>
>
>> VENDOR MSG
>>
>>
> < ERROR (vendor unsupported)
> < PACKET_IN (lldp)
> 
> and then disconnect
> - Rob
> .
>
>
> On Fri, Oct 15, 2010 at 9:07 PM, kk yap  wrote:
>
>
>> What about having a tcpdump of the control traffic between NOX to/from
>> FV, and FV to/from switch?  Each disconnection will have a new
>> connection following it, then you will see the hellos, feature
>> requests and replies, etc.
>>
>> I would like to see the NOX's log too.  NOX typically does not kill a
>> connection silently.
>>
>> Just my knee-jerk reaction on how to debug this.
>>
>> Regards
>> KK
>>
>> On 15 October 2010 20:23, Niky Riga  wrote:
>>
>>
>>> Hi,
>>>
>>> We have installed the latest FlowVisor 0.6 beta5, but we still see
>>> the
>>> dpids
>>> flapping.
>>> Rob believes that it's nox that initiates the disconnection so I
>>> would
>>> like
>>> to try and debug this.
>>> Is there a way to increase the debug level beyond debug?:-) Where
>>> should
>>> I
>>> start looking
>>> in the code to see why nox decides to tear down a connection?
>>>
>>> Thanks,
>>> Niky
>>>
>>> ___
>>> 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] Problems about installing NOX 0.6.0

[Rob Sherwood]

[pre-cursor to moving this conversation offlist]

If you are interested in helping, we're on #gec9demos on EFNET (an IRC
server)

- Rob
.


On Sat, Oct 16, 2010 at 9:21 AM, Nicholas Bastin wrote:

> On Fri, Oct 15, 2010 at 18:35, kk yap  wrote:
>
>> 
>> Actually in this case, Chui-Hui will not be able to anything if we
>> have went the tarball way.  We are essentially not very customized to
>> CentOS.  Tarballs are also particularly hard to update.
>> 
>>
>
> There doesn't have to be any difference between a source tarball and a git
> clone, other than the fact that we at least all know what is in the tarball
> - the unchanging nature of the tarball is what is appealing here, not a
> downside.  I would prefer that source tarballs at least didn't require
> autoconf, but even that wouldn't be the end of the world in this case.
>
> I'm looking into getting it to build on CentOS 5.5, but unfortunately the
> only way to get the DVD image is via torrent so my setup time is a bit
> longer than I'd planned.
>
> ..insert obligatory gripe here about asking why distributions can't
> just make iso's available on amazon s3 and pass the download cost on to me
> in exchange for a download that actually works...
>
> --
> Nick
>
> ___
> 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] Problems about installing NOX 0.6.0

[Nicholas Bastin]

On Fri, Oct 15, 2010 at 18:35, kk yap  wrote:

> 
> Actually in this case, Chui-Hui will not be able to anything if we
> have went the tarball way.  We are essentially not very customized to
> CentOS.  Tarballs are also particularly hard to update.
> 
>

There doesn't have to be any difference between a source tarball and a git
clone, other than the fact that we at least all know what is in the tarball
- the unchanging nature of the tarball is what is appealing here, not a
downside.  I would prefer that source tarballs at least didn't require
autoconf, but even that wouldn't be the end of the world in this case.

I'm looking into getting it to build on CentOS 5.5, but unfortunately the
only way to get the DVD image is via torrent so my setup time is a bit
longer than I'd planned.

..insert obligatory gripe here about asking why distributions can't
just make iso's available on amazon s3 and pass the download cost on to me
in exchange for a download that actually works...

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

Re: [nox-dev] TCP packets are not parsed correctly

[Niky Riga]

Updated and it seems to work just fine.

Thanks!
Niky

James "Murphy" McCauley wrote:
Fixed (hopefully!) in the main branch. 


-- Murphy

On Oct 16, 2010, at 1:27 AM, Niky Riga wrote:

  

Thanks, should I switch to the destiny branch, or this is fixed at the head of 
the tree?

--niky

James "Murphy" McCauley wrote:


Hopefully it's fixed in the repository now.

-- Murphy

On Oct 15, 2010, at 8:27 PM, Niky Riga wrote:

 
  

Hi,

Given that this bug is blocking one of the Gec9 plenary demos, I would like to 
start debugging it.
Do you have an idea where should I start looking? In which file do you believe 
the problem is?

Thanks,
niky

Niky Riga wrote:
   


I am running nox zaku as released on the September 15th, should I update?

--niky

James McCauley wrote:
 
  

didn't look at the original problem, but the rolled back patch does look wrong 
to me. I think it's almost right now, but the last part should be arr[i + 2]

On Oct 15, 2010 12:58 AM, "Kyriakos Zarifis" mailto:kyr.zari...@gmail.com>> wrote:
   


___
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] Port stats reply never make it to the controller

[Niky Riga]

Hi,

I am running FV 0.6 beta 5 and nox zaku

I am running a monitoring module that periodically pokes the switches 
for stats, but the port stats reply (almost) never make it back to the 
controller.

Replies for other type of stats (table, aggregate stats) are received.

I receive port stats only from one switch (dpid 0012e2b8f3d0) which is 
at Stanford, and those are empty.

I am guessing that this is a FlowVisor problem but I am not sure.

My configuration includes all kinds of scenarios :

switch ->FV (0.6beta5)->FV (0.6beta5)->controller
switch ->FV (0.6beta4)->FV (0.6beta5)->controller
switch ->FV (0.6beta5)->controller

Attached are nox log files.
* bbn-monitor.out (ouput of bbn's monitoring module)
* monitor.out (ouput of standard nox monitoring module)

Let me know if you need more info.

Niky



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

Re: [nox-dev] TCP packets are not parsed correctly

[James "Murphy" McCauley]

Fixed (hopefully!) in the main branch. 

-- Murphy

On Oct 16, 2010, at 1:27 AM, Niky Riga wrote:

> Thanks, should I switch to the destiny branch, or this is fixed at the head 
> of the tree?
> 
> --niky
> 
> James "Murphy" McCauley wrote:
>> Hopefully it's fixed in the repository now.
>> 
>> -- Murphy
>> 
>> On Oct 15, 2010, at 8:27 PM, Niky Riga wrote:
>> 
>>  
>>> Hi,
>>> 
>>> Given that this bug is blocking one of the Gec9 plenary demos, I would like 
>>> to start debugging it.
>>> Do you have an idea where should I start looking? In which file do you 
>>> believe the problem is?
>>> 
>>> Thanks,
>>> niky
>>> 
>>> Niky Riga wrote:
>>>
 I am running nox zaku as released on the September 15th, should I update?
 
 --niky
 
 James McCauley wrote:
  
> didn't look at the original problem, but the rolled back patch does look 
> wrong to me. I think it's almost right now, but the last part should be 
> arr[i + 2]
> 
> On Oct 15, 2010 12:58 AM, "Kyriakos Zarifis"  > wrote:
>
 ___
 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] TCP packets are not parsed correctly

[Niky Riga]

Thanks, should I switch to the destiny branch, or this is fixed at the 
head of the tree?


--niky

James "Murphy" McCauley wrote:

Hopefully it's fixed in the repository now.

-- Murphy

On Oct 15, 2010, at 8:27 PM, Niky Riga wrote:

  

Hi,

Given that this bug is blocking one of the Gec9 plenary demos, I would like to 
start debugging it.
Do you have an idea where should I start looking? In which file do you believe 
the problem is?

Thanks,
niky

Niky Riga wrote:


I am running nox zaku as released on the September 15th, should I update?

--niky

James McCauley wrote:
  

didn't look at the original problem, but the rolled back patch does look wrong 
to me. I think it's almost right now, but the last part should be arr[i + 2]

On Oct 15, 2010 12:58 AM, "Kyriakos Zarifis" mailto:kyr.zari...@gmail.com>> wrote:


___
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