ConfD User Community

Integrating netopeer2-cli with confD Netconf Server


#1

I am trying to integrate netopeer2-cli with confD NETCONF server.
I am facing some issues here. Regarding this i have some query.

1)Once netopeer2-cli connected with NETCONF server, it will load all modules in server automatically?? if yes which path it will load.
2)whatever modules present in server side needs to present on client side too?? if yes which path?? or how to set path??
3) edit-config and get commands are throwing some libyang errors.
get --filter-xpath
ly ERROR: Invalid “:type” metadata with value “xpath”. (/ietf-netconf:get/filter)
ly ERROR: Enum “xpath” is disabled by its 1. if-feature condition. (/ietf-netconf:get/filter)

edit-config is also not supporting for running/candidate.
ly ERROR: Failed to find “running” as a sibling to “ietf-netconf:config-target”.

Please let me know do i need to take care of any configurations here?
I have confirmed that server capability support for xpath.
Any help is appreciated.


#2

I have found the issue, confD ietf-netconf.yang module doesn;t have any features enabled.
found this from capabilities .
urn:ietf:params:xml:ns:netconf:base:1.0?module=ietf-netconf&revision=2011-06-01

So only not able to do operations like get, get-config and edit-config.
It requires all features enabled in module ietf-netconf.yang like below,
urn:ietf:params:xml:ns:netconf:base:1.0?module=ietf-netconf&revision=2011-06-01&features=writable-running,candidate,rollback-on-error,validate,startup,xpath

But how to enable this features in ietf-netconf module?
Tried to compile with features enabled but with ietf-netconf.fxs confd is crashing, found from confd user guide, no need to put ietf-netconf.fxs in load path.

Then how to get ietf-netconf module with features enabled?
Please let me know how i can do this .


#3

I believe you should instead ask the netopeer2 community why netopeer2 have the

<capability>urn:ietf:params:xml:ns:netconf:base:1.0?module=ietf-netconf&amp;revision=2011-06-01</capability>

…announced with features statements:

<capability>urn:ietf:params:xml:ns:netconf:base:1.0?module=ietf-netconf&amp;revision=2011-06-01&amp;features=writable-running,candidate,rollback-on-error,validate,startup,xpath</capability>

…and more importantly for you, why the netopeer2-cli NETCONF client, if as you describe, require that the feature statements are announced.

The

<capability>urn:ietf:params:netconf:base:1.1</capability>
<capability>urn:ietf:params:netconf:capability:candidate:1.0</capability>

etc. statements are enough for announcing capabilities to the NETCONF client according to the NETCONF RFCs.