<commit> Copy the candidate data store to the running
data store<lock> /
<unlock>Lock or unlock the entire configuration data
store system<close-
session>Gracefully terminate the NETCONF session<kill-
session>Forcibly terminate the NETCONF sessionThe NETCONF
attributes:
merge: When this attribute is specified, the configuration data is
merged with the configuration at the corresponding level in the
configuration data store. This is the default behavior.
replace: The configuration data replaces any related configuration in
the configuration data store. Only the configuration that is present in
the config parameter is affected.
create: The configuration data is added to the configuration only if the
configuration data does not exist on the device. If the configuration
already exists, an <rpc-error> message is returned with the <error-tag>
value data-exists.
delete: When this attribute is specified, the configuration data is
deleted from the configuration data store.NETCONF defines the existence of one or more
configuration data stores and allows configuration
operations on these data stores. A configuration data
store is a set of configuration data that is needed to get
the device from its default initial state into a desired
operational state. The configuration data stores do not
contain operational data. Three types of configuration
data stores are defined in NETCONF:
running: This data store holds the complete configuration currently
active on the network device. Only one running data store can exist on a