[CONTROLLER-734] Exception thrown when loading Tail-F NCS Device with SNMP MIB Model into ODL Created: 26/Aug/14  Updated: 19/Oct/17  Resolved: 27/Aug/14

Status: Resolved
Project: controller
Component/s: mdsal
Affects Version/s: Helium
Fix Version/s: None

Type: Bug
Reporter: Raghurama Bhat Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC


Attachments: Zip Archive files.zip    
External issue ID: 1624

 Description   

See the following exceptions when the NCS Netconf Server is mounted into ODL and I try to access:

http://10.194.126.101:9080/restconf/config/opendaylight-inventory:nodes/node/ncs/yang-ext:mount/tailf-ncs:devices

Logs and the YANG Model attached.

java.lang.IllegalArgumentException: Failed to normalize data [Node[ImmutableCompositeNode], qName[SNMPv2-MIB], modify[n/a], children.size = 2]

org.opendaylight.controller.md.sal.common.impl.util.compat.DataNormalizationException: Supplied QName (urn:ietf:params:xml:ns:yang:smiv2:SNMPv2-MIB)SNMPv2-MIB is not valid according to schema container config,



 Comments   
Comment by Raghurama Bhat [ 26/Aug/14 ]

Attachment files.zip has been added with description: Log file and the YANG Model (Zipped)

Comment by Tony Tkacik [ 27/Aug/14 ]

Your netconf device did not provided schemas required for YANG model you attached.

[remote-connector-processing-executor-4] WARN o.o.c.s.c.netconf.NetconfDevice - RemoteDevice

{ncs}

: Unable to build schema context, unsatisfied imports:

{SourceIdentifier [name=encryption-usm@0000-00-00]=[ModuleImportImpl [name=SNMP-USER-BASED-SM-MIB, revision=null]], SourceIdentifier [name=SNMPv2-MIB@2002-10-16]=[ ModuleImportImpl [name=SNMPv2-TC, revision=null]], SourceIdentifier [name=BASIC-CONFIG-MIB@2011-11-16]=[ ModuleImportImpl [name=SNMP-FRAMEWORK-MIB, revision=null], ModuleImportImpl [name=SNMPv2-TC, revision=null]]}

, will reattempt with resolved only

Generated at Wed Feb 07 19:53:44 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.