I would also suggest to get the wireshark trace as well.

On Mon, Apr 10, 2017 at 3:31 PM, Luis Gomez <[email protected]> wrote:

> Hi Yann, can you paste here the REST request (URL, method, body) you are
> pushing to config DS. Normally what you put in config DS should first go to
> switch and then be reported in oper DS after flow stats are collected by
> controller.
>
> BR/Luis
>
>
> > On Apr 10, 2017, at 1:50 PM, yann bourdeau <[email protected]>
> wrote:
> >
> > Hi!
> >
> >       I’m still having issues with my FlowMod with experimenters action
> that does go in configuration data store, but it never goes to the
> operational data store and the switch. I have looked at the code how it
> works in RestConf (module NetConf). I went through to code until
> BrokerFacade.java in sal-rest-connector. The flow got added to the config
> data store. I have assumed that some kind of RPC should be called when this
> store is modified.  I have put traces in functions registerListeners and
> invokeRPC. They are never called. I was not able to find documentation on
> how the relationship between the config data store and the operational
> store work. Can someone enlighten me? Putting the flow via the RPC
> (add:flow) call in REST works without an issue(it pushes to the switch my
> flow with experimenter action). Any help or documentation will be greatly
> appreciated.
> >
> > Thanks,
> >
> > Yann Bourdeau, M.Ing.
> > Senior Software Developer
> > 438-499-4607
> > [email protected]
> >
> >
> >
> > _______________________________________________
> > 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
>



-- 
Thanks
Anil
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to