Hi Kyriakos, Thank you again for your answer but same problem. I am using this command for launch nox :
./nox_core -v -v -i ptcp:2525 monitoring pyswitch spanning_tree trackhost_pktin When I ping between between my two openflow switch, in my terminal on my controller I get that : http://hpics.li/bf6d59c And in my GUI I get that : http://hpics.li/3dabe49 In the red scare, normally I should get the information which are display in the terminal but in my case I see nothing but the lateral bar is going down , so the information are send to the GUI but not visible so certainly a bug. And in the blue square like you can see 0 flows. 2012/5/10 Kyriakos Zarifis <[email protected]> > Oh, and optionally, if you want to see hosts pop up on the GUI when they > appear in the network (when the send traffic), you also want to run the > component "trackhost_pktin". > > > On Thu, May 10, 2012 at 4:35 AM, Kyriakos Zarifis > <[email protected]>wrote: > >> Hi Julien, >> >> there is 2 command line arguments that you need to add in order to see >> more things on the GUI: >> >> First, make sure you run nox with the "-v -v" flags. This will make sure >> that the verbosity is set to maximum, and debugging messages will be sent >> to the GUI. >> If you do that you should see those messages showing up on the the left >> panel of the GUI. >> >> Now, if you want to see the flows, you also need to make sure that you >> run the "monitoring" component. This is the component that is responsible >> for gathering statistics from the switches. The GUI uses this to poll >> switch information using the interactive topology view. If you double-click >> on a switch, a new panel should appear on the left side, which will show >> you the switch's flow table. Similarly, by right clicking on the switch you >> can get a bunch of other stats about the switch. >> >> >> On Thu, May 10, 2012 at 2:33 AM, Julien Ratinaud >> <[email protected]>wrote: >> >>> Hi Kyriakos, >>> >>> Thank you very much for this clear answer, now I don't get the error. I >>> will have an other question. Now, when I ping between two host, I get the >>> information of this ping on my controller, I use the NOX GUI right now and >>> I have tried a lot of different controller. But all the time, I get almost >>> the same problem. I don't see any flow. I was thinking by pinging between >>> two host the informations would go to my controller and these informations >>> wil be display on the GUI. In my case, I just get the topology, not more. >>> >>> >>> 2012/5/9 Kyriakos Zarifis <[email protected]> >>> >>>> Hi Julien, >>>> >>>> you get this because your network has a loop, and pyswitch doesn't deal >>>> with loop (unless you run spanning_tree with it) >>>> pyswitch initially floods packets for which it doesn't know where the >>>> destination is, and keeps track of where it received packets from given >>>> source hosts. >>>> For example, in your plan1 topology, when client1 sends a packet to >>>> client2 or client3, OFswitch1 will register that client1 is on its port1, >>>> and will then flood the packet to the other 2 ports. >>>> Since there is a loop, however, those flooded packets will return back >>>> to those 2 "internal" ports (2 and 3), and that's when you get that >>>> message. >>>> >>>> >>>> On Wed, May 9, 2012 at 5:30 AM, Julien Ratinaud >>>> <[email protected]>wrote: >>>> >>>>> Hello everybody, >>>>> >>>>> I am student in Bachelor Computer Networks and Telecommunications and >>>>> the project I have to realized for the end of my year is to create an >>>>> Openflow network. I am currently using a NOX controller which is connected >>>>> to three openflow switch. My three Openflow switch are well connected to >>>>> my >>>>> controller. But, when I am launching a ping for example, I am getting this >>>>> error on my controller : >>>>> >>>>> *pyswitch|ERR:'**warning** learned port = inport'* >>>>> *pyswitch|ERR:'**warning** learned port = inport'* >>>>> * >>>>> * >>>>> *My topology** : **http://hpics.li/f8a9209 and http://hpics.li/ee64160 >>>>> * >>>>> * >>>>> * >>>>> Thank You ! >>>>> * >>>>> * >>>>> * >>>>> * >>>>> * >>>>> * >>>>> >>>>> * >>>>> * >>>>> * * >>>>> * >>>>> * >>>>> * >>>>> * >>>>> * >>>>> * >>>>> * >>>>> * >>>>> >>>> >>>> >>> >> >
