About Iman1

Iman1 · ‎02-20-2019

Thanks Joe

Iman1 · ‎02-20-2019

yeah good find... I'm not sure how errcode.xml is imported and used inside ncs. If someone could shed more light on it, that would be great... I wish there was some documentation around it (maybe there is?)... The use-case is simple... we don't necessarily want NSO's default error-messages which refer to the internal structure of service yang to be passed to a NB system/user. Ability to customize/generalize the error text returned to NB systems/users who are unaware of NSO details is very much desired.

Iman1 · ‎02-20-2019

Here's a sample of error-message NSO would return to NB API by default: "error-message": "invalid value for: loopback0v4 in /myservice:myservice[myservice:device='Router24']/myservice:loopbacks/myservice:loopback0v4: \"10.10.10.1000\" is not a valid value."

Iman1 · ‎02-20-2019

Thanks, yes I have seen that part of RFC but it seems in all the examples error-message is applicable when a condition is evaluated on datatype (for example: range, pattern, etc.). I'm not trying to impose further conditions on "inet:ipv4-address", rather want to just customize the error message that NSO returns to NB API when an invalid IP address is sent. By default, NSO's error-message returned to NB API contains the internal xpath to the IPv4 address in question, I want to customize that to a more generic error message.

Iman1 · ‎02-19-2019

Hi Is there any way to define custom error-message for data types in yang? For example: type inet:ipv4-address { error-message "Invalid IPv4 address for loopback0"; } PS - the above produces an error: unexpected keyword 'error-message'

Iman1 · ‎10-01-2018

Given that to fully add the device to NSO, the ssh key of the device needs to be fetched too, has anyone figured out how to handle that part as well via REST API? admin@ncs> request devices device R02 ssh fetch-host-keys the key fetched from above command should fit in XYZ below. <ssh> <host-key> <algorithm>ssh-rsa</algorithm> <key-data>XYZ</key-data> </host-key> </ssh>

Iman1 · ‎08-13-2018

reopening this thread from last year... Hi @Jan Lindblad - Do you have any more info to share regarding this issue? Particularly, I'm interested to know more about the 'mechanisms' that NSO uses for detecting whether the device configuration has changed or not (netconf NED). I recently worked with Cisco to fix the detection mechanism in CLI NED for iosxr devices. The CLI NED was using commit-id on iosxr device as transaction-id to detect configuration changes and when it was not available it was failing. Cisco fixed this by adding the fallback mechanism that now compares config hashes when the primary method is not available. I wonder, how different the detection methods are when it comes to netconf NED? Wouldn't comparing config hashes still be a standard fallback mechanism when other methods are not available?

Iman1 · ‎02-23-2018

