I'm trying to understand discovery.py's use of lldp scanning. I'm
relatively new to python, but it looks like it only sends one lldp packet on
the network at a time (lines 315-350), but I can't figure out why this would
be. Since the lldp packets have no rule for forwarding, they should only
Because do you have only one controller and the controller have that send
and receive the LLDP packets for all (ports) OpenFlow switches. Do you can
to implement Python threads or multiple controller. But do you will have
many LLDP packets for treat at the some time. Was that?
Greetings,
Well, there are two things to consider:
1. If by scanning the network simultaneously you mean doing a
broadcast at every switch, then you will be a bit handicapped. That's
because when you do a broadcast, you have to send the same packet out
of every port and so your packet cannot carry the
Yes! Or you can change the parameters, to send more packets at less time:
LLDP_SEND_PERIOD = .10
TIMEOUT_CHECK_PERIOD = 5.
LINK_TIMEOUT = 10.
But, how said the Ali, you can overload the network/controller.
Hope that helps too.
Carlos Macapuna
www.macapuna.com.br
On Sun,
To be precise, what I want to do is iterate over all of the ports and send a
packet out of each of them, NOT broadcast - I understand that that wouldn't
work if I wanted to get specific port information. My reading of
discovery.py (which might not be right, again, I'm new to python) seems to
Ok, good, that's what I was hoping for. Thanks!
On Sun, Nov 14, 2010 at 5:44 PM, Martin Casado cas...@nicira.com wrote:
Would there be a problem with having multiple lldp packets on different
wires in the same network?
No, there would be no problem. The reason for the delay is to save
Hi,
Comment inline.
Regards
KK
On 14 November 2010 09:51, Rohit Manohar rdman...@ncsu.edu wrote:
Hi
Please ignore the previous mail.
We have decided to implement load distribution based on counters maintained
by a switch for a flow. When we install a flow in a switch, we will set some
Inline.
On Nov 14, 2010, at 2:55 PM, kk yap wrote:
Hi,
Comment inline.
Regards
KK
On 14 November 2010 09:51, Rohit Manohar rdman...@ncsu.edu wrote:
Hi
Please ignore the previous mail.
We have decided to implement load distribution based on counters maintained
by a switch for a
To close the thread the following worked for me for compiling NOX 0.4
(OpenFlow-1.0 wire-compatible version) on Ubuntu 10.04:
g++ version:
g++ (Ubuntu 4.4.3-4ubuntu5) 4.4.3
packages:
sudo apt-get install automake m4 libtool openssl libssl-dev libboost-dev
libboost-filesystem-dev libxerces-c2-dev
I have installed nox and want to use a virtual testing environment using
qemu. I have used Openflow1.0 to make the nox controller. When I try
./secchan nl:0 tcp:10.0.2.2:2525 I get an error 'Version Negotiation failed.
We support version 0x97 to 0x97 inclusive but peer supports no later than
10 matches
Mail list logo
