NOTE: The startup-prune-ok parameter applies to YumaPro SDK 17.10-7+.


The startup-prune-ok parameter for netconfd-pro specifies if unknown nodes can be skipped at boot-time.


If set to 'true' then the server will prune unknown data nodes from the startup configuration instead of treating this as an error.

A log_info message will be printed.  If other known data nodes depend on the pruned nodes, then an error may occur anyway.

If so, the startup-error parameter will determine how this is handled.


If set to 'false' then unknown data nodes found in the startup configuration will cause an error.
Unknown data nodes can occur if modules were previously loaded dynamically,

or if a YANG feature is configured from enabled to disabled. The default is 'false'.


The startup-prune-ok parameter can be set via the command line when booting netconfd-pro:


user@system> netconfd-pro --startup-prune-ok=true


or configured in netconfd-pro's configuration file, which is located by default at /etc/yumapro/netconfd-pro.conf:


#### leaf startup-prune-ok
# If set to 'true' then the server will prune unknown
# data nodes from the startup configuration instead
# of treating this as an error.
# If set to 'false' then unknown data nodes found in
# the startup configuration will cause an error.
#
# startup-prune-ok false
#
startup-prune-ok true