Adding the right list, If controller did not push the flows to the switch, the easiest is to use RPC calls to remove the flows, see an example of RPC below:
POST http://192.168.0.101:8181/restconf/operations/sal-flow:remove-flow <http://192.168.0.101:8181/restconf/operations/sal-flow:remove-flow> <?xml version="1.0" encoding="UTF-8" standalone="no"?> <input xmlns="urn:opendaylight:flow:service"> <node xmlns:inv="urn:opendaylight:inventory">/inv:nodes/inv:node[inv:id="openflow:1"]</node> <table_id>0</table_id> <priority>2</priority> <strict>true</strict> <match> <ethernet-match> <ethernet-type> <type>2048</type> </ethernet-type> </ethernet-match> <ipv4-destination>10.0.1.0/24</ipv4-destination> </match> </input> > On Feb 10, 2017, at 12:11 PM, Simo <[email protected]> wrote: > > Hello, > I am trying to clear the tables of a Openflow switch after it connects to ODL > controlle, but when I try to delete a flow from the CONFIGURATION datastore I > must specify a key and FlowID of a existing entry. The Flow entry that I am > using to clear the table does not exist in the datastrore, it is just a > Mach_all entry with strict=false to select all flows in the table and drop > them. Is there a way to send such flow to the Openflow switch ? > > Regards > > -- > > Simo > > _______________________________________________ > controller-dev mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/controller-dev
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
