Hi,
Is it possible to add additional attributes in a NETCONF RPC request in addition to message-id?
See the following example:
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1" some-attribute="0001">
Looking at the NETCONF RFC...
In this case the GUI is trying to be helpful by validating the changes before doing commit. You will see the same thing in the CLI if you do "validate".
admin@ncs% commit dry-run
cli {
local-node {
data -servicey newservice {
...
It should work for both, I did not see any issues using the GUI.
I saw that you used post_modification in your first post and just want to mention that configuration set in post_mod (and pre_mod) is not automatically removed when the service is delet...
What does your code look like now?
This is what you should see when deleting servicex.
admin@ncs% delete servicex test-service
[ok][2023-05-04 08:13:27]
[edit]
admin@ncs% commit dry-run
cli {
local-node {
data -servicey test-service-crea...
Hi, I am not sure I follow exactly what you are trying to achieve but I will try to answer anyway.
One service creating another service is something we usually call a stacked service.
See the following example:
leaf device {
type leafre...
