ConfD User Community

Netconf-console doesn't respond to XML request


#1

Hi,

I downloaded CONFD basic and am running into some problems with
netconf-console.

I am using OpenConfig and have written some source code that essentially
handles the components/component YANG objects.

I create 2 instances successfully as per the following CLI output:
vk@vk-VirtualBox:~/kautuk/NOS-S$ /home/vk/kautuk/confd/bin/confd -c confd.conf --addloadpath /home/vk/kautuk/confd/etc/confd --addloadpath openfxs/
vk@vk-VirtualBox:~/kautuk/NOS-S$ ./nos-s 0.0.0.0 &
[1] 24491
**vk@vk-VirtualBox:~/kautuk/NOS-S$ **
vk@vk-VirtualBox:~/kautuk/NOS-S$ ps
** PID TTY TIME CMD**
22616 pts/8 00:00:01 bash
24491 pts/8 00:00:00 nos-s
24492 pts/8 00:00:00 ps
**vk@vk-VirtualBox:~/kautuk/NOS-S$ /home/vk/kautuk/confd/bin/confd_cli **
Welcome to ConfD Basic

The CLI may only be used during product development.
Commercial use of the CLI is prohibited.
You must disable the CLI in confd.conf for production.
For more information, visit http://www.tail-f.com.
vk connected from 10.10.17.15 using ssh on vk-VirtualBox
vk-VirtualBox# config
Entering configuration mode terminal
vk-VirtualBox(config)# components component oe1
vk-VirtualBox(config-component-oe1)# top
vk-VirtualBox(config)# commit
Commit complete.
vk-VirtualBox(config)# com
Possible completions:
** components **
** — **
** commit Commit current set of changes**
** compare Compare configuration**
vk-VirtualBox(config)# components component oe2
vk-VirtualBox(config-component-oe2)# top
vk-VirtualBox(config)# commit
Commit complete.
**vk-VirtualBox(config)# show full-configuration **
components component oe1
** properties property oe1**
** !**
** properties property oe2**
** !**
** subcomponents subcomponent oe1**
** !**
** subcomponents subcomponent oe2**
** !**
!
components component oe2
** properties property oe1**
** !**
** properties property oe2**
** !**
** subcomponents subcomponent oe1**
** !**
** subcomponents subcomponent oe2**
** !**
!
vk-VirtualBox(config)# exit
**vk-VirtualBox# show components **
components component oe1
** state type OPTICAL_CHANNEL**
** chassis state**
** port state**
** power-supply state**
** fan state**
** fabric state**
** storage state**
** cpu state**
** integrated-circuit state**
** backplane state**
**NAME NAME VALUE CONFIGURABLE **
---------------------------------
**oe1 - - - **
**oe2 - - - **

**NAME NAME **
------------
**oe1 - **
**oe2 - **

components component oe2
** state type OPTICAL_CHANNEL**
** chassis state**
** port state**
** power-supply state**
** fan state**
** fabric state**
** storage state**
** cpu state**
** integrated-circuit state**
** backplane state**
**NAME NAME VALUE CONFIGURABLE **
---------------------------------
**oe1 - - - **
**oe2 - - - **

**NAME NAME **
------------
**oe1 - **
**oe2 - **

vk-VirtualBox# exit
vk@vk-VirtualBox:~/kautuk/NOS-S$

After that, I try sending a very rudimentary XML request via netconf-console as
per the following command line output:
vk@vk-VirtualBox:~/kautuk/NOS-S$ cat a.xml **

**

** **
** **

vk@vk-VirtualBox:~/kautuk/NOS-S$ ~/kautuk/confd/bin/netconf-console --host=127.0.0.1 --port=2022 --rpc=a.xml
vk@vk-VirtualBox:~/kautuk/NOS-S$
vk@vk-VirtualBox:~/kautuk/NOS-S$ netstat -anp | grep confd
(Not all processes could be identified, non-owned process info
** will not be shown, you would have to be root to see it all.)**
*tcp 0 0 127.0.0.1:4565 0.0.0.0: LISTEN 24476/confd **
*tcp 0 0 0.0.0.0:2022 0.0.0.0: LISTEN 24476/confd **
*tcp 0 0 0.0.0.0:2024 0.0.0.0: LISTEN 24476/confd **
**tcp 0 0 127.0.0.1:4565 127.0.0.1:42986 ESTABLISHED 24476/confd **
**tcp 0 0 127.0.0.1:4565 127.0.0.1:42984 ESTABLISHED 24476/confd **
**unix 2 [ ] DGRAM 851926 24476/confd **
**vk@vk-VirtualBox:~/kautuk/NOS-S$ **
vk@vk-VirtualBox:~/kautuk/NOS-S$

As you can see by the above output, netconf-console doesn’t respond at all.
I checked the 2022 port and it works well because the --hello option used with
netconf-console returns the capabilities successfully as follows:
vk@vk-VirtualBox:~/kautuk/NOS-S$ ~/kautuk/confd/bin/netconf-console --host=127.0.0.1 --port=2022 --hello

