Hello Alexis, Thank you very much for the suggestion. Unfortunately we are using Lithium release since in the Beryllium's OpenFlow plugin, there is a "role request" sent after the "feature request". Our switches do not support the "role request" option and hence, the connection to controller terminates.
Do you know if there is a way to skip the "role request" step in the Boron release? In any case I will check whether we can use the Boron release... Thanks! Michael. On Fri, Oct 21, 2016 at 11:45 AM, Alexis de Talhouët < [email protected]> wrote: > Hello, > > Using Boron, what you're trying to use is deprecated, hence you should use > the following: > > 1. Install `odl-openflowplugin-flow-services` > 2. Connect your switch > 3. Send the following request: > > > POST /restconf/operations/opendaylight-direct- > statistics:get-node-connector-statistics > Host: localhost:8181 > Content-Type: application/json > Authorization: Basic YWRtaW46YWRtaW4= > > { > "input": > { > "node" : "/opendaylight-inventory:nodes/opendaylight-inventory: > node[opendaylight-inventory:id=\"openflow:187811733353539\"]" , > "store-stats" : false > } > } > > 4. Set store-stats to `true` if you want to keep them in the datastore. > > > You can also get the stats only for a specified port, but while trying, it > appears not to be working well > Add this to the above payload: > > "node-connector-id" : "/opendaylight-inventory: > nodes/opendaylight-inventory:node[opendaylight-inventory: > id=\"openflow:187811733353539\"]/opendaylight-inventory: > node-connector[opendaylight-inventory:id='openflow: > 187811733353539:LOCAL']", > > Instead of `LOCAL`, specify the port you want. > > Hope this helps, > Alexis > > > > On Sep 20, 2016, at 12:00 PM, Michael Borokhovich <[email protected]> > wrote: > > Thanks Luis. Could you please suggest a relevant forum/mailing list? The > issue is specific to the OpenDaylight and not just OpenFlow. The OpenFlow > part works as expected but the ODL operational datastore is not updated as > I would expect... > > > On Tue, Sep 20, 2016 at 11:39 AM, Luis Gomez <[email protected]> wrote: > >> Forwarding question to OpenFlow people. >> >> On Sep 19, 2016, at 2:19 PM, Michael Borokhovich <[email protected]> >> wrote: >> >> Hi, >> >> I'm trying to get statistics using the following RPC call and not via the >> default statistics-manager. >> >> POST /restconf/operations/opendaylight-flow-statistics:get-all- >> flows-statistics-from-all-flow-tables { "input": { "node" : >> "/opendaylight-inventory:nodes/opendaylight-inventory:node[ >> opendaylight-inventory:id=\"openflow:1000\"]" } } >> >> However, the response of this request is just "transaction-id". While I >> can see the OpenFlow "Flow Stat Request" and "Flow Stat Reply" messages are >> exchanged between the controller and the switch, the operational datastore >> seems not to be updated as a result of calling the above RPC. I check the >> operational datastore using: GET /restconf/operational/opendayl >> ight-inventory:nodes/node/openflow:1000/table/0 >> >> My question is - how can I get the flow statistics sent to the controller >> by the switch as a result of the above RPC >> (get-all-flows-statistics-from-all-flow-tables)? >> And why is the operational datastore is not updated? >> >> Thanks! >> >> Michael. >> _______________________________________________ >> opendaylight-users mailing list >> [email protected] >> https://lists.opendaylight.org/mailman/listinfo/opendaylight-users >> >> >> > _______________________________________________ > openflowplugin-dev mailing list > [email protected] > https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev > > >
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
