On Aug 26, 2012, at 6:51 PM, Tatyana Yatskevich wrote: > I don't see any down events and I never had a completely correct run. I > attached a snapshot of passing control messages during the ping (destination > MAC address was already discovered). We can see that the controller installs > flow entries to first 4 switches and then to the rest 3. There are some > "Poisoning message" from authenticator module which I don't understand.
I actually don't remember if the down events will get printed on the console by default; it may make sense to write a small component that just prints link and switch down messages. My reason for asking is that I have long suspected that there may be an issue where you don't get optimal paths after links go down, but have never looked into it really deeply (and at this point, I probably never will). > I tried POX controller and it looks like it works correctly so far. But I see > a million of LLDP messages dropped.They don't seem to effect the network's > working but they are disturbing cause they make a passing messages analysis > more difficult. Are you also running the spanning_tree component? If not, you probably should. :) You also might get somewhat better results with the version in the github.com/MurphyMc/pox fork, which is where my pre-upstream work is being collected. -- Murphy