<?xml version="1.0" encoding="UTF-8"?> urn:ietf:params:netconf:base:1.0 urn:ietf:params:netconf:base:1.1 urn:ietf:params:netconf:capability:writable-running:1.0 urn:ietf:params:netconf:capability:xpath:1.0 urn:ietf:params:netconf:capability:validate:1.0 urn:ietf:params:netconf:capability:validate:1.1 urn:ietf:params:netconf:capability:rollback-on-error:1.0 urn:ietf:params:netconf:capability:with-defaults:1.0?basic-mode=explicit&also-supported=report-all-tagged urn:ietf:params:netconf:capability:yang-library:1.0?revision=2016-06-21&module-set-id=91b6f4e16640fa803113c3beb083dab6 http://tail-f.com/ns/netconf/actions/1.0 http://tail-f.com/ns/netconf/extensions http://openconfig.net/yang/alarms/types?module=openconfig-alarm-types&revision=2018-11-21 http://openconfig.net/yang/interfaces?module=openconfig-interfaces&revision=2018-11-21 http://openconfig.net/yang/interfaces/ethernet?module=openconfig-if-ethernet&revision=2019-04-16 http://openconfig.net/yang/lldp?module=openconfig-lldp&revision=2018-11-21 http://openconfig.net/yang/lldp/types?module=openconfig-lldp-types&revision=2018-11-21 http://openconfig.net/yang/openconfig-types?module=openconfig-types&revision=2018-11-21 http://openconfig.net/yang/platform?module=openconfig-platform&revision=2019-04-16 http://openconfig.net/yang/platform-types?module=openconfig-platform-types&revision=2019-06-03 http://openconfig.net/yang/platform/port?module=openconfig-platform-port&revision=2018-11-21 http://openconfig.net/yang/platform/transceiver?module=openconfig-platform-transceiver&revision=2018-11-25 http://openconfig.net/yang/terminal-device?module=openconfig-terminal-device&revision=2018-11-21 http://openconfig.net/yang/transport-types?module=openconfig-transport-types&revision=2019-06-21 http://openconfig.net/yang/types/yang?module=openconfig-yang-types&revision=2018-11-21 http://tail-f.com/ns/aaa/1.1?module=tailf-aaa&revision=2015-06-16 http://tail-f.com/ns/common/query?module=tailf-common-query&revision=2017-12-15 http://tail-f.com/ns/kicker?module=tailf-kicker&revision=2017-09-28 http://tail-f.com/ns/progress?module=tailf-progress&revision=2018-06-21 http://tail-f.com/yang/acm?module=tailf-acm&revision=2013-03-07 http://tail-f.com/yang/common?module=tailf-common&revision=2018-04-19 http://tail-f.com/yang/common-monitoring?module=tailf-common-monitoring&revision=2013-06-14 http://tail-f.com/yang/confd-monitoring?module=tailf-confd-monitoring&revision=2013-06-14 http://tail-f.com/yang/netconf-monitoring?module=tailf-netconf-monitoring&revision=2016-11-24 http://tail-f.com/yang/xsd-types?module=tailf-xsd-types&revision=2017-11-20 urn:ietf:params:xml:ns:yang:iana-crypt-hash?module=iana-crypt-hash&revision=2014-08-06&features=crypt-hash-sha-512,crypt-hash-sha-256,crypt-hash-md5 urn:ietf:params:xml:ns:yang:ietf-inet-types?module=ietf-inet-types&revision=2013-07-15 urn:ietf:params:xml:ns:yang:ietf-netconf-acm?module=ietf-netconf-acm&revision=2012-02-22 urn:ietf:params:xml:ns:yang:ietf-netconf-monitoring?module=ietf-netconf-monitoring&revision=2010-10-04 urn:ietf:params:xml:ns:yang:ietf-netconf-notifications?module=ietf-netconf-notifications&revision=2012-02-06 urn:ietf:params:xml:ns:yang:ietf-yang-library?module=ietf-yang-library&revision=2016-06-21 urn:ietf:params:xml:ns:yang:ietf-yang-types?module=ietf-yang-types&revision=2013-07-15 urn:ietf:params:xml:ns:netconf:base:1.0?module=ietf-netconf&revision=2011-06-01 urn:ietf:params:xml:ns:yang:ietf-netconf-with-defaults?module=ietf-netconf-with-defaults&revision=2011-06-01 15 vk@vk-VirtualBox:~/kautuk/NOS-S$

#2

Sorry the a.xml code wasn’t pasted properly in my original post.

A.xml is as follows:

_**<get>**_
_**    <filter>**_
_**    <components xmlns='http://openconfig.net/yang/platform'/>**_
_**    </filter>**_
_**</get>**_

#3

A.xml is as per the following screenshot:


#4

To get more details try netconf-console -s raw --host=127.0.0.1 --port=2022 --rpc=a.xml

BTW use something like ```xml <my><xml/></my>``` to display your xml properly