Does the controller's listening socket appear in the output of "netstat -l"?
On Fri, May 04, 2012 at 12:17:23AM -0500, Anisha Kolasani wrote: > Is there any way I could find out why the controller might be rejecting the > connection? I would appreciate if somebody could give a suggestion. > > Thank you, > Anisha. > > On Fri, May 4, 2012 at 12:05 AM, Justin Pettit <[email protected]> wrote: > > > It looks like your controller is refusing the connection, since your > > tcpdump output shows a reset [R] to the connection request. > > > > --Justin > > > > > > On May 3, 2012, at 5:39 PM, Anisha Kolasani <[email protected]> wrote: > > > > > > Some lines from the OVS log file are showing: > > > > *OVS log file:* > > > > May 03 16:40:45|231992|rconn|DBG|br0<->tcp:127.0.0.1:6633: entering > > BACKOFF > > May 03 16:40:53|232147|rconn|WARN|br0<->tcp:127.0.0.1:6633: connection > > failed (Connection refused) > > > > May 03 18:46:41|00109|rconn|INFO|br0<->tcp:127.0.0.1:6633: waiting 1 > > seconds before reconnect > > > > May 03 18:46:41|00110|rconn|DBG|br0<->tcp:127.0.0.1:6633: entering > > BACKOFF > > > > May 03 18:46:41|00111|connmgr|WARN|br0: unsupported controller > > "--out-of-band" > > > > > > When I saw the *tcpdump on lo*, there were requests passing with the > > controller: > > > > > > localhost.50703 > localhost.6633: Flags [S], cksum 0xfe30 (incorrect -> > > 0x302d), seq 266318493, win 32792, options [mss 16396,sackOK,TS val 4046000 > > ecr 0,nop,wscale 4], length 0 > > 17:35:04.516841 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP > > (6), length 40) > > localhost.6633 > localhost.50703: Flags [R.], cksum 0x0f58 (correct), > > seq 0, ack 266318494, win 0, length 0 > > 17:35:12.518817 IP (tos 0x0, ttl 64, id 53647, offset 0, flags [DF], proto > > TCP (6), length 60) > > > > > > > > How can the OVS be configured in --out-of-band control mode? Are there any > > documents I could refer too..? > > > > I tried using 'ovs-openflowd' to set controller to the swithch.. but there > > was not command like that. Any pointers regarding this? > > > > > > Thank you, > > > > Anisha. > > > > > > > > On Thu, May 3, 2012 at 4:51 PM, Ben Pfaff <[email protected]> wrote: > > > >> On Thu, May 03, 2012 at 04:44:56PM -0500, Anisha Kolasani wrote: > >> > My system settings are: > >> > > >> > *sudo ovs-vsctl show* > >> > 12681540-b7fe-4f22-8c25-8371ae195eb5 > >> > Bridge "br0" > >> > Controller "tcp:127.0.0.1:6633" > >> > fail_mode: standalone > >> > Port "eth0" > >> > Interface "eth0" > >> > Port "br0" > >> > Interface "br0" > >> > type: internal > >> > Port "tap0" > >> > Interface "tap0" > >> > Port "tap1" > >> > Interface "tap1" > >> > > >> > > >> > There are no flows that I can see.. > >> > *sudo ovs-ofctl dump-flows br0* > >> > NXST_FLOW reply (xid=0x4): > >> > > >> > > >> > I am running the controller at the port 6633 in the same machine...But, > >> the > >> > following two are the only two message I see when the controller starts: > >> > > >> > *sudo ./nox_core -v -i ptcp:6633 pyswitch* > >> > 00001|nox|INFO:Starting nox_core > >> > (/home/anisha/nox/build/src/.libs/lt-nox_core) > >> > 00002|nox|INFO:nox bootstrap complete > >> > > >> > I am not sure why the bridge br0 is not able to connect to the Nox > >> > controller. > >> > If anybody has tried this before, could you please let me know any > >> pointers > >> > to as to where its going wrong? > >> > >> You should probably configure OVS for out-of-band control. > >> > >> But what's in the OVS log? > >> > > > > _______________________________________________ > > discuss mailing list > > [email protected] > > http://openvswitch.org/mailman/listinfo/discuss > > > > _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
