This section provides the NETCONF configuration command reference. Topics in this section include:
This command is used to control whether committed changes are automatically persistent (that is, copied to the <startup> datastore) or not, when a commit is successful.
no auto-config-save
This command enables or disables support of the candidate datastore in the SR OS NETCONF server. If the candidate is disabled then requests that reference the candidate datastore return an error, and when a NETCONF client establishes a new session the candidate capability is not advertised in the SR OS <hello>. This command also controls support of the <commit> and <discard-changes> operations.
When management-interface configuration-mode is set to classic, then the candidate capability is disabled, even if candidate is configured.
candidate
This command enables or disables support of the writable-running capability in the SR OS NETCONF server. If writable-running is disabled then requests that reference the running datastore as a target return an error, and when a NETCONF client establishes a new session the writable-running capability is not advertised in the SR OS <hello>.
When management-interface configuration-mode is set to model-driven, then the writable-running capability is disabled, even if writable-running is configured.
writable-running
This command disables the NETCONF server. The shutdown command is blocked if there are any active NETCONF sessions. Use the admin disconnect command to disconnect all NETCONF sessions before shutting down the NETCONF service.
This command authorizes various netconf capabilities for the user.
This command enables the context where permission to use various NETCONF operations is controlled.
This operation authorizes a user associated with the profile to send a kill session NETCONF operation. This kill session operation allows a NETCONF client to kill another NETCONF session, but not the session in which the operation is requested.
no kill-session
This operation authorizes a user associated with the profile to send a lock NETCONF operation. This lock operation allows a NETCONF client to lock the running datastore or the candidate datastore.
no lock