search

CESNET / netopeer2

NETCONF toolset
BSD 3-Clause "New" or "Revised" License
300 stars 189 forks source link

Error with get-schema format not supported when connecting to netopeer2 server #1595

Closed kurimusityu closed 4 months ago

kurimusityu commented 4 months ago

Hi, When the netopeer2 client connects to the netopeer2 server, the module is loaded from the server via get-schema, but this request fails with an unexpected reply. Is there anything you can tell us about this factor?

We can see the following log sequence.

root@raspberrypi:~# netopeer2-cli 
load_config: No saved configuration.
> verb 2
> connect --host 192.168.1.6
nc VERBOSE: Trying to connect via IPv4 to 192.168.1.6:830.
nc VERBOSE: Successfully connected to 192.168.1.6:830 over IPv4.
[2024/06/25 16:42:06.509095, 2] ssh_config_parse_line:  Unapplicable option: SendEnv, line: 51
[2024/06/25 16:42:06.509226, 1] ssh_config_parse_line:  Unsupported option: HashKnownHosts, line: 52
[2024/06/25 16:42:06.509357, 2] ssh_connect:  libssh 0.9.8 (c) 2003-2021 Aris Adamantiadis, Andreas Schneider and libssh contributors. Distributed under the LGPL, please refer to COPYING file for information about your rights, using threading threads_pthread
[2024/06/25 16:42:06.509445, 2] ssh_connect:  Socket connecting, now waiting for the callbacks to work
[2024/06/25 16:42:06.509536, 1] socket_callback_connected:  Socket connection callback: 1 (0)
[2024/06/25 16:42:06.578771, 2] ssh_client_connection_callback:  SSH server banner: SSH-2.0-libssh_0.10.6
[2024/06/25 16:42:06.578869, 2] ssh_analyze_banner:  Analyzing banner: SSH-2.0-libssh_0.10.6
[2024/06/25 16:42:06.579925, 1] ssh_known_hosts_read_entries:  Failed to open the known_hosts file '/etc/ssh/ssh_known_hosts': No such file or directory
[2024/06/25 16:42:06.580524, 2] ssh_kex_select_methods:  Negotiated curve25519-sha256,rsa-sha2-512,aes256-gcm@openssh.com,aes256-gcm@openssh.com,aead-gcm,aead-gcm,none,none,,
[2024/06/25 16:42:06.604371, 2] ssh_init_rekey_state:  Set rekey after 4294967296 blocks
[2024/06/25 16:42:06.604495, 2] ssh_init_rekey_state:  Set rekey after 4294967296 blocks
[2024/06/25 16:42:06.604796, 2] ssh_packet_newkeys:  Received SSH_MSG_NEWKEYS
[2024/06/25 16:42:06.605793, 2] ssh_packet_newkeys:  Signature verified and valid
[2024/06/25 16:42:06.613278, 1] ssh_packet_userauth_failure:  Access denied for 'none'. Authentication that can continue: publickey,password
[2024/06/25 16:42:06.613382, 2] ssh_packet_userauth_failure:  Access denied for 'none'. Authentication that can continue: publickey,password
nc VERBOSE: Publickey athentication.
nc VERBOSE: No key pair specified.
nc WARNING: Authentication denied.
nc VERBOSE: Password authentication (host "192.168.1.6", user "root").
root@192.168.1.6 password: 
nc VERBOSE: Authentication successful.
[2024/06/25 16:42:34.464423, 2] channel_open:  Creating a channel 43 with 64000 window and 32768 max packet
[2024/06/25 16:42:34.465419, 2] ssh_packet_channel_open_conf:  Received a CHANNEL_OPEN_CONFIRMATION for channel 43:43
[2024/06/25 16:42:34.465511, 2] ssh_packet_channel_open_conf:  Remote window : 32000, maxpacket : 35000
[2024/06/25 16:42:34.466459, 2] channel_request:  Channel request subsystem success
ly VERBOSE: Searching for "ietf-inet-types" in "/root".
ly VERBOSE: Newer revision than "ietf-inet-types@2013-07-15" not found, using this as the latest revision.
ly VERBOSE: Searching for "ietf-yang-types" in "/root".
ly VERBOSE: Newer revision than "ietf-yang-types@2013-07-15" not found, using this as the latest revision.
[2024/06/25 16:42:34.510007, 2] grow_window:  growing window (channel 43:43) to 1280000 bytes
nc VERBOSE: Capability for <get-schema> support found.
nc VERBOSE: Capability for yang-library support found.
nc VERBOSE: Capability for XPath filter support found.
nc VERBOSE: Capability for NMDA RPCs support not found.
nc VERBOSE: Reading module "ietf-netconf@<latest>" from local file "/usr/local/share/yang/modules/netopeer2/ietf-netconf@2013-09-29.yang".
nc VERBOSE: Reading module "ietf-netconf-acm@2018-02-14" from local file "/usr/local/share/yang/modules/netopeer2/ietf-netconf-acm@2018-02-14.yang".
nc VERBOSE: Reading module "ietf-yang-metadata@2016-08-05" from local file "/usr/local/share/yang/modules/libyang/ietf-yang-metadata@2016-08-05.yang".
nc VERBOSE: Reading module "ietf-yang-library@2019-01-04" from local file "/usr/local/share/yang/modules/libyang/ietf-yang-library@2019-01-04.yang".
nc VERBOSE: Unable to identify revision of the import module "ietf-datastores" from the available server side information.
nc VERBOSE: Reading module "ietf-datastores@<latest>" from server via get-schema.
[2024/06/25 16:42:34.564952, 2] channel_rcv_change_window:  Adding 1248206 bytes to channel (43:43) (from 31782 bytes)
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>
nc VERBOSE: Reading module "ietf-datastores@<latest>" from local file "/usr/local/share/yang/modules/netopeer2/ietf-datastores@2018-02-14.yang".
nc VERBOSE: Reading module "sysrepo@2021-10-08" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="3">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "sysrepo@2021-10-08".
nc VERBOSE: Reading module "sysrepo-monitoring@2022-08-19" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="4">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "sysrepo-monitoring@2022-08-19".
nc VERBOSE: Reading module "sysrepo-plugind@2022-08-26" from local file "/usr/local/share/yang/modules/sysrepo/sysrepo-plugind@2022-08-26.yang".
nc VERBOSE: Reading module "ietf-netconf-with-defaults@2011-06-01" from local file "/usr/local/share/yang/modules/sysrepo/ietf-netconf-with-defaults@2011-06-01.yang".
nc VERBOSE: Reading module "ietf-netconf-notifications@2012-02-06" from local file "/usr/local/share/yang/modules/sysrepo/ietf-netconf-notifications@2012-02-06.yang".
nc VERBOSE: Reading module "ietf-origin@2018-02-14" from local file "/usr/local/share/yang/modules/sysrepo/ietf-origin@2018-02-14.yang".
nc VERBOSE: Reading module "ietf-netconf-nmda@2019-01-07" from local file "/usr/local/share/yang/modules/netopeer2/ietf-netconf-nmda@2019-01-07.yang".
nc VERBOSE: Reading module "nc-notifications@2008-07-14" from local file "/usr/local/share/yang/modules/netopeer2/nc-notifications@2008-07-14.yang".
nc VERBOSE: Reading module "notifications@2008-07-14" from local file "/usr/local/share/yang/modules/netopeer2/notifications@2008-07-14.yang".
nc VERBOSE: Reading module "ietf-x509-cert-to-name@2014-12-10" from local file "/usr/local/share/yang/modules/libnetconf2/ietf-x509-cert-to-name@2014-12-10.yang".
nc VERBOSE: Reading module "ietf-keystore@2019-07-02" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="5">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-keystore@2019-07-02".
nc VERBOSE: Reading module "ietf-crypto-types@2019-07-02" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="6">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-crypto-types@2019-07-02".
nc VERBOSE: Reading module "ietf-truststore@2019-07-02" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="7">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-truststore@2019-07-02".
nc VERBOSE: Reading module "ietf-tcp-common@2019-07-02" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="8">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-tcp-common@2019-07-02".
nc VERBOSE: Reading module "ietf-ssh-server@2019-07-02" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="9">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-ssh-server@2019-07-02".
nc VERBOSE: Reading module "iana-crypt-hash@2014-08-06" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="10">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "iana-crypt-hash@2014-08-06".
nc VERBOSE: Reading module "ietf-tls-server@2019-07-02" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="11">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-tls-server@2019-07-02".
nc VERBOSE: Reading module "ietf-netconf-server@2019-07-02" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="12">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-netconf-server@2019-07-02".
nc VERBOSE: Reading module "ietf-interfaces@2018-02-20" from local file "/usr/local/share/yang/modules/netopeer2/ietf-interfaces@2018-02-20.yang".
nc VERBOSE: Reading module "ietf-ip@2018-02-22" from local file "/usr/local/share/yang/modules/netopeer2/ietf-ip@2018-02-22.yang".
nc VERBOSE: Reading module "ietf-network-instance@2019-01-21" from local file "/usr/local/share/yang/modules/netopeer2/ietf-network-instance@2019-01-21.yang".
nc VERBOSE: Reading module "ietf-subscribed-notifications@2019-09-09" from local file "/usr/local/share/yang/modules/netopeer2/ietf-subscribed-notifications@2019-09-09.yang".
nc VERBOSE: Reading module "ietf-restconf@2017-01-26" from local file "/usr/local/share/yang/modules/netopeer2/ietf-restconf@2017-01-26.yang".
nc VERBOSE: Reading module "ietf-yang-push@2019-09-09" from local file "/usr/local/share/yang/modules/netopeer2/ietf-yang-push@2019-09-09.yang".
nc VERBOSE: Reading module "ietf-yang-patch@2017-02-22" from local file "/usr/local/share/yang/modules/netopeer2/ietf-yang-patch@2017-02-22.yang".
nc VERBOSE: Reading module "iana-hardware@2018-03-13" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="13">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "iana-hardware@2018-03-13".
nc VERBOSE: Reading module "iana-if-type@2017-01-19" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="14">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "iana-if-type@2017-01-19".
nc VERBOSE: Reading module "ieee802-types@2020-06-04" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="15">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ieee802-types@2020-06-04".
nc VERBOSE: Reading module "ieee802-dot1q-types@2020-06-04" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="16">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ieee802-dot1q-types@2020-06-04".
nc VERBOSE: Reading module "ieee802-dot1q-cfm-types@2020-06-04" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="17">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ieee802-dot1q-cfm-types@2020-06-04".
nc VERBOSE: Reading module "ieee802-dot1q-cfm@2020-06-04" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="18">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ieee802-dot1q-cfm@2020-06-04".
nc VERBOSE: Reading module "ieee802-dot1x-types@2020-02-18" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="19">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ieee802-dot1x-types@2020-02-18".
nc VERBOSE: Reading module "ietf-system@2014-08-06" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="20">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-system@2014-08-06".
nc VERBOSE: Reading module "ieee802-dot1x@2020-02-18" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="21">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ieee802-dot1x@2020-02-18".
nc VERBOSE: Reading module "ietf-dhcpv6-common@2021-01-29" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="22">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-dhcpv6-common@2021-01-29".
nc VERBOSE: Reading module "ietf-dhcpv6-types@2018-09-04" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="23">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-dhcpv6-types@2018-09-04".
nc VERBOSE: Reading module "ietf-hardware@2018-03-13" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="24">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "ietf-hardware@2018-03-13".
nc VERBOSE: Reading module "o-ran-wg4-features@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="25">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-wg4-features@2023-08-14".
nc VERBOSE: Reading module "o-ran-hardware@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="26">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-hardware@2023-08-14".
nc VERBOSE: Reading module "o-ran-ald-port@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="27">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-ald-port@2023-08-14".
nc VERBOSE: Reading module "o-ran-ald@2021-12-01" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="28">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-ald@2021-12-01".
nc VERBOSE: Reading module "o-ran-antenna-calibration@2021-12-01" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="29">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-antenna-calibration@2021-12-01".
nc VERBOSE: Reading module "o-ran-interfaces@2021-12-01" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="30">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-interfaces@2021-12-01".
nc VERBOSE: Reading module "o-ran-usermgmt@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="31">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-usermgmt@2022-08-15".
nc VERBOSE: Reading module "o-ran-processing-element@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="32">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-processing-element@2022-08-15".
nc VERBOSE: Reading module "o-ran-certificates@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="33">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-certificates@2022-08-15".
nc VERBOSE: Reading module "o-ran-compression-factors@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="34">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-compression-factors@2023-08-14".
nc VERBOSE: Reading module "o-ran-module-cap@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="35">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-module-cap@2023-08-14".
nc VERBOSE: Reading module "o-ran-common-yang-types@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="36">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-common-yang-types@2023-08-14".
nc VERBOSE: Reading module "o-ran-uplane-conf@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="37">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-uplane-conf@2023-08-14".
nc VERBOSE: Reading module "o-ran-beamforming@2023-04-10" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="38">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-beamforming@2023-04-10".
nc VERBOSE: Reading module "o-ran-common-identity-refs@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="39">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-common-identity-refs@2022-08-15".
nc VERBOSE: Reading module "o-ran-delay-management@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="40">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-delay-management@2022-08-15".
nc VERBOSE: Reading module "o-ran-dhcp@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="41">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-dhcp@2022-08-15".
nc VERBOSE: Reading module "o-ran-ecpri-delay@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="42">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-ecpri-delay@2023-08-14".
nc VERBOSE: Reading module "o-ran-ethernet-forwarding@2021-12-01" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="43">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-ethernet-forwarding@2021-12-01".
nc VERBOSE: Reading module "o-ran-externalio@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="44">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-externalio@2023-08-14".
nc VERBOSE: Reading module "o-ran-fan@2021-12-01" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="45">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-fan@2021-12-01".
nc VERBOSE: Reading module "o-ran-file-management@2023-04-10" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="46">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-file-management@2023-04-10".
nc VERBOSE: Reading module "o-ran-fm@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="47">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-fm@2022-08-15".
nc VERBOSE: Reading module "o-ran-ieee802-dot1q-cfm@2023-04-10" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="48">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-ieee802-dot1q-cfm@2023-04-10".
nc VERBOSE: Reading module "o-ran-laa@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="49">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-laa@2022-08-15".
nc VERBOSE: Reading module "o-ran-laa-operations@2021-12-01" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="50">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-laa-operations@2021-12-01".
nc VERBOSE: Reading module "o-ran-lbm@2021-12-01" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="51">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-lbm@2021-12-01".
nc VERBOSE: Reading module "o-ran-mplane-int@2021-12-01" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="52">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-mplane-int@2021-12-01".
nc VERBOSE: Reading module "o-ran-operations@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="53">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-operations@2023-08-14".
nc VERBOSE: Reading module "o-ran-performance-management@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="54">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-performance-management@2023-08-14".
nc VERBOSE: Reading module "o-ran-shared-cell@2023-08-14" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="55">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-shared-cell@2023-08-14".
nc VERBOSE: Reading module "o-ran-software-management@2022-12-05" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="56">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-software-management@2022-12-05".
nc VERBOSE: Reading module "o-ran-supervision@2022-12-05" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="57">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-supervision@2022-12-05".
nc VERBOSE: Reading module "o-ran-sync@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="58">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-sync@2022-08-15".
nc VERBOSE: Reading module "o-ran-trace@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="59">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-trace@2022-08-15".
nc VERBOSE: Reading module "o-ran-transceiver@2023-04-10" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="60">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-transceiver@2023-04-10".
nc VERBOSE: Reading module "o-ran-troubleshooting@2022-08-15" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="61">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-troubleshooting@2022-08-15".
nc VERBOSE: Reading module "o-ran-udp-echo@2019-02-04" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="62">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-udp-echo@2019-02-04".
nc VERBOSE: Reading module "o-ran-ves-subscribed-notifications@2020-12-10" from server via get-schema.
nc WARNING: Received an unexpected reply to <get-schema>:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="63">
  <rpc-error>
    <error-type>application</error-type>
    <error-tag>invalid-value</error-tag>
    <error-severity>error</error-severity>
    <error-message xml:lang="en">The requested format is not supported.</error-message>
  </rpc-error>
