Operating System: Linux
Platform: PC

Hi, I have fixed the NullPointer exception. But it looks like your device does not respond correctly to get request with filter netconf-state/schemas. So it looks like your device supports netconf monitoring, but does not expose any schemas.

Here is the commit to fix null pointer:
https://git.opendaylight.org/gerrit/#/c/10158/

But since your device does not support netconf monitoring, you would have to place your schemas into cache folder before ODL start.

Hi,

The null pointer exception is resolved with your patch

Have added the schema files in cache/schema folder but still getting one more exception as below:

2014-08-22 15:01:49.289 IST [remote-connector-processing-executor-2] WARN o.o.c.s.c.n.NetconfStateSchemas - RemoteDevice

: Initialization in sal failed, disconnecting from device
java.lang.IllegalStateException: RemoteDevice

: Session terminated Session closed

I see, can you show me the hello message produced by your device ?

Hi Maros,

The hello message produced by the device is as follows:

<hello xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<capabilities>
<capability>urn:ietf:params:netconf:base:1.0</capability>
<capability>urn:ietf:params:netconf:capability:candidate:1.0</capability>
<capability>urn:ietf:params:netconf:capability:confirmed-commit:1.0</capability>
<capability>urn:ietf:params:netconf:capability:validate:1.0</capability>
<capability>urn:ietf:params:netconf:capability:url:1.0?scheme=http,ftp,file</capability>
<capability>urn:ietf:params:xml:ns:netconf:base:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:candidate:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:confirmed-commit:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:validate:1.0</capability>
<capability>urn:ietf:params:xml:ns:netconf:capability:url:1.0?protocol=http,ftp,file</capability>
<capability>http://xml.juniper.net/netconf/junos/1.0</capability>
<capability>http://yang.juniper.net/yang/1.1/jc?module=configuration</capability>
<capability>urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring</capability>
<capability>http://xml.juniper.net/dmi/system/1.0</capability>
</capabilities>
<session-id>27216</session-id>
</hello>

Looking at the hello message, not many yang based capabilities there. Except maybe: <capability>http://yang.juniper.net/yang/1.1/jc?module=configuration</capability>. What yang modules did you put under cache/schema folder ?

Or what yang modules do you expect to be downloaded from the device and used ?

Because your device provides no schemas, and in hello message there is maybe one yang schema reported. In case you need to override the capabilities from hello message, there is a way via netconf-connector configuretion.

Hi Maros,

I have already added configuration.yang file in cache/schema folder, but faced the above mentioned issue.

Note: The same setup was working fine with the older odl code(Cloned on June 19,2014) but showing the issues with new odl code(Cloned on Aug 21, 2014)

Can you show me the whole log ? or can I connect to your device from my PC to debug ?

Hi Maros,

Device does not have internet connectivity, so you will not be able to connect to my netconf device.

Sharing with you the log file.

Attachment Opendaylight.log:26-08-2014 has been added with description: Log File Attached

Ok,

So your device has this capability in hello message
http://yang.juniper.net/yang/1.1/jc?module=configuration
without revision.

Netconf-connector currently ignores capabilities without revision parameter.

What you can do as a workaround:

1. add revision to the schema in cache/schema folder.
2. change configuration of netconf-connector, by adding this list property:
<yang-module-capabilities>
<capability>
http://yang.juniper.net/yang/1.1/jc?module=configuration?revision=YYYY-MM-DD
</capability>
</yang-module-capabilities>

Hi Maros,
Are you suggesting to put the capability as added in the last line of attached file(snapshot.txt) of 99-netconf-connector.xml?
i have added configuration@1970-01-01.yang file in cache/schema folder but getting the exception

Exception:
2014-08-27 19:07:14.139 IST [config-pusher] ERROR o.o.c.l.b.i.UncaughtExceptionPolicy - Thread Thread[config-pusher,5,main] died because of an uncaught exception
java.lang.IllegalStateException: Max wait for capabilities reached.Not enough capabilities for ConfigSnapshot

