search

CESNET / netopeer2

NETCONF toolset
BSD 3-Clause "New" or "Revised" License
291 stars 186 forks source link

There is no rpc-reply when <delete-config> target is candidate #1473

Closed lqlucky closed 9 months ago

lqlucky commented 9 months ago

Hi,

I found use the following RPC , netopeer2-server (2.0.22) do not send rpc-reply

<rpc message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<delete-config>
<target>
<candidate/>
</target>
</delete-config>
</rpc>

Is this a bug?

michalvasko commented 9 months ago

You are using a really old netopeer2-server so the first thing to do would be to update it. However, delete-config does not allow candidate as the child of target, it does not make sense and I could not even send such an RPC using netopeer2-cli because of this.

lqlucky commented 9 months ago

Will consider updating to the latest version later, we use other client and there is no restriction that target cannot be candidate. Is there a standard document about delete-config does not allow candidate as the child of target?

michalvasko commented 9 months ago

Yes, there is the standard NETCONF RFC.

lqlucky commented 9 months ago

OK, solved my question. Thanks for your reply