Statement introduced in Junos OS Release 16.2R2 on MX Series and T Series routers.
Statement introduced in Junos OS Release 17.3R1 on SRX300, SRX320, SRX340, SRX345, SRX550M, SRX1500, SRX4100, SRX4200, SRX5400, SRX5600, and SRX5800 devices and vSRX instances.
Statement introduced in Junos OS Release 18.1R1 on EX2300, EX3400, EX4300, EX4600, and EX9200 switches.
Statement introduced in Junos OS Release 18.3R1 on ACX Series and PTX Series routers and QFX Series switches.
Statement introduced in Junos OS Release 19.4R1 on EX4300-48MP, EX9251, and EX9253 switches.
Configure settings for the ephemeral configuration database.
The ephemeral database is an alternate configuration database that enables Juniper Extension Toolkit (JET) applications and NETCONF and Junos XML protocol client applications to simultaneously load and commit configuration changes on devices running Junos OS and with significantly greater throughput than when committing data to the candidate configuration database. Devices running Junos OS provide a default ephemeral database instance as well as the ability to configure multiple user-defined instances of the ephemeral configuration database.
The ephemeral database is not subject to the same verification required in the static configuration database. As a result, the ephemeral configuration database does not support configuration groups or interface ranges, or macros, commit scripts, or translation scripts. Additionally, certain configuration statements cannot be configured through the ephemeral database as described in Unsupported Configuration Statements in the Ephemeral Configuration Database. Junos OS validates the syntax but does not validate the semantics of configuration data committed to the ephemeral database. Therefore, all configuration data must be validated before loading it into the ephemeral database and committing it on the device. If you commit invalid configuration data to the database, it can cause Junos OS processes to restart or even crash and result in disruption to the system or network.
When you configure statements at the [edit system configuration-database ephemeral] hierarchy level and commit the configuration, all Junos OS processes must check and evaluate their complete configuration, which might cause a spike in CPU utilization, potentially impacting other critical software processes.
If the ephemeral configuration database is present on a device running Junos OS, commit operations on the static configuration database might take longer, because additional operations must be performed to merge the static and ephemeral configuration data.
We do not recommend using the ephemeral database on devices that have graceful Routing Engine switchover (GRES) enabled. If you elect to use the ephemeral database when GRES is enabled, you must explicitly configure the allow-commit-synchronize-with-gres statement to enable the device to synchronize ephemeral configuration data to the backup Routing Engine when you request a commit synchronize operation on an ephemeral instance. If GRES is enabled, and you do not configure the allow-commit-synchronize-with-gres statement, the device does not synchronize the ephemeral instance to the backup Routing Engine when you request a commit synchronize operation on that instance.
Ephemeral configuration data does not persist across reboots. In addition, when you install a package that requires rebuilding the Junos OS schema, such as an OpenConfig or YANG package, the device deletes all ephemeral configuration data in the process of rebuilding the schema.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
maintenance—To view this statement in the configuration.
maintenance—To add this statement to the configuration.