netconf ned compile - error: expected revision

[mfierbau]

Hi,

Attempting to (re)compile a Cisco IOS-XR netconf ned and I am running into issues with revisions in tail-f models in 4.5.3.  Could someone point me to where the problem may be and how I might be able to correct it?

This is from doing a "make" within the package directory (which has worked in previous releases).

/opt/ncs/ncs-4.5.3/netsim/confd/bin/confdc --yangpath ../src/yang \

          `ls ../src/yang/tailf-common-ann.yang  > /dev/null 2>&1 && \

              echo "-a ../src/yang/tailf-common-ann.yang"` \

          -c -o tailf-common.fxs  ../src/yang/tailf-common.yang

../src/yang/tailf-common.yang:273:12: warning: illegal character after \

../src/yang/tailf-common.yang:273:19: warning: illegal character after \

../src/yang/tailf-common.yang:273:26: warning: illegal character after \

../src/yang/tailf-common.yang:273:33: warning: illegal character after \

/opt/ncs/ncs-4.5.3/netsim/confd/src/confd/yang/tailf-cli-extensions.yang:0: error: expected revision '2012-08-23', got '2017-08-23'

/opt/ncs/ncs-4.5.3/netsim/confd/src/confd/yang/tailf-meta-extensions.yang:0: error: expected revision '2010-08-19', got '2017-03-08'

make[2]: *** [tailf-common.fxs] Error 1

make[2]: Leaving directory `/opt/ncs/packages/cisco-iosxr-nc/netsim'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/opt/ncs/packages/cisco-iosxr-nc/netsim'

make: *** [all] Error 2

Thanks,

Marty

[frjansso]

Try doing a make clean and then make... sometimes the revision compilation goes out of sync.

[mfierbau]

I believe I had done this previously.  Just to verify, I did a "make clean" then a "make".  I have the exact same result.

FWIW - this is a new install (not an upgrade) of 4.5.3, so I would not expect any previous modules that did not come with this exact 4.5.3 installer.

[frjansso]

Can you zip up the package and post here and I can try it?

[mfierbau]

Here is the NED package.  Thanks!

[frjansso]

I cannot reproduce.

I unzipped your package and then as Larry mentioned, there are some references to confd models, from Cisco-IOS-XR-sysadmin-aaa-aaa-show.yang Cisco-IOS-XR-sysadmin-aaa-disaster-recovery.yang, so I removed those two models.

Now I can build:

make clean all -C src

[mfierbau]

Larry / Fredrik  -  thanks. The circular reference was indeed the cause of the original problem.  The NED compiles.

[lmanor · Accepted solution]

Martin,

Given that 'old' revisions of the included files that it is expecting, the yang file being compiled: tailf-common.yang is probably that from the XR confd instance on the device as retrieved from pioneer perhaps.  This file should be removed from the list on Yang files that you need to build for the NED:

From Pioneer README:

Files that are already part of NSO must not be included in the YANG

files when building a NED. This include:

* ietf-inet-types

* ietf-yang-types

* tailf-*

-Larry

[mfierbau]

Just want to follow up to this post, in the event that another runs into this issue. 

In addition to Larry's suggestion above, the circular reference was indeed the initial problem.  Once those were removed, the NED compiled successfully.  This was true using pioneer's build-netconf-ned as well as using the ncsc for 4.5.3.

However, a package reload caused the following internal error:

admin@ncs# packages reload

>>> System upgrade is starting.

>>> Sessions in configure mode must exit to operational mode.

>>> No configuration changes can be performed until upgrade has completed.

>>> System upgrade has been cancelled.

Error: Internal error: internal

I found that I also needed to remove the following:

ietf-netconf-monitoring.yang

nc-notifications.yang

notifications.yang

The NED now loads successfully.

[lmanor]

Martin,

Great to hear you were able to work your way through this.

Just curious what led you to determine what files needed to be removed in order to resolve the 'Internal error'.

Was there something in a log that caused you to target these files? other indicator? trial and error?

Thanks,

-Larry

[mfierbau]

Unfortunately the error messages were non-descriptive.  I was able to find the models by comparing a older working NED's yang models with this NED's models.  I then disabled them one-by-one until I found the source of the problem.