Re: [ovs-discuss] Vswitch not connecting to controller

2015-01-19 Thread Prasanna Yabaluri
: {sec_since_connect="12", state=ACTIVE} target : "tcp:192.168.0.106:6653" On Mon, Jan 19, 2015 at 12:08 PM, Ben Pfaff wrote: > On Mon, Jan 19, 2015 at 10:49:54AM -0500, Prasanna Yabaluri wrote: > > Ping does respond from switch to controller ... > > >

[ovs-discuss] Vswitch not connecting to controller

2015-01-19 Thread Prasanna Yabaluri
Ping does respond from switch to controller ... root@user1-GT5464:/home/user1# ping 192.168.0.106 PING 192.168.0.106 (192.168.0.106) 56(84) bytes of data. 64 bytes from 192.168.0.106: icmp_seq=1 ttl=64 time=0.399 ms 64 bytes from 192.168.0.106: icmp_seq=2 ttl=64 time=0.390 ms root@user1-GT5464:/

[ovs-discuss] OpenvSwitch install 2.3.0 not working...

2015-01-17 Thread Prasanna Yabaluri
Not sure if install went fine After the install switch does not connect to controller. user1@user1-GT5464: sudo ovs-vsctl add-port br2 eth1 ovs-vsctl: Error detected while setting up 'eth1'. See ovs-vswitchd log for details. user1@user1-GT5464:/var/log$ sudo ovs-vsctl show 9080842e-e7f6-4ab

[ovs-discuss] Modify NW_DST is not working

2014-08-13 Thread Prasanna Yabaluri
Idea is to send any destination to a specific host. user1@devtest11:~$ sudo ovs-ofctl dump-flows mybridge3-rb NXST_FLOW reply (xid=0x4): cookie=0xa0ded2ab21, duration=1978.744s, table=0, n_packets=602, n_bytes=44688, idle_age=3, priority=32767,in_port=3 actions=mod_nw_dst:10.0.0.13,mod_dl_dst

Re: [ovs-discuss] Hosts can ping each other after removing flows....

2014-08-12 Thread Prasanna Yabaluri
: > On Mon, Aug 11, 2014 at 3:56 PM, Prasanna Yabaluri > wrote: > > Thanks! > > > > Thinking this command will do a clean state of vswitch and remove any > > configs by controller.I tried sudo ovs-vsctl emer-reset ..did not > work. > ovs-vsctl

Re: [ovs-discuss] Hosts can ping each other after removing flows....

2014-08-11 Thread Prasanna Yabaluri
, Gurucharan Shetty wrote: > On Mon, Aug 11, 2014 at 3:39 PM, Prasanna Yabaluri > wrote: > > Thank you for the response! the hosts are still pinging > > > > user1@devtest11:~$ sudo ovs-dpctl del-flows > > user1@devtest11:~$ > > user1@devtest11:~$ > >>>

Re: [ovs-discuss] Hosts can ping each other after removing flows....

2014-08-11 Thread Prasanna Yabaluri
Interface "eth2" Port "eth0" Interface "eth0" Port "eth3" Interface "eth3" ovs_version: "2.0.1" On Mon, Aug 11, 2014 at 11:10 AM, Gurucharan Shetty wrote: > On Sun, Aug 10, 2014 at

[ovs-discuss] L3 routing for OpenvSwitch

2014-08-11 Thread Prasanna Yabaluri
How to get routing enabled between the ports of openvswitch? Basically hosts connected to ports need to move around. Without using controller: Is this the way to go http://blog.scottlowe.org/2012/10/31/layer-3-routing-with-open-vswitch/ With controller: ?? ___

[ovs-discuss] Hosts can ping each other after removing flows....

2014-08-10 Thread Prasanna Yabaluri
Help needed for troubleshooting. I have vSwitch in fail_mode secure. Using floodlight controller.The two hosts can ping each other even after flows have been deleted ... 1. curl -X Delete flow name 2. sudo ovs-dpctl del-flows user1@devtest11:~$ sudo ovs-vsctl show 14593c41-8295-43a7-b63f-74eb93