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

Unavailable capabilities

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. Can anyone point me in the right direction please?

Unavailable capabilities

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?