Thanks Jan. Here is what I did:
1. followed Pioneer procedure to build the netconf ned. There were couple of errors (see below), so I disabled the offending models (actually disabled entire openconfig models since I have heard they have errors):
yang/cisco-xr-openconfig-interfaces-types.yang:8: error: module 'openconfig-interfaces' not found
make: *** [ncsc-out/.done] Error 1
failure Build failed
yang/tailf-common-monitoring.yang:164: error: the node 'mode' from module 'tailf-confd-monitoring' is not found
make: *** [ncsc-out/.done] Error 1
failure Build failed
2. disabled:
*openconfig*
tailf-confd-monitoring
3. instead of "pioneer yang install-netconf-ned", I simply created a symlink to the built ned directory from the runtime packages directory (because I noticed "pioneer yang install-netconf-ned" actually copies all the files over - please let me know if this is not ok)
4. packages reloaded successfully. Sync-from dry-run successfully shows the dry-run outcome
5. attempted to sync-from device:
admin@ncs% request sync-from
result false
info devices device ncs1 config policy-manager policy-maps policy-map qos QOS-IN policy-map-rule classify-set_cos4 qos service-function-path : the 'must' expression "path-id" failed
[ok][2017-08-15 16:40:13]
I'm assuming this is an error in the yang file?
This is the relevant snippet from that yang file that complains, it needs path-id but in the actual configuration of the device there is no path-id:
container service-function-path {
must "path-id" {
description "path id must be present.";
}
description "Policy action service function path.";
leaf path-id {
type uint32 {
range "1..16777215";
}
must "../index" {
description "index must be set.";
}
description "Service function path id.";
}
leaf index {
type uint8 {
range "1..255";
}
description "Service function path index.";
}
leaf metadata {
type string;
description "Service function path metadata name.";
}
}
and here is the actual configuration on the device from sync-from dry-run (for the section it complains):
<policy-map>
<type>qos</type>
<name>QOS-IN</name>
<policy-map-rule>
<class-name>classify-set_cos7</class-name>
<class-type>qos</class-type>
<set>
<traffic-class>3</traffic-class>
</set>
</policy-map-rule>
<policy-map-rule>
<class-name>classify-set_cos5</class-name>
<class-type>qos</class-type>
<set>
<traffic-class>2</traffic-class>
</set>
</policy-map-rule>
<policy-map-rule>
<class-name>classify-set_cos4</class-name>
<class-type>qos</class-type>
<set>
<traffic-class>1</traffic-class>
</set>
</policy-map-rule>
</policy-map>
