Ask Your Question
0

Flow not being put in Operational datastore

asked 2017-03-05 13:16:17 -0700

klaatz gravatar image

I have PUT a simple flow into the config datastore via POSTMAN (Chrome app). The operation returns a STATUS 200 OK.

When I run ovs-ofctl dump-flows h1 -O OpenFlow13 in mininet I can see the flow in the table, however the flow is not in the Operational datastore.

From my understanding, the flow is PUT into the MD-SAL's config data store and then ODL pushes it southbound to the switch (or so it should). Then when the flow is in the switch, it should be in the operational datastore since it reflects the runtime of the network..

Any help would be appreciated! If I have misunderstood something please do say :)

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted
0

answered 2017-03-10 07:22:59 -0700

penguin360 gravatar image

updated 2017-03-10 07:24:51 -0700

I have the same issue. However, then I do a GET request, I see the flow, but dump-flows does not show it, why? Can some help?

edit flag offensive delete publish link more

Comments

Are you sure you are doing GET on the operational datastore? When I PUT the flow I can GET it from the config datastore too but not the operational so I'd say check that you are getting the right one :)

klaatz ( 2017-03-11 10:04:48 -0700 )edit

If your issue is not resolved, which switch and it's version are you using, is the connection between switch and controller established, what are the features you have installed? can you attach the RESTresponse of GET call on config and operational DS. Hope u get solution in process.. :)

sunilkumarms ( 2017-03-24 07:04:31 -0700 )edit

I have been able to make a flow and it was added to the operational datastore now, I think I had previously specified a now existent port causing ODL the switch to reject the flow.

klaatz ( 2017-04-05 06:08:25 -0700 )edit
0

answered 2017-04-05 06:10:52 -0700

klaatz gravatar image

I have this working now.

The error was that the in port that I was specifying did not exist in the switch and therefore the flow was rejected. After changing 'openflow:1' to 'openflow:1:1', the flow was pushed to the switch and later to the operational datastore.

I would advise to be careful when creating flows as a typo like this can make you search for an error and solution for a long time!

edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

Follow
1 follower

Stats

Asked: 2017-03-05 13:16:17 -0700

Seen: 49 times

Last updated: Apr 05