The startup-error parameter for netconfd-pro controls the server's behavior should it encounter any errors

while loading the startup configuration at boot time. Possible values are 'stop' and 'continue'.


If the startup-error parameter is set to 'stop', then any errors in the startup configuration will be treated as fatal errors.

If set to 'continue', the server will attempt to continue if any errors are found in the database loaded from NV-storage to running at boot time.


The startup-error parameter can be invoked via the command line when starting netconfd-pro:


user@system>netconfd-pro --startup-error=continue


or configured in the /etc/yumapro/netconfd-pro.conf file:


#### leaf startup-error
#
#  Controls the server behavior if any errors are
#  encountered while loading the startup configuration
#  file into the running configuration at boot-time.
#  It is possible for the startup configuration
#  to contain errors within optional nodes.  If this
#  parameter is set to 'continue', then the validation
#  tests on the running config (controlled by running-error)
#  should not fail due to missing optional nodes.
#
#  enum stop
#    Terminate the program if any errors are
#    encountered in the startup configuration.
#
#  enum continue
#    Continue the program if any errors are
#    encountered in the startup configuration.
#    The entire module-specific data structure(s)
#    containing the error node(s) will not be added
#    to the running configuration at boot-time.
#
# startup-error stop  

startup-error continue