Thanks Jan. Do you have any thoughts on my first question? ( how's Cisco-IOS-XR-infra-dumper-cfg even called? There is nothing in Cisco-IOS-XR-infra-infra-clock-cfg.yang that would reference or import Cisco-IOS-XR-infra-dumper-cfg) basically, how are yang models relate to each other? The router has some clock stuff configs and that hits the infra-infra-clock-cfg, but there's nothing I could find in infra-infra-clock-cfg that would import/point to infra-dumper-cfg. So if I'm not missing something, there must be *some other* mechanism that brings infra-dumper-cfg into action once the infra-infra-clock-cfg is hit. How?

Iman1 · ‎02-20-2018

Hi Device (VC04) is IOS-XR 6.1.3. admin@ncs> request devices device vc04 sync-from dry-run cli config { infra-infra-clock-cfg:clock { + time-zone { + time-zone-name MST; + hour-offset -6; + minute-offset 0; + } } } [ok][2018-02-20 18:00:04] admin@ncs> request devices device vc04 sync-from result false info devices device vc04 config exception choice3 : the 'must' expression "(compress and not(lower-limit) and not(higher-limit) and file-path and not(filename)) or (compress and lower-limit and higher-limit and file-path and filename)" failed From xpath log: 20-Feb-2018::18:20:41.498 Evaluating XPath for: /devices/device[name='vc04']/config/infra-dumper-cfg:exception/choice3: (compress and not(lower-limit) and not(higher-limit) and file-path and not(filename)) or (compress and lower-limit and higher-limit and file-path and filename) get_elem("/ncs:devices/device{vc04}/config/infra-dumper-cfg:exception/choice3/compress") = not_found get_elem("/ncs:devices/device{vc04}/config/infra-dumper-cfg:exception/choice3/compress") = not_found 20-Feb-2018::18:20:41.504 XPath for: /devices/device[name='vc04']/config/infra-dumper-cfg:exception/choice3 returns false I found the above error is related to Cisco-IOS-XR-infra-dumper-cfg.yang Here is its choice 3 section causing the error: container choice3 { must "(compress and not(lower-limit) and not(higher-limit)"+ " and file-path and not(filename)) or (compress and"+ " lower-limit and higher-limit and file-path and filename)" { description "Describes valid combinations of leafs"; } description "Preference of the dump location"; leaf compress { type boolean; description "Specify 'true' to compress core files dumped on this path, 'false' to not compress"; } leaf lower-limit { type uint32 { range "0..4"; } description "Lower limit. This is required if Filename is specified."; } leaf higher-limit { type uint32 { range "5..64"; } description "Higher limit. This is required if Filename is specified."; } leaf file-path { type string; description "Protocol and directory"; } leaf filename { type string; description "Dump filename"; } } My question is, how's Cisco-IOS-XR-infra-dumper-cfg even called? There is nothing in Cisco-IOS-XR-infra-infra-clock-cfg.yang that would reference or import Cisco-IOS-XR-infra-dumper-cfg Second question - what did go wrong? Thanks

Iman1 · ‎02-19-2018

Hey Jan I encountered this again and this time I enabled raw trace to find more information. Basically, upon issuing check-sync, NSO initiates hello to device, and the device returns its full capabilities. Then NSO suddenly closes the session with this: <?xml version="1.0" encoding="UTF-8"?> <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1"> <close-session/></rpc> My guess is that NSO was looking for something special in the returned capabilities from the device, and since it didn't find it, then it killed the session. Is my understanding correct? If so, what was it that NSO was looking for in the list of capabilities from the device? A special yang? Device is IOS-XR 6.1.3. Thanks

Iman1 · ‎02-15-2018

Any XML expert to know the answer to above? As an alternative solution, can a temporary variable be created inside the XML template and its value increased during each iteration of foreach loop? (to mimic the array index) Thanks

Iman1 · ‎12-21-2017

Jan, sorry for delay... I was away and then busy for a while. Attached are the YANGs as you requested.

Iman1 · ‎11-13-2017

Thanks Roque. Yes, I'm aware of that particular issue with Nokia's netconf implementation. The way I have worked around that issue is by disabling running DS capability on Nokia device, and that way NSO only tries to hold a lock on candidate DS. I think we'll have to wait for SROS 16 at minimum for a permanent fix to this issue. The problem I have in this thread though seems to be YANG related, and I'm wondering how to go about troubleshooting it. Iman

Iman1 · ‎11-13-2017

Thanks Jan. I enabled the Pioneer log as you said, but unfortunately my eyes don't see any extra information there. Nothing interesting in logs/ncs.log and logs/devel.log either. Am I missing something? Is there no further step to figure out why Pioneer complains about an internal compilation error? ==> logs/ncs-python-vm-pioneer.log <== 2017-11-13 16:56:43 - pioneer - DEBUG - ========== pioneer cb_action() ========== 2017-11-13 16:56:43 - pioneer - DEBUG - thandle=173 usid=54 2017-11-13 16:56:43 - pioneer - DEBUG - yang_build_netconf_ned() with device mr30 2017-11-13 16:56:43 - pioneer - DEBUG - Cleaning up existing ned-directory 2017-11-13 16:56:43 - pioneer - DEBUG - Starting build of 151 YANG modules, this may take some time 2017-11-13 16:56:43 - pioneer - DEBUG - run '/bin/bash /root/ncs/4.4.2/ncs-run-4.4.2/state/packages-in-use/1/pioneer/python/pioneer/ncs-make-package-verbose /win7/Nokia/15.0.R4_ALL_YANG/YANG/ 15r4 /root/ncs/4.4.2/ncs-4.4.2/packages/neds', input len=0 2017-11-13 16:56:43 - pioneer - DEBUG - run_outputfun '/bin/bash /root/ncs/4.4.2/ncs-run-4.4.2/state/packages-in-use/1/pioneer/python/pioneer/ncs-make-package-verbose /win7/Nokia/15.0.R4_ALL_YANG/YANG/ 15r4 /root/ncs/4.4.2/ncs-4.4.2/packages/neds 2017-11-13 16:56:43 - pioneer - DEBUG - run_outputfun, going in 2017-11-13 16:56:43 - pioneer - DEBUG - run_outputfun, output len=378 2017-11-13 16:56:43 - pioneer - DEBUG - PATH=/root/ncs/4.4.2/ncs-4.4.2//bin:/root/ncs/4.4.2/ncs-4.4.2/lib/ncs/erts/bin:/root/ncs/4.4.2/ncs-4.4.2/lib/ncs/bin:/root/ncs/4.4.2/ncs-4.4.2//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/root/go/bin ncs-make-package --verbose --netconf-ned /win7/Nokia/15.0.R4_ALL_YANG/YANG/ 15r4 --dest /root/ncs/4.4.2/ncs-4.4.2/packages/neds --no-java 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=57 2017-11-13 16:56:44 - pioneer - DEBUG - Wrote package to /root/ncs/4.4.2/ncs-4.4.2/packages/neds 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=113 2017-11-13 16:56:44 - pioneer - DEBUG - make clean fxs -C /root/ncs/4.4.2/ncs-4.4.2/packages/neds/src NCSC=/root/ncs/4.4.2/ncs-4.4.2//bin/ncsc --verbose 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=71 2017-11-13 16:56:44 - pioneer - DEBUG - make: Entering directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/src' 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=28 2017-11-13 16:56:44 - pioneer - DEBUG - rm -rf ncsc-out ../load-dir 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=35 2017-11-13 16:56:44 - pioneer - DEBUG - cd ../netsim && make clean || true 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=77 2017-11-13 16:56:44 - pioneer - DEBUG - make[1]: Entering directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/netsim' 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=76 2017-11-13 16:56:44 - pioneer - DEBUG - make[1]: Leaving directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/netsim' 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=18 2017-11-13 16:56:44 - pioneer - DEBUG - mkdir -p ncsc-out 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=21 2017-11-13 16:56:44 - pioneer - DEBUG - mkdir -p ../load-dir 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=299 2017-11-13 16:56:44 - pioneer - DEBUG - /root/ncs/4.4.2/ncs-4.4.2//bin/ncsc --verbose --ncs-compile-bundle yang \ --ncs-device-dir ncsc-out \ --ncs-device-type netconf \ && \ cp ncsc-out/modules/fxs/*.fxs ../load-dir; 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=24 2017-11-13 16:56:44 - pioneer - DEBUG - Internal compiler error 2017-11-13 16:56:44 - pioneer - DEBUG - run_outputfun, output len=160 2017-11-13 16:56:44 - pioneer - DEBUG - Makefile:25: recipe for target 'ncsc-out/.done' failed make: *** [ncsc-out/.done] Error 1 make: Leaving directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/src' 2017-11-13 16:56:44 - pioneer - DEBUG - run_finished, output len=1357 2017-11-13 16:56:44 - pioneer - DEBUG - Output from build PATH=/root/ncs/4.4.2/ncs-4.4.2//bin:/root/ncs/4.4.2/ncs-4.4.2/lib/ncs/erts/bin:/root/ncs/4.4.2/ncs-4.4.2/lib/ncs/bin:/root/ncs/4.4.2/ncs-4.4.2//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/root/go/bin ncs-make-package --verbose --netconf-ned /win7/Nokia/15.0.R4_ALL_YANG/YANG/ 15r4 --dest /root/ncs/4.4.2/ncs-4.4.2/packages/neds --no-java Wrote package to /root/ncs/4.4.2/ncs-4.4.2/packages/neds make clean fxs -C /root/ncs/4.4.2/ncs-4.4.2/packages/neds/src NCSC=/root/ncs/4.4.2/ncs-4.4.2//bin/ncsc --verbose make: Entering directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/src' rm -rf ncsc-out ../load-dir cd ../netsim && make clean || true make[1]: Entering directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/netsim' make[1]: Leaving directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/netsim' mkdir -p ncsc-out mkdir -p ../load-dir /root/ncs/4.4.2/ncs-4.4.2//bin/ncsc --verbose --ncs-compile-bundle yang \ --ncs-device-dir ncsc-out \ --ncs-device-type netconf \ && \ cp ncsc-out/modules/fxs/*.fxs ../load-dir; Internal compiler error Makefile:25: recipe for target 'ncsc-out/.done' failed make: *** [ncsc-out/.done] Error 1 make: Leaving directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/src' 2017-11-13 16:56:44 - pioneer - DEBUG - Build failed. Error and warning messages below. See log for complete details Internal compiler error make: *** [ncsc-out/.done] Error 1

Iman1 · ‎11-12-2017

I'm trying to build netconf NED for Nokia (ALU) device. Following the Pioneer approach I encounter an Internal compiler error (please see below) . I'm going to guess it's due to problems in Nokia's yang but my question is how can I go about troubleshooting this and find which yang is problematic? There is a line below that says See log for complete details, but I couldn't locate any log related to this. Where does Pioneer store logs related to error below? Is there a way to troubleshoot further and figure out which of the Nokia's yang modules are the problem? Thanks. admin@ncs% request pioneer yang build-netconf-ned yang-directory /win7/Nokia/15.0.R4_ALL_YANG/YANG/ ned-directory /root/ncs/4.4.2/ncs-4.4.2/packages/neds name 15r4 Cleaning up existing ned-directory Starting build of 151 YANG modules, this may take some time PATH=/root/ncs/4.4.2/ncs-4.4.2//bin:/root/ncs/4.4.2/ncs-4.4.2/lib/ncs/erts/bin:/root/ncs/4.4.2/ncs-4.4.2/lib/ncs/bin:/root/ncs/4.4.2/ncs-4.4.2//bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/go/bin:/root/go/bin ncs-make-package --verbose --netconf-ned /win7/Nokia/15.0.R4_ALL_YANG/YANG/ 15r4 --dest /root/ncs/4.4.2/ncs-4.4.2/packages/neds --no-java Wrote package to /root/ncs/4.4.2/ncs-4.4.2/packages/neds make clean fxs -C /root/ncs/4.4.2/ncs-4.4.2/packages/neds/src NCSC=/root/ncs/4.4.2/ncs-4.4.2//bin/ncsc --verbose make: Entering directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/src' rm -rf ncsc-out ../load-dir cd ../netsim && make clean || true make[1]: Entering directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/netsim' make[1]: Leaving directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/netsim' mkdir -p ncsc-out mkdir -p ../load-dir /root/ncs/4.4.2/ncs-4.4.2//bin/ncsc --verbose --ncs-compile-bundle yang \ --ncs-device-dir ncsc-out \ --ncs-device-type netconf \ && \ cp ncsc-out/modules/fxs/*.fxs ../load-dir; Internal compiler error Makefile:25: recipe for target 'ncsc-out/.done' failed make: *** [ncsc-out/.done] Error 1 make: Leaving directory '/root/ncs/4.4.2/ncs-4.4.2/packages/neds/src' Build failed. Error and warning messages below. See log for complete details Internal compiler error make: *** [ncsc-out/.done] Error 1 failure Build failed [ok][2017-11-11 22:45:14]

Iman1 · 02-20-2019

Thanks Joe

Iman1 · 02-20-2019

yeah good find... I'm not sure how errcode.xml is imported and used inside ncs. If someone could she...

Iman1 · 02-20-2019

Here's a sample of error-message NSO would return to NB API by default: "error-message": "invalid va...

Iman1 · 02-20-2019

Thanks, yes I have seen that part of RFC but it seems in all the examples error-message is applicabl...

Iman1 · 02-19-2019

Hi Is there any way to define custom error-message for data types in yang? For example: type inet:ip...

Iman1 · 10-01-2018

Given that to fully add the device to NSO, the ssh key of the device needs to be fetched too, has an...

Iman1 · 08-13-2018

reopening this thread from last year... Hi @Jan Lindblad - Do you have any more info to share regard...

Iman1 · 02-23-2018

Thanks Jan.Do you have any thoughts on my first question? ( how's Cisco-IOS-XR-infra-dumper-cfg even...

Iman1 · 02-20-2018

HiDevice (VC04) is IOS-XR 6.1.3.admin@ncs> request devices device vc04 sync-from dry-run cli config ...

Iman1 · 02-19-2018

Hey JanI encountered this again and this time I enabled raw trace to find more information. Basicall...

Iman1 · 02-15-2018

Any XML expert to know the answer to above? As an alternative solution, can a temporary variable be ...

Iman1 · 12-21-2017

Jan, sorry for delay... I was away and then busy for a while. Attached are the YANGs as you requeste...

Iman1 · 11-13-2017

Thanks Roque.Yes, I'm aware of that particular issue with Nokia's netconf implementation. The way I ...

Iman1 · 11-13-2017

Thanks Jan. I enabled the Pioneer log as you said, but unfortunately my eyes don't see any extra inf...

Iman1 · 11-12-2017

I'm trying to build netconf NED for Nokia (ALU) device. Following the Pioneer approach I encounter a...

Date Registered	‎10-18-2016 05:06 PM
Date Last Visited	‎05-08-2019 12:36 PM
Total Messages Posted	28
Total Helpful Votes Received	1

Re: custom error-message for datatypes

Re: custom error-message for datatypes

Re: custom error-message for datatypes

Re: custom error-message for datatypes

custom error-message for datatypes

Re: NSO DEVICE ADD via REST API

Re: check-sync returns "unsupported"

Re: Cisco-IOS-XR-infra-dumper-cfg causi...

Cisco-IOS-XR-infra-dumper-cfg causing e...

Re: check-sync returns "unsupported"

Re: xpath position()

Re: Pioneer's Internal compiler error

Re: Pioneer's Internal compiler error

Re: Pioneer's Internal compiler error

Pioneer's Internal compiler error

Re: custom error-message for datatypes

Re: custom error-message for datatypes

Re: custom error-message for datatypes

Re: custom error-message for datatypes

custom error-message for datatypes

Re: NSO DEVICE ADD via REST API

Re: check-sync returns "unsupported"

Re: Cisco-IOS-XR-infra-dumper-cfg causing error

Cisco-IOS-XR-infra-dumper-cfg causing error

Re: check-sync returns "unsupported"

Re: xpath position()

Re: Pioneer's Internal compiler error

Re: Pioneer's Internal compiler error

Re: Pioneer's Internal compiler error

Pioneer's Internal compiler error