</rpc-reply>

nc WARNING: Failed to load module "o-ran-ves-subscribed-notifications@2020-12-10".
ly VERBOSE: Use of anydata to define configuration data is not recommended. /ietf-subscribed-notifications:filters/stream-filter/{uses='stream-filter-elements'}/filter-spec/stream-subtree-filter/stream-subtree-filter
ly VERBOSE: Use of anydata to define configuration data is not recommended. /ietf-yang-push:{augment='/sn:filters'}/ietf-yang-push:selection-filter/{uses='selection-filter-types'}/filter-spec/datastore-subtree-filter/datastore-subtree-filter
ly VERBOSE: Use of anydata to define configuration data is not recommended. /ietf-subscribed-notifications:subscriptions/subscription/{uses='subscription-policy'}/{uses='subscription-policy-dynamic'}/{uses='subscription-policy-modifiable'}/target/stream/stream-filter/within-subscription/{uses='stream-filter-elements'}/filter-spec/stream-subtree-filter/stream-subtree-filter
ly VERBOSE: Use of anydata to define configuration data is not recommended. /ietf-yang-push:{augment='/sn:subscriptions/sn:subscription/sn:target'}/ietf-yang-push:datastore/{uses='datastore-criteria'}/{uses='selection-filter-objects'}/selection-filter/within-subscription/{uses='selection-filter-types'}/filter-spec/datastore-subtree-filter/datastore-subtree-filter
ly VERBOSE: The ordered-by statement is ignored in lists representing notification content (/ietf-yang-push:push-change-update/datastore-changes/{uses='ypatch:yang-patch'}/yang-patch/edit).
nc WARNING: Some modules failed to be loaded, any data from these modules (and any other unknown) will be ignored.

