NETCONF Clustering

Follow the steps below in order to configure NETCONF. Note that it doesn’t matter whether you are running on a single node or a cluster – the steps are the same. If you are running a cluster then simply enter these commands on ogene of the cluster nodes and that node will pass the information to the other nodes.

Netconf mount
Before we can add the NETCONF device we must configure a set of parameters (via the command line). Enter the following commands in a terminal, using the values that are relevant for your particular case.

Add device via mdsal’s netconf topology
Before you can add a device you must install one of the following OpenDaylight features:

odl-netconf-topology
odl-netconf-clustered-topology

Then run the following curl command from a terminal, replacing the variables e.g. ‘${NETCONF_NAME}’ with the values you configured in the previous step (Netconf mount)

Now that the device has been added, you can interrogate it using the RESTCONF service provided by MD-SAL (OpenDaylight’s Model-driven Service Abstraction Layer). A straightforward way to use the RESTCONF service is to use curl commands from the command line. Various commands can be used, for various purposes. We list these below. We also provide examples of these commands and the responses they generate. You can run these examples if you install the toaster feature in karaf. The idea of the toaster feature is to provide an example (based on a toaster and the functions it implements) to show you how to run various commands. To install the toaster feature, run OpenDaylight and then enter the following command on the karaf commandline:

Getting config data from device

To retrieve configuration data from the remote NETCONF device, use the following command in a terminal, replacing ${ODL_HOST} with the IP address of the machine on which you are running the FRINX OpenDaylight distribution.

Toaster example command:

Toaster example response:

Getting operational data from device (SROS does not support this. For SROS devices, see the end of this document)
Similar to the above command, but extracts operational rather than config data. Again, replace ${ODL_HOST} with the IP address of the machine on which you are running the FRINX OpenDaylight distribution.

Toaster example command:

Toaster example response:

Getting a list of netconf devices + their connection status
Replace ${ODL_HOST} with the IP address of the machine on which you are running the FRINX OpenDaylight distribution.

Deleting device
To delete the remote NETCONF device from OpenDaylight, enter the following command in a terminal, replacing ${ODL_HOST} with the IP address of the machine on which you are running the FRINX OpenDaylight distribution.

Vendor/device specific implementations

Using SROS 13
To configure netconf, use following restconf call. Note the first line below (which configures the IP of the machine hosting the FRINX OpenDaylight distribution) should be edited as required. Within the first line of the curl command, replace ${ODL_HOST} with the IP address of the machine on which the FRINX OpenDaylight distribution is running: :

The only difference between normal configuration and this is the customization factory and 2 added capabilities that are missing in hello message.

Using SROS 140R04
For this version, use netconf-customization-alu-ignore-candidate as customization factory. The purpose of the customization is to ensure that the response from the SROS device is in the required format.

To configure the mountpoint for SROS 14, enter the following command, replacing ${ODL_HOST} with the IP address of the machine on which the FRINX OpenDaylight distribution is running:

Feature Guide
Feature introduced in FRINX 1.4.1 NETCONF clustering module