I think "set-controller" is all you need. I've been using POX with OVS 1.9. Check if NOX closes the connection for whatever reason. Does wireshark give a clue on who ended the TCP session?
On Fri, Apr 19, 2013 at 2:29 PM, alan04 <[email protected]> wrote: > Hello everyone, > > I am a newbie to NOX and OpenFlow. I have some problems in setting the * > NOX*(*0.9.2 core-beta*) controller using* Open VSwitch (OVS) 1.9.90*. > Hope some one could give me some help or suggestions. > > Generally, my problem is in controller setting part on switch. When I set > the NOX controller to OVS, OVS seems not working under OpenFlow model: Two > PCs connect to the switch can still ping each other, but wireshark on > controller PC doesn't receive the ping message between the PCs. > > Here is the procedure and results: > Controller PC: 192.168.1.11 > Switch Eth1(eth0): 192.168.1.10 > PC1 linked ge-1/1/1 (192.168.1.200) > PC2 linked ge-1/1/4 (192.168.1.5) > *1. Set Controller IP/Port to OVS* > I use ovs-vsctl --db=tcp:192.168.1.10:*6633* set-controller br0 tcp: > 192.168.1.11:*6633* > then it is set: > root@XorPlus#ovs-vsctl --db=tcp:192.168.1.10:6633 show > d7c577c8-ba63-4b21-b987-**1f0f14be2eed > Bridge "br0" > Controller "tcp:192.168.1.11:6633" > Port "br0" > Interface "br0" > type: internal > Port "ge-1/1/1" > Interface "ge-1/1/1" > type: pronto > Port "ge-1/1/4" > Interface "ge-1/1/4" > type: pronto > *2.snoop seems not work:* > root@XorPlus#ovs-ofctl snoop br0 > ovs-ofctl: br0: failed to connect to socket (Connection reset by peer) > *3. On controller PC, I start the NOX with no application, it keeps > telling me the connection is set: * > root@Comp:~/nox/build/src# ./nox_core -i ptcp:*6633* > NOX 0.9.2~core~beta (nox_core), compiled Apr 17 2013 14:08:55 > 00001|connection_manager|WARN:**connected: 192.168.1.11:*6633*<-> > 192.168.1.**10 <http://192.168.1.10/>:*44103* > 00002|connection_manager|WARN:**connected: 192.168.1.11:6633<->192.168.1.* > *10:44104 <http://192.168.1.10:44104/> > 00003|connection_manager|WARN:**connected: 192.168.1.11:6633<->192.168.1.* > *10:44105 <http://192.168.1.10:44105/> > 00004|connection_manager|WARN:**connected: 192.168.1.11:6633<->192.168.1.* > *10:44107 <http://192.168.1.10:44107/> > 00005|connection_manager|WARN:**connected: 192.168.1.11:6633<->192.168.1.* > *10:44108 <http://192.168.1.10:44108/> > 00006|connection_manager|WARN:**connected: 192.168.1.11:6633<->192.168.1.* > *10:44109 <http://192.168.1.10:44109/> > 00007|connection_manager|WARN:**connected: 192.168.1.11:6633<->192.168.1.* > *10:44110 <http://192.168.1.10:44110/> > 00008|connection_manager|WARN:**connected: 192.168.1.11:6633<->192.168.1.* > *10:44111 <http://192.168.1.10:44111/> > .... > The wireshark can catch packets between them( packets between > 192.168.1.10 and 192.168.1.11) > > - But on switch, use root@XorPlus#ovs-vsctl --db=tcp:192.168.1.10:6633 > show, > > there's no "is connected: true" under "Controller "tcp:192.168.1.11:6633 > " " > > - And the port number(if it is) of switch(192.168.1.10) seems not fix > to 6633 > > > 4. I think for OVS once controller is connected, switch will change from > layer2 switch to OVS switch(disable flooding, begin OpenFlow function) > However, when I use PC1 (192.168.1.5) to ping PC2(192.168.1.200 ), they > can still ping each other, and the Wireshark on controller PC doesn't catch > packets from them. > > So I wonder if the controller is really connected with the switch? Besides > the "set-controller" command on OVS do I need to some other setting? > > Hope anyone with knowledge about this could give me some suggestions. > > Thanks, > Alan > > _______________________________________________ > discuss mailing list > [email protected] > http://openvswitch.org/mailman/listinfo/discuss > >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
