I would suggest running nox 0.6 (master) and open vswitch (http://vswitch.org).

Both have 1.0 branches however they're not yet stable so I'd suggested sticking with master.

Hi Martin,

I just want a stable version of nox and switch - can you suggest which version I should use

nox version 0.6 - should get from git clone git://noxrepo.org/nox - ? is that correct?

If I choose this nox version - which version of the switch working well with this nox?

Thank you,

thuymai



------------------------------------------------------------------------
*From:* Martin Casado <[email protected]>
*To:* Chonduy Nguyen <[email protected]>
*Cc:* [email protected]; [email protected]
*Sent:* Tue, January 26, 2010 5:54:51 PM
*Subject:* Re: [nox-dev] nox version

For 1.0 support, you need to pull from the nox 1.0 branch (git branch -a).

The version number is slowly creeping towards 1.0. Sorry about the confusion there ..

>
> Hi Martin,
>
> I just upgrade openflow to 1.0.0 but since the switch can't connect to nox > I check nox version - which I did download from website last week (on the link said version 0.6) > However, when I run nox_core command below - it showed me the nox_core version 0.8.0 ( which seems openflow old version)
>
> > ./nox_core --version
> NOX 0.8.0~full~beta (nox_core), compiled Jan 21 2010 12:46:53
> Compiled with OpenFlow 0x97 (exp)
>
>
> Is that mean the nox_core version that I get is really not 0.6 or the nox_core software didnot update version string correctly?
>
> Thanks
>
> Thuymai
>
>
>
> ------------------------------------------------------------------------
> *From:* Martin Casado <[email protected] <mailto:[email protected]>>
> *To:* Chonduy Nguyen <[email protected] <mailto:[email protected]>>
> *Cc:* [email protected] <mailto:[email protected]>; [email protected] <mailto:[email protected]>
> *Sent:* Tue, January 26, 2010 3:34:37 PM
> *Subject:* Re: [nox-dev] directoryws not on version 0.6
>
> Alternatively, you can listen for host_bind_event which is thrown for each new host detected. It contains the dpid, port, and addresses associated with each detected host.
>
> > Hi Martin,
> >
> > I saw the method get_authed_addresses(*args) require hostid - where I expect the module discovered link connection > > between host and switch as we don't know what hostid or switch outthere. > > is there anyway I can get the list of hosts in authenticator without knowning or passing any info?
> >
> > Thanks
> >
> > ThuymaiNguyen
> >
> > ------------------------------------------------------------------------ > > *From:* Martin Casado <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> > > *To:* Chonduy Nguyen <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> > > *Cc:* [email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>; [email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>
> > *Sent:* Tue, January 26, 2010 1:33:08 PM
> > *Subject:* Re: [nox-dev] directoryws not on version 0.6
> >
> > It requires traffic in order to reconstruct host-level information.
> >
> > > Hi Martin,
> > >
> > > Thanks for your info, So, I can just run nox_core component pyauthenticator so this component will discover nodes which are connecting to the switch > > > "Without any traffic generated from that host to switch " ? or I need to run traffic ( example: having host1 ping host2)
> > >
> > > Thanks
> > >
> > > Thuymai
> > >
> > >
> > >
> > >
> > >
> > > ------------------------------------------------------------------------ > > > *From:* Martin Casado <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>>> > > > *To:* Chonduy Nguyen <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>>> > > > *Cc:* [email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>>
> > > *Sent:* Tue, January 26, 2010 12:47:57 PM
> > > *Subject:* Re: [nox-dev] directoryws not on version 0.6
> > >
> > > There are no webservices which directly expose authenticator. To do that, you're going to have to resolve PyAuth() and then call the accessor methods directly (e.g. get_authed_addresses(..) ).
> > >
> > > As an example of how to create a webservice, see src/nox/webapps/miscws/cpustats.py
> > >
> > > >
> > > > Hi Martin
> > > >
> > > > I upgraded nox to be 0.6 - but observed that the directorymanagerws.py and its directory folder is not > > > > available on this version - This one is the one using authenticator
> > > >
> > > > Do you have any idea?
> > > >
> > > > I would like to see full topology of switch connects to host - etc...
> > > >
> > > > Can you please give any more details advice ?
> > > >
> > > > Thank you,
> > > >
> > > > TNguyen
> > > >
> > > >
> > > > ------------------------------------------------------------------------ > > > > *From:* Martin Casado <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>>>> > > > > *To:* Chonduy Nguyen <[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>>>> > > > > *Cc:* [email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>>>
> > > > *Sent:* Mon, January 25, 2010 10:45:11 PM
> > > > *Subject:* Re: [nox-dev] nox core discovery
> > > >
> > > > Discovery only shows links between switches, not between switches and hosts. For that, you'll have to explore authenticator.
> > > >
> > > > > Hi
> > > > >
> > > > > I am new with this module -
> > > > > I have switch setup and connected with flowvisor - and nox_core ran with discoveryws and discovery module.
> > > > > The switch also connected to 2 other physical machines
> > > > >
> > > > > However, when I ran webservice to look at the discovery object - I saw it only show
> > > > >
> > > > > Ethernet packet of the switch - where the dst value is the value on the file ethernet.py (NDP_MULTICAST)
> > > > >
> > > > > I am wondering what can I do to get nox discovery to show a topology connection between switch and the other 2 client machines?
> > > > >
> > > > > Below are the print out of the discovery object of LLDP packets
> > > > >
> > > > > PORT 0: EthernetPackageDESC: [5a:8c:29:22:d3:a9>01:23:20:00:00:01:LLDP]<chassis ID:5a:8c:29:22:d3:a9><port ID:00:00><ttl:120><tlv end> > > > > > PORT : 1 EthernetPackageDESC: [5a:8c:29:22:d3:a9>01:23:20:00:00:01:LLDP]<chassis ID:5a:8c:29:22:d3:a9><port ID:00:01><ttl:120><tlv end>
> > > > > ~                        > Thanks
> > > > >
> > > > > Nguyen > ------------------------------------------------------------------------
> > > > >
> > > > > _______________________________________________
> > > > > nox-dev mailing list
> > > > > [email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>> <mailto:[email protected] <mailto:[email protected]> <mailto:[email protected] <mailto:[email protected]>>>>>
> > > > > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
> > > > >
> > > >
> > >
> > >
> >
> >
>
>




_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to