The version of the netopeer2 server we are using is 2.1.49 and the version of the netopeer2 client is 2.0.69.

thank you

michalvasko commented 4 months ago

I am quite sure this is an incompatibility between used libyang and libnetconf2 version. When updating, please update all the libraries and netopeer2 to a specific compatible version, the latest releases are always compatible.

kurimusityu commented 4 months ago

I will look into the compatibility of libyang and libnetconf2. Thanks.

By the way, the server-client connection is established after such an error message appears. At this time, get-schema works, is this normal?

> get-schema --model ietf-datastores
MODULE
module ietf-datastores {
  yang-version 1.1;
  namespace "urn:ietf:params:xml:ns:yang:ietf-datastores";
  prefix ds;

  organization
    "IETF Network Modeling (NETMOD) Working Group";
  contact
    "WG Web:   <https://datatracker.ietf.org/wg/netmod/>

     WG List:  <mailto:netmod@ietf.org>

     Author:   Martin Bjorklund
               <mailto:mbj@tail-f.com>

     Author:   Juergen Schoenwaelder
               <mailto:j.schoenwaelder@jacobs-university.de>

     Author:   Phil Shafer
               <mailto:phil@juniper.net>

     Author:   Kent Watsen
               <mailto:kwatsen@juniper.net>

     Author:   Rob Wilton
               <rwilton@cisco.com>";
  description
    "This YANG module defines a set of identities for identifying
     datastores.

