Ask Your Question
0

Unavailable capabilities

asked 2015-08-11 12:51:19 -0700

calciajd gravatar image

updated 2015-08-11 12:52:21 -0700

Looking at http://localhost:8080/restconf/operational/network-topology:network-topology/topology/topology-netconf/node/toaster shows several unavailable capabilites:

<unavailable-capabilities xmlns="urn:opendaylight:netconf-node-topology">
    <unavailable-capability>
        <failure-reason>unable-to-resolve</failure-reason>
        <capability>
            (urn:ietf:params:xml:ns:netconf:notification:1.0?revision=2008-07-14)notifications
        </capability>
    </unavailable-capability>
    <unavailable-capability>
        <failure-reason>unable-to-resolve</failure-reason>
        <capability>
            (urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?revision=2010-10-04)ietf-netconf-monitoring
        </capability>
    </unavailable-capability>
    <unavailable-capability>
        <failure-reason>missing-source</failure-reason>
        <capability>
            (urn:ietf:params:xml:ns:yang:ietf-netconf-server?revision=2014-01-24)ietf-netconf-server
        </capability>
    </unavailable-capability>
    <unavailable-capability>
        <failure-reason>unable-to-resolve</failure-reason>
        <capability>
            (urn:ietf:params:xml:ns:netmod:notification?revision=2008-07-14)nc-notifications
        </capability>
    </unavailable-capability>
</unavailable-capabilities>

I also see these log errors:

2015-08-11 14:51:41,562 | WARN  | sing-executor-11 | NetconfDevice                    | 292 - org.opendaylight
.controller.sal-netconf-connector - 1.2.0.Lithium | RemoteDevice{toaster}: Unable to build schema context, mis
sing source SourceIdentifier [name=ietf-netconf-server@2014-01-24], will reattempt without it

2015-08-11 14:51:41,587 | WARN  | sing-executor-11 | NetconfDevice                    | 292 - org.opendaylight
.controller.sal-netconf-connector - 1.2.0.Lithium | RemoteDevice{toaster}: Unable to build schema context, uns
atisfied imports {SourceIdentifier [name=nc-notifications@2008-07-14]=[ModuleImportImpl [name=ietf-yang-types,
 revision=2010-09-24]], SourceIdentifier [name=ietf-netconf-monitoring@2010-10-04]=[ModuleImportImpl [name=iet
f-yang-types, revision=2010-09-24]], SourceIdentifier [name=notifications@2008-07-14]=[ModuleImportImpl [name=
ietf-yang-types, revision=2010-09-24]]}, will reattempt with resolved only

I've confirmed these YANG files are in my cache/schema folder. I don't know what else has to happen for these models to become available. Other models on the same device are working just fine. Can anyone point me in the right direction please?

edit retag flag offensive close merge delete

Comments

@calciajd How did you solve this?

devp ( 2016-07-14 08:11:39 -0700 )edit

5 answers

Sort by » oldest newest most voted
1

answered 2015-08-24 08:09:48 -0700

calciajd gravatar image

Turns out there were errors in the yang model. Pyang didn't point this out, but the model had an error in the key of several lists. I didn't see this until I set the log level to DEBUG in karaf and then searched the log file for exceptions.

edit flag offensive delete publish link more
1

answered 2016-03-17 14:45:08 -0700

harshawasthi gravatar image

updated 2016-03-17 14:48:18 -0700

I resolved it using following method.

If you open ietf-yang-types.yang in netconf server(i am using openyuma) module directory. You can see 2 revisions. I think multiple revisions are creating the issue. Same pattern in other errors too.

Comment/remove the 2013-07-15 revision, warning related to ietf-yang-types goes away.

Just tested it.. You can do it for other errors too....

edit flag offensive delete publish link more

Comments

when I remove the 2013-07-15 ietf-inet-types, that doesn't work

amy ( 2016-03-22 22:36:47 -0700 )edit
0

answered 2016-03-09 23:41:09 -0700

amy gravatar image

I have the same error, do you know how to solve it?

edit flag offensive delete publish link more
0

answered 2016-03-10 07:53:01 -0700

bhavesh07 gravatar image

updated 2016-07-27 02:48:00 -0700

@devp This occurs because the revision declared into your device doesn't match the revisions declared in ODL.

To fix this at run-time, Go to the cache/schema folder :

Edit the ietf-netconf-notifications@2012-02-06... , ietf-netconf-monitoring@2010-10-04.yang , nc-notifications@2008-07-14.yang and notifications@2008-07-14.yang and remove all the revisions declared for imports ietf-inet-types and ietf-yang-types respectively.

e.g-

import ietf-yang-types {
  prefix yang;
}

import ietf-inet-types {
  prefix inet;
}

Restart the karaf again. You're done.

edit flag offensive delete publish link more

Comments

I know for “unable-to-resolve”,we need to import corresponding module. But for "missing-source" I have no idea. I am appreciate for your reply!

amy ( 2016-03-10 08:11:12 -0700 )edit

@amy Can you please post the ODL logs in debug mode for the unsatisfied imports ? "Missing-source" indicates that the particular yang isn't visible to the ODL.

bhavesh07 ( 2016-03-10 23:21:30 -0700 )edit

also I check the cache/schema, there are two versions of ietf-inet-types. I don't know how to solve it, any advice will be appreciate!

amy ( 2016-03-22 22:35:10 -0700 )edit

the log is RemoteDevice{router}: Unable to build schema context, unsatisfied imports {SourceIdentifier [name=ietf-netconf-notifications@2012-02-06]=[ModuleImportImpl [name=ietf-inet-types, revision=2010-09-24], ModuleImportImpl [name=ietf-netconf, revision=2011-06-01]]

amy ( 2016-03-23 00:21:37 -0700 )edit

@amy@bhavesh07@harshawasthi@calciajd I am facing a similar problem....can you explain how you solved the 'unable to resolve' error? I am new to odl and see similar log errors as asked in the question. Where do i go look and change stuff to correct this error?

devp ( 2016-07-14 08:02:33 -0700 )edit
0

answered 2016-07-26 12:35:57 -0700

devp gravatar image

@bhavesh07 The error message I get in the karaf logs is:

185 - org.opendaylight.controller.sal-netconf-connector - 1.2.3.Lithium-SR3 | RemoteDevice{router1}:

Unable to build schema context,

unsatisfied imports

{SourceIdentifier [name=ietf-netconf-notifications@2012-02-06]=[ModuleImportImpl [name=ietf-inet-types, revision=2010-09-24], ModuleImportImpl [name=ietf-netconf, revision=2011-06-01]],

SourceIdentifier [name=ietf-netconf-monitoring@2010-10-04]=[ModuleImportImpl [name=ietf-yang-types, revision=2010-09-24], ModuleImportImpl [name=ietf-inet-types, revision=2010-09-24]],

SourceIdentifier [name=nc-notifications@2008-07-14]=[ModuleImportImpl [name=ietf-yang-types, revision=2010-09-24]],

SourceIdentifier [name=notifications@2008-07-14]=[ModuleImportImpl [name=ietf-yang-types, revision=2010-09-24]]}, will reattempt with resolved only

edit flag offensive delete publish link more

Comments

@devp I have updated my answer. Hope this helps.

bhavesh07 ( 2016-07-27 02:49:42 -0700 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Stats

Asked: 2015-08-11 12:51:19 -0700

Seen: 676 times

Last updated: Jul 27 '16