Hello Justin, About the API I was asking about... Any chance of any of you implementing it or should I? I would love to add it... Would you mind pointing me to a code snippet I should focus on to do this... I would appreciate it...
Thanks, Ashok p.s.: Given certain fields (parameters, e.g. a five tuple) the API would return a flow_id (cookie). This would be implemented in the openvswitch datapath. If you have some time, please do point me to code that I should focus on. Appreciate it. On Tue, Dec 23, 2014 at 6:53 PM, Ashok Chippa <[email protected]> wrote: > Thank you Justin. Appreciate the pointer. > > On Tue, Dec 23, 2014 at 5:58 PM, Justin Pettit <[email protected]> wrote: > >> On Dec 23, 2014, at 5:39 PM, Ashok Chippa <[email protected]> wrote: >> > >> > Hello, >> > >> > I used the set-controller command after installing 4 or 5 flows. After >> the command, the flows simply disappeared!!! Please see below: >> > >> > root@ashok-vb:~# ovs-ofctl dump-flows br-int >> > NXST_FLOW reply (xid=0x4): >> > cookie=0x0, duration=113926.488s, table=0, n_packets=45, n_bytes=4410, >> idle_age=30519, hard_age=16, priority=9,icmp,nw_src=1.1.1.1,nw_dst=1.1.1.2 >> actions=CONTROLLER:65535 >> > cookie=0x0, duration=113916.183s, table=0, n_packets=30, n_bytes=2940, >> idle_age=30632, hard_age=16, priority=9,icmp,nw_src=1.1.1.2,nw_dst=1.1.1.1 >> actions=CONTROLLER:65535 >> > cookie=0x0, duration=114127.663s, table=0, n_packets=102, >> n_bytes=5236, idle_age=30524, hard_age=16, priority=0 >> actions=CONTROLLER:65535 >> > cookie=0x0, duration=115138.613s, table=1, n_packets=0, n_bytes=0, >> idle_age=65534, hard_age=65534, priority=0 actions=NORMAL >> > root@ashok-vb:~# ovs-vsctl set-controller br-int tcp:127.0.0.1:6789 >> > root@ashok-vb:~# ovs-ofctl dump-flows br-int >> > NXST_FLOW reply (xid=0x4): >> > root@ashok-vb:~# ovs-ofctl set-controller 127.0.0.1:6789 >> > ovs-ofctl: unknown command 'set-controller'; use --help for help >> > root@ashok-vb:~# ovs-vsctl set-controller 127.0.0.1:6789 >> > ovs-vsctl: no bridge named 127.0.0.1:6789 >> > root@ashok-vb:~# ovs-vsctl set-controller br-int 127.0.0.1:6789 >> > 2014-12-24T00:39:06Z|00002|vsctl|WARN|target type "127.0.0.1:6789" is >> possibly erroneous >> > root@ashok-vb:~# ovs-ofctl dump-flows br-int >> > NXST_FLOW reply (xid=0x4): >> > cookie=0x0, duration=18.688s, table=0, n_packets=0, n_bytes=0, >> idle_age=18, priority=0 actions=NORMAL >> > >> > From the above output, one can see that I did not deliberately delete >> any flows... >> >> This is expected behavior and documented in the ovs-vswitchd.conf.db man >> page: >> >> controller: set of Controllers >> OpenFlow controller set. If unset, then no OpenFlow >> controllers >> will be used. >> >> If there are primary controllers, removing all of them >> clears >> the flow table. If there are no primary controllers, >> adding one >> also clears the flow table. Other changes to the set of >> con‐ >> trollers, such as adding or removing a service >> controller, >> adding another primary controller to supplement an existing >> pri‐ >> mary controller, or removing only one of two primary >> con‐ >> trollers, have no effect on the flow table. >> >> --Justin >> >> >> >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
