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

Revision history [back]

click to hide/show revision 1
initial version

Connecting to legacy devices via NETCONF connector

Hello,

I'm new to the controller so I'm sorry in advance for any silly questions :)

I have managed to mount Cisco 1841 router to the connector using Lithium release, but I am not able to do so using the Boron release. I think I know where the problem is, but I have almost no clue how to solve it, here it goes: I have pushed the config to the controller successfully, so it tries to mount my router, but there is an error while exchanging capabilities:

java.lang.IllegalArgumentException: Device PAULIUS_RT has advertised neither :writable-running nor :candidate capability. At least one of these should be advertised. Failed to establish a session. at com.google.common.base.Preconditions.checkArgument(Preconditions.java:145)[65:com.google.guava:18.0.0]

I know that this is a false alarm and a very silly one - my router advertises capability: <capability>urn:ietf:params:netconf:capability:writeable-running:1.0</capability>, the difference being ":writable-running" on the controller versus ":writeable-running" on the router.

How could I change the code for the connector to understand ":writeable-running" instead of ":writable-running"? Or maybe it is possible to install an earlier release of org.opendaylight.netconf.sal-netconf-connector to the current Boron ODL release? The current release has this version of the connector: org.opendaylight.netconf.sal-netconf-connector - 1.4.1.Boron-SR1, the version that works the way I want it to work is this: 244 - org.opendaylight.controller.sal-netconf-connector - 1.2.0.Lithium.

Do you have any ideas? Thanks in advance, Paulius