     Copyright (c) 2018 IETF Trust and the persons identified as
     authors of the code.  All rights reserved.

     Redistribution and use in source and binary forms, with or
     without modification, is permitted pursuant to, and subject to
     the license terms contained in, the Simplified BSD License set
     forth in Section 4.c of the IETF Trust's Legal Provisions
     Relating to IETF Documents
     (https://trustee.ietf.org/license-info).

     This version of this YANG module is part of RFC 8342
     (https://www.rfc-editor.org/info/rfc8342); see the RFC itself
     for full legal notices.";

  revision 2018-02-14 {
    description
      "Initial revision.";
    reference
      "RFC 8342: Network Management Datastore Architecture (NMDA)";
  }

  identity datastore {
    description
      "Abstract base identity for datastore identities.";
  }

  identity conventional {
    base datastore;
    description
      "Abstract base identity for conventional configuration
       datastores.";
  }

  identity running {
    base conventional;
    description
      "The running configuration datastore.";
  }

  identity candidate {
    base conventional;
    description
      "The candidate configuration datastore.";
  }

  identity startup {
    base conventional;
    description
      "The startup configuration datastore.";
  }

  identity intended {
    base conventional;
    description
      "The intended configuration datastore.";
  }

  identity dynamic {
    base datastore;
    description
      "Abstract base identity for dynamic configuration datastores.";
  }

  identity operational {
    base datastore;
    description
      "The operational state datastore.";
  }

  typedef datastore-ref {
    type identityref {
      base datastore;
    }
    description
      "A datastore identity reference.";
  }
}
michalvasko commented 4 months ago

Yes, an explicit CLI get-schema executes different code than the internal one in libnetconf2.

kurimusityu commented 4 months ago

libyang version was 2.1.111, libnetconf2 version was 2.1.28.

I will update these to compatible versions and try again. Thanks.

kurimusityu commented 4 months ago

I found that libnetconf2 v2.1.28 is compatible with libyang v2.1.30. Therefore, we built libyang v2.1.30. As a result, when a netopeer2 client connects to a netopeer2 server, the module is successfully loaded from the server via get-schema.

Thanks. I will close this issue.