. Expected but not found: [urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector- cfg&revision=2013-10-28, http://yang.juniper.net/yang/1.1/jc?module=configuration&revision=1970-01-01]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationServiceWithRetries(ConfigPusherImpl.java:158) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.pushConfigWithConflictingVersionRetries(ConfigPusherImpl.java:134) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.internalPushConfigs(ConfigPusherImpl.java:111) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.process(ConfigPusherImpl.java:78) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.osgi.ConfigPersisterActivator$InnerCustomizer$1.run(ConfigPersisterActivator.java:177) ~[na:na]
at java.lang.Thread.run(Thread.java:744) ~[na:1.7.0_55]
Caused by: org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl$NotEnoughCapabilitiesException: Not enough capabilities for ConfigSnapshot

. Expected but not found: [urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector- cfg&revision=2013-10-28, http://yang.juniper.net/yang/1.1/jc?module=configuration&revision=1970-01-01]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationService(ConfigPusherImpl.java:196) ~[na:na]
at org.opendaylight.controller.netconf.persist.impl.ConfigPusherImpl.getOperationServiceWithRetries(ConfigPusherImpl.java:151) ~[na:na]
... 5 common frames omitted

and if i add the <yang-module-capabilities>
<capability>
http://yang.juniper.net/yang/1.1/jc?module=configuration?revision=YYYY-MM-DD
</capability>
</yang-module-capabilities> in required capabilities or after the required one's i am getting xml exception.
Kindly guide me how can i move ahead with correct configuration.

Thanks in advance.

Attachment snapshot.txt has been added with description: netconf-connector snapshot

Hi Maros,

I have hard coded the capabilities in NetconfClientSession.java file(as mentioned in CONTROLLER-256) after which we don't need to add yang capabilities in xml explicitly and it skips the above mentioned exception.

After doing this also, I am facing the same error of "Sal Initialization Failure"

2014-09-02 11:16:36.317 IST [remote-connector-processing-executor-2] WARN o.o.c.s.c.n.NetconfStateSchemas - RemoteDevice

: Initialization in sal failed, disconnecting from device
java.lang.IllegalStateException: RemoteDevice

: Session terminated Session closed

Ok, so you have file configuration@1970-01-01.yang in cache/schema. Does the file contain revision statement with 1970-01-01 revision ?

If so, adding this configuration under your netconf-connector:

<yang-module-capabilities>
<capability>
http://yang.juniper.net/yang/1.1/jc?module=configuration?revision=1970-01-01
</capability>
</yang-module-capabilities>

should do the trick.

Also are you running latest controller ?

Hi Maros,

1. Yes, configuration@1970-01-01.yang in cache/schema contains 1970-01-01 revision statement as below:

module configuration {
namespace "http://yang.juniper.net/yang/1.1/jc";
prefix jc;

revision 1970-01-01

2. Added configuration under your netconf-connector as below:

<required-capabilities> <capability>urn:opendaylight:params:xml:ns:yang:controller:md:sal:connector:netconf?module=odl-sal-netconf-connector-cfg&revision=2013-10-28</capability>
</required-capabilities>
<yang-module-capabilities>
<capability>
http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;revision=1970-01-01
</capability>
</yang-module-capabilities>

3. Yes, I am running the new controller code cloned on Sept-02.

After doing all the changes, its not working.
Please suggest.

Thanks in advance
Sachi

This xml:

<yang-module-capabilities>
<capability>
http://yang.juniper.net/yang/1.1/jc?module=configuration&amp;revision=1970-01-01
</capability>
</yang-module-capabilities>

Needs to be under module element. It is part of netconf-connector configuration.

Hi Maros,

Have added the above as part of netconf-connector configuration.

Now, I am not getting any error and device is not getting initialized also.

Anything else I need to add.

Thanks

Could you please rerun with detailed logs ?

Add these lines to configuration/logback.xml before you start ODL. Delete logs/ folder and rerun:

<logger name="org.opendaylight.protocol.framework" level="TRACE"/>
<logger name="org.opendaylight.controller.netconf" level="TRACE"/>
<logger name="org.opendaylight.controller.sal.connect.netconf" level="TRACE"/>
<logger name="org.opendaylight.yangtools.yang.model.repo.util" level="TRACE"/>
<logger name="org.opendaylight.yangtools.yang.parser.repo" level="TRACE"/>

And please attach produced opendaylight.log file afterwards.

And what do you mean by not getting initialized ? There is nothing under nodes/node from restconf ? or just no data are transfered ?

Send the logs on mmarsale@cisco.com.

The size of the file was larger so was not able to attach it on bugzilla.

The log says "RemoteDevice

: Netconf connector initialized successfully" but it does not show any log for my "sachi-m10" netconf connector.