Ask is moving to Stack Overflow and! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode


Netconf Protocol Plugin - What to do if device doesn't support IETF NETCONF Monitoring

asked 2014-06-02 23:18:00 -0700

updated 2014-06-03 11:06:13 -0700



I have been working on a netconf device which doesn't support ietf netconf monitoring. I gathered that in this case since there are no yang files to be downloaded from the device, I need to write my own yang files and put them under /cache/schema folder.

I tried it and figured out that yang files are not being read from this location and raised this Bug-628.

Now my question is that is there any progress on above bug and really what to do if the device doesn't support netconf monitoring. It seems lots of folks have been trying their hands on ODL's netconf protocol plugin and this is one of biggest pain point with respect to this plugin.

There is another Bug-560 which is development blocking if someone wants to invoke RPCs on the device.

Would be glad to know if there exists any workaround.


edit retag flag offensive close merge delete


I ran into a similar issue and I did see .yang files get picked up from the cache/schema directory, so it is possible the rework pushed a day or two ago resolved this. Can you try again?

Devin Avery ( 2014-06-04 10:34:05 -0700 )edit

Hi Devin, Thanks for the update, latest I have is the controller code from 15th May. When did you try? And in that case, would it be a good idea to close Bug-628? -Kanika

kanika28 ( 2014-06-04 20:12:37 -0700 )edit

I believe the netconf refactoring code went into master only two/three days ago ( I was debugging yesterday). So I would give the new code a try and then close 628 if it works for you.

Devin Avery ( 2014-06-05 03:36:06 -0700 )edit

Sure thanks - I will take the latest code, check and update here :)

kanika28 ( 2014-06-05 04:06:00 -0700 )edit

1 answer

Sort by ยป oldest newest most voted

answered 2014-06-11 07:34:50 -0700

Maros gravatar image

Hi Kanika,

Looking at the 628 bug, what you need is something like "remote device capability overriding". You have placed the schemas in the cache/schema folder, but they do not get loaded and parsed as part of remote device schema context, because the device does not advertize them as capabilities in hello message. You just hardcoded these capabilities in the sal-netconf-connector. Is that correct ?

If so, the refactoring commit will not help with this. Also no work has been done to implement this enhancement so far. We just do not have the resources to implement or even plan for it in the near future. However, the 628 is in the open and anyone could pick it up and implement "remote device capability overriding" or perhaps some better solution to devices not supporting netconf monitoring.

The workaroud is probably only the hardcoded capabilities + schemas placed in cache/schema folder.


edit flag offensive delete publish link more


Thanks Maros for your inputs. So this essentially means for devices that do not support netconf monitoring yet, we should start writing our own southbound plugins rather than hardcoding the capabilities. Also, unless bug 560 is fixed, even after hardcoding, we cannot move forward.

kanika28 ( 2014-06-12 03:50:00 -0700 )edit
Login/Signup to Answer

Question Tools

1 follower


Asked: 2014-06-02 23:18:00 -0700

Seen: 1,013 times

Last updated: Jun 11 '14