ON THIS PAGE
<open-configuration>
Usage
<rpc>
<open-configuration>
<private/>
</open-configuration>
<open-configuration>
<ephemeral/>
</open-configuration>
<open-configuration>
<ephemeral-instance>instance-name</ephemeral-instance>
</open-configuration>
</rpc>Description
Create a private copy of the candidate configuration database or open the default instance or a user-defined instance of the ephemeral configuration database.
Before opening a user-defined instance of the ephemeral
configuration database, you must first enable the instance by configuring
the instance instance-name statement
at the [edit system configuration-database ephemeral] hierarchy
level on the device.
A client application can perform the same operations on the private copy or ephemeral instance as on the regular candidate configuration, including load and commit operations. There are, however, restrictions on these operations. For details, see <load-configuration> and <commit-configuration>.
To close a private copy or ephemeral instance and discard all uncommitted changes, execute the
<close-configuration/> operation. Changes to the private
copy or ephemeral instance are also lost if the NETCONF or Junos XML protocol
session ends for any reason before the changes are committed. It is not possible to
save the changes other than by performing a commit operation, for example, by
emitting the <commit-configuration/> tag.
The Junos XML protocol <open-configuration> operation does not emit an
"uncommitted changes will be discarded on exit" warning
message when opening a private copy of the candidate configuration. However, the
device still discards the uncommitted changes upon closing the private copy.
Contents
<private/> |
Open a private copy of the candidate configuration database. |
<ephemeral/> |
Open the default instance of the ephemeral configuration database. |
<ephemeral-instance> |
Open the specified instance of the ephemeral
configuration database. This instance must already be configured at
the |
Release Information
This operation is a Junos XML management protocol operation. It is supported in Junos XML protocol sessions, and it is supported as a Juniper Networks proprietary extension in NETCONF sessions on Junos devices that identify the URI http://xml.juniper.net/netconf/junos/1.0 in the capabilities exchange.
<ephemeral> and <ephemeral-instance> elements added in Junos OS Release 16.2R2.