As explained in this draft on IETF NETCONF Monitoring , a NETCONF data model (YANG) can be used to monitor the NETCONF protocol. The monitoring data model includes information about NETCONF datastores, sessions, locks and statistics. This data facilitates the management of a NETCONF server (a NETCONF server is a device that supports NETCONF operations).
A NETCONF client can discover the data models supported by a NETCONF server and <get-schema> operation can be used to retrieve these data models.
To verify that a NETCONF Server (device) supports NETCONF Monitoring, check the hello message received from the server. The device should advertise IETF netconf monitoring capability as below:
When NETCONF Monitoring is supported by the device, YANG files are downloaded from the device using <get-schema> operation to retrieve device information.
OpenDaylight & NETCONF Protocol Plug-in
With respect to OpenDaylight’s NETCONF Protocol Plug-in, it seems to work fine when the device supports IETF NETCONF Monitoring. For the cases, where device doesn’t support NETCONF Monitoring, we need to write our own YANG files representing the device and place these files in a special folder
FilesystemSchemaCachingProvider.java is responsible for reading the YANG files placed in \cache\schema directory.
However, there is an existing bug due to which yang files are not read from \cache\schema directory.
Bug-628: Loading YANG files from local directory when netconf server does not support netconf monitoring
Subscribe to this question on ask.opendaylight.org to get latest updates: